Named Pipe errors 22 and 34 on clustered SQL 2005


We are running a package that access MS SQL Server 2005 using named pipes. When we run it against a single SQL 2005 server it runs without a problem. However when we try and run it against a clustered server it fails with the following errors


R NT create & X - NT error, System, Error, code = (34) STATUS_ACCESS_DENIED


This happens when it is trying to create a file on \sql\query


The named pipe service is enabled. We did find the MS KB article Error message when you connect to a cluster virtual server by using the named pipes protocol: "The machines selected for remote communication is not available at this time." which seemed to be an answer however we found that the registry already had that entry and changing it made no difference.


Any ideas on how to resolve this error will be appreciated.

__________________
A.Rajesh Khanna

Hi,


This is quite normal if your package runs under an account which does not have premission to access file share on the target machine. NP and file sharing use same protocol, It has its own authentication mechanism. If that fails, SQL connection using NP won't proceed.



You can try the same osql command on your application server under the same account that your package runs under.



Thanks.

0x34= 52,

c:/> net helpmsg 52

You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the compter name and try again.



So, please check if there is duplicate machine name.

Thanks for the response, however in this case the response is not a network response rather it is coming from SQL Server. The full response in the SMB segment is


SMB: NT status code = 0xC0000022, Facility = System, Severity = Error, Code = (34) STATUS_ACCESS_DENIED


We can access this clustered server using ODBC, ping etc. with no issues. We can access a non-clustered SQL 2005 server without issues, this issue only appears when the application tries to access a clustered server SQL Server using named pipes (either SQL 2000 or SQL 2005).

Unfortunately this is a package so we cannot change it's access method otherwise it will already have been using ODBC

__________________
A.Rajesh Khanna

Are you able to access it using ODBC with NP protocol? try "osql -E -Snpervername\instance"

or "osql -E -S\\servername\pipe\MSSQL$INSTancename\sql\query"

If default instance. use -Snpervername or -S\\servername\pipe\sql\query.



Thanks.

Hi, that was very interesting. When I try and access it using



"osql -E -S\\servername\pipe\sql\query" from my desktop running Windows XP I get to the SQL server and can issue commands.



When I try running the same command from the application server on which the package runs (running Windows server 2003 SP2 I get the following response



[DBNETLIB]SQL Server does not exist or access denied.

[DBNETLIB]ConnectionOpen (Connect()).



So this may be related to the OS rather than the server? More confusion

__________________
A.Rajesh Khanna

This is quite normal if your package runs under an account which does not have premission to access file share on the target machine. NP and file sharing use same protocol, It has its own authentication mechanism. If that fails, SQL connection using NP won't proceed.



You can try the same osql command on your application server under the same account that your package runs under.



Thanks.