Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2003-12-02 : 08:29:17
|
| Sam writes "I've an ASP connection issue that is driving me mad.When I open a web page that causes a SQL connection to be made, I get the '[Microsoft][ODBC Server Driver][Named Pipes] SQL Server does not exist or access denied.' message.If I run a fat client application on the same server that connects to the same database it opens. The developer says the connection strings are the same.Now for the madding part. After I connect to the database with the fat client application, I can now connect to the database through the thin client. The fat client can be closed or open - no difference to the thin client app.These same applications are running on servers at multiple locations, but only one location is causing me trouble.I've run SysInternals FileMon to try to find the problem: the logs split when the failing instance tries to run dllhost.exe & the successful instance executes scrrun.dll.The developer swears the installs are identical. He says the problem occurred after I ran Microsoft's IISLock Down utility. However, I had to re-run the utility to backout the changes that were causing him problems.All servers are running W2k Server with the latest SPs & hot fixes. Each server is running IIS & SQL. Each server has the same SPs, etc. as well as having run the IISLock Down utility to install & backout settings.Thanks for the help.Sam" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-02 : 12:17:59
|
| The error message that you are getting is due to the client machine not being able to connect to the database server. This can be due to network problems, aliases needing to be setup, SQL Server service is stopped on the database server, etc... So in the connection string, are you using the database server name, the IP address, or an alias? If the first two, can the client ping the machine. If the third, did you setup the alias on the client machine. What protocol is it trying to connect with? I can help you create an explicit entry in the registry for TCPIP which probably will solve the problem. Let me know.Tara |
 |
|
|
|
|
|
|
|