Operation failed - $//([project]) in client status window

A collection of information about SourceOffSite, including solutions to common problems.

Moderator: SourceGear

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

Operation failed - $//([project]) in client status window

Post by lbauer » Thu Feb 12, 2004 9:50 am

Operation failed - $//(<project>) appears in client status window

If this error occurs for any project:

Please verify that the option in SourceSafe called "Remove local copy after Add or Check In" is not enabled in your VSS installation on the SOS Server machine. This can be verified via Tools -> Options -> Local Files in the SourceSafe Explorer. If this option is enabled, SOS cannot function properly.

Please Note: this SourceSafe option setting is only relevant for the SourceOffSite server machine; SourceSafe setting on SourceOffSite client machines do not effect this issue. Also, this setting is user-specific, so you must log into this VSS client as each of your users so that the setting will be associated with their login.

The SourceOffSite Server acts as a VSS Explorer client as far as the VSS database is concerned. When "Remove local copy after Add or Check In" is enabled as a user setting, files that are transferred from the SOS Server to the VSS database are immediately removed from the Server. This causes problems because the Client is no longer able to get the file from Server's temp directory. When these files are deleted prematurely, the communication between our Client and Server breaks down.

If this error occurs on only one or two projects or files:

The error will likely correspond to an error message in the log file: "\\…\…\vss\data\a\aapaaaaa.a" not found". This error usually points to a problem with a VSS data file that the VSS Automation component is not able to deal with. The SourceOffSite Server uses the VSS Automation component to communicate with the VSS database. If there are any inconsistencies in your database, it may prevent SOS from working properly.

The information at the following link should help you resolve the problem: http://support.microsoft.com/support/kb ... 0/9/14.asp

Please Note: while this article refers to analyze, the automation component will return the same type of error.
Linda Bauer
Technical Support Manager

Post Reply