Re: SQL Server does not exist or access denied
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 21 Jun 2007 06:12:00 -0600
Is this a named instance or a default instance?
Have you verified the port SQL Server is listening on? A few
ways to do that but a couple of options are to Check the SQL
error logs from when SQL Server started, on the server
execute netstat -an from the command prompt.
Did you try getting rid of the DSN and using connection
string without the DSN in your app? What happens if you test
the DSN in the ODBC administrator applet?
Is there some reason you need to use a DSN?
-Sue
On Tue, 19 Jun 2007 07:50:43 -0500, "Raj"
<raj@xxxxxxxxxxxxxx> wrote:
Hello,
I have an application server (running Windows 2003 server with IIS 6.0 ) and
database server (running MS SQL 2000).
Both are on different domains and not trusted each other. ( But having same
IP range )
I have created a SystemDSN pointing to a database in my database server.
I am able to connect to the database through query analyzer, Enterprise
manager.
When I try to connect to the database through SystemDSN from my ASP pages I
got the error:
SQL Server does not exist or access denied.
Here's what I have tried:
1. I am using only TCP/IP port
2. Have changed dynamic port to static 1433
Telnet to databaseserver 1433 results in error.
Please let me know the correct workaround
Please note: The only option I can use to connect to the database is
SystemDSN.
Thank you very much.
Regards,
Raj.
.
- Follow-Ups:
- References:
- Prev by Date: Re: SQL Server does not exist or access denied
- Next by Date: Re: >4 GB RAM
- Previous by thread: Re: SQL Server does not exist or access denied
- Next by thread: Re: SQL Server does not exist or access denied
- Index(es):
Relevant Pages
|