Configuring BizTalk Server 2009 runtime failed on windows server 2008 machine. MSDTC related issue.

Dear all,

I am getting error while congfiguring BizTalk Runtime on our test server(Windows 2008 Server). Its a multiple server installation ( 1. Domain controller 2. BizTalk Server 2009 3. SQL Server 2008) and for all operating system is Windows Server 2008. BizTalk Group and SSO are configured successfully but while configuring BizTalk runtime it showing an error in the log file as.. “New transaction cannot enlist in specified transaction coordinator”. I already done lots of modification related to MSDTC to make sure its functionality. But same error persists.. After that I used the DTCTester.exe tool to check the DTC between BizTalk machine and SQL Server machine. This tool showing an error as ” New transaction cannot enlist in specified transaction coordinator”. While troubleshooting this i followed the stpes mentioned in(http://support.microsoft.com/default.aspx?scid=kb;en-us;306843). and did following modification in the registry

 ——————————————————————————————————————————————————————————————————–

Configure both servers so that MS DTC communication flows between the firewall. Follow these steps to control RPC dynamic port allocation. Note You must follow these steps on both computers. Note The firewall must be open in both directions for the specified ports. To start Registry Editor, click Start, click Run, type regedt32, and then click OK. You must use the Regedt32.exe file instead of the Regedit.exe file. The Regedit.exe file does not support the REG_MULTI_SZ data type that is required for the Ports value. In Registry Editor, expand the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc Click the RPC folder, and then click Add Key on the Edit menu. In the Add Key dialog box, type Internet in the Key Name box, and then click OK. Click the Internet folder, and then click Add Value on the Edit menu. In the Add Value dialog box, type Ports in the Value Name box. In the Data Type box, select REG_MULTI_SZ, and then click OK. In the Multi-String Editor dialog box, specify the port or ports that you want RPC to use for dynamic port allocation in the Data box, and then click OK. Each string value that you type specifies either a single port or an inclusive range of ports. For example, to open port 5000, specify “5000”. To open port 5000 to port 5020 inclusive, specify “5000-5020”. You can specify multiple ports or ports ranges by specifying one port or port range per line. All ports must be in the range of 1024 to 65535. If any port is outside this range or if any string is invalid, RPC treats the whole configuration as invalid. We recommend that you open ports from 5000 and higher, and that you open a minimum of 15 to 20 ports. Follow step e through step h to add another key. Use the following values: Value: PortsInternetAvailable Data type: REG_SZ Data: Y This signifies that the ports that are listed under the Ports value are to be made Internet-available. Configure your firewall to allow for incoming access to the specified dynamic ports and to port 135 (the RPC Endpoint Mapper port). Restart the computer. After RPC restarts, it assigns incoming ports dynamically, based on the registry values that you have specified. For example, to open ports 5000 through 5020 inclusive, create the following named values: Ports : REG_MULTI-SZ : 5100-5200 PortsInternetAvailable : REG_SZ : Y UseInternetPorts : REG_SZ : Y DTC also requires that you can resolve computer names by using NetBIOS or DNS. You can test whether NetBIOS can resolve the names by using the PING protocol and the server name. The client computer must be able to resolve the name of the server. Additionally, the server must be able to resolve the name of the client. If NetBIOS cannot resolve the names, you can add entries to the Lmhosts files on the computers.

—————————————————————————————————————————————————————————————————

After doing the above change in the registry of both the machine. I tried to test again with the DTCTester tool. Now it showing following error—– “The partner transaction manager has disabled its support for remote/network transactions”. I

 already done changes in MSDTC for many times and restarted the machine. but no luck.

I am stucked on this problem for more than 8 hours…………. Reqesting to all of you…… please help me to resolve this issue.

Thanks & Regards,

Abhijit