I have installed BizTalk Server 2006 R2 on my Windows XP SP3 machine and trying to make the BizTalk WCF Publishing work. Publishing went fine but when I tried to access the service using the url location (recieve port location) I was plagued with errors.

Error  # 1:

Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.

The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC).

 Solution :

1. Go to Event Log  in the Application Logs there should be a warning log about ASP.NET.   Go to process information and get the account name:

Process information:

Process ID: 7472

Process name: aspnet_wp.exe

Account name: {AccountName}           

 2. Open command prompt, then type:

aspnet_regiis -ga {AccountName}

probelem 1 solved.

Error  # 2:

The Messaging Engine failed to register the adapter for “WCF-BasicHttp” for the receive location “/RPaulo/TestService.svc”. Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.

Solution:

Looking at the event log I see that the user account for ASP.NET is trying to connect to BizTalkMgtDb

An attempt to connect to “BizTalkMgmtDb” SQL Server database on server “RPauloBts” failed.

Error: “Login failed for user ‘RPauloBts\ASPNET’.”

Quickest fix is to add the ASPNET account to both BizTalk Application Users and BizTalk Isolated Host Users.

Everything should be ok now.