dotnet - 2003 server. Urget. Please!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Quick scenario followed by details below
ASP.NET application and MSDE installed on our Win2k dev server. All is good
Replicated this on our Win2.3k production server... problem!

Error is 'server does not exist or access is denied

Details
I installed MSDE via oSQL: setup sapwd=xxx securitymode=sq
Then I installed SQL server client tools only
Restored the DB to the new instance from a .bak file

Created the login, gave it access to the required db and made it dbo
Set up IIS for the dot net app and did all the necessaries IIS and NTFS wise... treble checked

The dotnet app has a connection string that passes the db username and pwd. (checked by running query analyser and connecting). The app error log gives the above error

What can be wrong? The IIS/SQL/app is all the same server. have tried (local) and 127.0.0.1 for datasource
SQL is running. IIS is fine. NTFS is correct. SQL account has full permissions on sql. ASPNET and IUSR_machinename given full control for testing
Ran SQL profiler and there isn't even a log on attempt by the user/app
Any one shed any light? Any more details needed then feel free to yell out
Supposed to be launching this tomorrow and am stumped for any more debugging options

Ja
 
Knocked up the simplest of ASPX pages to whittle down the complexity..
Text box passes the connection string and a second text box is populated with either "connected" or the error message
Always the same.... server does not exist or access denied :(
 
Jay,

Look in [SQL Server Install Path]\80\Tools\Binn for the svrnetcn.exe app.
Run it and make sure named pipes and TCP/IP is enabled for both servers.

-Brian

Jay said:
Knocked up the simplest of ASPX pages to whittle down the complexity...
Text box passes the connection string and a second text box is populated
Click to expand...
with either "connected" or the error message.
 
Solved
When I installed MSDE..... >setup sapwd=xxx etc et
The instance inherited the name of the machine it was installed on
I changed the connection string in my web.config file to point to the instance name as opposed to (local) or 127.0.0.
All is well with the world again

Jay
 
Back
Top