BeginSaveShelveSet returned: Critical Error!

[robe070]

I found this error in the server log file. There were no errors shown in Vault Client:

Code: Select all

----17/05/2011 6:16:22 PM    robert--ROBPC(10.2.1.32)--SSL Disabled	BeginSaveShelveSet returned: Critical Error!
 
----17/05/2011 6:16:22 PM    robert--ROBPC(10.2.1.32)--SSL Disabled	BeginSaveShelveSet returned: 1233 

Shelveset looks OK.

So what does the error mean?

[Beth]

I think that error code means the shelve set already exists.

[Beth]

Would you be willing to show a little more of the server code before the error? That may help us determine what led to this.

Also, do you know what the user was doing at the time? Did the user double-click the shelve button?

[robe070]

The shelveset does exist already! Strange thing to report as an error. Its like the stack trace in the client log when a user enters the wrong password. The message that the password failed is good. The stack trace is bad. A waste of time for administrators.

I'd ask for an enhancement that both these errors are only displayed in debug logs.

[Beth]

I have entered a feature request.

Quiet mode though does log errors thrown from the server, and this qualifies under than even though it may seem trivial. Debug mode is for logging the non-error actions, which helps determine root cause.

F: 15952

[robe070]

The issue is that it is thrown at all! Its a normal part of the processing to deal with a shelveset that already exists. Its not an error condition. The user gets informed and makes a choice.

[Beth]

There's more details to this than I am able to explain, but I do have this logged so that the developers can look into it.