Setting up source offsite

rashmi.rajashekar · Post by **rashmi.rajashekar** » Wed Jul 19, 2006 12:02 am

Hi :
I have VSS server(VSS 6.0) databse set up in ServerA (win 2000)
I have setup the source offsite server(3.5.3 win) demo version on ServerB (win 2000).
I have source offsite client on wksA (win xp)

The source offsite server is configured to access VSS database on ServerA thru port 8888 in unsecure mode. The source offsite server service is started using domain account.

When i try to connect from source offsite client, the connection is established, login is successful, but it fails to build the tree structure.

Log :

Tue Jul 18 21:46:15 PDT 2006 - wksA (16.19.1.1) - Connection Established
Tue Jul 18 21:46:31 PDT 2006 - wksA (16.19.1.1) - "userA" connected to database: \\VSSPATH\srcsafe.ini
Tue Jul 18 21:46:32 PDT 2006 - wksA (16.19.1.1) - Begin Get Project Tree Operation: $/
Tue Jul 18 22:13:47 PDT 2006 - ServerB (15.21.9.43) - File "\\VSSPATH\data\f\fcedaaaa.a" not found
Tue Jul 18 22:13:47 PDT 2006 - ServerB (15.21.9.43) - Socket write failed
Tue Jul 18 22:13:48 PDT 2006 - ServerB (15.21.9.43) - User "userA" disconnected

What is the problem / work around for this .

Regards,
Rashmi

lbauer · Post by **lbauer** » Wed Jul 19, 2006 9:16 am

This could indicate database corruption in your VSS database or it might just be a configuration problem.

-- Please verify that the option in the SourceSafe Explorer called
"Remove local copy after Add or Check In." is not enabled in your VSS
installation on the SOS Server machine. If this option is enabled,
SourceOffSite cannot function properly. Make sure this is disabled for
each user profile (you can check this by logging in to the VSS client on the
SOS Server machine as different users.)

-- If there is database corruption, the error message "File "\\VSSPATH\data\f\fcedaaaa.a" not found
in the log file 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: While this article refers to analyze, the automation component will return the same type of error.

http://support.microsoft.com/support/kb ... 0/9/14.asp

rashmi.rajashekar · Post by **rashmi.rajashekar** » Fri Jul 21, 2006 4:51 am

Thanks for response

No the option "Remove Local copy after Add or Check in" is not enabled in sos server / VSS explorer.

If the same databse is opened using Microsoft VSS client, it opens up without any problem.

What other configuration issues cud have led to this prob?

lbauer · Post by **lbauer** » Fri Jul 21, 2006 8:33 am

No the option "Remove Local copy after Add or Check in" is not enabled in sos server / VSS explorer.

Make sure this is disabled for each user profile (you can check this by logging in to the VSS client on the SOS Server machine as different users.)

If this setting *is* disabled for each user profile, then the error message indicates possible database corruption. Running Analyze with the -f and -c parameters is highly recommended.

The SOS Server communicates with the VSS database via the SourceSafe automation component, and the automation component is much more sensitive to even minor database corruption. So connecting with a VSS Client might work fine, but the automation component may report errors.