MS SQL Server Connectivity - STATUS_ACCESS_DENIED using named pipes on cluster

Author

STATUS_ACCESS_DENIED using named pipes on cluster

Adam

2005-05-31, 8:23 pm

We recently moved to a sql 2000 cluster. An application uses named pipes odbc
connection to connect to sql server. It cannot use tcp/ip. When trying to
connect to the new cluster, the odbc connection test is successful (and
verified it is using named pipes). Yet when this application (actually a
windows service) tries to connect to the named pipe (using sql authentication
in all cases here) it yields STATUS_ACCESS_DENIED
in the network trace. It
indeed is connecting to \sql\query to the local pipe mapping done on the
cluster seems to be working. Running net view \\clustername does work ok, so
ipc is working.
thoughts?

Sophie Guo [MSFT]

2005-06-01, 3:23 am

Hello,

This issue may caused by many factors and I suggest that you perform
troubleshooting steps to narrow down the issue:

Step 1: Make sure SQL server is listing on the TCP/IP, Shared memory, Named
Pipes.

You can use "SQL Server Network Utility" to enable TCP/IP and Named Pipes
for SQL server instance. Restart SQL server, then check the SQL server
error logs to make sure SQL server is listing on the TCP/IP, Shared memory,
Named Pipes.

Step 2: Enable only Named Pipes in "SQL server Client Network Utility".

Step 3: If you are using alias for the SQL server instance, make sure it is
configured correctly.

Step 4: Check if you can use SQL Query Analyzer(QA) to conntect to the
virtual server as sa.

If so, the client utility QA can connect to SQL server with Named Pipes
successully. Your application may have problems.

If not, check the SQL server error logs, Windows NT event logs, and SQL
server cluster logs to see the related error message.

The following articles are for your reference:

KB 831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127

306985 RPC Errors When Connecting a Cluster Virtual Server with Named Pipes
http://support.microsoft.com/?id=306985

254321 Clustered SQL Server do's, don'ts, and basic warnings
http://support.microsoft.com/?id=254321

I hope the information is helpful.

Sophie Guo
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================
====================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Adam

2005-06-01, 8:23 pm

Hi Sophie,
Thanks for the info. Named pipes do work OK as I can test via odbc
administrator and it works fine. I have verified that the dsn says its using
the named pipe... its just when the program uses the pipe it fails with
access denied.
Im leaning towards what permissions are required for an nt4 machine to
connect to a pipe on a windows 2003 machine? Since the named pipe works fine
when I run it interactively but when the service runs it (and thus using the
machine account I believe) it fails, thus leading me in that direction.
I captured a trace doing it through odbc administrator and it works using
named pipes. When the service runs and requests the connection
to \\sql\pipe\query it gets accessed denied so Im fairly convinced its a
user context issue dealing with pipes. Ant thoughts on that?

Thanks,
Adam

"Sophie Guo [MSFT]" wrote:

> Hello,
>
> This issue may caused by many factors and I suggest that you perform
> troubleshooting steps to narrow down the issue:
>
> Step 1: Make sure SQL server is listing on the TCP/IP, Shared memory, Named
> Pipes.
>
> You can use "SQL Server Network Utility" to enable TCP/IP and Named Pipes
> for SQL server instance. Restart SQL server, then check the SQL server
> error logs to make sure SQL server is listing on the TCP/IP, Shared memory,
> Named Pipes.
>
> Step 2: Enable only Named Pipes in "SQL server Client Network Utility".
>
> Step 3: If you are using alias for the SQL server instance, make sure it is
> configured correctly.
>
> Step 4: Check if you can use SQL Query Analyzer(QA) to conntect to the
> virtual server as sa.
>
> If so, the client utility QA can connect to SQL server with Named Pipes
> successully. Your application may have problems.
>
> If not, check the SQL server error logs, Windows NT event logs, and SQL
> server cluster logs to see the related error message.
>
> The following articles are for your reference:
>
> KB 831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
> http://support.microsoft.com/?id=831127
>
> 306985 RPC Errors When Connecting a Cluster Virtual Server with Named Pipes
> http://support.microsoft.com/?id=306985
>
> 254321 Clustered SQL Server do's, don'ts, and basic warnings
> http://support.microsoft.com/?id=254321
>
> I hope the information is helpful.
>
>
> Sophie Guo
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> ====================
====================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================
====================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Sophie Guo [MSFT]

2005-06-02, 3:23 am

Hello,

I suggest that you install SQL server 2000 client tools on a Windows NT
Workstation 4.0 machine. Check if you can use SQL Query Analyzer(QA) on the
NT4 machine to connect to the virtual server as sa. If so, the application
has problems.

Note: NT4 has been out of product Lifecycle. Please refer to the following
article:

http://support.microsoft.com/gp/lifewinfaq#Windows

Please make sure the Named Pipes in "SQL server Client Network Utility" are
enabled on the Windows NT 4 machine.

I hope the information is helpful.

Sophie Guo
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================
====================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Sponsored Links