Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
panthagani
Yak Posting Veteran
58 Posts |
 Posted - 2010-02-09 : 12:14:25
|
| Hello,My application uses distributed transactions to update a subscriber database in a transactional replication setup. The distributed transaction is initiated on the publisher. From the last two days, the following error is observed whenever a distributed transaction is initiated. (I got this by profiling the user actions in the front end and executing one of the RPC calls).DBCC execution completed. If DBCC printed error messages, contact your system administrator.OLE DB provider "SQLNCLI" for linked server "CRMREPORTING" returned message "No transaction is active.".Msg 7391, Level 16, State 2, Line 1The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "CRMREPORTING" was unable to begin a distributed transaction.Checked everything suggested at http://support.microsoft.com/default.aspx?scid=kb;en-us;306212.Still the same. Please advise. Thank you! |
|
|
panthagani
Yak Posting Veteran
58 Posts |
Posted - 2010-02-11 : 06:41:27
|
| I forgot to mention that this is a SQL 2005 cluster. Reinstalled MSDTC. Still the same. The client is considering escalating to Microsoft. Any thing else I need to check before that? Please advise. Thank you. |
 |
|
|
vmenon
Starting Member
17 Posts |
Posted - 2010-02-11 : 07:02:08
|
| The link that you provided does not work.The error provided indicates an issue with MSDTC service on cluster. To troubleshoot at your end, Please can you check this out http://support.microsoft.com/kb/294209/ might be helpful to you.The summary of the article says:This article describes how to rebuild a broken Microsoft Distributed Transaction Coordinator (MSDTC) installation for use with a failover clustered SQL Server installation, and how to move the MSDTC clustered resource to a new group.Microsoft only supports running MSDTC on cluster nodes as a clustered resource. We do not recommend or support running MSDTC in stand-alone mode on a cluster. Using MSDTC as a non-clustered resource on a Windows cluster is problematic. This configuration is problematic because transactions could be orphaned and you may experience data corruption if a cluster failover occurs. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-02-11 : 10:30:11
|
| why are you updating the subscriber? just replicate the changes |
|
|
|
panthagani
Yak Posting Veteran
58 Posts |
Posted - 2010-02-15 : 04:41:00
|
| All, thank you for your advise. The customer decided and escalated to Microsoft and they suggested checking the ports between the MSDTC on the cluster server (publisher) and the MSDTC on the stand alone subscriber. One of the ports (not sure what port they added) has not been added to the firewall. Once this was done, the problem got solved. Thanks again! |
|
|
|
|
|
|
OLE DB provider cannot begin distributed tran