After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore stopped working and generates:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?
It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank you.

After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore sto
pped working and generates:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (Wra
pperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/defaul...scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you.

After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore stopped working and generates
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead())
Server: Msg 11, Level 16, State 1, Line
General network error. Check your network documentation
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you.

After enabling named pipes and disabling again, not able to start engine

I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:

TITLE: Connect to Server

Cannot connect to ****** (replaced my servername with stars here for privacy).

ADDITIONAL INFORMATION:

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK

found it, I had also enabled IP1 and IP2 which prevented me from connecting it apears|||It also seems that there's a bug in ASP.NET that prevents the Named Pipes protocol from being able to be used in default setup configuration. Perhaps this isn't experienced by many people as TCP/IP connections are also enabled by default and they work. Have a look here:

BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159

I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.

After enabling named pipes and disabling again, not able to start engine

I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:

TITLE: Connect to Server

Cannot connect to ****** (replaced my servername with stars here for privacy).

ADDITIONAL INFORMATION:

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK

found it, I had also enabled IP1 and IP2 which prevented me from connecting it apears|||It also seems that there's a bug in ASP.NET that prevents the Named Pipes protocol from being able to be used in default setup configuration. Perhaps this isn't experienced by many people as TCP/IP connections are also enabled by default and they work. Have a look here:

BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159

I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.