Primary Server will not start

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

Moderator: SourceGear

PostPosted: Fri Aug 13, 2004 9:34 am
Having a problem getting the Primary Server to start. I keep getting an error that the dependancies do not exist or are marked for deletion. Well, i go in and check the services for SOS and sure enough, theres no SQL dependancy listed. SQL is installed on the machine most definately, its one of our bigger servers, so i cant figure out why during the installation the program isnt finding SQL. Can anyone help???

tbaker@exacttarget.com

Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Mon Aug 16, 2004 8:24 am
Is this a new installation, or did SOS Collab previously work?

Is the SOS Collab database on the same machine as the SOS Collab Servers or on a different machine?

Are you using MS SQL Server or MSDE?

Is there a ggdata database? Is there a login for gguser and a user "gguser" for the ggdata database?

In your Control Panel->Admin Tools->ODBC settings, is there an entry under System DSN for gg_sql_server? Is it connecting to the correct machine?

Let me know what you find out.
Linda Bauer
SourceGear
Technical Support Manager
PostPosted: Mon Aug 16, 2004 9:19 am
- its a new installation

- the SOS Collab database is on the same machine

- i beleive we're running SQL Server

- there is a ggdata database, and also a login for gguser. it conencts to the correct machine an i get a successful test connection.

- there is a gg_sql_server entry and it points to this machine that SOS is installed on

Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Mon Aug 16, 2004 11:16 am
Is MS SQL Server using a named instance or a default instance?
Linda Bauer
SourceGear
Technical Support Manager
PostPosted: Mon Aug 16, 2004 11:27 am
its a named instance, i called it SOS

Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Mon Aug 16, 2004 1:44 pm
That's probably the cause of the error. The SOS Collab installer expects to use a default instance.

You should be able to correct the problem with a registry edit.

Look for this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SOSCEPrimary

Edit the value for DependOnService to mssqlserver$"named_instance",
using your actual named instance without the quotes.
Linda Bauer
SourceGear
Technical Support Manager
PostPosted: Mon Aug 16, 2004 2:16 pm
i tried editing the Key but it was a little difficult as ive never done it before. in the key looked like a bunch of HEX numbers in a grid, the on the right side there was sssqlserver$ spelled out, but with a period inbetween each letter. i used that same convention to change the key, so it looked like this m.s.s.q.l.s.e.r.v.e.r.$.s.o.s. it still said the dependancy was eiher marked for deletion or non existant.

Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Wed Aug 18, 2004 3:49 pm
It might be better to uninstall SOS Collab and start over with some new instructions. I've created a Knowledge Base article on how to install SOS Collab to a named instance of MS SQL Server:

http://support.sourcegear.com/viewtopic.php?p=5925
Linda Bauer
SourceGear
Technical Support Manager

Return to Support (Collab)

Who is online

Users browsing this forum: No registered users and 4 guests

cron