An error occured while trying to connect to the TPM Management Web Service

February 28, 2007   12:09


While adding my BizTalk Server with the Business Activity Services Portal I received the error message “Cannot display BizTalk Hosts. An error occurred while trying to connect to the TPM Management Web Service. Contact your administrator for more information.”

After some investigation I found out that the web service was not responding. Some general info on the web about the message “Service Unavailable” indicated that the security rights where not correctly setup. O boy. Security rights and user management is not my middle name. I always make a mess of that.

Error in the TPM Management Web Service

After my installation I changed the user password of the user account that runs the TpmWSAppPool in IIS. Fixing the Password under the Identity tab in the TpmWSAppPool solved the first part of the problem. But now I experienced a new error message.

“Could not create Windows user token from the credentials specified in the config file. Error from the operating system ‘Logon failure: unknown user name or bad password.” Again some problems with user rights. In the web.config of the web service I changed the line

“<identity impersonate=’true’ username = ‘registry: HKLM\SOFTWARE\Microsoft\BizTalk Server\3.0\TPMgmtWS\identity\ASPNET_SETREG,userName’ password = ‘registry: HKLM\SOFTWARE\Microsoft\BizTalk Server\3.0\TPMgmtWS\identity\ASPNET_SETREG,password’/>” to “<identity impersonate = ‘false’ username = ” password=”/>” because my ASPNET user already has administrative privliges. And now it works! Case closed.

Of course only change these settings at your development PC so you can quickly continue the development. You will probably be killed by some IT administrator if you configure it like this in production. If someone has instructions to configure this in a correct way, let me know.

Tags: , , , , , , .









The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.