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

MS-SQL 2000 Enterprise clustered installation fails

Hi everyone,
I have problem installing MS-SQL 2000 enterprise on Windows Server 2003 Ent.
cluster. The message I'm getting is "Setup failed to perform required
operations on the cluster nodes." The only thing "cluster.log" says in
regards of the MS-SQL is that "the virtual SQL server name can't be found.
Now, that's not the first time I'm doing this installation. Often I got in
the same problem, but by relaxing the local Policy (we are running very
restrictive GPO) usually resolved the problem. Therefore, I thing the problem
comes from the GPO restrictions. Also, I'm using the same domain account
used to install MSCS and I had no issues there.
My question is, what's the best way to approach this problem and what are
the MS-SQL requirements (in terms account permissions)?
The install account must be an admin on all nodes.
The MS task scheduler must be enabled on all nodes. <-- this is likely the
problem.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"kkantchev@.hotmail.com" <kkantchevhotmailcom@.discussions.microsoft.com>
wrote in message news:370B4F33-07E5-43A2-B4F3-4D0F485809AC@.microsoft.com...
> Hi everyone,
> I have problem installing MS-SQL 2000 enterprise on Windows Server 2003
> Ent.
> cluster. The message I'm getting is "Setup failed to perform required
> operations on the cluster nodes." The only thing "cluster.log" says in
> regards of the MS-SQL is that "the virtual SQL server name can't be found.
> Now, that's not the first time I'm doing this installation. Often I got in
> the same problem, but by relaxing the local Policy (we are running very
> restrictive GPO) usually resolved the problem. Therefore, I thing the
> problem
> comes from the GPO restrictions. Also, I'm using the same domain account
> used to install MSCS and I had no issues there.
> My question is, what's the best way to approach this problem and what are
> the MS-SQL requirements (in terms account permissions)?
|||Are you, or the cluster service account, also a Domain Admin? If not, then
you will need to have your Domain Admins create Domain Local Groups before
the installation.
Check out the installation logs; they contain the point of failure and
specifics about why it failed.
http://support.microsoft.com/kb/910228/en-us
http://msdn2.microsoft.com/en-us/library/ms143702.aspx
Good luck.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OsZVE65SHHA.2256@.TK2MSFTNGP02.phx.gbl...
> The install account must be an admin on all nodes.
> The MS task scheduler must be enabled on all nodes. <-- this is likely
the
> problem.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "kkantchev@.hotmail.com" <kkantchevhotmailcom@.discussions.microsoft.com>
> wrote in message
news:370B4F33-07E5-43A2-B4F3-4D0F485809AC@.microsoft.com...[vbcol=seagreen]
found.[vbcol=seagreen]
in[vbcol=seagreen]
account[vbcol=seagreen]
are
>
sql

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:

Msg 5133, Level 16, State 1, Line 1

I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
the error in subject when I try to create a database using this statement:
CREATE DATABASE [ESBMessageTracking] ON PRIMARY
( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE = 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
LOG ON
( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF' ,
SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
COLLATE SQL_Latin1_General_CP1_CI_AS
GO
I have confirmed the path is correct. Don't know what is going on. Help
please."SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:F5366135-EE7C-4C97-A782-C9A088E0FD96@.microsoft.com...
>I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
> the error in subject when I try to create a database using this statement:
> CREATE DATABASE [ESBMessageTracking] ON PRIMARY
> ( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE
> => 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> LOG ON
> ( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF'
> ,
> SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> COLLATE SQL_Latin1_General_CP1_CI_AS
> GO
> I have confirmed the path is correct. Don't know what is going on. Help
> please.
Did you confirm both PATH*S* are correct? Your MDF is on F: but your LDF is
on E: Next time, it would help if you included the entire error message
so - most people have not memorized the error numbers.|||Scott,
Thanks. I Did confirm both paths exist. Here's the error message:
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "F:\Microsoft SQL
Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF" failed
with the operating system error 1008(An attempt was made to reference a token
that does not exist.).
Msg 1802, Level 16, State 1, Line 1
CREATE DATABASE failed. Some file names listed could not be created. Check
related errors.
What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
server' it does not find the path even though it exists. It is like it
connot deal with the embedded blank.
"Scott Morris" wrote:
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:F5366135-EE7C-4C97-A782-C9A088E0FD96@.microsoft.com...
> >I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
> > the error in subject when I try to create a database using this statement:
> > CREATE DATABASE [ESBMessageTracking] ON PRIMARY
> > ( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
> > Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE
> > => > 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> > LOG ON
> > ( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
> > Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF'
> > ,
> > SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> > COLLATE SQL_Latin1_General_CP1_CI_AS
> > GO
> >
> > I have confirmed the path is correct. Don't know what is going on. Help
> > please.
> Did you confirm both PATH*S* are correct? Your MDF is on F: but your LDF is
> on E: Next time, it would help if you included the entire error message
> so - most people have not memorized the error numbers.
>
>|||"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:EC0C75CA-DF07-42D6-A414-565C1B1EBF79@.microsoft.com...
> Scott,
> Thanks. I Did confirm both paths exist. Here's the error message:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "F:\Microsoft SQL
> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF" failed
> with the operating system error 1008(An attempt was made to reference a
> token
> that does not exist.).
> Msg 1802, Level 16, State 1, Line 1
> CREATE DATABASE failed. Some file names listed could not be created. Check
> related errors.
> What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
> server' it does not find the path even though it exists. It is like it
> connot deal with the embedded blank.
The embedded blank shouldn't be a problem - the log file has one as well.
Apparently you have the exact same path on two different disks, using one
for data and one for logs. A bit strange that these paths appear to be sql
server installation paths - but what do I know.
First, things like this generally mean that there is a security or account
issue. Just because you personally have access to an E or F drive doesn't
mean that sql server and the accounts it uses internally do. Second,
clusters have their own complicated setup - something beyond my experience.
BTW - it appears that you posted this question last month in the cluster NG.
Is this a follow-on? Have you done the same things Geoff recommended?
http://groups.google.com/group/microsoft.public.sqlserver.clustering/browse_thread/thread/63ea092f04d74333/e447afb0ba5e592b?lnk=st&q=&rnum=1&hl=en#e447afb0ba5e592b|||I agree with Scott, in your SQL cluster group, both E:\ and F:\ disks must
have a cluster resource in the same group and SQL Server cluster resource
must depend on both drives in order to use them.
Ayad Shammout
"Scott Morris" <bogus@.bogus.com> wrote in message
news:OCN$M014HHA.600@.TK2MSFTNGP05.phx.gbl...
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:EC0C75CA-DF07-42D6-A414-565C1B1EBF79@.microsoft.com...
>> Scott,
>> Thanks. I Did confirm both paths exist. Here's the error message:
>> Msg 5133, Level 16, State 1, Line 1
>> Directory lookup for the file "F:\Microsoft SQL
>> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF"
>> failed
>> with the operating system error 1008(An attempt was made to reference a
>> token
>> that does not exist.).
>> Msg 1802, Level 16, State 1, Line 1
>> CREATE DATABASE failed. Some file names listed could not be created.
>> Check
>> related errors.
>> What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
>> server' it does not find the path even though it exists. It is like it
>> connot deal with the embedded blank.
> The embedded blank shouldn't be a problem - the log file has one as well.
> Apparently you have the exact same path on two different disks, using one
> for data and one for logs. A bit strange that these paths appear to be
> sql server installation paths - but what do I know.
> First, things like this generally mean that there is a security or account
> issue. Just because you personally have access to an E or F drive doesn't
> mean that sql server and the accounts it uses internally do. Second,
> clusters have their own complicated setup - something beyond my
> experience. BTW - it appears that you posted this question last month in
> the cluster NG. Is this a follow-on? Have you done the same things Geoff
> recommended?
> http://groups.google.com/group/microsoft.public.sqlserver.clustering/browse_thread/thread/63ea092f04d74333/e447afb0ba5e592b?lnk=st&q=&rnum=1&hl=en#e447afb0ba5e592b
>

MsDtsSrvr.ini.xml file configration

Hi All,

How to configure MsDtsSrvr.ini.xml file in a active\active cluster.

Regards, Balaji Thiruvenkataraju

Add the named instances in, as per your previous post which I answered would make sense. Why, are you having a problem?

MSDTC/SQL Server 2000/Windows Server 2003 cluster

Hi
I have to machines (SKADB01 and SKADB02) which are in a Windows 2003
Cluster. The cluster has two groups - one for Microsoft BizTalk Server
2002 and one for SQL Server 2000. The cluster is an actice/passive
cluster, and the SQL Server Group runs on one of the machines and the
BizTalk group runs on the other machine per default. If one machine
should fail, the other will take over for it.
My problem is, that BizTalk only runs if the SQL Server is running on
SKADB02. If I fail SQL Server over to SKADB01, I get errors with DTC.
"Enable Network DTC Access" is enabled on both machines, and in the
BizTalk group, there has been created an MSDTC ressource.
I do not know that much about clustering and DTC. It just seems to me,
that the errormessages point to DTC.
Does anyone have any idea?
Thanks
Jan Eliasen, representing himself and not the company he works for.
If your message is "MSDTC on server [..] is unavailable. Error 5" (access
denied) your problem may be that the MSDTC cluster resource has started after
the SQL Server Instance. This is a known problem.
"Jan Eliasen" wrote:

> Hi
> I have to machines (SKADB01 and SKADB02) which are in a Windows 2003
> Cluster. The cluster has two groups - one for Microsoft BizTalk Server
> 2002 and one for SQL Server 2000. The cluster is an actice/passive
> cluster, and the SQL Server Group runs on one of the machines and the
> BizTalk group runs on the other machine per default. If one machine
> should fail, the other will take over for it.
> My problem is, that BizTalk only runs if the SQL Server is running on
> SKADB02. If I fail SQL Server over to SKADB01, I get errors with DTC.
> "Enable Network DTC Access" is enabled on both machines, and in the
> BizTalk group, there has been created an MSDTC ressource.
> I do not know that much about clustering and DTC. It just seems to me,
> that the errormessages point to DTC.
> Does anyone have any idea?
> Thanks
> --
> Jan Eliasen, representing himself and not the company he works for.
>
|||Hi
That is not the problem I get. All my errormessages come from BizTalk,
which can not get to SQL Server sometimes.
If My BizTalk group is running on one SKADB01 and the SQL SErver group
is running on SKADB02, where should the MSDTC ressource be running?
Does it make a difference?
Jan Eliasen
On Thu, 26 Aug 2004 18:43:04 -0700, "Stephen Strong"
<StephenStrong@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>If your message is "MSDTC on server [..] is unavailable. Error 5" (access
>denied) your problem may be that the MSDTC cluster resource has started after
>the SQL Server Instance. This is a known problem.
>
>"Jan Eliasen" wrote:
Jan Eliasen, representing himself and not the company he works for.
|||MSDTC can run on any node. But Biztalk2002 is not a cluster aware
application and it is a bad idea to use Biztalk in an active/active cluster
with SQL. Biztalk is more of a group aware application. Look in to creating
a server group and addind two servers into the group if you are looking into
scaling biztalk.
"Jan Eliasen" wrote:

> Hi
> That is not the problem I get. All my errormessages come from BizTalk,
> which can not get to SQL Server sometimes.
> If My BizTalk group is running on one SKADB01 and the SQL SErver group
> is running on SKADB02, where should the MSDTC ressource be running?
> Does it make a difference?
> Jan Eliasen
>
> On Thu, 26 Aug 2004 18:43:04 -0700, "Stephen Strong"
> <StephenStrong@.discussions.microsoft.com> wrote:
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>
|||Hi.
Thanks for you answer. We are running BizTalk in an active/passive
cluster - not an active/active cluster.
Jan Eliasen
On Tue, 31 Aug 2004 09:07:04 -0700, "Rony Thomas"
<rony_p_thomas@.hotmail.com> wrote:
[vbcol=seagreen]
>MSDTC can run on any node. But Biztalk2002 is not a cluster aware
>application and it is a bad idea to use Biztalk in an active/active cluster
>with SQL. Biztalk is more of a group aware application. Look in to creating
>a server group and addind two servers into the group if you are looking into
>scaling biztalk.
>"Jan Eliasen" wrote:
Jan Eliasen, representing himself and not the company he works for.
|||i just built on active-active sql cluster for biztalk servers. we have
2 biztalk servers and i plan to use each node for each biztalk server.
in case, one node is down and it can switch to another node. i set up
the DTC and move biztalks' db to the cluster. i always got error of
biztalk for the node which does have DTC.
based on your theory, it looks that my plan does not work. we don't
want group biztalk servers because one is used internally and the
other externally.
how about biztalk 2004?
thanks,
jj
On Tue, 31 Aug 2004 09:07:04 -0700, "Rony Thomas"
<rony_p_thomas@.hotmail.com> wrote:
[vbcol=seagreen]
>MSDTC can run on any node. But Biztalk2002 is not a cluster aware
>application and it is a bad idea to use Biztalk in an active/active cluster
>with SQL. Biztalk is more of a group aware application. Look in to creating
>a server group and addind two servers into the group if you are looking into
>scaling biztalk.
>"Jan Eliasen" wrote:

MSDTC with Windows 2003 Server

I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:

> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,

MSDTC with Windows 2003 Server

I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,
Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:

> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,

MSDTC with Windows 2003 Server

I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,

MSDTC with SQL Server 2000

Hi,
I have a three nodes cluster with Win 2003. On that I have four SQL
intances. MSTDC is installed on the Quorum. When a failover happens, the SQL
groups start before MSDTC and that create a problem with the transactions
after. To assure a good fonctionality I have to restart my SQL Servers (Not
Funny). I can't configure a dependencies betwen groups in Cluster
Administrators.
How can avoid a human intervention so that the services start correctly
while a failover ? I means ... to assure the service MSDTC is up before SQL
instances.
This is a known issue and fixed with Windows Server 2003 SP1. Install SP1 on
both nodes
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
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:6043A12C-0923-4389-977F-C8DCBAADCC28@.microsoft.com...
> Hi,
> I have a three nodes cluster with Win 2003. On that I have four SQL
> intances. MSTDC is installed on the Quorum. When a failover happens, the
> SQL
> groups start before MSDTC and that create a problem with the transactions
> after. To assure a good fonctionality I have to restart my SQL Servers
> (Not
> Funny). I can't configure a dependencies betwen groups in Cluster
> Administrators.
> How can avoid a human intervention so that the services start correctly
> while a failover ? I means ... to assure the service MSDTC is up before
> SQL
> instances.
>
|||Also, it is recommended to build MS DTC resource in a Cluster Group
independent from the Quorum or SQL Server Groups.
You receive error messages when you perform a distributed transaction when
you have a SQL Server 2000 virtual server in a Windows Server 2003 clustered
environment
http://support.microsoft.com/default...b;en-us;889706
How to configure Microsoft Distributed Transaction Coordinator on a Windows
Server 2003 cluster
http://support.microsoft.com/kb/301600/
Sincerely,
Anthony Thomas

"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:uEdLa7EyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> This is a known issue and fixed with Windows Server 2003 SP1. Install SP1
on[vbcol=seagreen]
> both nodes
> 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
>
> "Psa555" <Psa555@.discussions.microsoft.com> wrote in message
> news:6043A12C-0923-4389-977F-C8DCBAADCC28@.microsoft.com...
the[vbcol=seagreen]
transactions
>
|||Thanks ... I read about SP1 for Win2003 and that should fix my problem.
Thanks for the hint ...
Best regard ..
"Rodney R. Fournier [MVP]" a écrit :

> This is a known issue and fixed with Windows Server 2003 SP1. Install SP1 on
> both nodes
> 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
>
> "Psa555" <Psa555@.discussions.microsoft.com> wrote in message
> news:6043A12C-0923-4389-977F-C8DCBAADCC28@.microsoft.com...
>
>
|||That's in our plan to move MSDTC on separate group ...
Thanks ...
Best regard ..
"Anthony Thomas" a écrit :

> Also, it is recommended to build MS DTC resource in a Cluster Group
> independent from the Quorum or SQL Server Groups.
> You receive error messages when you perform a distributed transaction when
> you have a SQL Server 2000 virtual server in a Windows Server 2003 clustered
> environment
> http://support.microsoft.com/default...b;en-us;889706
> How to configure Microsoft Distributed Transaction Coordinator on a Windows
> Server 2003 cluster
> http://support.microsoft.com/kb/301600/
> Sincerely,
>
> Anthony Thomas
>
> --
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:uEdLa7EyFHA.3812@.TK2MSFTNGP09.phx.gbl...
> on
> the
> transactions
>
>

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 after reboot

I have:
w2k3 enterprise server
A/P Cluster
Sql 2000 sp4
All was well until we did a scheduled reboot. Now, DTS packages report that
the MSDTC is not running. I checked the Cluster Admin and services, all is
well.
I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
DNS, ETC. I ran these down and nothing is out of wack.
Any Ideas? Thanks!Hi
Did you try DTCPing? This may help
http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
John
"tbithoney" wrote:
> I have:
> w2k3 enterprise server
> A/P Cluster
> Sql 2000 sp4
> All was well until we did a scheduled reboot. Now, DTS packages report that
> the MSDTC is not running. I checked the Cluster Admin and services, all is
> well.
> I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> DNS, ETC. I ran these down and nothing is out of wack.
> Any Ideas? Thanks!
>|||Apparently, there is a HOTFIX for this issue.
the error is:
Server: Msg 8501, Level 16, State 3
As described in:
http://support.microsoft.com/default.aspx?scid=kb;en-us;889706
Have you tried this before?
"John Bell" wrote:
> Hi
> Did you try DTCPing? This may help
> http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
> John
> "tbithoney" wrote:
> > I have:
> > w2k3 enterprise server
> > A/P Cluster
> > Sql 2000 sp4
> >
> > All was well until we did a scheduled reboot. Now, DTS packages report that
> > the MSDTC is not running. I checked the Cluster Admin and services, all is
> > well.
> >
> > I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> > DNS, ETC. I ran these down and nothing is out of wack.
> >
> > Any Ideas? Thanks!
> >|||Hi
I have not tried this, it would be good practive to try it on a different
system first.
John
"tbithoney" wrote:
> Apparently, there is a HOTFIX for this issue.
> the error is:
> Server: Msg 8501, Level 16, State 3
> As described in:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889706
> Have you tried this before?
>
> "John Bell" wrote:
> > Hi
> >
> > Did you try DTCPing? This may help
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
> >
> > John
> >
> > "tbithoney" wrote:
> >
> > > I have:
> > > w2k3 enterprise server
> > > A/P Cluster
> > > Sql 2000 sp4
> > >
> > > All was well until we did a scheduled reboot. Now, DTS packages report that
> > > the MSDTC is not running. I checked the Cluster Admin and services, all is
> > > well.
> > >
> > > I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> > > DNS, ETC. I ran these down and nothing is out of wack.
> > >
> > > Any Ideas? Thanks!
> > >

MSDTC settings in a cluster.

Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:

> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
[vbcol=seagreen]
> On the node that has control of the MSDTC resource. The cluster service ta
ke
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
>

MSDTC settings in a cluster.

Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
> On the node that has control of the MSDTC resource. The cluster service take
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
> > Hi everyone,
> >
> > I am new to this so any help will be much appreciated.
> >
> > I have a problem running triggers between two SQL servers. I am running
> > Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> > which pointed me to enable MSDTC by checking the Allow Outbound and
> > Allow Inbound checkboxes. My question is where do I set these boxes on
> > the cluster, on the nodes that make up the cluster or on both?
> >
> > Thanks for your help!
> > Eugene.
> >
> >

MSDTC service not starting

I have to install MSDTC on an Active/Passive cluster. I got instructions
from microsoft's website on how to enable MSDTC:
http://support.microsoft.com/kb/817064/
but when I follow the instructions, the service never starts. Even when I
try to start the service manually I am unsuccessful.
P.S. The cluster is being prepared for use by SQL Server 2005, and the DB
files will be stored on a Dell CX300 (SAN)..
Any suggestions on what may have caused this.
OK I got the service to start, but only after killing the cluster (in cluster
admin). Now while this was great at the time, it does not make much sense.
The reason being that anytime the cluster is present after that, the MSDTC
service stops. The new issue I have is that while configuring the MSDTC, I
was unable to create the "Physical Disk" resource (for the MSDTC Group),
because the wizard is unable to see/recognise any drives at all !!. Now I
really need some suggestions...
Can anyone help? It wil be most appreciated.
"iqv1" wrote:

> I have to install MSDTC on an Active/Passive cluster. I got instructions
> from microsoft's website on how to enable MSDTC:
> http://support.microsoft.com/kb/817064/
> but when I follow the instructions, the service never starts. Even when I
> try to start the service manually I am unsuccessful.
> P.S. The cluster is being prepared for use by SQL Server 2005, and the DB
> files will be stored on a Dell CX300 (SAN)..
> Any suggestions on what may have caused this.
|||Thank you very much for your assistance Edwin...
"Edwin vMierlo [MVP]" wrote:

> First of all, you need to properly configure MSDTC in your cluster.
> Exact instructions here : http://support.microsoft.com/kb/301600
> You do not necessarily have to create a seperate group with a seperate disk
> resource, unless you expect heavy usage of the MSDTC.
> It is acceptable to put your MSDTC in the default cluster group, using the
> Quorum disk.
> If you have problems adding disk to your cluster, you might want to try this
> article : http://support.microsoft.com/kb/555312
> Rgds,
> Edwin.
>
> "iqv1" <iqv1@.discussions.microsoft.com> wrote in message
> news:C6706333-DB5E-42AE-9CE0-0999A127BDE8@.microsoft.com...
> cluster
> sense.
> I
> instructions
> I
> DB
>
>

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 Resource in the Cluster Group

Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
It's more a matter of usage and availability. If you use it a lot, even
though its small, it takes it toll on the disk. You would never want MSDTC
to take cycles away from what the quorum is trying to use. As for
availability, what happens if you have a resource failure? By default, the
group is afftected. Putting more things in ANY group, affects the group as a
whole. For the Highest Availability, keep everything separate.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:E91F75E1-1006-4062-8BC7-35D94FD3E77F@.microsoft.com...
> Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
> if
> the MSDTC has its own IP Address and Network Name?
> In my planned multiple instance sql cluster, I can see giving up a
> physical
> disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
> doesn't use tons on disk space, can I put it in the same group as the
> defualt
> instance of SQL, again as long has it has its own IP Address and Network
> Name?

MSDTC resource in a Cluster

I've read and heard some conflicting information about the best method for
setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a and
Windows 2003. 2 node cluster with currently only once instance of MSSQL
with a great chance of growing.
A few questions I have:
Should the resource be in the cluster group or the virtual server group?
What else does it need, ip address, name...?
If it's not yet being used, is it safe to have it on the quorum drive
(currently 1GB RAID1)?
Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
Thanks,
Joseph
Hi,
I've found this paper
http://support.microsoft.com/default...b;en-us;301600
It suggests to put MSDTC in its own group with its storage resource(disk).
On other hand if that is not possible you can put it in a group with disk.
Anyway I would mess with quorum drive, so I would put it in a Virtual Server
group.
Danijel
"Joseph" <Joseph@.discussions.microsoft.com> wrote in message
news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
> I've read and heard some conflicting information about the best method for
> setting up a MSDTC resource in a cluster. I am running MSSQL 2000 SP3a
> and
> Windows 2003. 2 node cluster with currently only once instance of MSSQL
> with a great chance of growing.
> A few questions I have:
> Should the resource be in the cluster group or the virtual server group?
> What else does it need, ip address, name...?
> If it's not yet being used, is it safe to have it on the quorum drive
> (currently 1GB RAID1)?
> Has anyone found a white paper specific to Win2k3, MSSQL2k and MSDTC?
> Thanks,
> Joseph
>
|||The official best practice is "put MSDTC in its own group" but to do that
you will need an extra disk, Network Name and IP Address.
Unless you know you will be hitting MSDTC hard, like in a BizTalk
environment for example then leave it in the cluster group. In the event of
an MSDTC failure the Cluster Group will failover to the passive node. The
only "outage" will be for admin's connected to the Virtual Cluster Name in
Cluster Administrator as the resources are re-started on the new node. It
will not affect any other groups.
Alternatively, if MSDTC was in the SQL Group then a failure would cause a
SQL Server outage. If your application is entirely dependant on MSDTC, this
might be fine but its more likely that you wouldn't want that to happen.
You can set MSDTC to not affect the group but then you don't have the
benefit of failover.
In summary, leave MSDTC in the Cluster Group. It makes sense and we support
it
Christian Bolton
Microsoft
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:nVfFd.8296$F6.1420730@.news.siol.net...
> Hi,
> I've found this paper
> http://support.microsoft.com/default...b;en-us;301600
> It suggests to put MSDTC in its own group with its storage resource(disk).
> On other hand if that is not possible you can put it in a group with disk.
> Anyway I would mess with quorum drive, so I would put it in a Virtual
> Server group.
> Danijel
> "Joseph" <Joseph@.discussions.microsoft.com> wrote in message
> news:OEv$n4M%23EHA.2552@.TK2MSFTNGP09.phx.gbl...
>

MSDTC Required?

I am preparing for the installation of SQL Server 2005 Standard on a
two-node cluster. The SQL Server books Online" topic named "Before
Installing Failover Clustering" indicates that you must install MSDTC if you
are installing the Database Engine and SSIS, Notification Services or
Workstations components. I am not planning on installing SSIS or
Notification Services but would like to install the Workstations components
(specifically SSMS and the other tools) on the clustered nodes.
Is it really necessary to install MSDTC in the cluster if I don't plan on
doing distributed transactions? I want to keep the installation as simple
as possible and don't see why I need to install MSDTC in the cluster with
the Workstation components.
Any help would be appreciated.
Thanks!
Chris
SQL works a lot better with MSDTC. You can go ahead and install it in the
cluster group if you do not have a lot of distributed transactions.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
>I am preparing for the installation of SQL Server 2005 Standard on a
>two-node cluster. The SQL Server books Online" topic named "Before
>Installing Failover Clustering" indicates that you must install MSDTC if
>you are installing the Database Engine and SSIS, Notification Services or
>Workstations components. I am not planning on installing SSIS or
>Notification Services but would like to install the Workstations components
>(specifically SSMS and the other tools) on the clustered nodes.
> Is it really necessary to install MSDTC in the cluster if I don't plan on
> doing distributed transactions? I want to keep the installation as simple
> as possible and don't see why I need to install MSDTC in the cluster with
> the Workstation components.
> Any help would be appreciated.
> Thanks!
> Chris
>
|||Can you clarify "Works a lot better with..."
I always install it as a matter of procedure but if it's not necessary, how
does it help?
"Geoff N. Hiten" wrote:

> SQL works a lot better with MSDTC. You can go ahead and install it in the
> cluster group if you do not have a lot of distributed transactions.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
>
|||SQL tries to initialize a DTS connection when it starts up. When MSDTC is
not there, SQL has to wait for a timeout so you get slower startups and
failovers.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"burt_king" <burt_king@.yahoo.com> wrote in message
news:CA063DB1-C405-44E5-9628-9C10AE5C7630@.microsoft.com...[vbcol=seagreen]
> Can you clarify "Works a lot better with..."
> I always install it as a matter of procedure but if it's not necessary,
> how
> does it help?
>
> "Geoff N. Hiten" wrote:
|||MS DTC is installed on each cluster node as part of the Windows OS
installation. What is required is to make it "clustered."
If you will only be installing a single SQL Server instance, then you can
configure the MS DTC cluster resource to use the same cluster resource group
as the SQL Server installation.
Otherwise, follow the instructions to set up a dedicated cluster resource
group for MS DTC, which will require a dedicated shared cluster disk, IP
address, and Network Name resources.
Do not run MS DTC as a resource in the Quorum cluster resource group.
Sincerely,
Anthony Thomas

"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
> I am preparing for the installation of SQL Server 2005 Standard on a
> two-node cluster. The SQL Server books Online" topic named "Before
> Installing Failover Clustering" indicates that you must install MSDTC if
you
> are installing the Database Engine and SSIS, Notification Services or
> Workstations components. I am not planning on installing SSIS or
> Notification Services but would like to install the Workstations
components
> (specifically SSMS and the other tools) on the clustered nodes.
> Is it really necessary to install MSDTC in the cluster if I don't plan on
> doing distributed transactions? I want to keep the installation as simple
> as possible and don't see why I need to install MSDTC in the cluster with
> the Workstation components.
> Any help would be appreciated.
> Thanks!
> Chris
>
|||What if this were active/active sql 2000 instances. Still one MSDTC?
"Anthony Thomas" wrote:

> MS DTC is installed on each cluster node as part of the Windows OS
> installation. What is required is to make it "clustered."
> If you will only be installing a single SQL Server instance, then you can
> configure the MS DTC cluster resource to use the same cluster resource group
> as the SQL Server installation.
> Otherwise, follow the instructions to set up a dedicated cluster resource
> group for MS DTC, which will require a dedicated shared cluster disk, IP
> address, and Network Name resources.
> Do not run MS DTC as a resource in the Quorum cluster resource group.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
> you
> components
>
>
|||Each cluster can only have a single MSDTC instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"SQLdba" <burt_king@.yahoo.com> wrote in message
news:D7919F72-F753-4232-80CE-DCD52FA271EA@.microsoft.com...[vbcol=seagreen]
> What if this were active/active sql 2000 instances. Still one MSDTC?
>
> "Anthony Thomas" wrote:
|||In which case, the recommended solution is to have a dedicated MS DTC
cluster resource group with dedicated dependencies (Shared Disk, IP Address,
and Network Name).
In times past, Microsoft recommended adding this resource to the Quorum
group; however, it was determined that this was a bad practices because
whenever the quorum goes offline, and DTC handles are destroyed if the two
resources are collocated.
In a dedicated group, even if the quorum group is moved, or the DTC group is
moved, pending DTC transactions and SQL Server handles are maintained.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eKAYYTxaHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Each cluster can only have a single MSDTC instance.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "SQLdba" <burt_king@.yahoo.com> wrote in message
> news:D7919F72-F753-4232-80CE-DCD52FA271EA@.microsoft.com...
can[vbcol=seagreen]
resource[vbcol=seagreen]
IP[vbcol=seagreen]
plan
>
|||Actually, the recommendation was changed based on testing high-volume
systems where certain storage systems could be saturated by the DTC traffic
to the point where the Quorum disk appeared unresponsive, thus causing a
cluster failure. Since Microsoft is officially hardware agnostic, this led
to a blanket recommendation for a dedicated MSDTC group, which later was
modified to apply only to high volume systems.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eZDWpk7aHHA.4140@.TK2MSFTNGP06.phx.gbl...
> In which case, the recommended solution is to have a dedicated MS DTC
> cluster resource group with dedicated dependencies (Shared Disk, IP
> Address,
> and Network Name).
> In times past, Microsoft recommended adding this resource to the Quorum
> group; however, it was determined that this was a bad practices because
> whenever the quorum goes offline, and DTC handles are destroyed if the two
> resources are collocated.
> In a dedicated group, even if the quorum group is moved, or the DTC group
> is
> moved, pending DTC transactions and SQL Server handles are maintained.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eKAYYTxaHHA.3272@.TK2MSFTNGP03.phx.gbl...
> can
> resource
> IP
> plan
>

MSDTC on Windows Server 2003

I am running a sql server 2000 cluster on a windows server 2003
machine. Every time I try to install MSDTC it fails and this is what
is in the Event Viewer:
MS DTC setup failed to populate the shared cluster registry. The DTC
resource will not be able to come online.Error Specifics:
d:\nt\com\complus\dtc\shared\mtxclu\mtxclusetuphel per.cpp:120,
CmdLine: "C:\WINDOWS\cluster\resrcmon.exe" -e 880 -m 884 -p 1204, Pid:
2524
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The Event ID is 4389. The Source is MS DTC Client.
I've clicked on the link and Microsoft "does not have any more
information at this time."
Can anyone tell me what the problem is?
Thanks
JF
Sorry, but you need to install DTC (to W2K3) and MSDTC before installing SQL2K
on a W2K3 Cluster.
Try articles 817064 and 301600.
Gone are the nice days of running comclust.exe (as in W2K) !
Cheers
LM
On 06/05/2004 jf@.uk.com wrote:
>I am running a sql server 2000 cluster on a windows server 2003
>machine. Every time I try to install MSDTC it fails and this is what
>is in the Event Viewer:
>
>MS DTC setup failed to populate the shared cluster registry. The DTC
>resource will not be able to come online.Error Specifics:
>d:\nt\com\complus\dtc\shared\mtxclu\mtxclusetuphe lper.cpp:120,
>CmdLine: "C:\WINDOWS\cluster\resrcmon.exe" -e 880 -m 884 -p 1204, Pid:
>2524
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>
>The Event ID is 4389. The Source is MS DTC Client.
>I've clicked on the link and Microsoft "does not have any more
>information at this time."
>Can anyone tell me what the problem is?
>
>Thanks
>JF
Cheers
LM