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

MSSQL - (2) - 17055

In the Event Log I received next message:
Source: MSSQL
Category: (2)
ID: 17055
17204:
FCB: Open failed: Could not open device <DB path> for virtual device number
(VDN) 1.
I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
database working is OK.
What's the problem?
Michael S. Androsov
EXPOCENTRPerhaps some other process had the file open at that time? Anti-virus or similar?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Michael S. Androsov" <MichaelSAndrosov@.discussions.microsoft.com> wrote in message
news:4EA285B5-9FA9-44B6-9523-1B34397EB4FC@.microsoft.com...
> In the Event Log I received next message:
> Source: MSSQL
> Category: (2)
> ID: 17055
> 17204:
> FCB: Open failed: Could not open device <DB path> for virtual device number
> (VDN) 1.
> I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
> database working is OK.
> What's the problem?
> Michael S. Androsov
> EXPOCENTR
>

MSSQL - (2) - 17055

In the Event Log I received next message:
Source: MSSQL
Category: (2)
ID: 17055
17204:
FCB: Open failed: Could not open device <DB path> for virtual device number
(VDN) 1.
I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
database working is OK.
What's the problem?
Michael S. Androsov
EXPOCENTR
Perhaps some other process had the file open at that time? Anti-virus or similar?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Michael S. Androsov" <MichaelSAndrosov@.discussions.microsoft.com> wrote in message
news:4EA285B5-9FA9-44B6-9523-1B34397EB4FC@.microsoft.com...
> In the Event Log I received next message:
> Source: MSSQL
> Category: (2)
> ID: 17055
> 17204:
> FCB: Open failed: Could not open device <DB path> for virtual device number
> (VDN) 1.
> I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
> database working is OK.
> What's the problem?
> Michael S. Androsov
> EXPOCENTR
>

MSSQL - (2) - 17055

In the Event Log I received next message:
Source: MSSQL
Category: (2)
ID: 17055
17204:
FCB: Open failed: Could not open device <DB path> for virtual device number
(VDN) 1.
I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
database working is OK.
What's the problem?
Michael S. Androsov
EXPOCENTRPerhaps some other process had the file open at that time? Anti-virus or sim
ilar?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Michael S. Androsov" <MichaelSAndrosov@.discussions.microsoft.com> wrote in
message
news:4EA285B5-9FA9-44B6-9523-1B34397EB4FC@.microsoft.com...
> In the Event Log I received next message:
> Source: MSSQL
> Category: (2)
> ID: 17055
> 17204:
> FCB: Open failed: Could not open device <DB path> for virtual device numbe
r
> (VDN) 1.
> I have a SQL Server 2000 (SP3a) on a Windows NT Server 4.0 (SP6a). Now
> database working is OK.
> What's the problem?
> Michael S. Androsov
> EXPOCENTR
>sql

msreplication_queue table growing on subscriber - why

Have a live and standby server and failed over to the standby after (i
thought) using EM to turn off replication.
Now find out that the ms_replication_table on the subscriber is growing -
what have I missed ?
The very least I need to do is remove/delete this table as I now don't have
enough disk space for a backup and currently no tape drive
Suggestions please
Thanks
Luci
I suppose the question is "do you need to send this data back to the
publisher?". If so, then running the queue reader agent will prepare the
table for truncation. If you aren't interested in this data, then you'll need
to drop the subscription. If the publisher is no longer available, then you
can use sp_removedbreplication to remove this table and any other remnants of
replication.
Cheers,
Paul Ibison
|||Thanks for quick reply Paul.
No we don't need this data (we're not replicating at the moment) not
even sure where its coming from as the original live is not in use !
Tried running sp_removedbreplication on the subscriber yesterday but the
transaction log just doubled ( and we have no space).
To stop it growing then, do I just go on the original publisher and just
drop the subscription - presume thats a an option in EM ? or do I have to run
a stored procedure on there ?
Cheers
Luci
"Paul Ibison" wrote:

> I suppose the question is "do you need to send this data back to the
> publisher?". If so, then running the queue reader agent will prepare the
> table for truncation. If you aren't interested in this data, then you'll need
> to drop the subscription. If the publisher is no longer available, then you
> can use sp_removedbreplication to remove this table and any other remnants of
> replication.
> Cheers,
> Paul Ibison
|||Hi Luci,
I was suggesting sp_removedbreplication for the case where the publisher was
not available, but this should still be ok. If you run sp_dropesubscription
on the publisher we should be back to normal. The balooning of the
transaction log on the subscriber is normal when you are deleting so much
data. You might want to backup the log and then shrink it, or if the log is
not required for the backup strategy, you could use simple recovery mode and
then shring the log file.
HTH,
Paul Ibison
|||Thanks again Paul
Plan to do this tonight out of hours tonight, going with your second
suggestion by
putting db in simple mode and trying sp_removedbreplication on the
subscriber first.
Cheers
Luci
PS Glad you answered as I found this forum through your replicationanswers
website Thank you again !
"Paul Ibison" wrote:

> Hi Luci,
> I was suggesting sp_removedbreplication for the case where the publisher was
> not available, but this should still be ok. If you run sp_dropesubscription
> on the publisher we should be back to normal. The balooning of the
> transaction log on the subscriber is normal when you are deleting so much
> data. You might want to backup the log and then shrink it, or if the log is
> not required for the backup strategy, you could use simple recovery mode and
> then shring the log file.
> HTH,
> Paul Ibison
>
|||What I'd probably try is to delete the queue records in batches. The batch
size could be 10000 and each time round the loop you backup the log with
truncate_only set. this way the records will get removed without balooning
the log, and you can drop the subscription at the end...
HTH,
Paul Ibison
|||Hi
Just to let you know we got there in the end.
Ended up truncating the msreplication_queue_table, then tried
sp_removedbreplication again which failed as it couldn't drop tables and the
tempdb couldn't extend. So, manually dropped the tables in question, after
which
the sp_removedbreplication did work. Thank you for your help. Cheers Luci
"Paul Ibison" wrote:

> What I'd probably try is to delete the queue records in batches. The batch
> size could be 10000 and each time round the loop you backup the log with
> truncate_only set. this way the records will get removed without balooning
> the log, and you can drop the subscription at the end...
> HTH,
> Paul Ibison
>

Msmerge_genhistory problems

Hi,
I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
Recently all replications were failed. The error message is :
Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
index 'unc1MSmerge_genhistory'.
I investigated and discovered that the procedure sp_MsMakegeneration is
responsable for produce the error on line:
update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal = @.genguid,
coldate = @.dt where generation = @.gen
The problem is intermittent.
Error: 2601, Severity: 14, State: 3
Has anyone saw the same problem ?
Thanks
Rodrigo Varella
is this applicable?
http://support.microsoft.com/kb/276427/en-us
and how about
http://groups.google.com/group/microsoft.public.sqlserver.replication/msg/6f9a6ad3c148beef?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:B45D4DE6-B2F9-4B0E-BD89-9FF6A6B3DEA7@.microsoft.com...
> Hi,
> I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
> Recently all replications were failed. The error message is :
> Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
> index 'unc1MSmerge_genhistory'.
> I investigated and discovered that the procedure sp_MsMakegeneration is
> responsable for produce the error on line:
> update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal =
> @.genguid,
> coldate = @.dt where generation = @.gen
> The problem is intermittent.
> Error: 2601, Severity: 14, State: 3
> Has anyone saw the same problem ?
> Thanks
> Rodrigo Varella
>
>
|||Hi Hilary,
Thanks about the articles, but I had seem them before. My environment is
SQL 2000 full patched.
Rodrigo Varella
"Hilary Cotter" wrote:

> is this applicable?
> http://support.microsoft.com/kb/276427/en-us
> and how about
> http://groups.google.com/group/microsoft.public.sqlserver.replication/msg/6f9a6ad3c148beef?dmode=source
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
> message news:B45D4DE6-B2F9-4B0E-BD89-9FF6A6B3DEA7@.microsoft.com...
>
>
|||can you reinitialize and redistribute the snapshot to the subscribers?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks about the articles, but I had seem them before. My environment
> is
> SQL 2000 full patched.
> Rodrigo Varella
> "Hilary Cotter" wrote:
|||I also found this - it looks like its from a PSS incident.
http://www.gobrien.net/kb/sox/sox/01/11/28/X700048.txt
It suggests dropping the index.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...[vbcol=seagreen]
> Hi Hilary,
> Thanks about the articles, but I had seem them before. My environment
> is
> SQL 2000 full patched.
> Rodrigo Varella
> "Hilary Cotter" wrote:
|||Hilary,
The procedure solves the problem!
Thank you!
Rodrigo Varella
"Hilary Cotter" wrote:

> I also found this - it looks like its from a PSS incident.
> http://www.gobrien.net/kb/sox/sox/01/11/28/X700048.txt
> It suggests dropping the index.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Rodrigo Varella" <RodrigoVarella@.discussions.microsoft.com> wrote in
> message news:FCB2167B-556B-4642-BE3A-F7513044ACB4@.microsoft.com...
>
>
|||I sometimes get this. I think it happens when you have an unreliable
environment - is this true in your case?. The fix is to run DBCC
DBREINDEX on the affected index.
Rodrigo Varella wrote:
> Hi,
> I have 12 merge replications (1 Pub, 2 Subs) with remote distributor.
> Recently all replications were failed. The error message is :
> Cannot insert duplicate key row in object 'MSmerge_genhistory' with unique
> index 'unc1MSmerge_genhistory'.
> I investigated and discovered that the procedure sp_MsMakegeneration is
> responsable for produce the error on line:
> update dbo.MSmerge_genhistory set guidsrc = @.genguid, guidlocal = @.genguid,
> coldate = @.dt where generation = @.gen
> The problem is intermittent.
> Error: 2601, Severity: 14, State: 3
> Has anyone saw the same problem ?
> Thanks
> Rodrigo Varella
>
>
|||I have more than 3.000 subscriptions and more than 100 publications. We have
used replications since 2000. We reindex all tables every day. I have never
seem this problem before. My enviroment is checked constantly. We discovered
the duplicate row in msmerge_genhistory using the snapshot procedure. I have
no idea the origin of the problem. It happened suddenly.
Rodrigo Varella
"JE" wrote:

> I sometimes get this. I think it happens when you have an unreliable
> environment - is this true in your case?. The fix is to run DBCC
> DBREINDEX on the affected index.
> Rodrigo Varella wrote:
>
|||I'm running inot the same problem, what was snapshot procedure you used to
resolve this? The link referenced is no longer viewable.
Thank you,
Pauly C
"Rodrigo Varella" wrote:
[vbcol=seagreen]
> I have more than 3.000 subscriptions and more than 100 publications. We have
> used replications since 2000. We reindex all tables every day. I have never
> seem this problem before. My enviroment is checked constantly. We discovered
> the duplicate row in msmerge_genhistory using the snapshot procedure. I have
> no idea the origin of the problem. It happened suddenly.
> Rodrigo Varella
> "JE" wrote:

msg18452 login failed

Hi.. all
after I connect sql I got the message "msg 18452 Login failed for user 'tt'. Reason : not associated with trusted sql server connection"
I should fix the problem, how?? please suggest me...
Thanks ppplease check for your server configuration(in Alias tab, what's network libraries used) in Client Network Utility ! is the server name was correct, if the server configuration
was correct may you check with which user you are connected !

may this help !

4ndr3.

Msg 18456

I am getting error message on login as follows:
K:\>isql -U BSCI\ziegelmd
Password:
Msg 18456, Level 14, State 1:
Login failed for user 'BSCI\ziegelmd'.
DB-Library: Login incorrect.
I can login using isqlw, and the test connection via Visual Studio 2003
works. The security is set up for SQL Server and Windows. Starts in system
account. User BSCI\ziegelmd is set up for the master database. I am using
the same password as Windows domain logon. Everything is on XP professional
OS. This problem is stopping me dead in my tracks. Any suggestions would be
highly appreciated.ISQL -E
The -E indicates trusted connection and will use the currently logged on
user's NT credentials.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"dziegel" wrote:
> I am getting error message on login as follows:
> K:\>isql -U BSCI\ziegelmd
> Password:
> Msg 18456, Level 14, State 1:
> Login failed for user 'BSCI\ziegelmd'.
> DB-Library: Login incorrect.
> I can login using isqlw, and the test connection via Visual Studio 2003
> works. The security is set up for SQL Server and Windows. Starts in system
> account. User BSCI\ziegelmd is set up for the master database. I am using
> the same password as Windows domain logon. Everything is on XP professional
> OS. This problem is stopping me dead in my tracks. Any suggestions would be
> highly appreciated.
>

Msg 18456

I am getting error message on login as follows:
K:\>isql -U BSCI\ziegelmd
Password:
Msg 18456, Level 14, State 1:
Login failed for user 'BSCI\ziegelmd'.
DB-Library: Login incorrect.
I can login using isqlw, and the test connection via Visual Studio 2003
works. The security is set up for SQL Server and Windows. Starts in system
account. User BSCI\ziegelmd is set up for the master database. I am using
the same password as Windows domain logon. Everything is on XP professional
OS. This problem is stopping me dead in my tracks. Any suggestions would be
highly appreciated.
ISQL -E
The -E indicates trusted connection and will use the currently logged on
user's NT credentials.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"dziegel" wrote:

> I am getting error message on login as follows:
> K:\>isql -U BSCI\ziegelmd
> Password:
> Msg 18456, Level 14, State 1:
> Login failed for user 'BSCI\ziegelmd'.
> DB-Library: Login incorrect.
> I can login using isqlw, and the test connection via Visual Studio 2003
> works. The security is set up for SQL Server and Windows. Starts in system
> account. User BSCI\ziegelmd is set up for the master database. I am using
> the same password as Windows domain logon. Everything is on XP professional
> OS. This problem is stopping me dead in my tracks. Any suggestions would be
> highly appreciated.
>

Msg 18456

I am getting error message on login as follows:
K:\>isql -U BSCI\ziegelmd
Password:
Msg 18456, Level 14, State 1:
Login failed for user 'BSCI\ziegelmd'.
DB-Library: Login incorrect.
I can login using isqlw, and the test connection via Visual Studio 2003
works. The security is set up for SQL Server and Windows. Starts in system
account. User BSCI\ziegelmd is set up for the master database. I am using
the same password as Windows domain logon. Everything is on XP professional
OS. This problem is stopping me dead in my tracks. Any suggestions would b
e
highly appreciated.ISQL -E
The -E indicates trusted connection and will use the currently logged on
user's NT credentials.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"dziegel" wrote:

> I am getting error message on login as follows:
> K:\>isql -U BSCI\ziegelmd
> Password:
> Msg 18456, Level 14, State 1:
> Login failed for user 'BSCI\ziegelmd'.
> DB-Library: Login incorrect.
> I can login using isqlw, and the test connection via Visual Studio 2003
> works. The security is set up for SQL Server and Windows. Starts in syst
em
> account. User BSCI\ziegelmd is set up for the master database. I am usin
g
> the same password as Windows domain logon. Everything is on XP profession
al
> OS. This problem is stopping me dead in my tracks. Any suggestions would
be
> highly appreciated.
>

msdtssrvr.exe - sql 2005 sp2

Installed sp2 for sql 2005

cannot start msdtssrvr.exe

event viewer returns:

The SQL Server Integration Services service failed to start due to the following error:

The system cannot find the file specified.

I tried to locate the msdtssrvr.exe in C:\Program Files\Microsoft SQL Server\90\DTS\Binn\

I cannot locate the file .

Ron

You need to install SSIS from the installation media. The SSIS service is not installed by default, though I'm surprised you have a service listed for SSIS in the first place.

MSDTS Transaction Failed.

Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/defaul...kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***

MSDTS Transaction Failed.

Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason?
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default...b;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason?
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***

MSDTS Transaction Failed.

Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.developersdex.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default.aspx?scid=kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.developersdex.com ***

MSDTC w/ Oracle 8i EventID=4156

On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
"OracleXaLib"="oraclient8.dll"
"OracleSqlLib"="orasql8.dll"
"OracleOciLib"="oci.dll"
It appeared to fix our problems -- but...
After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
Since making the registry change, 328 of these errors have occurred to date.
Are there any suggestions on how to rectify this problem?
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?
|||below is the likely solution
PRB: MS DTC Event 4156: "Session Idle Timeout Over"
Article ID : 290334
Last Review : February 20, 2002
Revision : 1.0
This article was previously published under Q290334
On this Page
SYMPTOMS
CAUSE
RESOLUTION
REFERENCES
SYMPTOMS
You may see the following entry in the application event log:
String message: Session idle timeout over, tearing down the session.
CAUSE
This message indicates that the connection between a Distributed Transaction Coordinator (DTC) client and Microsoft Distributed Transaction Coordinator (MS DTC) is being torn down due to inactivity.
RESOLUTION
This message is usually just informational and can be ignored. Under normal circumstances, MS DTC tears down inactive connections after 10 minutes of idle time.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
197810 FIX: Upgrading DTC to Close Idle Connections
250987 HOWTO: Reinstall MS DTC for a Nonclustered Windows NT 4.0 Server
279786 HOWTO: Reinstall MS DTC for a Nonclustered Windows 2000 Serve

Quote:

Originally posted by Mirna Da Costa
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?

MSDTC w/ Oracle 8i EventID=4156

On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MT
xOCI registry settings in order to correct the problem of failed ODBC connec
tions to an Oracle 8.1.7 linked server.
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
"OracleXaLib"="oraclient8.dll"
"OracleSqlLib"="orasql8.dll"
"OracleOciLib"="oci.dll"
It appeared to fix our problems -- but...
After doing so, we began getting MSDTC EventID 4156 information events in th
e application log - String message: Session idle timeout over, tearing down
the session.
Since making the registry change, 328 of these errors have occurred to date.
The first one occurred ~2 hours after making the registry change.
OPENQUERY statements to the Oracle server are now intermittently requiring l
ong access times (minutes) that used to take a split second.
Since making the registry change, 328 of these errors have occurred to date.
Are there any suggestions on how to rectify this problem?Hello !!
I have the exact same error message. Did you find any resolution for this '
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\
MTxOCI registry settings in order to correct the problem of failed ODBC conn
ections to an Oracle 8.1.7 linked server.
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in
the application log - String message: Session idle timeout over, tearing do
wn the session.
> Since making the registry change, 328 of these errors have occurred to dat
e. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring
long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to dat
e.
> Are there any suggestions on how to rectify this problem?|||below is the likely solution
PRB: MS DTC Event 4156: "Session Idle Timeout Over"
Article ID : 290334
Last Review : February 20, 2002
Revision : 1.0
This article was previously published under Q290334
On this Page
SYMPTOMS
CAUSE
RESOLUTION
REFERENCES
SYMPTOMS
You may see the following entry in the application event log:
String message: Session idle timeout over, tearing down the session.
CAUSE
This message indicates that the connection between a Distributed
Transaction Coordinator (DTC) client and Microsoft Distributed
Transaction Coordinator (MS DTC) is being torn down due to inactivity.
RESOLUTION
This message is usually just informational and can be ignored. Under
normal circumstances, MS DTC tears down inactive connections after 10
minutes of idle time.
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
197810 FIX: Upgrading DTC to Close Idle Connections
250987 HOWTO: Reinstall MS DTC for a Nonclustered Windows NT 4.0 Server
279786 HOWTO: Reinstall MS DTC for a Nonclustered Windows 2000 Serve
Mirna Da Costa wrote:[vbcol=seagreen]
> *Hello !!
> I have the exact same error message. Did you find any resolution for
> this '
> Mirna.-
>
> "elpepe" wrote:
>
> MSDTC\MTxOCI registry settings in order to correct the problem of
> failed ODBC connections to an Oracle 8.1.7 linked server.
> events in the application log - String message: Session idle timeout
> over, tearing down the session.
> to date. The first one occurred ~2 hours after making the registry
> change.
> requiring long access times (minutes) that used to take a split
> second.
> to date.
acsekar
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message808237.html

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.