Operation failed - Show History

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
kratka
Posts: 1
Joined: Wed Nov 01, 2006 10:55 am

Operation failed - Show History

Post by kratka » Wed Nov 01, 2006 11:05 am

SOS client shows "Operation failed - $/...." for some files, not all, when trying to show history. Many files within the same folder can show history just fine, but not the specific one I need. The source safe server log file shows error entries as listed below. No errors exist in the application or system event logs.

I have seen a few "Operation failed" posts on this forum and have tried a few things such as clearing the temp directory at C:\Program Files\SourceOffSite Server\temp with no luck. I believe I have a supported configuration as well:

SOS Server: 4.0.2
SOS Server for: Visual Source Safe 6.0
Operating system: Windows NT 5.2 Service Pack 1 (Windows Server 2003 sp1)

SOS Client: 4.12
Using secure port (HTTPS)

C:\Program Files\SourceOffSite Server\Log.txt file:
11/1/2006 9:47:34 AM - Connection accepted from 10.0.16.107:44954 on local address <ip address here>, session id is 13.
11/1/2006 9:47:57 AM - 13: GetFileHistoryException: File or project not found
11/1/2006 9:47:57 AM - 11/1/2006 9:47:57 AM - Server Exception (400): OPERATION_FAILED
11/1/2006 9:47:57 AM - 13: Server Error: 400
11/1/2006 9:50:52 AM - 13: GetFileHistoryException: File or project not found
11/1/2006 9:50:52 AM - 11/1/2006 9:50:52 AM - Server Exception (400): OPERATION_FAILED
11/1/2006 9:50:52 AM - 13: Server Error: 400


Help!

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Nov 01, 2006 3:21 pm

This type of error means the Visual SourceSafe automation component is unable to access historical versions of the file. This is usually due to VSS database corruption.

The SOS Server communicates with the VSS database via the automation component. The automation component is very sensitive to database corruption. I'd suggest running Analyze on your VSS database to clear up any database corruption. Details here:
http://support.sourcegear.com/viewtopic.php?t=50
Linda Bauer
SourceGear
Technical Support Manager

Post Reply