Error message: "The server was unable to connect

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

Moderator: SourceGear

Post Reply
rchin
Posts: 5
Joined: Wed Apr 21, 2004 3:28 pm

Error message: "The server was unable to connect

Post by rchin » Wed May 05, 2004 3:53 pm

RE: http://support.sourcegear.com/viewtopic ... ject+clsid

I read it.

We are still in the trial-testing phase...
so latest SOS, VSS 6.0....

No SSO problem accessing LOCAL VSS DB (let's call "demodb") until I created a new db....

I created a NEW, non-local VSS DB on another file server.
No problem seeing it for LAN users.
Added it to the list in SSO Server Manager.

Now remote guy can NOT access demodb:

Error: "The server was unable to connect to the SourceSafe database. Check your server's log file for additional information."

last few lines of log:
5/5/2004 3:43:21 PM - 9: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.
5/5/2004 4:45:13 PM - Connection accepted from 192.168.1.2:3660, session id is 10.
5/5/2004 4:45:13 PM - 10: Exception during Login: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.
5/5/2004 4:45:13 PM - 10: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.
5/5/2004 5:03:59 PM - Connection accepted from 192.168.1.2:3772, session id is 11.
5/5/2004 5:04:00 PM - 11: Exception during Login: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.
5/5/2004 5:04:00 PM - 11: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.


So are you serious that my creating a new DB throws the poor m$ registry off whack ? :shock:

Just not fond of editing the registry.... :x

Thanks :
Top
corey
Posts: 250
Joined: Tue Dec 30, 2003 10:13 am

Post by corey » Thu May 06, 2004 8:14 am

I've never seen the process of creating a new VSS database cause a registration problem with the SourceSafe Automation component before, but according to your log file that's definitely the problem, so it happened somehow. I've created many VSS databases in the past and its never messed up my ssapi.dll registration.
Corey Steffen
SourceGear LLC
Top
rchin
Posts: 5
Joined: Wed Apr 21, 2004 3:28 pm

and what should I do ?

Post by rchin » Thu May 06, 2004 12:54 pm

and what should I do ? follow the regedit instruction ?
Top
corey
Posts: 250
Joined: Tue Dec 30, 2003 10:13 am

Post by corey » Thu May 06, 2004 1:01 pm

Yes.
Corey Steffen
SourceGear LLC
Top
rchin
Posts: 5
Joined: Wed Apr 21, 2004 3:28 pm

KB Article Question

Post by rchin » Thu May 06, 2004 2:59 pm

In the KB article to "Manually registering the Automation component
"
It says:
>>
3. Under the Edit menu, start a search for
"783CD4E4-9D54-11CF-B8EE-00608CC9A71F"
(this is the Class ID for the VSS Automation component)
<<

My value is : 783CD4E0-9D54-11CF-B8EE-00608CC9A71F
(see attached)

Should I go on following the article ? :?: :?: :?:

Thanks
Attachments
registry.gif
registry.gif (148.05 KiB) Viewed 9232 times
Top
corey
Posts: 250
Joined: Tue Dec 30, 2003 10:13 am

Post by corey » Thu May 06, 2004 3:36 pm

No, that doesn't look right. It may be easier to just reinstall the SourceSafe client in your case. Can you try that?
Corey Steffen
SourceGear LLC
Top
rchin
Posts: 5
Joined: Wed Apr 21, 2004 3:28 pm

Reinstallation Instruction Please

Post by rchin » Fri May 07, 2004 12:30 pm

Please provide re-installation instruction.

First un-install ?
Download another from this site ?

Thanks
:?:
Top
Post Reply

Return to “Support (SourceOffSite)”