connection memory

I was under the assumption that each connection consumes around 25K of
memory . Is that correct ?
Is this connection memory consumed from the buffer pool or the memtoleave
area ?According to BOL each connection uses this amount:
12 KB + (3 * Network Packet Size)
It comes from the memory pool in the first 2GB or 3GB depending on the /3GB
switch setting and not the MemToLeave.
Andrew J. Kelly SQL MVP
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:uQZuZWh7FHA.4012@.TK2MSFTNGP14.phx.gbl...
>I was under the assumption that each connection consumes around 25K of
>memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>|||Hi,
please read *memory, amount SQL Server uses* in BOL for more and *memory,
architecture : SQL Server Memory Pool * for more on Memory Architecture. if
you wants to read more on SQL SERVER INTERNALS please read *INSIDE SQL SERVER
BY KALEN DELANY *
HTH
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Hassan" wrote:
> I was under the assumption that each connection consumes around 25K of
> memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>
>

connection memory

How much memory does each connection to SQL Server hold ? Is that stored in
the buffer pool area ?Connection memory is stored both in the buffer pool and the mem-to-leave
area. You can get an idea of how much memory each connection is using by
querying the sysprocesses table (see the memusage column), but keep in mind
that some of that memory is shared so it's impossible (as far as I know) to
get an exact number. You can also get some helpful information about
connection memory from DBCC MEMORYSTATUS.
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Hassan" <hassan@.hotmail.com> wrote in message
news:uingOA98HHA.4612@.TK2MSFTNGP03.phx.gbl...
> How much memory does each connection to SQL Server hold ? Is that stored
> in the buffer pool area ?
>
>|||It costs 28KB to only establish a connection to SQL Server 2005.
--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT
"Hassan" <hassan@.hotmail.com> wrote in message
news:uingOA98HHA.4612@.TK2MSFTNGP03.phx.gbl...
> How much memory does each connection to SQL Server hold ? Is that stored
> in the buffer pool area ?
>
>sqlsql

connection memory

I was under the assumption that each connection consumes around 25K of
memory . Is that correct ?
Is this connection memory consumed from the buffer pool or the memtoleave
area ?
According to BOL each connection uses this amount:
12 KB + (3 * Network Packet Size)
It comes from the memory pool in the first 2GB or 3GB depending on the /3GB
switch setting and not the MemToLeave.
Andrew J. Kelly SQL MVP
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:uQZuZWh7FHA.4012@.TK2MSFTNGP14.phx.gbl...
>I was under the assumption that each connection consumes around 25K of
>memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>
|||Hi,
please read *memory, amount SQL Server uses* in BOL for more and *memory,
architecture : SQL Server Memory Pool * for more on Memory Architecture. if
you wants to read more on SQL SERVER INTERNALS please read *INSIDE SQL SERVER
BY KALEN DELANY *
HTH
Regards
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Hassan" wrote:

> I was under the assumption that each connection consumes around 25K of
> memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>
>

connection memory

I was under the assumption that each connection consumes around 25K of
memory . Is that correct ?
Is this connection memory consumed from the buffer pool or the memtoleave
area ?According to BOL each connection uses this amount:
12 KB + (3 * Network Packet Size)
It comes from the memory pool in the first 2GB or 3GB depending on the /3GB
switch setting and not the MemToLeave.
Andrew J. Kelly SQL MVP
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:uQZuZWh7FHA.4012@.TK2MSFTNGP14.phx.gbl...
>I was under the assumption that each connection consumes around 25K of
>memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>|||Hi,
please read *memory, amount SQL Server uses* in BOL for more and *memory,
architecture : SQL Server Memory Pool * for more on Memory Architecture. i
f
you wants to read more on SQL SERVER INTERNALS please read *INSIDE SQL SERVE
R
BY KALEN DELANY *
HTH
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Hassan" wrote:

> I was under the assumption that each connection consumes around 25K of
> memory . Is that correct ?
> Is this connection memory consumed from the buffer pool or the memtoleave
> area ?
>
>

Connection from ASP- ODBC vs. SQLOLEDB

I am having a problem in an ASP site (HTTP/1.1:New application failed which
I believe has been caused by inefficient database connections/memory leaks).
One of the recent changes to the way connections are made is
changed connection string from
driver={SQL Server};server=production;uid=pub;pwd=pub;
database=pub
to
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=pub;Data Source=Production
I thought that the OLE DB Provider is quicker/more efficient than the ODBC
driver for SQL Server, isn't it (although in one of the ASP file, I had to
change the CursorLocation used by ADO Recordset from adUseServer to
adUseClient to get a specific ASP file functioning).
Would I normally expect any other adverse outcome switching from ODBC to
SQLOLEDB ?Hi Patrick,
Thank you for using the newsgroup an it is my pleasure to help you with you
issue.
As for you question of when develope ASP application, which is the
recommended method to connect the database, from my experiece, for the
script, ADO is preferable.
1) ODBC is an API for database access that's both a formal and a de facto
industry standard. Besides being one of the most popular database
interfaces used by applications today, ODBC has gained status as the formal
call-level interface standard by American National Standards Institute
(ANSI) and International Organization for Standardization (ISO). SQL Server
provides a high-performance ODBC interface for all Windows-based
programming environments, and it can be distributed royalty-free with any
application. The SQL Server ODBC driver implements every function in the
ODBC 3 specification. In ODBC-speak, this makes it fully Level 2 (the
highest level) conformant.
RDO is an object interface that's closely tied to ODBC, which means that it
exposes all the functionality in the ODBC driver and is easily available to
Visual Basic programs. RDO supports building visual controls tied directly
to SQL Server data, which greatly reduces the amount of code that must be
written to display data on the screen.
2) OLE DB
OLE DB was first released by Microsoft in 1996 to provide a COM interface
to any tabular data source (that is, data that can be represented with rows
and columns). This includes data in spreadsheets and even text files. OLE
DB can be considered an object version of ODBC but is more powerful in that
it can access data from data sources beyond those that ODBC can access.
Unlike other object interfaces to SQL Server such as RDO, OLE DB doesn't
make programming a call-level interface like ODBC any easier. Also, because
OLE DB uses pointer data types extensively, it's only accessible from C and
C++.
3) ADO
ADO is a higher-level object interface on top of OLE DB that provides much
of the same functionality and performance. Because ADO is pointerless, it
can be accessed from scripting languages such as JScript and development
software such as Visual Basic, as well as from C and C++.
ADO is the recommended and supported interface for Internet applications
written using the Microsoft Visual InterDev development tool. Applications
written with Visual InterDev can call ADO from Active Server Pages (ASP)
and incorporate code written in VBScript or JScript.
For more information, I recommend you to ask you question in our related
newsgroup and the right engineer there will provide you detailed answer
about it:
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.publi
c.inetserver.asp.general
Hope this helps.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||The ASP code is already using ADO (adodb.connection, adodb.recordset
objects). However, the connectionString used for opening a DB connection
has been changed from
driver={SQL Server};server=production;uid=pub;pwd=pub;database=pub
in old environment to
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=pub;Data Source=Production
in new environment
The new provider is better than ODBC isn't it, in terms of the underlying
way ADO use to connect to SQL Server 2000?
Also, could any of the following have any effect on memory usage (e.g., poor
garbage collections in terms of not closing connections):
- SQL Server Client Network Utility- "Enable Shared Memory": I am not sure
whether this should be ticked or not. The Server is a Windows 2000 Server
SP4 which is a Domain Controller, running SQL Server 2000 Standard Edition,
ASP, ASP.NET as well as Microsoft Content Management Server 2002 SP1a. (The
application that has failed is the ASP application connecting using ADO)
- SQL Server Client Network Utility- Protocol: Should Named Pipes be used in
preference to TCP/IP
?
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:5JdW06MAEHA.320@.cpmsftngxa06.phx.gbl...
> Hi Patrick,
> Thank you for using the newsgroup an it is my pleasure to help you with
you
> issue.
> As for you question of when develope ASP application, which is the
> recommended method to connect the database, from my experiece, for the
> script, ADO is preferable.
> 1) ODBC is an API for database access that's both a formal and a de facto
> industry standard. Besides being one of the most popular database
> interfaces used by applications today, ODBC has gained status as the
formal
> call-level interface standard by American National Standards Institute
> (ANSI) and International Organization for Standardization (ISO). SQL
Server
> provides a high-performance ODBC interface for all Windows-based
> programming environments, and it can be distributed royalty-free with any
> application. The SQL Server ODBC driver implements every function in the
> ODBC 3 specification. In ODBC-speak, this makes it fully Level 2 (the
> highest level) conformant.
> RDO is an object interface that's closely tied to ODBC, which means that
it
> exposes all the functionality in the ODBC driver and is easily available
to
> Visual Basic programs. RDO supports building visual controls tied directly
> to SQL Server data, which greatly reduces the amount of code that must be
> written to display data on the screen.
> 2) OLE DB
> OLE DB was first released by Microsoft in 1996 to provide a COM interface
> to any tabular data source (that is, data that can be represented with
rows
> and columns). This includes data in spreadsheets and even text files. OLE
> DB can be considered an object version of ODBC but is more powerful in
that
> it can access data from data sources beyond those that ODBC can access.
> Unlike other object interfaces to SQL Server such as RDO, OLE DB doesn't
> make programming a call-level interface like ODBC any easier. Also,
because
> OLE DB uses pointer data types extensively, it's only accessible from C
and
> C++.
> 3) ADO
> ADO is a higher-level object interface on top of OLE DB that provides much
> of the same functionality and performance. Because ADO is pointerless, it
> can be accessed from scripting languages such as JScript and development
> software such as Visual Basic, as well as from C and C++.
> ADO is the recommended and supported interface for Internet applications
> written using the Microsoft Visual InterDev development tool. Applications
> written with Visual InterDev can call ADO from Active Server Pages (ASP)
> and incorporate code written in VBScript or JScript.
> For more information, I recommend you to ask you question in our related
> newsgroup and the right engineer there will provide you detailed answer
> about it:
>
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.publi
> c.inetserver.asp.general
> Hope this helps.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Hi Patrick,
Thank you for your update.
In my last reply, I just want to say to choose the OLEDB, sorry for the
mistype. For you questions, I will answer them one by one
1)As for the ASP will use the ADO to connect the database and in my last
email, I said ADO is a higher-level object interface on top of OLE DB, so
the level of connect the database would be:
For the provider of OLEDB:
ASP -> ADO -> OLEDB -> Database
For the the provider of ODBC:
ASP -> ADO -> OLEDB -> ODBC -> Database
Also, if the database is SQL Server, you could get for more from OLEDB for
both of them are Microsoft technologies.
Please refer to the following link for detailed information
Choosing Your Data Access Strategy
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoledb/htm
l/choosingcomponents.asp
2) Named Pipes vs. TCP/IP Sockets
In a fast local area network (LAN) environment, Transmission Control
Protocol/Internet Protocol (TCP/IP) Sockets and Named Pipes clients are
comparable in terms of performance. However, the performance difference
between the TCP/IP Sockets and Named Pipes clients becomes apparent with
slower networks, such as across wide area networks (WANs) or dial-up
networks. This is because of the different ways the interprocess
communication (IPC) mechanisms communicate between
peers.
For named pipes, network communications are typically more interactive. A
peer does not send data until another peer asks for it using a read
command. A network read typically involves a series of peek named pipes
messages before it begins to read the data. These can be very costly in a
slow network and cause excessive network traffic, which in turn affects
other network clients.It is also important to clarify if you are talking
about local pipes or network pipes. If the server application is running
locally on the computer running an instance of Microsoft SQL Server?2000,
the local Named Pipes protocol is an option. Local named pipes runs in
kernel mode and is extremely fast.
For TCP/IP Sockets, data transmissions are more streamlined and have less
overhead. Data transmissions can also take advantage of TCP/IP Sockets
performance
enhancement mechanisms such as windowing, delayed acknowledgements, and so
on, which can be very beneficial in a slow network. Depending on the type
of
applications, such performance differences can be significant.TCP/IP
Sockets also support a backlog queue, which can provide a limited smoothing
effect compared to named pipes that may lead to pipe busy errors when you
are attempting to connect to SQL Server.
In general, sockets are preferred in a slow LAN, WAN, or dial-up network,
whereas named pipes can be a better choice when network speed is not the
issue, as it
offers more functionality, ease of use, and configuration options. You
could just choose which protocol to use depends on you production
environment.
3) As for Shared Memory Net-Library is used only for intra-computer
communications, you could let it as the default setting on the client
network utility.
Hope this helps!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other end o

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.

Connection Error: (provider: Shared Memory Provider, error: 0 - No process is on the other e

Hello,

Please bear with me as I am no Sql Server guru, but am getting this error that is preventing me from continuing with my development work. I am the only developer on my team running Sql Server 2005 and it has been working just fine for the last week. I opened the Management Studio this morning, just like every other morning and got this error:

TITLE: Connect to Server

Cannot connect to (local).

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: 233)

Of course the help page says no help is available. I have googled myself sick and still have not found a way so resolve this...has anyone else had this error and/or a fix? I am using XP Pro SP2...any help would be greatly appreciated!

Thanks!
Steph

This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory). There is a chance they provide more information to identify the root cause of the failure.

|||Did not see any weird error message may cause this problem.|||Try and connecting to the SQL Server box using the DAC (Dedicated Admin Connection) e.g if your server name is "SERVER" enter "ADMIN:Server" in Server name and click connect.|||

Not sure if you have resolved this or not. I had the same error trying to connect to a new SQL Server 2005 installation with the management studio from a remote machine and discovered that the named pipes protocol was diasabled in the SQL Server network configuration protocols. I enabled it and restarted SQL Server and the problem was resolved.

Good Luck

Lane

|||

I checked the SQL Server log (message 2 above) and realised there were too many connections opened. The error description was verbose. Closed them and it worked.

Cheers

|||

yaah!!!! i have done same and it worked.. but after opening 5 or 6 connection, m getting the same error message again.....

Cheers!!

|||Another mistake that can cause this error is incorrect credentials in a connection string.|||

execute sp_configure and increment the conexion

|||reboot your db server...|||

The reason this message appears is because of the web.config connectionString. Rather than using the default authentication details of Integrated Security=True:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;Integrated Security=True"

Use "User ID=sa Password=test" for example in the connection string:

connectionString="Data Source=STL-COPELAND\SQLSERVER2005;Initial Catalog=RJ;User ID=sa Password=test"

Rod Copeland

|||

I spent a couple hourse working on this issue until i realised my SQL Server Agent Was stopped. It wasn't set to auto start to reboots didn't help. Oddly all my win32 apps would work fine and asp.net apps running from other machines could get the SQL data but a asp.net 2.0 app running off localhost would throw this error.

Ben

|||

I enable the Protocols "Named Pipes" and it works.

Thanks Lane.

|||After a while like 5 hours that I tried to solve this problem Thanks Lane I found your post... & Now it works|||I received this error after dropping connections while detaching a database. I restarted the SQL server service as well as agent and IIS. nothing seemed to fix it. I then logged into SQL Server under another admin login. I looked at the properties under my usual login and found that the default database was not set, which seemed strange. I reset the default database and logged back in under my account. Not quite sure what SQL Server did, but now it's fixed.