Author: AceCorban | Posted on: 6/8/2009 10:12:35 AM | Views : 559

We migrated a series of apps to different servers, some of which were developed before I showed up.  The developer of one in particular is out of town, so I have to fix it.  I'm getting the following error: "SQL Server does not exist or access denied."
No sweat, I've seen this error a thousand times before, it is most likely a connection string issue, user login issue, remote connections, or mixed authentication mode issue.  So I run through the standard checklist of troubleshooting, nothing fixes the issue.  Then I realize that logging into the application works (so I can connect to the SQL Server then, but not later in the app).  Figuring maybe there is a connection string hardcoded somewhere in the broken piece, I come to discover that the broken piece is classic ASP, whereas the functional piece is .NET.
 //connStr is pulled from web.config: //"provider=SQLO ...

Go to the complete details ...