'Operation Failed' trying to view file history

dgodwin · Post by **dgodwin** » Tue Sep 18, 2007 2:25 am

Hi,

There's been a number of threads on this problem but I've yet to find a definitive solution.

When trying to view history from a 4.0.2 client on a 4.1 SOS server I get the following error in the server log:

18/09/2007 3:32:05 PM - 1: GetFileHistoryException: Error loading resource string
18/09/2007 3:32:05 PM - 18/09/2007 3:32:05 PM - Server Exception (400): OPERATION_FAILED
18/09/2007 3:32:05 PM - 1: Server Error: 400

The server is running on a W2k3 server with VSS2005. The VSSAPI.dll version is 6.0.31222.0

Any help is much appreciated.
Thanks.

lbauer · Post by **lbauer** » Tue Sep 18, 2007 7:11 am

The first thing I would suggest is to upgrade your client to SOS 4.1.x. There may be an incompatibility.

In fact, upgrading client and server to SOS 4.2 would be a good idea, since we didn't fully test SOS 4.0 with VSS 2005.

Are other users experiencing the same problem?

Can you get history from other projects/files?

Have you run the VSS utility Analyze on your VSS database recently? Database corruption can cause problems getting history information.

Also, what is the SSAPI.dll (rather than VSSAPI.dll) version in the VSS 2005 directory?

dgodwin · Post by **dgodwin** » Tue Sep 18, 2007 7:16 pm

I am the only one testing at the moment as I am trying to set up the SOS server for some remote users.

Is it a free upgrade to 4.2?

The ssapi.dll is version 6.0.31222.0.

I did run an analyze after reading the first few threads on this problem.

Finally, yes, some history I can read but some I cannot.

dgodwin · Post by **dgodwin** » Tue Sep 18, 2007 7:34 pm

FYI - I've just upgraded to 4.2 client and server and am getting the same behaviour as before.

dgodwin · Post by **dgodwin** » Tue Sep 18, 2007 11:29 pm

Correction, the version of the 2005 ssapi.dll is 8.0.50727.42.

(I was looking in the VSS6.0 directory)

Terence · Post by **Terence** » Wed Sep 19, 2007 10:49 am

We've identified a problem in our own testing and we have reported this to Microsoft. Who has, in turn, acknowledged the issue with Visual SourceSafe 2005.

For now, the workaround would be to go back to VSS6.0 or wait until a patch from Microsoft is released.

JasonCCH · Post by **JasonCCH** » Thu Jun 05, 2008 11:04 am

Has there ever been a solution to this?

We were using 3.5.3 SOS server with VSS 2005 for almost two years, and had no problems and recently migrated to a new server and installed 4.2 of SOS server and client and are still using VSS 2005 with the same database.

Now we have several files where we cannot view the history and get operation failed. The ssapi.dll version is 8.0.50727.42

I know the history is there because I can view it in VSS just fine. I have several developers who need to check out an earlier version of a file and cannot. Please help!

Terence · Post by **Terence** » Thu Jun 05, 2008 11:17 am

This is usually solved by applying the update from Microsoft. That update can be found here: http://www.microsoft.com/downloads/deta ... laylang=en