Expose Orchestration as WCF Service – Errors – Resolutions

Error 1 :

Receive location for address “/ExposeOrchWCFService/ExposeOrchWCFService_ProcessPO_prtRcvPO.svc” not found. (The BizTalk receive location may be disabled.)

Resolution:

WCF Service Publishing Wizard will create a new Receive location in the application you have specified in the wizard. That receive location need to be enabled.

Error 2:

Cannot open database “BizTalkMgmtDb” requested by the login. The login failed.
Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’.

Resolution:

This happens when you create Orchestration and expose as WCF Service. The WCF Publishing Wizard will create Website in IIS. If newly created application is running under ASP.Net 4.0 Application pool, you will see this error while browsing the .svc file.  All you need to do is to change the Application Pool to WCFHttpAppPool

Error 3:

The requested service, ‘http://localhost/ExposeOrchWCFService/ExposeOrchWCFService_ProcessPO_prtRcvPO.svc’ could not be activated. See the server’s diagnostic trace logs for more information.

Resolution:

Check whether BizTalk Orchestration and application is started.

Leave a comment

TechFindings...by Maheshkumar Tiwari

BizTalk, WCF, ESB ToolKit, Azure, MuleSoft

danrosanova

Middleware, Services, and Integration

Steef-Jan Wiggers Blog

BizTalk, WCF, ESB ToolKit, Azure, MuleSoft

MSDN Magazine (en-us)

BizTalk, WCF, ESB ToolKit, Azure, MuleSoft

Sandro Pereira BizTalk Blog

My notes about BizTalk Server 2004, 2006, 2006 R2, 2009, 2010, 2013 and now also Windows Azure BizTalk Services.

BizTalk Server Monitoring & Management Solution | BizTalk360

BizTalk, WCF, ESB ToolKit, Azure, MuleSoft

Ajay Solanki

BizTalk, WCF, ESB ToolKit, Azure, MuleSoft

Richard Seroter's Architecture Musings

Blog Featuring Code, Thoughts, and Experiences with Software and Services