MS SQL Server Clustering - Unable to install Named Instance

Author

Unable to install Named Instance

Josh Martins

2005-12-04, 11:23 am

I'm have created a single node cluster running on Windows 2003 Ent. X64. All
the required disk resources for clustering SQL Server has been configured, a
MSDTC group has also been created and configured.

When trying to install a NAMED INSTANCE of SQL Server the installation fails
when trying to bring the SQL Server service online. (At this point
everything gets rolled back.) The following error can be found in the
application event log:

The description for Event ID ( 17052 ) in Source ( MSSQL$AS20 ) 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.

Usually this would be caused by Windows 2003 restricting TCP/IP until SP3 is
installed. (Remember that this is a single node cluster though.) Also, even
if I do create a named pipes alias the exact same thing happens.

(Note that installing a default instance work perfectly!)

The application event log does contain the following error:
Could not initialize the MS DTC user interface server object.

I'm thinking that whatever is causing the MSDTC error is also responsible
for the troubles with installing a named instance of SQL Server. (All the
MSDTC resources are online though.) I don' t know when this error started -
I got the server with this error already there.

Any ideas on what else could be causing the problem or how to correct the
MDDTC error above?

Tom Moreau

2005-12-04, 11:23 am

Check out:

http://support.microsoft.com/defaul...kb;en-us;815431

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada tom@cips.ca
www.pinpub.com

"Josh Martins" <NOSPAM_josh@nospam.com_NOSPAM> wrote in message
news:uflpw8O%23FHA.1312@TK2MSFTNGP09.phx.gbl...
> I'm have created a single node cluster running on Windows 2003 Ent. X64.
> All the required disk resources for clustering SQL Server has been
> configured, a MSDTC group has also been created and configured.
>
> When trying to install a NAMED INSTANCE of SQL Server the installation
> fails when trying to bring the SQL Server service online. (At this point
> everything gets rolled back.) The following error can be found in the
> application event log:
>
> The description for Event ID ( 17052 ) in Source ( MSSQL$AS20 ) 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.
>
> Usually this would be caused by Windows 2003 restricting TCP/IP until SP3
> is installed. (Remember that this is a single node cluster though.) Also,
> even if I do create a named pipes alias the exact same thing happens.
>
> (Note that installing a default instance work perfectly!)
>
> The application event log does contain the following error:
> Could not initialize the MS DTC user interface server object.
>
> I'm thinking that whatever is causing the MSDTC error is also responsible
> for the troubles with installing a named instance of SQL Server. (All the
> MSDTC resources are online though.) I don' t know when this error
> started - I got the server with this error already there.
>
> Any ideas on what else could be causing the problem or how to correct the
> MDDTC error above?
>

Josh Martins

2005-12-04, 11:23 am

From my previous post:
"Usually this would be caused by Windows 2003 restricting TCP/IP until SP3
is
installed. (Remember that this is a single node cluster though.) Also, even
if I do create a named pipes alias the exact same thing happens."

I'm I perhaps not creating the alias correctly? I'm just typing in
MY_VIRTUAL_SEVERNAME
\MY_INSTANCE in the alias box, and leaving the rest as
defaults created by the wizzard.

Also, I don't believe that it is necessary to even create an alias as
described in the artice you pointed out since this is a single node cluster.

Comments?

"Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message
news:%23acBuLP%23FHA
.1140@tk2msftngp13.phx.gbl...
> Check out:
>
> http://support.microsoft.com/defaul...kb;en-us;815431
>
> --
> Tom
>
> ----------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada tom@cips.ca
> www.pinpub.com
>
> "Josh Martins" <NOSPAM_josh@nospam.com_NOSPAM> wrote in message
> news:uflpw8O%23FHA.1312@TK2MSFTNGP09.phx.gbl...
>
>

Josh Martins

2005-12-04, 1:23 pm

On thing that I did not mention is that although the OS is Windows 2003 X64
we are running with the 32 bit version of SQL Server.

"Josh Martins" <NOSPAM_josh@nospam.com_NOSPAM> wrote in message
news:uflpw8O%23FHA.1312@TK2MSFTNGP09.phx.gbl...
> I'm have created a single node cluster running on Windows 2003 Ent. X64.
> All the required disk resources for clustering SQL Server has been
> configured, a MSDTC group has also been created and configured.
>
> When trying to install a NAMED INSTANCE of SQL Server the installation
> fails when trying to bring the SQL Server service online. (At this point
> everything gets rolled back.) The following error can be found in the
> application event log:
>
> The description for Event ID ( 17052 ) in Source ( MSSQL$AS20 ) 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.
>
> Usually this would be caused by Windows 2003 restricting TCP/IP until SP3
> is installed. (Remember that this is a single node cluster though.) Also,
> even if I do create a named pipes alias the exact same thing happens.
>
> (Note that installing a default instance work perfectly!)
>
> The application event log does contain the following error:
> Could not initialize the MS DTC user interface server object.
>
> I'm thinking that whatever is causing the MSDTC error is also responsible
> for the troubles with installing a named instance of SQL Server. (All the
> MSDTC resources are online though.) I don' t know when this error
> started - I got the server with this error already there.
>
> Any ideas on what else could be causing the problem or how to correct the
> MDDTC error above?
>

Josh Martins

2005-12-05, 7:23 am

Solved.

When running CliConfig.exe make sure you execute it from the WOW directory
if running on x64. If you run the 32bit one the settings are not detected
when installing SQL Server.

"Josh Martins" <NOSPAM_josh@nospam.com_NOSPAM> wrote in message
news:ecAoOXP%23FHA.1248@TK2MSFTNGP14.phx.gbl...
> From my previous post:
> "Usually this would be caused by Windows 2003 restricting TCP/IP until SP3
> is
> installed. (Remember that this is a single node cluster though.) Also,
> even
> if I do create a named pipes alias the exact same thing happens."
>
> I'm I perhaps not creating the alias correctly? I'm just typing in
> MY_VIRTUAL_SEVERNAME
\MY_INSTANCE in the alias box, and leaving the rest as
> defaults created by the wizzard.
>
> Also, I don't believe that it is necessary to even create an alias as
> described in the artice you pointed out since this is a single node
> cluster.
>
> Comments?
>
> "Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message
> news:%23acBuLP%23FHA
.1140@tk2msftngp13.phx.gbl...
>
>

Sponsored Links