MSSQL 2000 on Cluster Server --> ERROR

Dear
we have a problem when installing MSSQL 2000 on a MS Windows Advanced Server in Cluster
We have a node 1 and a node 2 correct configured
so thats not the problem.
what we did prior to install MSSQL
We did run " comclust " on node 1 ( dos box is open on node 1 ), then we go to node 2 and run " comclust ", we close the dos box on node 2, and then the dos box on node
then we entered the cd in de cd-rom drive from node 1
and we pushed setup.bat
then we configured and aswered all questions correctly.
Also the SQL login name has " domain admin rights "
then we get the message " installing blah blah ... this will take a few minutes "
then after a few minutes we get a message with an error " ERROR: 15457; SEVERITY 0; State 0. "
and installation stops.
I have searched the internet and a thousend message boards about this problem, but non where succesful.
They are saying that this is not an error message but an informational message ...
And that it can be fixed due running reconfigure command in the query annalyzer.
But we can't connect to the sql due no service installed !!
is there someone who can help with this problem.
I really cant see a sollution for this problem.

log:

2003-10-07 15:50:05.13 server SQL server listening on TCP, Shared Memory, Named Pipes.
2003-10-07 15:50:05.13 server SQL server listening on 192.168.0.1:1433, 10.2.101.15:1433, 10.2.101.17:1433, 127.0.0.1:1433.
2003-10-07 15:50:05.14 server SQL Server is ready for client connections
2003-10-07 15:50:05.16 spid5 Starting up database 'tempdb'.
2003-10-07 15:50:05.19 spid4 Warning ******************
2003-10-07 15:50:05.19 spid4 Attempting to change default collation to Latin1_General_CS_AS.
2003-10-07 15:50:07.50 spid4 Clustered index restored for master.sysdatabases.
2003-10-07 15:50:07.53 spid4 Non-clustered index restored for master.sysobjects.
2003-10-07 15:50:07.55 spid4 Non-clustered index restored for master.sysobjects.
2003-10-07 15:50:07.57 spid4 index restored for master.syscolumns.
2003-10-07 15:50:07.58 spid4 index restored for master.systypes.
2003-10-07 15:50:07.58 spid4 index restored for master.sysusers.
2003-10-07 15:50:07.75 spid4 index restored for master.sysproperties.
2003-10-07 15:50:07.75 spid4 index restored for master.sysfulltextcatalogs.
2003-10-07 15:50:07.78 spid4 index restored for master.sysxlogins.
2003-10-07 15:50:07.85 spid4 index restored for master.sysdevices.
2003-10-07 15:50:07.86 spid4 index restored for master.sysservers.
2003-10-07 15:50:07.88 spid4 index restored for master.syslanguages.
2003-10-07 15:50:07.89 spid4 index restored for master.syscharsets.
2003-10-07 15:50:07.89 spid4 index restored for master.sysfilegroups.
2003-10-07 15:50:08.97 spid4 index restored for master.spt_values.
2003-10-07 15:50:08.97 spid4 index restored for master.spt_datatype_info_ext.
2003-10-07 15:50:08.97 spid4 index restored for master.MSreplication_options.
2003-10-07 15:50:08.99 spid4 index restored for master.spt_datatype_info.
2003-10-07 15:50:09.02 spid4 Non-clustered index restored for tempdb.sysobjects.
2003-10-07 15:50:09.02 spid4 Non-clustered index restored for tempdb.sysobjects.
2003-10-07 15:50:09.02 spid4 index restored for tempdb.syscolumns.
2003-10-07 15:50:09.02 spid4 index restored for tempdb.systypes.
2003-10-07 15:50:09.02 spid4 index restored for tempdb.sysusers.
2003-10-07 15:50:09.03 spid4 index restored for tempdb.sysproperties.
2003-10-07 15:50:09.03 spid4 index restored for tempdb.sysfulltextcatalogs.
2003-10-07 15:50:09.03 spid4 index restored for tempdb.sysfilegroups.
2003-10-07 15:50:09.05 spid4 Non-clustered index restored for model.sysobjects.
2003-10-07 15:50:09.05 spid4 Non-clustered index restored for model.sysobjects.
2003-10-07 15:50:09.07 spid4 index restored for model.syscolumns.
2003-10-07 15:50:09.07 spid4 index restored for model.systypes.
2003-10-07 15:50:09.08 spid4 index restored for model.sysusers.
2003-10-07 15:50:09.08 spid4 index restored for model.sysproperties.
2003-10-07 15:50:09.10 spid4 index restored for model.sysfulltextcatalogs.
2003-10-07 15:50:09.10 spid4 index restored for model.sysfilegroups.
2003-10-07 15:50:09.27 spid4 Non-clustered index restored for msdb.sysobjects.
2003-10-07 15:50:09.30 spid4 Non-clustered index restored for msdb.sysobjects.
2003-10-07 15:50:09.35 spid4 index restored for msdb.syscolumns.
2003-10-07 15:50:09.35 spid4 index restored for msdb.systypes.
2003-10-07 15:50:09.38 spid4 index restored for msdb.sysusers.
2003-10-07 15:50:09.38 spid4 index restored for msdb.sysproperties.
2003-10-07 15:50:09.38 spid4 index restored for msdb.sysfulltextcatalogs.
2003-10-07 15:50:09.38 spid4 index restored for msdb.sysfilegroups.
2003-10-07 15:50:09.39 spid4 index restored for msdb.sysjobschedules.
2003-10-07 15:50:09.41 spid4 index restored for msdb.syscategories.
2003-10-07 15:50:09.41 spid4 index restored for msdb.systargetservers.
2003-10-07 15:50:09.41 spid4 index restored for msdb.systargetservergroups.
2003-10-07 15:50:09.42 spid4 index restored for msdb.RTblDatabaseVersion.
2003-10-07 15:50:09.44 spid4 index restored for msdb.sysalerts.
2003-10-07 15:50:09.44 spid4 index restored for msdb.sysoperators.
2003-10-07 15:50:09.44 spid4 index restored for msdb.syscachedcredentials.
2003-10-07 15:50:09.47 spid4 index restored for msdb.logmarkhistory.
2003-10-07 15:50:09.53 spid4 index restored for msdb.RTblNamedObj.
2003-10-07 15:50:09.53 spid4 index restored for msdb.sysdtscategories.
2003-10-07 15:50:09.53 spid4 index restored for msdb.sysdbmaintplan_databases.
2003-10-07 15:50:09.53 spid4 index restored for msdb.mswebtasks.
2003-10-07 15:50:09.55 spid4 index restored for msdb.RTblProps.
2003-10-07 15:50:09.55 spid4 index restored for msdb.RTblRelshipProps.
2003-10-07 15:50:09.55 spid4 index restored for msdb.sysdownloadlist.
2003-10-07 15:50:09.57 spid4 index restored for msdb.sysjobs.
2003-10-07 15:50:09.57 spid4 index restored for msdb.sysjobsteps.
2003-10-07 15:50:09.61 spid4 Non-clustered index restored for pubs.sysobjects.
2003-10-07 15:50:09.61 spid4 Non-clustered index restored for pubs.sysobjects.
2003-10-07 15:50:09.63 spid4 index restored for pubs.syscolumns.
2003-10-07 15:50:09.64 spid4 index restored for pubs.systypes.
2003-10-07 15:50:09.64 spid4 index restored for pubs.sysusers.
2003-10-07 15:50:09.64 spid4 index restored for pubs.sysproperties.
2003-10-07 15:50:09.64 spid4 index restored for pubs.sysfulltextcatalogs.
2003-10-07 15:50:09.64 spid4 index restored for pubs.sysfilegroups.
2003-10-07 15:50:09.67 spid4 index restored for pubs.titleauthor.
2003-10-07 15:50:09.69 spid4 index restored for pubs.stores.
2003-10-07 15:50:09.69 spid4 index restored for pubs.sales.
2003-10-07 15:50:09.71 spid4 index restored for pubs.roysched.
2003-10-07 15:50:09.72 spid4 index restored for pubs.pub_info.
2003-10-07 15:50:09.75 spid4 index restored for pubs.employee.
2003-10-07 15:50:09.78 spid4 index restored for pubs.authors.
2003-10-07 15:50:09.78 spid4 index restored for pubs.publishers.
2003-10-07 15:50:09.80 spid4 index restored for pubs.titles.
2003-10-07 15:50:09.85 spid4 Non-clustered index restored for Northwind.sysobjects.
2003-10-07 15:50:09.85 spid4 Non-clustered index restored for Northwind.sysobjects.
2003-10-07 15:50:09.88 spid4 index restored for Northwind.syscolumns.
2003-10-07 15:50:09.88 spid4 index restored for Northwind.systypes.
2003-10-07 15:50:09.88 spid4 index restored for Northwind.sysusers.
2003-10-07 15:50:09.88 spid4 index restored for Northwind.sysproperties.
2003-10-07 15:50:09.88 spid4 index restored for Northwind.sysfulltextcatalogs.
2003-10-07 15:50:09.89 spid4 index restored for Northwind.sysfilegroups.
2003-10-07 15:50:09.94 spid4 index restored for Northwind.Orders.
2003-10-07 15:50:09.94 spid4 index restored for Northwind.Products.
2003-10-07 15:50:09.96 spid4 index restored for Northwind.CustomerCustomerDemo.
2003-10-07 15:50:09.96 spid4 index restored for Northwind.CustomerDemographics.
2003-10-07 15:50:09.96 spid4 index restored for Northwind.Territories.
2003-10-07 15:50:09.96 spid4 index restored for Northwind.EmployeeTerritories.
2003-10-07 15:50:09.97 spid4 index restored for Northwind.Employees.
2003-10-07 15:50:09.97 spid4 index restored for Northwind.Categories.
2003-10-07 15:50:10.00 spid4 index restored for Northwind.Customers.
2003-10-07 15:50:10.02 spid4 index restored for Northwind.Suppliers.
2003-10-07 15:50:10.57 spid4 Default collation successfully changed.
2003-10-07 15:50:10.57 spid4 Recovery complete.
2003-10-07 15:50:10.57 spid4 Warning: override, autoexec procedures skipped.
2003-10-07 15:50:15.94 spid51 Error: 15457, Severity: 0, State: 1
2003-10-07 15:50:15.94 spid51 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2003-10-07 15:50:16.02 spid51 Error: 15457, Severity: 0, State: 1
2003-10-07 15:50:16.02 spid51 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2003-10-07 15:50:16.13 spid4 SQL Server is terminating due to 'stop' request from Service Control Manager.

Thanks in advance

KurtHowdy

Is it possible the install has completed and the service shutdown is part of that?

Cheers

SG|||ok found the sollution , workaround

on technet : PSS ID 318672
Q318672

hope this helps for other users|||This article was previously published under Q318672
BUG #: 236113 (SHILOH_BUGS)
SYMPTOMS
A Microsoft SQL Server 2000 virtual server set up on multiple nodes may fail with this error message:
Setup failed to perform the required operation on the cluster nodes
The Sqlstp.log file will also contain the following error messages.

NOTE: The Sqlstp.log file is located in the %WINDIR% folder of the node from which you run the Virtual Server Setup program.
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0xa4]
Thread [0xa4] exit code: [0x0]
CRemoteProcess::RunUntilComplete [0xa8] exit code: 2
Remote process exit code was '2' (NODE2).
...
...
CThreadPool::RunUntilComplete returned 2
CThreadPool::RunUntilComplete execution level=1, need execution: 0
One or more errors occurred while running the remote/unattended setups.

In the preceding error message, identify the remote node that has a remote process exit code of 2. In the preceding example, the remote node is NODE2. On the remote node, open the Sqlstpn.log file located in the %WINDIR% folder, and look for this error message:
13:50:08 Begin Action: ShowDlgInstanceName
13:50:20 End Action: ShowDlgInstanceName
13:50:20 ShowDlgInstanceName returned : -1
13:50:20 ShowDlgInstanceName: GetLastError returned: 50044
13:50:20 End Action DialogShowSdInstanceName
13:50:20 End Action ShowDialogs
13:50:20 Action CleanUpInstall:
13:50:20 StatsGenerate returned: 2
13:50:20 StatsGenerate (0x0,0x1,0xf00000,0x200,1033,0,0x0,0x1000000a,0,0, 0
13:50:20 StatsGenerate -1,cluster)
13:50:20 Installation Failed.

NOTE: You may receive the error message
Setup failed to perform the required operation on the cluster nodes
for causes other than the one described in this article. The only way to confirm if the error message is caused by the problem described in this article is to check the SQL Server setup logs and to compare the error footprint.
CAUSE
A race condition between the Setup program that is running on the first node (the node on which the Virtual Server set up is initiated) and the Setup programs that are running remotely on the other nodes.

The SQL Server 2000 Virtual Server set up involves a main set up process that starts one unattended installation for every node that is part of the virtual server. If the number of the unattended installations is two, or more, the race condition may occur.

WORKAROUND
Install a single node virtual server by running the Setup program on any node of the cluster. For more information, see the "How to install a one-node failover cluster (Setup)" topic in SQL Server 2000 Books Online.
Add the second node to the virtual server by running the Setup program again on the node you used in step 1. For more information, see the "How to add nodes to an existing virtual server (Setup)" topic in SQL Server 2000 Books Online.
Repeat step 2 for any number of nodes that you want to add to the virtual server.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: cluster install fails 50044

Keywords: kbbug KB318672
Technology: kbAudDeveloper kbSQLServ2000Search kbSQLServSearch

MSI unable to start the SQL instance service

Hi,
I am deploying a SQL on a three node active cluster setup. Each node will
have a SQL instance running in the cluster virtual server context. This is
the baseline setup required for deploying application databases on the three
SQL instances. Application databases are deployed using an MSI which creates
the database, roles, accounts etc.
The problem that I am facing is that when the Application Database MSI
executes, it will first recycle the SQL instance service to ensure that it is
up and running. At that point it is successfully able to stop the service but
fails to start the service giving the below error:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11920
Date: 10/12/2006
Time: 2:50:05 PM
User: myDomain\sql_account
Computer: SQLSERVER01
Description:
Product: Application Database -- Error 1920. Service 'MSSQL$\VS01'
(MSSQL$\VS01) failed to start. Verify that you have sufficient privileges to
start system services.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The SQL service account has all the permissions on the machine. It is a
domain admin account with local admin privileges. It also has SystemAdmin
role on the SQL instance.
Can anyone tell me if there are any permissions that are missed that could
cause the above error?
Is there a security setting that I can check to validate permissions?
Thanks,
Mehul
The SQL service exists on all three nodes, but is only supposed to run on
one node at a time and then only under the control and direction of the
Cluster Service. You do not have to cycle the service to determine if it is
running, you can use the cluster.exe application or the WMI application
interface to determine if aclustered instance is running.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:6C83D7C2-0514-4195-A46E-FE6D9C0E8831@.microsoft.com...
> Hi,
> I am deploying a SQL on a three node active cluster setup. Each node will
> have a SQL instance running in the cluster virtual server context. This is
> the baseline setup required for deploying application databases on the
> three
> SQL instances. Application databases are deployed using an MSI which
> creates
> the database, roles, accounts etc.
> The problem that I am facing is that when the Application Database MSI
> executes, it will first recycle the SQL instance service to ensure that it
> is
> up and running. At that point it is successfully able to stop the service
> but
> fails to start the service giving the below error:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11920
> Date: 10/12/2006
> Time: 2:50:05 PM
> User: myDomain\sql_account
> Computer: SQLSERVER01
> Description:
> Product: Application Database -- Error 1920. Service 'MSSQL$\VS01'
> (MSSQL$\VS01) failed to start. Verify that you have sufficient privileges
> to
> start system services.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> The SQL service account has all the permissions on the machine. It is a
> domain admin account with local admin privileges. It also has SystemAdmin
> role on the SQL instance.
> Can anyone tell me if there are any permissions that are missed that could
> cause the above error?
> Is there a security setting that I can check to validate permissions?
> Thanks,
> Mehul
|||Geoff,
The configuration is an Active-Active-Active one. Hence the SQL service will
run on each node.
"Geoff N. Hiten" wrote:

> The SQL service exists on all three nodes, but is only supposed to run on
> one node at a time and then only under the control and direction of the
> Cluster Service. You do not have to cycle the service to determine if it is
> running, you can use the cluster.exe application or the WMI application
> interface to determine if aclustered instance is running.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:6C83D7C2-0514-4195-A46E-FE6D9C0E8831@.microsoft.com...
>
>
|||Then you have three instances, which will show up as three different
services on each node. You still need to leave them under the control of
the cluster service.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:3D1AD5FD-FB0A-4C46-A858-E8523BBB61A4@.microsoft.com...[vbcol=seagreen]
> Geoff,
> The configuration is an Active-Active-Active one. Hence the SQL service
> will
> run on each node.
> "Geoff N. Hiten" wrote:
|||Geoff,
Yes this is correct.
If the SQL instance services need to be restarted, what is the recommended
way?
"Geoff N. Hiten" wrote:

> Then you have three instances, which will show up as three different
> services on each node. You still need to leave them under the control of
> the cluster service.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:3D1AD5FD-FB0A-4C46-A858-E8523BBB61A4@.microsoft.com...
>
>
|||Use the cluster.exe command-line utility to stop and restart instances from
within a script.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...[vbcol=seagreen]
> Geoff,
> Yes this is correct.
> If the SQL instance services need to be restarted, what is the recommended
> way?
> "Geoff N. Hiten" wrote:

MSDTC Troubles, Do I Even Need It?

I am running a two node cluster. The failover node had a hardware
failure and I had to re-install Windows. I have been trying to add the
node back into the cluster for 3 days and it continually fails with
MSDTC. Mostly it's been complaining that a DCPromo occured but it
can't handle it correctly-- and msdtc -resetlog doesnt seem to do
anything.
Finally I manually failed MSDTC then failed the cluster over to the new
node...and since MSDTC didnt need to be started it looked like
everything started fine.
So the question is, why exactly do I even need MSDTC in my simple 2
node SQL Server cluster?
Furthermore, can I un-install and re-install MSDTC in an exsisting SQL
Cluster without royally messing things up?
Finally, a bonus question. There seems to be a lot of confusion about
how to upgrade a new node to SQL Server SP3 when the other node already
has it applied. What is the process?
Running the two-node SQL Server 2000 cluster on Windows 2003 SP1
Enterprise Edition.
Answers below...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Hexteque" <hexteque80-demo@.yahoo.com> wrote in message
news:1133252905.313630.34360@.o13g2000cwo.googlegro ups.com...
>I am running a two node cluster. The failover node had a hardware
> failure and I had to re-install Windows. I have been trying to add the
> node back into the cluster for 3 days and it continually fails with
> MSDTC. Mostly it's been complaining that a DCPromo occured but it
> can't handle it correctly-- and msdtc -resetlog doesnt seem to do
> anything.
So your node(s) are also domain controllers? This is a very, very bad idea -
http://support.microsoft.com/?kbid=281662

> Finally I manually failed MSDTC then failed the cluster over to the new
> node...and since MSDTC didnt need to be started it looked like
> everything started fine.
> So the question is, why exactly do I even need MSDTC in my simple 2
> node SQL Server cluster?
>
Neither SQL or Clustering requires it. If you don't have an application that
uses it, don't install it.

> Furthermore, can I un-install and re-install MSDTC in an exsisting SQL
> Cluster without royally messing things up?
>
Test your applications with it offline, if they fully work, you don't need
it.

> Finally, a bonus question. There seems to be a lot of confusion about
> how to upgrade a new node to SQL Server SP3 when the other node already
> has it applied. What is the process?
>
1) dcpromo to remove the domain controller component of each machine. 2)
remove DNS 3) follow this http://support.microsoft.com/?kbid=811168

> Running the two-node SQL Server 2000 cluster on Windows 2003 SP1
> Enterprise Edition.
>
|||All qs have been answered by Rodney. I wanted to shed some light on the last qs

> Finally, a bonus question. There seems to be a lot of confusion about
> how to upgrade a new node to SQL Server SP3 when the other node already
> has it applied. What is the process?
I am assuming that you are adding a new node to the cluster and the old node has SQL Server 200 0 + SP3 install. The process is as follows:
1) Install the operating system on the new node.
2) Join the existing cluster. After joining the cluster, as a test moving the Cluster group (assuming it only has the Quorum, Cluster IP address and Cluster networ name resources) to the new node. If this step succeeds,
go to next steps. Do not test failing SQL Server to the new node yet.
3) Run the Setup program on old node and add new node to the failover cluster. For more information, see How to add nodes to an existing virtual server (Setup).
4) Make sure both nodes are up and running. Do not failover SQL Server from old node to new node. Run SP3a setup on old node and the setup will automatically install it on the new node.
5) After setup is complete, reboot any/all node as required
6) Test failover
How to add nodes to an existing virtual server (Setup)
-----
1 )On the Welcome screen of the Microsoft SQL Server Installation Wizard, click Next.
2) On the Computer Name screen, click Virtual Server and specify the virtual server to which you want to add a node. Click Next.
3) On the Installation Selection screen, click Advanced options. Click Next.
4) On the Advanced Options screen, click Maintain a virtual server for failover clustering. Click Next.
5) On the Failover Clustering screen, click Next.
You do not need to enter an IP address.
6) On the Cluster Management screen, select the node and click Add.
7)If the node is listed as unavailable, you must modify the disk resources in the cluster group of the virtual server so the disk is available for the node you want to add to the Microsoft SQL Server configuration. Click
Next.
8)On the Remote Information screen, enter login credentials for the remote cluster node that has administrator privileges on the remote node of the cluster. Click Next.
9)On the Setup Complete screen, click Finish.
HTH,
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
|||If your old node had MS03-031, you will need to run MS03-031 setup on the old node and setup will automatically install MS03-031 on new node.
If your node did not have MS03-031 (critical security patch for SQL Server 2000) then it is highly recommended that all SQL Server 2000 whether it is clustered or standalone have MS03-031 installed. This requires
SP3/3a to be installed first).
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
|||FYI, Security patch MS03-031 brings SQL up to build 818.
Also, you may have to run the setup program twice, depending on how you
removed the old node. If you only evicted the node from the cluster and did
not run the SQL setup, you will have to re-run the setup to remove the old
node from the SQL configuration information. Once the old node information
is gone from both SQL and the cluster configuration, you can follow the
steps Uttam described.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:D1xb0yf9FHA.4028@.TK2MSFTNGXA02.phx.gbl...
> If your old node had MS03-031, you will need to run MS03-031 setup on the
> old node and setup will automatically install MS03-031 on new node.
> If your node did not have MS03-031 (critical security patch for SQL Server
> 2000) then it is highly recommended that all SQL Server 2000 whether it is
> clustered or standalone have MS03-031 installed. This requires
> SP3/3a to be installed first).
> 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
>

MSDTC stopped working on primary node

Looking for some advice on an issued that just popped up. Not sure if
this was the cause but after applying MS04-011 and 012 MSDTC will not
run on the primary Node. Main application error message is:
"MS DTC was unable to start because the installation of was not
configured to run on a cluster. Please run comclust.exe and restart
MS DTC. Error Specifics: .\msdtc.cpp:825, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 2160"
Just curious if anyone has run comclust again after MSDTC has been
setup and if this will cause any issues. I think that it shouldn't
but it doesn't hurt to check.
Thanks,
Derek
Did you run comclust on both nodes of the cluster?
If so you should be able to run comclust -r on the primary node while the
resource is on the secondary node. After this you can run comclust on this
node. This should resolve the problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand - Yes I ran comclust on both nodes at initial setup. I'll give
comclust -r a try tonight.
Thanks,
Derek

MSDTC Resource on Win2003 cluster

I am having trouble to fail over MSDTC Resource group to a second node in a two node cluster. It is running fine on the first node but refuse to start on the second node.
Any help will be greatly appreciated.
Yuhong
yuhong.huo@.yale.edu
I found the solution. Just want post it here in case anybody run into the same problem.
I took the MSDTC Cluster Group offline on the first node and ran msdtc.exe -resetlog command on the second node. And it worked. See article: http://support.microsoft.com/?kbid=243204
Yuhong
|||You may want to check kb article..
http://support.microsoft.com/default...b;EN-US;248025
Van Thothathri
Windows Clustering
High Availability Microsoft Enterprise Server Products
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
"Yuhong Huo" <anonymous@.discussions.microsoft.com> wrote in message
news:EEA345EC-A673-48A9-8E61-2580049D5F14@.microsoft.com...
>I am having trouble to fail over MSDTC Resource group to a second node in a
>two node cluster. It is running fine on the first node but refuse to start
>on the second node.
> Any help will be greatly appreciated.
> Yuhong
> yuhong.huo@.yale.edu

MsDTc on each node feasibly?

Is there a possibility to create on each node a MSDTC resource (even local on
each server)?
When you talk about a MSDTC resource, I assume you are talking about it as a
cluster resource. There is only one MSDTC resource in a cluster, not one for
each node.
What may be the reason you want it on each node?
Linchi
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:F712ECF3-D326-4CCC-8BCD-AA2425A6B503@.microsoft.com...
> Is there a possibility to create on each node a MSDTC resource (even local
> on
> each server)?
|||Thanks for the confirmation. The reason is I like to create a DB env.
active/active for our application that needs MsDTc. The first node DB for
the application and the second node for reporting and is a replicata of the
first DB.
Do you have maybe a solution for this?
Many thanks in advance,
Walter
"Linchi Shea" schreef:

> When you talk about a MSDTC resource, I assume you are talking about it as a
> cluster resource. There is only one MSDTC resource in a cluster, not one for
> each node.
> What may be the reason you want it on each node?
> Linchi
> "Walter" <Walter@.discussions.microsoft.com> wrote in message
> news:F712ECF3-D326-4CCC-8BCD-AA2425A6B503@.microsoft.com...
>
>
|||You can have multiple SQL instances on a cluster. You still need only one
instance of MSDTC for the entire cluster. There are several techniques that
will allow you to create the shadow database for reporting. Replication and
Log shipping are the most popular. Each has its own advantages and
disatvantages, so it is important to learn the capabilities of each.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Walter" <Walter@.discussions.microsoft.com> wrote in message
news:7CB2BC93-2B37-471B-BD4B-049A1F71658D@.microsoft.com...[vbcol=seagreen]
> Thanks for the confirmation. The reason is I like to create a DB env.
> active/active for our application that needs MsDTc. The first node DB for
> the application and the second node for reporting and is a replicata of
> the
> first DB.
> Do you have maybe a solution for this?
> Many thanks in advance,
> Walter
> "Linchi Shea" schreef:

MSDTC Doesn't seem to work

Hi,
I have a 2 node SQL 2000 Cluster
When I run the dtctester.exe I run into the following error :
================================================== ===
DSN: dtctest
User Name: ******
Password: ******
tablename= #dtc24358
Creating Temp Table for Testing: #dtc24358
Warning: No Columns in Result Set From Executing: 'create table #dtc24358
(ival int)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
Driver]Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cursor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.
================================================== ====
Any help is greatly appreciated. Thanks a Lot.
Regards,
Vick
Just a quick note on it... I'm running the dtctester.exe from a different
box... So I give the sql ip address and user/passwd..
"Vick Shaw" <nospam@.msft.com> wrote in message
news:elTzA1GUHHA.868@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I have a 2 node SQL 2000 Cluster
> When I run the dtctester.exe I run into the following error :
> ================================================== ===
> DSN: dtctest
> User Name: ******
> Password: ******
> tablename= #dtc24358
> Creating Temp Table for Testing: #dtc24358
> Warning: No Columns in Result Set From Executing: 'create table #dtc24358
> (ival int)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> Driver]Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid
> cursor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> ================================================== ====
> Any help is greatly appreciated. Thanks a Lot.
> Regards,
> Vick
>
|||You need to properly configure DTC for Cluster and Network Connections:
http://support.microsoft.com/kb/817064/
http://support.microsoft.com/kb/301600
If you are running Win2K3 SP1, you will need to reset the DTC security
parameters:
http://support.microsoft.com/kb/899191
Since you are beginning the transaction on a remote host, that host will
also need to properly configure its DTC services.
Finally, if the communication must transit any firewalls, then you will need
to restrict RPC ports on both Client and Server for Internet Ports, and then
authorize these Ports in the firewall ACLs.
http://support.microsoft.com/kb/300083
http://support.microsoft.com/kb/250367/EN-US/
Because we authorize much of the Remote Administration utilities outbound
with an outgoing trust from our secured network, we typically configure this
restricted range to 50005100.
Good luck.
Anthony Thomas

"Vick Shaw" <nospam@.msft.com> wrote in message
news:Oo9Vr2GUHHA.4188@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> Just a quick note on it... I'm running the dtctester.exe from a different
> box... So I give the sql ip address and user/passwd..
> "Vick Shaw" <nospam@.msft.com> wrote in message
> news:elTzA1GUHHA.868@.TK2MSFTNGP05.phx.gbl...
#dtc24358
> Driver]Invalid
>
|||Thanks Anthony,
After reading the KB I realize that I installed MSDTC manually on both the
cluster node by Add/Remove Widows Compenet. If I uninstall the DTC the same
way and reinstall thru the Cluster Admin it should work right ?
Thanks again..
Vick
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:u1EiXhQUHHA.4632@.TK2MSFTNGP04.phx.gbl...
> You need to properly configure DTC for Cluster and Network Connections:
> http://support.microsoft.com/kb/817064/
> http://support.microsoft.com/kb/301600
> If you are running Win2K3 SP1, you will need to reset the DTC security
> parameters:
> http://support.microsoft.com/kb/899191
> Since you are beginning the transaction on a remote host, that host will
> also need to properly configure its DTC services.
> Finally, if the communication must transit any firewalls, then you will
need
> to restrict RPC ports on both Client and Server for Internet Ports, and
then
> authorize these Ports in the firewall ACLs.
> http://support.microsoft.com/kb/300083
> http://support.microsoft.com/kb/250367/EN-US/
> Because we authorize much of the Remote Administration utilities outbound
> with an outgoing trust from our secured network, we typically configure
this[vbcol=seagreen]
> restricted range to 5000-5100.
> Good luck.
>
> Anthony Thomas
>
> --
> "Vick Shaw" <nospam@.msft.com> wrote in message
> news:Oo9Vr2GUHHA.4188@.TK2MSFTNGP06.phx.gbl...
different[vbcol=seagreen]
> #dtc24358
Server
>
|||I appologize for breaking up the response in two mails.
I enabled DTC access on both the nodes using add/remove Programs but I added
the MSDTC as a cluster resource thru the cluster Admin console... I've also
applied the required Registry settings for MSDTC (security) but still I'm
not able to get it working. Alos there are no firewalls ...
Thanks again..
Vick.
"Vick Shaw" <nospam@.msft.com> wrote in message
news:OklJjJRUHHA.4796@.TK2MSFTNGP05.phx.gbl...
> Thanks Anthony,
> After reading the KB I realize that I installed MSDTC manually on both the
> cluster node by Add/Remove Widows Compenet. If I uninstall the DTC the
same[vbcol=seagreen]
> way and reinstall thru the Cluster Admin it should work right ?
> Thanks again..
> Vick
>
> "Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
> news:u1EiXhQUHHA.4632@.TK2MSFTNGP04.phx.gbl...
> need
> then
outbound
> this
> different
> Server
>

MSDTC cluster resource

I am configuring a two node SQL cluster and i have 5 physical disk arrays and
i intend to use them in the following order
disk array 1 for quorum
disk array 2 for DATA
disk array 3 for backup
disk array 4 for TempDB
disk array 5 create two partition (1 for Tlog and 2 for MDTC disk resorces)
Will there be any probelm or is there anything wrong with creating two
partitions on the disk array 5 to make available two disk resource for those
two resources i have mentioned above e.g the MSDTC resource and the TLOg
storage . Since i want the MSDTC resource to be in its own resource group.
Please any help will be gladly appreciated.
Slawal
Clustering does not understand partitions, only disks. With that said, array
5 should stay one partition. MSDTC is only 4 MB by default. Are you sure you
will even use MSDTC with SQL? If not, you don't have to install it
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"slawal" <slawal@.discussions.microsoft.com> wrote in message
news:4D82411F-5802-4DE7-AF51-62614083B82E@.microsoft.com...
>I am configuring a two node SQL cluster and i have 5 physical disk arrays
>and
> i intend to use them in the following order
> disk array 1 for quorum
> disk array 2 for DATA
> disk array 3 for backup
> disk array 4 for TempDB
> disk array 5 create two partition (1 for Tlog and 2 for MDTC disk
> resorces)
> Will there be any probelm or is there anything wrong with creating two
> partitions on the disk array 5 to make available two disk resource for
> those
> two resources i have mentioned above e.g the MSDTC resource and the TLOg
> storage . Since i want the MSDTC resource to be in its own resource group.
> Please any help will be gladly appreciated.
>
> Slawal
|||While SQL Server does not require MS DTC, MS DTC on a cluster is only
supported when clustered and it is recommended to cluster it.
When clustering MS DTC it is preferred to have it in its own group with its
own resources, This will require your partion to appear as a physical disk
to place the disk in its own group.
Your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support

MSDTC & W2K3 & SQL 2000 issue

I have MSDTC installed in the Cluster group (no other disks available). It fails over fine, comes online on either node, no problem. My DBA alerted me, that she cannot start Distributed Transaction Coordinator on the node that is NOT in control of the MSD
TC resource using SQL Server Enterprise Manager. This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA) CAN start MSDTC on either/both nodes of the W2K cluster. W
hy won't DTC start on the other node in Ent Mgr? The DBA says that this is necessary for something to function correctly, so I have to fix it? Any ideas/help would be appreciated.
A clustered instance of SQL server uses a cluster-wide MSDTC instance
instead of a local MSDTC instance on each host node. As such, the cluster
admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
Mangler. So, the behavior your DBA noted is correct for a cluster, but
since MSDTC is running the application will function correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"wbielinski at abms dot org" <wbielinski at abms dot
org@.discussions.microsoft.com> wrote in message
news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> I have MSDTC installed in the Cluster group (no other disks available). It
fails over fine, comes online on either node, no problem. My DBA alerted me,
that she cannot start Distributed Transaction Coordinator on the node that
is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
start on the other node in Ent Mgr? The DBA says that this is necessary for
something to function correctly, so I have to fix it? Any ideas/help would
be appreciated.
|||It is a good idea to place MSDTC in its own resource group and another thing
I will check is that the Network access for DTC is enabled. YOu can look for
this in control panel/add remove programs/add remove components/Application
Server.
"Geoff N. Hiten" wrote:

> A clustered instance of SQL server uses a cluster-wide MSDTC instance
> instead of a local MSDTC instance on each host node. As such, the cluster
> admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
> Mangler. So, the behavior your DBA noted is correct for a cluster, but
> since MSDTC is running the application will function correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "wbielinski at abms dot org" <wbielinski at abms dot
> org@.discussions.microsoft.com> wrote in message
> news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> fails over fine, comes online on either node, no problem. My DBA alerted me,
> that she cannot start Distributed Transaction Coordinator on the node that
> is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
> This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
> configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
> CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
> start on the other node in Ent Mgr? The DBA says that this is necessary for
> something to function correctly, so I have to fix it? Any ideas/help would
> be appreciated.
>
>

MSDTC - The Microsoft Clustering Service failed restore a registry

Cluster active-active.
The node B was reinstalled after a hardware failure.
Now the node B is ok. The failover is ok, except because I receive the
message"The Microsoft Clustering Service failed restore a registry key for
resource SQL Server " when I move the Instance B from Node A to Node B.
How can I install MSDTC without affect the Node A (without unistall msdtc
from this node) ?
Node A - Instance A (msdtc resource is online)
thanks for your help.
You don't install DTC, it is already on the machine. It is part of the OS.
You just configure the resource into the cluster. All you should have to do
is edit the properties of the DTC resource and add NodeB as a possible
owner.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Shima" <Shima@.discussions.microsoft.com> wrote in message
news:F5B0FAB8-C20C-4009-96A9-98AB79D5D965@.microsoft.com...
> Cluster active-active.
> The node B was reinstalled after a hardware failure.
> Now the node B is ok. The failover is ok, except because I receive the
> message"The Microsoft Clustering Service failed restore a registry key for
> resource SQL Server " when I move the Instance B from Node A to Node B.
> How can I install MSDTC without affect the Node A (without unistall msdtc
> from this node) ?
> Node A - Instance A (msdtc resource is online)
> thanks for your help.