March 17, 2008 at 6:24 am
I am really green when it comes to SQL Server 2005. I get this error when trying to access my application via its website. I have come across this problem before and increased the user connections, but this time I cant get to the server properties via the SSM Studio or via cmd prompt.
when I try to access the website I get this message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
/asts3/includes/common.inc, line 44
When I attempt to access the server properties via SSM Studio I get this error..
SQL Server Error 10053, a connection was successfully established with the server but then an error occurred with the login. this is sporadic because i successfully login, go the the server properties and then get the same error. Very strange.
when i use the command prompt to enter in the command
EXEC sp_configure 'user connections',25
go (i get the error message after i hit enter here)
reconfigure
go
I get an error telling me the user connections option is a advanced option or does not exist.
I am totally new to sql so I have used my pocket consultant to assist in the syntax, which still could be off. Any guidance would be greatly appreciated.
March 18, 2008 at 7:18 am
You need to enable advanced options first
sp_configure 'show advanced options',1
RECONFIGURE
sp_configure 'user connections'
-- sp_configure 'user connections',0
-- RECONFIGURE
However, I suspect that you have a different issue. The default is 0 (Auto configure).
March 18, 2008 at 7:20 am
Which version of SS are you using? What about the Server configuration?
March 18, 2008 at 7:59 am
the number of connections was set to 3 initially because of the small amount of users who are allowed to access the database. I had the error before and increased it to 4 but weeks later the same problem has come back. The version of SS 2005 i am using is 9.0.2050.
what specifics are you wanting to know about the server configuration?
all services are automatically started
using windows authentication
network config is tcp/ip only (the others are disabled)
native client protocol is tcp/ip (the others are disabled)
concerning enabling advanced options and user connections increase to unlimited/#, when i use each command will it return an indicator that the command executed correctly?
I have seen from other sites that the EXEC precedes the sp_configure command. As I said I am very new to this environment and am just starting to learn T-SQL (have not yet had opportunity to take the first class) but will when I get this going.
hope i have answered your server configure question.
March 18, 2008 at 8:08 am
The current version of SS 2k5 is 9.0.3228 http://support.microsoft.com/default.aspx?scid=kb;en-us;949095&sd=rss&spid=2855, although I don't see any need to apply what are called Cumulative Updates. I would however go to MS and download Service Pack 2.
If you are concerned about leaving the advanced options enabled, just set to 0(zero) after you change user connections.
As for needing exec. It works either way, but technically you should have the exec in front.
However, unless you are concerned about run away user connections, I would just set it to unlimited. However, the default is unlimited (32k), so someone had to change this in the first place.
March 18, 2008 at 8:10 am
Oh, the rest of it? I was only curious if actual connections was set to 0, which would imply the issue was something other than running out of actual connections.
March 18, 2008 at 10:06 am
For some strange reason it is now working. when it did allow me to go into the server properties under object explorer it did not reflect the user connections as 0. I changed it within the server properties>connections.
I am really confused about how sporadic the SSMS is allowing me to access the server properties. I suspect it may be a network/security login problem of some sort.
I am using both SQL Server and Windows authentication as requested per the vendor who built the web-application we are using.
The log reflects a NT authority login and a SQL Server login id that is not trusted. The exceeded user connection error occurs when trying to login using the SQL SErver login not the NT connection.
I am going to have to talk with the application developer and maybe they can give me some insight.
Thanks and if you have any leads i should take a look at I would greatly appreciate it.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply