Error message: "The server was unable to connect
Moderator: SourceGear
Error message: "The server was unable to connect
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 ?
Just not fond of editing the registry....
Thanks :
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 ?
Just not fond of editing the registry....
Thanks :
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
SourceGear LLC
and what should I do ?
and what should I do ? follow the regedit instruction ?
KB Article Question
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
"
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 (148.05 KiB) Viewed 9501 times
Reinstallation Instruction Please
Please provide re-installation instruction.
First un-install ?
Download another from this site ?
Thanks
First un-install ?
Download another from this site ?
Thanks