Re[2]: SOS 4.0.2 - Databases missing in client interface
Ani <[email protected]> Wed, 23 Jun 2004 16:40:29 +0900
| Newsgroups | gmane.comp.version-control.vss.sourceoffsite.classic |
|---|---|
| Message-ID | <[email protected]> |
Hello, On Mon, 21 Jun 2004 11:26:07 -0500 Linda Bauer <[email protected]> wrote: > Hi, Ani, > > Usually the databases don't appear in the drop down because the SOS Server > can't access them for some reason. You can check the log.txt file in the > SOS Server directory for possible error message. > > First, verify that the account used by the SOS Server service has access to > the machine/drive/directory where each VSS database resides. You may have > had a domain account configured with SOS 3.5.x; the new installation of SOS > 4.0 may be using the default, the Local System account. > > If that doesn't work, I suggest reconfiguring the paths to the problem > databases, using the Browse button in the SOS Server Manager. > > If you continue to experience difficulty, send me a copy of the log.txt > file in the SOS Server > directory. I found the cause of the problem. When I opened the log file, I found that only those databases for which the scrcsafe.ini file was in capital letters (SRCSAFE.INI) were not being recognised as valid databases by SourceSafe. To confirm this, I created a new database ensuring that the srcsafe.ini file was NOT in capital letters, then added the database to SourceSafe... bingo! it worked! As a double-check, I created another database and this time, changed the srcsafe.ini file so that it was in capital letters. SourceSafe DID NOT recognise this database when I tried accessing it. I don't know but this may qualify as a SourceOffsite bug. Thanks, Ani. > > > Linda Bauer > SourceGear > Technical Support > > visit our support forum at > http://support.sourcegear.com > > > At 05:45 AM 6/21/2004, Ani wrote: > >Hi, > > > >We did an upgrade from 3.5.3 to 4 for the SOS Server and client. > >There's a funny problem. Only a few of the databases are being > >displayed in the login window when we are trying to connect to the new > >server. We had copied the two files as instructed after installing the > >new version. Even though all the databases are being shown in the > >new server manager, the same databases are not being made available to > >the remote user when he is trying to connect using the new client. We > >even tried removing the database and adding it again, but it didn't > >work. > > > >Any ideas as to how this problem can be overcome? > > > >Thanks. > > > >Ani. > > > > > >_______________________________________________ > >This is the SourceGear sos-list. > >Send postings to [email protected]. > >To unsubscribe or edit your mail options, go to: > >http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list > >and follow the instructions at the bottom of the page. >