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 |
|
schwizzla
Starting Member
3 Posts |
 Posted - 2007-11-14 : 05:33:12
|
| Transactional updateable not working in a Vitual Environment. Subscriber cannot update Publisher I have it working in LIVE but not UAT (the only differnce being that UAT is virtual) Hi I have One Publisher and Two Subscribers set up on three virtual SQL Servers on a UAT environment.I cannot apply an update at the subscriber and I am getting the errorServer: Msg 7391, Level 16, State 1, Line 5The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].I have tried check the DTC security settings, service setting, domain account permissions, SQL permissions, Remote Server configurations are exaclty as they are in LIVE. The subscribers are authenticating using sa and the sa account password is the same on all three servers. The Service accounts also have access on all three servers.The only difference is that UAT is on virtual servers and the LIVE is on physical hardware.Has anyone come accross probelmes setting up TU on Virtual servers. I am just wondering whether there are any additonal setting on the virtual Server configuration that may affect distributed transactions.Thanks in advanceSiz |
|
|
schwizzla
Starting Member
3 Posts |
Posted - 2007-11-14 : 10:24:21
|
| I have sorted this now. Turns out the follwing error was occuringThe local MS DTC detected that the MS DTC on CISQHSSQLT008V has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration informationSomething to bear in mind when working on Virtual SQL Servers |
 |
|
|
|
|
|
Transactional updateable not working