I found this page while trying to solve my com+ problem too. The server and Client configuration are also same as mentioned the first post with a small difference.I am using SQL Server 2005. SQLSTATE=24000,Native error=0,msg=Invalid cursor state The failure returned from dtctester is the standard "Invalid cursor state" that I've seen on a variety of MSDN pages: There is the bit about WINS/DNS entries or "Misconfigured network" but I don't really know how to go about checking those. Now, the question is, what else is there? The dtctester fails every time with very ambiguous error information. * wcf transaction code runs fine on my machine if I point it at a local database. * I have rebooted all machines in question after changing dtc security settings * Based on an old blog post from Florin Lazar, I have checked the RestrictRemoteClient registry key and it is set to 0 * security config for dtc on both machines set to allow everything (all check boxes are checked) with No Authentication Required * several other computers in the same domain can run both my wcf transaction code and the dtctester util without problem * I am running winxp sp2 on both client and server In a nutshell, I can't get dtctester utility to work. The problem started while doing some experimenting with the new WCF stuff, but has evolved into a simple client side dtc problem. I am having some trouble with the DTC on a client machine and need help to get it working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |