Check-in fails with error code 1602
Moderator: SourceGear
Check-in fails with error code 1602
We are using version 7.2.1. We have a c# console app that uses the Vault APIs to automatically check out and check in members to various repositories. We are receiving an error code 1602 on a check in. I cannot find documentation on this error code so is this coming from the Vault API's and if so, what does it mean? Thanks.
Re: Check-in fails with error code 1602
Do any other users have the same files checked out?
Take a look in the Vault Server Log for any errors occurring at the same time as the 1602 error. What do you see?
What errors do you see in the Event Viewer on the machine running the Vault API?
Can other users check out, edit, and check in the same files?
Take a look in the Vault Server Log for any errors occurring at the same time as the 1602 error. What do you see?
What errors do you see in the Event Viewer on the machine running the Vault API?
Can other users check out, edit, and check in the same files?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Check-in fails with error code 1602
Thanks Beth for getting back to me.
I believe I have found the issue by checking the server logs. The checkin is failing with - (e96bd424-c27d-4d48-897c-0ca90d2d1c9b) BeginTx returned: FailOutofDateObjVerID (e96bd424-c27d-4d48-897c-0ca90d2d1c9b) CheckIn: $/GAM364/DNN/MMIS/moroles.xml returned: FailOutofDateObjVerID.
Looking further in this forum shows that this error can be related to needing to do a merge. I took a closer look at the console application and some logic paths could result in doing things a bit out of turn which could cause the bad merge status.
Bottom line is the console app was updated to always - Set working folder, check out, save modified file, check in. Some logic paths were not always following that order.
So I guess the 1602 is referring to Merge issues?
I believe I have found the issue by checking the server logs. The checkin is failing with - (e96bd424-c27d-4d48-897c-0ca90d2d1c9b) BeginTx returned: FailOutofDateObjVerID (e96bd424-c27d-4d48-897c-0ca90d2d1c9b) CheckIn: $/GAM364/DNN/MMIS/moroles.xml returned: FailOutofDateObjVerID.
Looking further in this forum shows that this error can be related to needing to do a merge. I took a closer look at the console application and some logic paths could result in doing things a bit out of turn which could cause the bad merge status.
Bottom line is the console app was updated to always - Set working folder, check out, save modified file, check in. Some logic paths were not always following that order.
So I guess the 1602 is referring to Merge issues?
Re: Check-in fails with error code 1602
Error 1602 is the "FailOutofDateObjVerID" error.
This means the file in the working folder is in a 'Needs Merge' state. The file must receive changes from the server before any kind of commit can continue. A GET with automatic-merge should resolve the problem, assuming there are no conflicts in the contents of the file retrieved with GET.
This means the file in the working folder is in a 'Needs Merge' state. The file must receive changes from the server before any kind of commit can continue. A GET with automatic-merge should resolve the problem, assuming there are no conflicts in the contents of the file retrieved with GET.
Jeff Clausius
SourceGear
SourceGear