Make sure that you are running the correct CliConfig.exe, do a search for
it. You need to run it from the WOW directory, if you run the normal 32-bit
"Josh Martins" <NOSPAM_josh@nospam.com_NOSPAM> wrote in message
news:eblkieP%23FHA.1028@TK2MSFTNGP11.phx.gbl...
> I'm having the exact same problem. The default instance works fine but the
> named instance fails.
>
> This happens on single nodes clusers where the named pipes alias is not
> even required, also, even if you do have the alias the problem still
> occurs.
>
> The following can the found in the event log:
>
> The description for Event ID ( 17052 ) in Source ( MSSQL$InstanceName )
> cannot be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
> description; see Help and Support for details. The following information
> is part of the event: [sqsrvres] OnlineThread: Error connecting to SQL
> Server.
>
> If you look at the logs you will see that SQL Server setup is successfull,
> in the cluster log you will notice the a connection to the SQL Server
> named instance cannot be established.
>
> Any others ideas?
>
> "Uttam Parui[MS]" <uttamkp@online.microsoft.com> wrote in message
> news:mGNmT8g9FHA.1236@TK2MSFTNGXA02.phx.gbl...
>> Have looked at the setup files particularly
>>
>> sqlstp.log
>> sqlstpN.log where N is an integer
>> sqlclstr.log -- this may have more info if the setup failed when it was
>> trying to bring the resource online.
>>
>>
>> Best Regards,
>>
>> Uttam Parui
>> Microsoft Corporation
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Are you secure? For information about the Strategic Technology
>> Protection Program and to order your FREE Security Tool
>> Kit, please visit
http://www.microsoft.com/security. >>
>> Microsoft highly recommends that users with Internet access update their
>> Microsoft software to better protect against viruses
>> and security vulnerabilities. The easiest way to do this is to visit the
>> following websites:
http://www.microsoft.com/protect >>
http://www.microsoft.com/security/guidance/default.mspx >>
>>
>
>