asp sql server: process

Showing posts with label process. Show all posts

Wednesday, March 7, 2012

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,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

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

Hello,

TITLE: Connect to Server

Cannot connect to (local).

ADDITIONAL INFORMATION:

Thanks!
Steph

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

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

|||

Ben

|||

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

Thanks Lane.

Saturday, February 25, 2012

Connection error after already connected

I am using Access 2002 as a front end and SQL Server 2000 as a back end.
After I have connected, I use ADO to run a process that gets ten different
sum queries from various SQL Server tables and writes the results to local
Access table. This loops thru 300 to 800 records.
The second time thru this process, at any of the queries, I will almost
always get this error:
-2147467259, Sql Server does not exist or access denied. Now I am already
connected and I have run this same query many times.
If I debug and force the same line, it runs.
Why is it hanging occasionally, and more importantly, what can I do to fix
this?
TIA,
Mike
Are you using named pipes or tcp/ip ?
Vikram
"Michael Beck" <mikeb@.Nospamamuletc.com> wrote in message
news:OxuPzTwTEHA.3336@.TK2MSFTNGP10.phx.gbl...
> I am using Access 2002 as a front end and SQL Server 2000 as a back end.
> After I have connected, I use ADO to run a process that gets ten different
> sum queries from various SQL Server tables and writes the results to local
> Access table. This loops thru 300 to 800 records.
> The second time thru this process, at any of the queries, I will almost
> always get this error:
> -2147467259, Sql Server does not exist or access denied. Now I am already
> connected and I have run this same query many times.
> If I debug and force the same line, it runs.
> Why is it hanging occasionally, and more importantly, what can I do to fix
> this?
> TIA,
> Mike
>
|||TCP/IP
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
news:efh1gyyTEHA.3180@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Are you using named pipes or tcp/ip ?
> Vikram
> "Michael Beck" <mikeb@.Nospamamuletc.com> wrote in message
> news:OxuPzTwTEHA.3336@.TK2MSFTNGP10.phx.gbl...
different[vbcol=seagreen]
local[vbcol=seagreen]
already[vbcol=seagreen]
fix
>

Connection error after already connected

I am using Access 2002 as a front end and SQL Server 2000 as a back end.
After I have connected, I use ADO to run a process that gets ten different
sum queries from various SQL Server tables and writes the results to local
Access table. This loops thru 300 to 800 records.
The second time thru this process, at any of the queries, I will almost
always get this error:
-2147467259, Sql Server does not exist or access denied. Now I am already
connected and I have run this same query many times.
If I debug and force the same line, it runs.
Why is it hanging occasionally, and more importantly, what can I do to fix
this?
TIA,
MikeAre you using named pipes or tcp/ip ?
Vikram
"Michael Beck" <mikeb@.Nospamamuletc.com> wrote in message
news:OxuPzTwTEHA.3336@.TK2MSFTNGP10.phx.gbl...
> I am using Access 2002 as a front end and SQL Server 2000 as a back end.
> After I have connected, I use ADO to run a process that gets ten different
> sum queries from various SQL Server tables and writes the results to local
> Access table. This loops thru 300 to 800 records.
> The second time thru this process, at any of the queries, I will almost
> always get this error:
> -2147467259, Sql Server does not exist or access denied. Now I am already
> connected and I have run this same query many times.
> If I debug and force the same line, it runs.
> Why is it hanging occasionally, and more importantly, what can I do to fix
> this?
> TIA,
> Mike
>|||TCP/IP
"Vikram Vamshi" <vikram.vamshi@.nospam.com> wrote in message
news:efh1gyyTEHA.3180@.TK2MSFTNGP11.phx.gbl...
> Are you using named pipes or tcp/ip ?
> Vikram
> "Michael Beck" <mikeb@.Nospamamuletc.com> wrote in message
> news:OxuPzTwTEHA.3336@.TK2MSFTNGP10.phx.gbl...
different[vbcol=seagreen]
local[vbcol=seagreen]
already[vbcol=seagreen]
fix[vbcol=seagreen]
>

Connection Error

Error Message:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

The error occurs in Visual Studio 2005 v 8.0.50725.42. I have my string in my web.config file. In Visual Studio it doesn't work. When you upload the page it connects and shows the data. Now, I have been several places and been asked, "So what's the issue?" The problem is that I want Visual Studio 2005 to connect so that I can use it to create Gridviews, use the Server Explorer and so on.

Is there an upgrade to VS2005? Is this a known bug? Is there a work-around - a configuration that needs to be setup in the web.config file? I've only just begun my .NET 2.0 experience so type slow and use small words...

Thanks!

I suppouse you are talking about connection string for a database ?, I think you should try this questions in forums about general development or data access, and also give more info about how are you making the connection string, if you are using the "connectionStrings" section and so on.

This forum is only related to Team System and TFS issues, sorry.

Wednesday, March 7, 2012

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Saturday, February 25, 2012

Connection error after already connected

Connection error after already connected

Connection Error

asp sql server

Blog Archive

About Me