username taken as database name

bruce · Post by **bruce** » Wed Nov 14, 2007 12:37 pm

We just upgraded from SOS 3.5 to 4.2. All appears well except the first time users log in using 4.2, they get an error saying that the database path does not exist. Odd thing is that the log file reports that the name of the database that could not be found is the user's username. For example, user giovanna logs in and specifies a valid database name, but generates the error:

11/13/2007 2:18:14 AM - 11: Exception during Login: The SourceSafe database path giovanna does not exist. Please select another database.
11/13/2007 2:18:14 AM - 11: The SourceSafe database path giovanna does not exist. Please select another database.

Thanks for any advise.
Bruce Rienzo

Beth · Post by **Beth** » Wed Nov 14, 2007 3:00 pm

Please go into the SOS server manager and check what you have listed there for databases.

Take note of the patch of one of the databases and remove it. Then add it in again. This time use the Browse button to get to it. Can you get to it?

Go to the SourceOffSite service in the Administrative Tools - Services area. Is that started? What happens if you restart it?

bruce · Post by **bruce** » Thu Nov 15, 2007 11:04 am

Looking at the databases listed in SOS server manager, all looks okay. There are six, all on another server in the domain. Deleting one and adding it again with the Browse button, the database was seen and appeared to add normally. (The Browse button was also used when this was originally configured.)

Checking the SOS service, it was running. Stopping the SOS service gave the error: An unhandled exception (‘System.ObjectDisposedException’) occurred in SosService.exe [1440]. Restarting to SOS service worked normally. Stopping and restarting again worked normally with no error.

Beth · Post by **Beth** » Fri Nov 16, 2007 4:18 pm

With those new users, did you create their user login in VSS instead of SOS? If you entered it in SOS, remove it and create their login in VSS. SOS will pick up that information from VSS.

bruce · Post by **bruce** » Mon Nov 19, 2007 1:28 pm

They are not new users. Thay are the existing SOS 3.5.3 users, already with active logins on vss. They are just new to SOS 4.2. I did have to create logins for them using the SOS 4.2 manager. Then, the remote users installed the SOS 4.2 client and had this problem.

Beth · Post by **Beth** » Mon Nov 19, 2007 4:16 pm

I did have to create logins for them using the SOS 4.2 manager.

You're not really creating logins for the users when you enter information into the SOS. You create logins in VSS. If you added users to SOS, I'd recommend clearing out the user tab. SOS 4 picks the users up from VSS just like SOS 3.5.3 does. You just don't see them until after the user logs in at least once.

Remove the users, restart the SOS service, and then have the users try logging in.

Also, did you uninstall SOS 3.5.3? If not, then did you set SOS 4.2 to use a different set of ports? Each SOS should have it's own ports it uses.