The server was unable to connect to the SourceSafe database

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

Moderator: SourceGear

Post Reply
Eric Jiang
Posts: 1
Joined: Wed Aug 26, 2009 7:20 pm

The server was unable to connect to the SourceSafe database

Post by Eric Jiang » Wed Aug 26, 2009 7:27 pm

Below is the log:

8/27/2009 1:47:18 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:06 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 296: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception getting file. Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 292: Exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Exception getting file. Invalid DOS path: a\aaaaaaaa
8/27/2009 1:59:07 AM - 296: Invalid DOS path: o\owqaaaaa (8004d845)
8/27/2009 2:29:01 AM - 296: Invalid DOS path: a\aaaaaaaa (8004d845)
8/27/2009 2:29:23 AM - 297: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 2:29:43 AM - Connection accepted from 161.88.24.117:4944 on local address 130.147.219.17:8888, session id is 298.
8/27/2009 2:29:48 AM - 298: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 2:30:00 AM - Connection accepted from 161.88.24.179:2222 on local address 130.147.219.17:8888, session id is 299.
8/27/2009 2:30:03 AM - 299: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 2:30:56 AM - Connection accepted from 161.88.82.135:2498 on local address 130.147.219.17:8888, session id is 300.
8/27/2009 2:31:03 AM - 300: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 2:33:14 AM - Connection accepted from 161.88.24.179:2252 on local address 130.147.219.17:8888, session id is 301.
8/27/2009 2:33:16 AM - 301: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 2:39:25 AM - Connection accepted from 161.88.24.179:2313 on local address 130.147.219.17:8888, session id is 302.
8/27/2009 2:39:27 AM - 302: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 4:12:43 AM - Connection accepted from 161.88.24.179:3407 on local address 130.147.219.17:8888, session id is 303.
8/27/2009 4:12:45 AM - 303: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 4:15:10 AM - Connection accepted from 161.88.24.179:3429 on local address 130.147.219.17:8888, session id is 304.
8/27/2009 4:15:18 AM - 304: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 4:15:30 AM - Connection accepted from 161.88.24.179:3434 on local address 130.147.219.17:8888, session id is 305.
8/27/2009 4:15:32 AM - 305: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 4:18:01 AM - Connection accepted from 161.88.24.121:1785 on local address 130.147.219.17:8888, session id is 306.
8/27/2009 4:18:09 AM - 306: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 5:24:31 AM - Connection accepted from 161.88.24.179:3961 on local address 130.147.219.17:8888, session id is 307.
8/27/2009 5:24:33 AM - 307: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 5:56:12 AM - Connection accepted from 161.88.24.179:4218 on local address 130.147.219.17:8888, session id is 308.
8/27/2009 5:56:14 AM - 308: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 8:26:39 AM - Connection accepted from 161.88.24.179:1608 on local address 130.147.219.17:8888, session id is 309.
8/27/2009 8:26:42 AM - 309: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
8/27/2009 8:26:49 AM - Connection accepted from 161.88.24.179:1631 on local address 130.147.219.17:8888, session id is 310.
8/27/2009 8:26:51 AM - 310: Exception during Login: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Could anyone tell me how to resolve it? Thanks!

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: The server was unable to connect to the SourceSafe database

Post by lbauer » Thu Aug 27, 2009 8:12 am

This looks like a .Net error. I don't think we've seen this error before with SourceOffSite.

I could use more information.

Is this a new error? Was SOS working properly before? If it was working before, what may have changed?

Do you get any errors on the client side? What operations are you attempting?

What version of SourceOffSite Server are you using?

What operating system is it installed on and is it 32- or 64-bit?

What version(s) of the .Net Framework is on the SourceOffSite server machine? Look in C:\Windows\Microsoft.NET\Framework for folders of the versions installed.

What version of SourceSafe are you using?

We also need to know the exact SourceSafe Automation Component version. To determine which version of the SourceSafe Automation Component (ssapi.dll) is used by SOS Server, look under this registry key:

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

The value will have the path to the specific ssapi.dll file used by SOS Server. For the version information, locate the ssapi.dll file. Right click on the ssapi.dll file, choose Properties->Version.

Are there any errors in the Windows Event viewer relate to the error?
Linda Bauer
SourceGear
Technical Support Manager

Post Reply