I had a server crash, and am trying to restore a classic ASP web application using an MS SQL 2008 Express database instance.
I successfully have the data tables and all intact records recovered in a new PC, with a new MS SQL installation.
The problem is, my connection file in the ASP application can no longer connect. On my login page I get:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/Connections/mande2.asp, line 20
My current connect string is:
MM_mande_STRING="Provider=SQLOLEDB;Data Source=localhost;UID=username; PWD=mypassword; database=database_name;"
I have a few questions, assuming that I've set up the correct user, assigned that user owner permissions on the restored database, and the user part of this is correct:
1. How do I tell if my MS SQL Server instance is "serving" to the outside world?
2. If I change the data source info from "localhost" to my actual server name and MS SQL instance "SERVER\SQLEXPRESS" the behavior changes. Instead of the error message, the page just loads forever when accessing the database from an ASP page on the site. Is this a clue of some kind? If I name this anything else (localhost, dilbert, etc) I get the error message from above.
3. Any other suggestions for checking the functionality of my new database instance and getting it reconnected?