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

MsDtsSrvr.ini.xml

Does anyone have a copy of this file from a clustered SQL2005 box with SSIS running? I would to see what you have. I cannot seem to get mine to work.

Thanks David

Hi, you probably already have read this, but just to make sure, the following article on clustering, steps 9-14 deal with the config file.

http://msdn2.microsoft.com/en-us/library/ms345193.aspx

If that does not help the some more info is likely needed such as, are you getting any errors? If so, then what? If not then perhaps posting the acutal contents might be good.

Hope that helps.

|||Thanks to all that replied. I have resolved this issue. I had set the registry entry (that tells SSIS where config file resides) one of my nodes on the cluster and not the other..

MSDTC fails on Windows 2003 but security has been reset so its not that.

I am running SQL Server 2000 (clustered server) with Windows 2003. For some reason MSDTC is failing on distributed transactions. I can run code that begins and commits a transaction from query analyzer, or run a stored procedure from Query Analyzer with the same code in it and both work great, but if I call the stored procedure from a DTS job, then the job fails with the following error:

DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14) Error string: The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. Error source: ..... Error string: OLE DB error trace [OLE/DB Provider 'MSDASQL' ITransactionJoin::JoinTransaction returned 0x8004d00a]. Error source: Microsoft OLE DB Provider for SQL Serve. The step failed.

Any help would be appreciated!Ensure MSDTC is started on the machine.
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3451 for your reference.

MSDTC and SQL2000 clustered

Hi,

I'm in doubt about an installation of SQL Server 2000 (single istance hot standby) on a Win2000 Advanced Server 2 nodes cluster (2 processors per node).

I suppose MSDTC was not activated during SQL2000 setup.

Is it absolutely necessary?
Can I have problems?

In what case is it necessary?

Many thanks?Originally posted by nisant
Hi,

I'm in doubt about an installation of SQL Server 2000 (single istance hot standby) on a Win2000 Advanced Server 2 nodes cluster (2 processors per node).

I suppose MSDTC was not activated during SQL2000 setup.

Is it absolutely necessary?
Can I have problems?

In what case is it necessary?

Many thanks?

I had a problem in an active\active failover installation. MSDTC was not configured and was causing problems with the fail over function. Once I configured it as a shared resource, everything seemed fine. Hope this helps...|||True, make sure MSDTC has been started and working whenever any distributed transactions are in process.

For information refer to DB journal (http://www.databasejournal.com/features/mssql/article.php/1690901) article.

MSDTC across different Windows versions

Hi there.
I have a MS Distributed Transaction Coordinator qestion which doesnt involve
a clustered setup at all. I know this may not technically be the correct
forum but I've solved other MSDTC issues here before so I was hoping...!
Do you know whether any problems should be anticipated with distributed
transactions if a series of linked or remote servers were set up on machines
with different operating systems? I'm about to set up a system with 2
machines on Winows2003 and one on Windows NT => I just want to know whether
it's possible to get a distributed transaction to run ok across all 3
servers...
Any info would be appreciated!
The same protocols are used; however, technically, DTC did not come around
until Win2K. For NT 4, it was Option Pack and MTS. So, there could be some
compatibility issues there.
However, the SQL Server BEGIN DISTRIBUTED TRANSACTION is the same.
Best I can say is Test, Test, Test.
Sincerely,
Anthony Thomas

"len" <len@.discussions.microsoft.com> wrote in message
news:E31BBA8A-F9CA-4BB2-B286-29B1062030B6@.microsoft.com...
> Hi there.
> I have a MS Distributed Transaction Coordinator qestion which doesnt
involve
> a clustered setup at all. I know this may not technically be the correct
> forum but I've solved other MSDTC issues here before so I was hoping...!
> Do you know whether any problems should be anticipated with distributed
> transactions if a series of linked or remote servers were set up on
machines
> with different operating systems? I'm about to set up a system with 2
> machines on Winows2003 and one on Windows NT => I just want to know
whether
> it's possible to get a distributed transaction to run ok across all 3
> servers...
> Any info would be appreciated!
>

MSDTC - running but not available - RPC error?

Hi there.
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:

> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support