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.

 All Forums
 SQL Server 2005 Forums
 .NET Inside SQL Server (2005)
 SQL Server is not working properly

Author  Topic 

Moebius
Starting Member

5 Posts

Posted - 2008-04-21 : 11:48:52
Hello friends, I have developed an ASP.NET 2.0 application. The problem is that the IIS server returns the next error:

SQL Server does not allow remote connections

Sometimes returns:

SQL Server does not exists.

My question is if there is any known bug with ASP.NET and SQL Server. My sql server have activated the Remote Connections (its working properly on other web page).

Its a problem of the number of connections??
Its a problem ofbad configuration??
Its a IIS problem??

Please bring me some help.

nr
SQLTeam MVY

12543 Posts

Posted - 2008-04-21 : 12:26:31
Sounds like a network problem except that you say other pages work fine.
Does this work sometimes - you seem t9o imply it does.

It's worthwhile monitoring the number of connections - that wouldn't give that error from sql server but maybe causing a problem in your app.


==========================================
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.
Go to Top of Page

jsmith8858
Dr. Cross Join

7423 Posts

Posted - 2008-04-21 : 12:28:10
Try stopping and then re-starting the SQL Server service, if you haven't already.

- Jeff
http://weblogs.sqlteam.com/JeffS
Go to Top of Page

Moebius
Starting Member

5 Posts

Posted - 2008-04-21 : 12:52:00
I though it was a network problem but it cannot be, because I have another web running with the same database.


The last error I get:
Exception message: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

In my computer both sql server and ASP.NET was working properly, but not in the server.
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2008-04-21 : 12:57:18
So the problem occurs whenever you try to run the app on the server but not when you run it on a remote machine?

With the memory allocation you have on the server it could be that your app cannot get enough memory to run - could be a lot of other things too. I take it you've checked the config file for the app?

==========================================
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.
Go to Top of Page

Moebius
Starting Member

5 Posts

Posted - 2008-04-21 : 13:39:42
In my computer (a remote machine) it works properly. In the IIS server (also a remote machine) it doesn´t works.

The IIS Server have 2 Gb RAM. Is a Pentium IV 3,2 Ghz 64 Bits with Windows 2003 server.
The sql server is equal.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-04-21 : 22:48:08
Tried connect with tcp/ip protocol instead of named pipes?
Go to Top of Page

Moebius
Starting Member

5 Posts

Posted - 2008-04-22 : 03:35:57
The connection was configurated to TCP/IP and Piped Names. I will try with TCP/IP only.
Go to Top of Page

Moebius
Starting Member

5 Posts

Posted - 2008-04-22 : 10:15:54
I was studying the problem. The problem isn´t about TCP/IP and Named Pipes. Probably the problem is that there are too much connections. Simeone have said me that what I have to revise is CommitTransaction method, but I don´t know what it is. Some help?
Go to Top of Page
   

- Advertisement -