Re: Application using MSDTC fails after cluster recovery
- From: "Rodney R. Fournier [MVP]" <rod@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 May 2005 12:29:58 -0500
This sounds like expected behavior, a DTS job is not cluster aware.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Virath" <Virath@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2AD2E60C-D650-4655-8ED9-C98DBAA99739@xxxxxxxxxxxxxxxx
> Well in our scenario the node a fails and both SQL group and MSDTC group
> fails to the surviving node and both come up online. So from the
> clustering
> stand point all is cool. However the DTS jobs fails and times out. We
> have
> DTS jobs from within SQL and also connections from BizTalk utilitizing the
> MSDTC stuff.
>
> The job errors out with this error code:
>
> Executed as user: Domain\account. DTSRun: Loading... DTSRun:
> Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun
> OnError:
> DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14) Error
> string: MSDTC on server Cluster VIP\Instance' is unavailable. Error
> source: Microsoft OLE DB Provider for SQL Server Help file:
> Help
> context: 0 Error Detail Records: Error: -2147217900
> (80040E14);
> Provider Error: 8501 (2135) Error string: MSDTC on server
> 'EBCS-HUBCL\HUB' is unavailable. Error source: Microsoft OLE DB
> Provider for SQL Server Help file: Help context: 0
> Error: -2147217900 (80040E14); Provider Error: 0 (0) Error string:
> Rows Selected 28 Error source: Microsoft OLE DB Provider for SQL
> Server
> Help file: Help context: 0 Error: -2147217900
> (80040E14); Provider Error: 0 (0) Error string: WHERE
> WCSUTCInserted
> BETWEEN '2005-04-24 04:14:26.403' AND '2005-04-25 04:14:26.403
>
> Even after the cluster has failed over and we manually fail the groups
> over,
> the jobs would error out. We just do fail the groups back and forth a few
> times. Which is not good.
>
> Thanks,
> Virath
> Tallan, Inc.
>
>
>
> "Rodney R. Fournier [MVP]" wrote:
>
>> I found that you HAVE to move the MSDTC group first, making sure it is
>> online, BEFORE you move the SQL group. MSDTC has to come up first. Have
>> you
>> tried that?
>>
>> Cheers,
>>
>> Rod
>>
>> MVP - Windows Server - Clustering
>> http://www.nw-america.com - Clustering Website
>> http://msmvps.com/clustering - Blog
>>
>> "Virath" <Virath@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:C5B75D14-F06D-4059-9FB9-488AA20CD2CE@xxxxxxxxxxxxxxxx
>> > Environment:
>> > Windows 20003 with SQL 2000 SP3 Active/Active/Passive Cluster
>> > MSDTC is in its own group and its won drive
>> >
>> >
>> > Issue:
>> > We use DTC packages to move SQL data. Every time we failover the
>> > cluster
>> > to
>> > a surviving node our DBA's DTS package fails even though the MSDTC
>> > group
>> > comes back on line just fine. This also effects our BizTalk 2004
>> > servers
>> > using MSDTC.
>> >
>> > Our current workaround is to stop all job's using MSDTC and then
>> > failing
>> > the
>> > MSDTC back and forth until the application works over MSDTC again.
>> >
>> > Has anyone else seen this?
>> > Is this a BizTalk thing?
>> > MSDTC thing?
>> >
>> > Any help would greatly be appreciated.
>> >
>> >
>> > Thank you,
>> > Virath Sem
>> > Tallan.com
>>
>>
>>
.
- References:
- Application using MSDTC fails after cluster recovery
- From: Virath
- Re: Application using MSDTC fails after cluster recovery
- From: Rodney R. Fournier [MVP]
- Re: Application using MSDTC fails after cluster recovery
- From: Virath
- Application using MSDTC fails after cluster recovery
- Prev by Date: Re: Application using MSDTC fails after cluster recovery
- Next by Date: Shared Disk
- Previous by thread: Re: Application using MSDTC fails after cluster recovery
- Next by thread: Cluster group doesn't come back online after network failure
- Index(es):
Relevant Pages
|
