Operation Failed on Check Out

gotdablues · Post by **gotdablues** » Fri Nov 04, 2005 4:45 pm

I am using the GUI client (v4.1.2) to Check Out or Get the Latest File. When I request the file, I get an operation failed on file. The Status column has the value 'Unknown'.

I am able to Check Out and Get The Latest on other files in the project.

In the Server log, I have the following message.

11/4/2005 5:38:06 PM - 2: Received message number 105.
11/4/2005 5:38:06 PM - 2: GetFile() file=Employee.cs
11/4/2005 5:38:06 PM - 11/4/2005 5:38:06 PM - Server Exception (400): [C:\Program Files\SourceOffSite Server\temp\MyUsername632667224529838750\Employee.cs] - OPERATION_FAILED
11/4/2005 5:38:06 PM - 2: Server Error: 400
11/4/2005 5:38:06 PM - 2: Received message number 106.
11/4/2005 5:38:06 PM - 2: Version information obtained for $/bps/CommonLibrary/bps_common/Employee.cs
11/4/2005 5:38:06 PM - 2: Received message number 105.
11/4/2005 5:38:06 PM - 2: GetFile() file=Employee.cs
11/4/2005 5:38:06 PM - 11/4/2005 5:38:06 PM - Server Exception (400): [C:\Program Files\SourceOffSite Server\temp\MyUsername632667224529838750\Employee.cs] - OPERATION_FAILED
11/4/2005 5:38:06 PM - 2: Server Error: 400
11/4/2005 5:39:06 PM - 2: Received message number 107.
11/4/2005 5:39:06 PM - 2: Received message number 105.
11/4/2005 5:39:06 PM - 2: GetFile() file=Employee.cs
11/4/2005 5:39:06 PM - 11/4/2005 5:39:06 PM - Server Exception (400): [C:\Program Files\SourceOffSite Server\temp\MyUsername632667224529838750\Employee.cs] - OPERATION_FAILED
11/4/2005 5:39:06 PM - 2: Server Error: 400

I have performed Analyze -F and -C against my database.

Thanks for your help.

Post by **Tonya** » Mon Nov 07, 2005 10:51 am

Server error 400 is a generic "operation failed" message. Does verbose logging provide any additional information?

http://support.sourcegear.com/viewtopic.php?t=463

I noticed that this file is a C# file. Was this file added to SourceOffSite using VS.Net? If so, were you using VS 2003 or VS 2005?

Thanks,

Tonya Nunn
SourceGear Support

gotdablues · Post by **gotdablues** » Mon Nov 07, 2005 11:36 am

Tonya,

The listing I provided you is the verbose output from the server (ie, log.txt).

The source code was loaded using VS2003.

Does this help?

I haven't tried checking out the file using VSS to see if it is an issue with the database.

Post by **Tonya** » Mon Nov 07, 2005 2:10 pm

I haven't tried checking out the file using VSS to see if it is an issue with the database.

Could you please attempt to do this and let me know the outcome? A lot of times the error message that you are receiving is due to a VSS database corrupction issue. However, you noted in the beginning that you already attempted to run Analyze on your VSS database.

Tonya

gotdablues · Post by **gotdablues** » Mon Nov 07, 2005 7:13 pm

I am able to perform a Get Latest Version and Check Out using Visual Source Safe.

Any thoughts on why SOS is having an issue?

Thanks.

Steve

gotdablues · Post by **gotdablues** » Mon Nov 07, 2005 7:43 pm

Does this check out problem have anything to do with local database.

I.e., C:\Documents and Settings\<username>\Application Data\SourceGear\SOS\servers\010020030247

steve

Post by **Tonya** » Tue Nov 08, 2005 10:42 am

Is this the only file that you are having problems with? Can other users successfully check the file out?

Since the file status is being displayed as Unknown for this file, I would suggest deleting the file from your working folder and attempting to perform a get latest again.

Tonya

gotdablues · Post by **gotdablues** » Tue Nov 08, 2005 10:57 am

Tonya,

this is happening to more files. Is your suggestion to clear out my working folder for all my project that I am having a problem with and then doing a Get Last Version on all files.

Is there anything in the local SOS database that needs fixing?

Thanks.

steve

Post by **Tonya** » Tue Nov 08, 2005 11:17 am

Steve,

First, I would try to use checksums to resolve the status of unknown files (Tools->Options->Files).

Then if it all possible, I would go ahead and wipe out your working folder for the entire project (if you're not going to lose any changes). Then attempt the Get Latest command.

If this doesn't resolve the problem, you could locate the client cache file. In SOS it's in your %appdata%\SourceGear\SOS\Server\<servername> directory. It's called databaseX.sos. Delete that file and it will force the project tree to be rebuilt. You'll need to reset working directories after this and perform a get latest for the entire tree to resolve the status.

Tonya

gotdablues · Post by **gotdablues** » Tue Nov 08, 2005 6:47 pm

Tonya,

I have done the following, but I am still having the same issues

1. Deleted the the database1.sos file and index.sos files.
2. Started SOS GUI, rebuilt the project tree and set the working folder.
3. Deleted the files in my source code directory.
4. Did a Get Last Version.

The following series of messages occured for every file in the project.

11/8/2005 7:38:59 PM - 21: Received message number 105.
11/8/2005 7:38:59 PM - 21: GetFile() file=aba.wsdl
11/8/2005 7:38:59 PM - 11/8/2005 7:38:59 PM - Server Exception (400): [C:\Program Files\SourceOffSite Server\temp\<username>632670754952182500\aba.wsdl] - OPERATION_FAILED
11/8/2005 7:38:59 PM - 21: Server Error: 400

Any additional thoughts?

Steve

gotdablues · Post by **gotdablues** » Tue Nov 08, 2005 7:08 pm

Tonya,

Just a quick followup.

For VSS, I am running Visual Source Safe 8.0. This is the version that is getting release with VS 2005. I am running this version because MS made improvements in the performance for remote clients. Unfortunately, the speed the of MS's changes do not compare to SourceOffsite. This is why I am hoping to get this resolved quickly.

Thanks.

Post by **Tonya** » Wed Nov 09, 2005 12:44 pm

SOS does not yet support the Visual SourceSafe 2005 automation component. We did some testing in-house and found that the Get Latest operation does not work if VSS 2005 is the version of the client installed on the SOS Server machine.

You may be able to work around this by using the ssapi.dll (automation component) from VSS 6.0c. I've attached a copy.

First search the registry for this key: "783CD4E4-9D54-11CF-B8EE-00608CC9A71F", which is the Class ID for the VSS Automation component. This will show the path to the ssapi.dll file used by the SOS Server. Then go to this location of this ssapi.dll file on the SOS Server machine. Rename this ssapi.dll file and replace it with the ssapi.dll file from this post.

We haven't tested this extensively, but we were able to do get, checkout, checkin, etc. from a VSS 2005 database.

We do plan to support VSS 2005 after final release.

Tonya

Post by **Tonya** » Wed Nov 09, 2005 2:35 pm

Actually, I am currently testing SOS with VSS 8.0 and I am unable to produce this problem. Could you tell me which version of the SSAPI.DLL file you are utilizing?

Tonya

gotdablues · Post by **gotdablues** » Wed Nov 09, 2005 7:13 pm

My version of ssapi.dll is 8.0.50215.44

Post by **Tonya** » Thu Nov 10, 2005 4:05 pm

Were these files added to VSS using 6.0 before upgrading to VSS 8.0?

Tonya