"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.
>