2

I have some Selenium test scripts which I'm using to test a Classic ASP web app, but I'm having problems after restoring the database (SQL Server 2005) with a backup file before every test is run. Immediately after the successful RESTORE (from a Python script running sqlcmd ...) when the ASP tries to connect to the db I get the following error...

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()).,,,Microsoft OLE DB Provider for ODBC

This is being generated by ADODB using this connection string...

"DSN=mydbdsn;UID=myuser;PWD=mypass;"

But trying to connect from a C++ ActiveX object via ODBC also fails with the same error.

Restarting IIS gets things back to normal. And SQL Server 2008 exhibits the same issue.

Does anyone have any idea why I can't connect to the database after a RESTORE?

Thanks,

Improve this question
1
  • As advised, the problem was with connections in the connection pool being disconnected by the RESTORE and then trying to be re-used by the app. Turning off the connection pool fixes things but I'd rather clear it before each RESTORE except I can't find a way to do this that doesn't involve .Net. Can anyone help? Commented Jul 20, 2010 at 21:06

3 Answers 3

Reset to default
2

Copying over from serverfault duplicate question:

From the RESTORE specifications:

During an offline restore, if the specified database is in use, RESTORE forces the users off after a short delay.

So make sure you open new connections after the restore. Existing connections from the connection pool are all busted by RESTORE, as clearly documented. Clear your connection pool before each test.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

I would guess that this is something to do with connection pooling and your connection being killed when the database is put into single user mode for the restore.

Is there any text in the error message other than what is in your question?

Improve this answer

Comments

0

Sounds like the connection to the server is being cached somewhere. Either connection pooling is established or your code is leaking connections somewhere... which is likely with classic asp.

Sounds like you might just want to make an IISRESET call part of your data restore plan.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.