ASP.NET Connection String

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

Guest

Hello, I have successfully been using the following connection string to
connect via a SQLConnection object in my ASP.Net application for many weeks:

Data Source=MARS-TEST;Initial Catalog=CascadeWMCClient;UID=marsweb;PWD=marsweb

Today, after our Network Support Technician added a hard drive to the
machine, I can no longer connect to the machine via an ASP.Net application on
my development PC. When I attempt to do so, I get this error: SQL Server Does
Not Exist Or Access Denied.

I am using the same connection string on our Web Server, and this will
connect fine, using the same connection string.

Can anyone explain the likely cause for the error above? It seems odd that
this has only occurred since the machine was rebooted?
 
Hi,

Can you connect to the SQL Server via Query Analyizer or Enterprise Manager
from your machine with those credentials? What about a different machine?
From your post it seems like just your machine cannot see SQL Server. Please
reply to this post with the details so the group may help diagnose your
problem better.

Hope this helps.
----------------------------------
 
If you can see the SQL Server on the network, try using the sql
server's IP in the connection string instead of "MARS-TEST". If you
can't see it on the network, that's your problem.
 
Corbin said:
If you can see the SQL Server on the network, try using the sql
server's IP in the connection string instead of "MARS-TEST". If you
can't see it on the network, that's your problem.
Click to expand...

Ok, well I can see both MARS-TEST and it's corresponding IP Address through
windows explorer. I can ping to both addresses and I have sucessfully managed
to connect to the server through enterprise manager, using the same username
and password that i am using in the connection string.

It might also be worth mentioning that I can connect through a VB.Net
windows application using the same connection string.
 
As a last resort, I stopped and then restarted the SQL Server on the machine.

This has fixed the problem, although to be honest, i have no idea why?!
 
Back
Top