| Author |
Topic |
|
mAdMaLuDaWg
Starting Member
42 Posts |
 Posted - 2004-05-05 : 10:53:04
|
| Hello All,I have an ASP.NET app on a Windows 2003 server and an MSDE SQL Server installed on another PC on the network. When I attempt to connect to the SQL server from the ASP.NET app I get a 'SQL Server does not exist or access is denied error'... however, the app works great every 1 out of 10 times or so! So I think it has to do with some configuration on SQL server (I have enterprise manager,BTW).Any ideas??Here is my connection string:data source=SQLServer;User ID=user1;password=CCC1;initial catalog=CharmsI just found out that If I run the ASP.NET web app from the server of the ASP.NET app server, it works fine all the time. However, if I run the web app from any other server on the network it intermittently works. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-05 : 12:10:21
|
| Do you have the lastest mdac?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
mAdMaLuDaWg
Starting Member
42 Posts |
Posted - 2004-05-05 : 12:44:37
|
| Yes |
|
|
|
mAdMaLuDaWg
Starting Member
42 Posts |
Posted - 2004-05-05 : 12:48:32
|
| Ok, here is something else I discovered... If I access the webapp on the webapp server, it works all the time. If I then goto anyother PC on the network and attempt to access the webapp, it works for a period of time (like 5 or ten minutes, then goes back to the 'SQL Server does not exist or access is denied' error). |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-05 : 13:21:40
|
| Could it be due to too much activity on the database - holding active connections and processing on them forcing the governor to kick in to slow things down?Check DBCC CONCURRENCYVIOLATIONThat should not depend on the PC you connect to the web app though - but maybe it is doing something odd.More likely it sounds like a roblem with the web app in that it isn't handling remote connections properly.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
mAdMaLuDaWg
Starting Member
42 Posts |
Posted - 2004-05-05 : 13:36:09
|
| No all the concurrencyviolation columns are zero.I think that Win2k3 is pooling a connection when I access the web app on the web app server. So when I use another PC it just uses the pooled connection, but after sometime the pooled connection expires.I'm stumped... I went through all the KB articles and forum posts through google, and still can't find out why this is happening. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-05-05 : 14:39:59
|
| Pooled connections should only be dropped if they are not being used. New ones should be created if one isn't available (but you probably have the pool set to a max of 5 against mdse).Try running the profiler on the server to see when connections are created and dropped.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
mAdMaLuDaWg
Starting Member
42 Posts |
Posted - 2004-05-05 : 14:48:02
|
| Exactly, if I access the web app from any place other than the web app server, connections cannot be created for some reason. I'll run the profiler to see about the connections and get back. |
|
|
|
mAdMaLuDaWg
Starting Member
42 Posts |
Posted - 2004-05-05 : 15:55:52
|
| Ok, I ran SQL Profiler and when I run the webapp from the webapp server, a connection is created that has the NTUSERNAME = mylogin and login=user1. Accessing the webapp from outside the webapp server uses this same connection.After the connection is dropped, I cannot create a new one unless I runn the webapp on the webapp server.Any idea why? |
|
|
|
|
SQL server does not exist or access is denied err.