This error was recorded in sgvault.log when performing a merge whilst attempting to list the merge versions. The Vault Client was in a wait state until the error was reported in sgvault.log at which time the Client was no longer in a wait state but no other user interface feedback occurred. This happens frequently and seems to be coincident with high CPU usage on the Vault Server. (This one incident was definitely coincident)
We are attempting to address the high CPU usage - http://support.sourcegear.com/viewtopic ... 292#p62292
The Vault Client needs to be killed via Task Manager. Obviously this is very annoying. It would be good if it was able to recover from the error. At the very least could it actually display an error on the client and then terminate?
BeginLabelQuery returned: FailInvalidSessionToken
Moderator: SourceGear
BeginLabelQuery returned: FailInvalidSessionToken
regards
Rob Goodridge
LANSA Pty Ltd
Software Made Simple
Vault 5.0.3
Rob Goodridge
LANSA Pty Ltd
Software Made Simple
Vault 5.0.3
Re: BeginLabelQuery returned: FailInvalidSessionToken
I can log a feature request for this.It would be good if it was able to recover from the error. At the very least could it actually display an error on the client and then terminate?
A label query can consume server resources, and perhaps this contibuted to the failed merge.
It would be important to address the overall performance issues, which it looks like you're doing in your other post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: BeginLabelQuery returned: FailInvalidSessionToken
Please DO log a feature request for this.
regards
Rob Goodridge
LANSA Pty Ltd
Software Made Simple
Vault 5.0.3
Rob Goodridge
LANSA Pty Ltd
Software Made Simple
Vault 5.0.3
Re: BeginLabelQuery returned: FailInvalidSessionToken
Done. I've logged feature request 15940 for this functionality.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager