Re: SQL Server 2005
- From: "Ross Mistry" <Ross@xxxxxxx>
- Date: Thu, 7 Feb 2008 09:58:02 -0800
Based on my experience, this issue might also occur if maximum number of
concurrent connections has been reached.
To work around this issue, you can use the sp_configure Transact-SQL
procedure to increase the maximum number of concurrent connections. You can
also manage the instance of SQL Server 2005 in other ways. For example, you
can use the sqlcmd utility.
To use sp_configure to increase the maximum number of concurrent
connections, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press
ENTER.
sqlcmd.exe -E -S servername\instancename
3. When you successfully connect to the instance of SQL Server 2005,
execute the following Transact-SQL statements at the SQL Server prompt.
sp_configure 'user connections', <NewNumber>
Go
Reconfigure
Go
0 means "unlimited" connections
4. Restart the SQL Server service for the change to take effect.
Note: The User connections option is an advanced setting. If you are using
the sp_configure system stored procedure to change the setting, you can
change user connections only when the Show advanced options setting is set
to 1. The setting takes effect after the server is restarted.
Also, you could change it from Management Studio directly
Right click the Server->Properties->Connections, and change "maximum number
of concurrent connections".
If the issue still occurs, please get the following to furhter troubleshoot:
1. collect SQL error log under and send it to me at petery@xxxxxxxxxxxxx
C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG
2. Test to see if other protocals work propelry
sqlcmd.exe -E -S tcp:servername\instancename
sqlcmd.exe -E -S lpc:servername\instancename
Please refer to the following topic in BOL for more details about Sqlcmd
tool:
How to: Connect to the Database Engine Using sqlcmd.exe
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/74b0fb71-7f8e-4171-9431-d075
28532524.htm
3. Does the issue occurs consistently? If you restart the server, can you
still reproduce the problem?
If you have any update, please feel free to let's know. Thank you.
"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message
news:1D7503D4-B097-4F5D-A710-0B457A09DA55@xxxxxxxxxxxxxxxx
Hi,
When you get this error, the reason of it is mostly using a wrong password
for your SQL Login. Ensure your password is correct. Users mostly say "I'm
sure it's correct!" However when I investigate the SQL Error Log, I see
that it says ""Login failed for user '...'. (Microsoft SQL Server, Error:
18456)". So the password is wrong...
--
Ekrem Önsoy
"saw" <swexpress(remove)@hotmail.com> wrote in message
news:%23OwFkLSaIHA.4140@xxxxxxxxxxxxxxxxxxxxxxx
Misty:
Using your recommendation, I was sucessful in resolving the prior issue.
But now, I am facing this issue,
When trying to connect to the SQL SERVER 2005 through Microsoft SQL
Server
Management Studio Express, I get the following error:
Cannot connect to (SERVER NAME) which both are on the same machine, I am
using one machine for everything since it is a lab machine.
Additional Information:
A connection was successfully established with the server, but then an
error
occurred during the login process. (provider: Shared Memory Provider,
error: 0 - No process is on the other end of the pipe.) (Microsoft SQL
Server, Error: 223)
This error prevents my application on the same server machine from
connecting to the sql server on the same machine.
Please let me know what I can do to correct the issue.
Your help is greatly appreciated.
"Ross Mistry" <Ross@xxxxxxx> wrote in message
news:%23A%23sgZRaIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
Additonal thoughts, you should be able to connect to SQL Server via SQL
Server Management Studio. This will provide you with whether or not SQL
Server is operational and if you can connect to the server at least
locally. If you cannot connect let me know what error messages you
receive in your logs (SQL Server and Event Viewer)
"Ross Mistry" <Ross@xxxxxxx> wrote in message news:...
Comments Below
Ross Mistry
"saw" <swexpress(remove)@hotmail.com> wrote in message
news:OjA0xRPaIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have an application that requires an database to be installed on the
same machine as a backend database. I downloaded SQL Server 2005 as
well as the SQL SERVER TOOLS 5.
Since the application as well as the sql are on the same machine I am
receiving error message as follows:
Not Recommended, however, it is fine provided that you don't run into
performance issues.
[SQL Native Client]Shared Memory Provider: No process is on the other
end of the Pipe. [SQL Native Client] Communication Link Failure.
At the bottom right side I don't the icon that the SQL Server is
running however within the services it is running.
This is a depreciated feature as of SQL Server 2005. If the services
are running then you should be in good shape.
Create an ODBC Connection, select the desired SQL Server, Database,
No client will be connected to this server as it is purely a lab
environment.
Could you also tell me how to test the ODBC as well as how to test SQL
Server?
provide credentials (Windows or SQL Mixed) and click Test Connection)
Thank you.
.
- References:
- Re: SQL Server 2005
- From: Ross Mistry
- Re: SQL Server 2005
- From: saw
- Re: SQL Server 2005
- From: Ekrem Önsoy
- Re: SQL Server 2005
- Prev by Date: Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
- Next by Date: Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
- Previous by thread: Re: SQL Server 2005
- Index(es):
Relevant Pages
|
