An error occured while trying to connect to the TPM Management Web ServiceFebruary 28, 2007 12:09While 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.
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
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. I received the following error in the group hub while testing the solution build in Microsoft tutorial 3, lesson 3: “Failed while creating a B2BOrchestrations.B2BProcess service” After 30 minutes I finally found the solution. BizTalk does not refresh the new deployment automatically. You should first restart the BizTalkServerApplication Host instance from the “Platform Settings – Host Instances” node in the BizTalk Server 2006 Administration Console. If that did not do the trick, you can also try to remove the orchestration from the GAC, redeploy it and then refresh the BizTalkServerApplication Host instance. Now I still have to solve some issue with dehydrated orchestrations. I guess my web service is not sending out the required acknowledgement |
||