Ok, this is my first crack at Blogging, so here goes. I am in the process of setting up a sandbox environment to replicate our production website for our internal developers to test against in...
See more...
Ok, this is my first crack at Blogging, so here goes. I am in the process of setting up a sandbox environment to replicate our production website for our internal developers to test against in Lab Manger. The workspace consists of the following systems: Domain Controller Accounting DB Server (SQL 2000 SP4) Commerce DB Server (SQL 2000 SP4) CMS DB Server (SQL 2005) Web Server(MS Commerce Server) I most of the setup completed, copies of the production DB's restored to my test systems, my CMS system up and running and i start going through testing the various aspects of the Web Site make sure every thing is working correctly. The web site is coming up as expected, i start to test the commerce piece, on line ordering etc. And i start to go through the purchase process and test the various payment methods. After A day i get the Credit Card's working and so this morning when i get in i start testing PO's Wire transfers Check's etc. To find out that it hangs up every time. I go back and check my MSDTC setting under component services to make sure that i have the correct security set, because we have run into problems in the past with that. I made a few adjustments and tried again, still did not work so i tried rebooting all the machines and that still did not work. I go back and run my DTC ping from the web server back to all my DB Servers to make sure everthing is talking correctly. Sure enough i connect to every server successfully. Try the web site again and sure enough it was broken. I finally try from the DB Servers back to the web server and i get the following information in the MSDTC Log File: ++++++++++++++++++++++++++++++++++++++++++++++ DTCping 1.9 Report for WebServer ++++++++++++++++++++++++++++++++++++++++++++++ RPC server is ready WARNING:the CID values for both test machines are the same while this problem won't stop DTCping test, MSDTC will fail for this 10-12, 11:02:20.443-->RPC server:WebServer received following information: Network Name: WebServer Source Port: 1221 Partner LOG: SQL2000A.log Partner CID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX So after spending some time googling the error i came up with this post that matched the systems i was seeing: bq. In regards to your question on SaveAsOrder, "During the checkout phase of a Commerce Server 2002 Web site, a Microsoft Microsoft Distributed Transaction Coordinator (MSDTC) transaction is used to save the order to the database. This operation is performed by an MSDTC transaction that uses remote procedure call (RPC) communications to connect to the Commerce database to save the orderform." For the complete article information that applies Windows 2000, see kb article Q820987 BUG: Hotfix Q331953 breaks MSDTC functionality for Commerce Server 2000 . The other Commerce Features do not use transactions. With that MSDTC must be working without any errors for SaveAsOrder to work. Now in regards to the error you get using DTCPING, "the CID values for both test machines are the same". This is where it gets tricky. For two reasons, MSDTC is supported by a different group and I know the basics of how MSDTC must work in order for Commerce Server to work properly. Second, I am not sure I understand what you mean by all the machines are on the same cluster. Do you mean same network but different machines? One web server and one database server. As kb article Q306842 mentions "If DTCPing returns an error message similar to the following: * Unexpected: My session guid is same as partner's guid* * check whether the current server has been duplicated or cloned from the* * other server. If so, locate the HKEY_CLASSES_ROOT\CID key in the registry.* Under this key, you may notice more than one GUID. Locate the GUID whose underlying Description key is MSDTC. Note that this GUID is also listed in the DTCPing output window. If the other server has a GUID that is exactly the same for MS DTC in its registry, you must create a new GUID for MS DTC in one of the registries. You can use GuidGen to do this. After you add this new GUID, and also all of its underlying keys to HKEY_CLASSES_ROOT\CID, make sure to delete the old GUID that it is replacing. So in order to try and fix the problem, i did the following: Backuped the Registry on My Web Server Generated a new guid from replaced all instances of the duplicate guid on my web server with the new one. I did not do the SQL server's because i did not want to take the chance of breaking SQL Rebooted the servers Tested the process and what do you know every Thing works just they way it is suppose to. So that leads to this question: When building a configuration in Lab Manager and using the the same template for multiple machines, am i going to see MSDTC errors on future deployments or was this an isolated instance?