Friday, 10 February 2012 00:30

What you need to do to fix "There was a failure executing the receive pipeline… failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache" Error after deploying BizTalk Solution

Written by 
Rate this item
(3 votes)

Recently after I deploy a new version of one BizTalk Application in production environment, in order to provide a new service and after having validated all the normal steps of an installation:

  • Check the correctly deployed (in BizTalk Management Console and in the Global Assembly Cache (GAC))
  • Correctly Application Binding
  • Restart Host instances

I keep getting this error:

“There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "IN_PORT" URI: "/MyService.WS/WebService_Provisioning.asmx" Reason: The document specification <Project.Schemas.MyRequest> from assembly <Project, Version=1.0.0.0, Culture=neutral, PublicKeyToken=776eb620b83c3d30> failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache.”

CAUSE

This error can happen for several reasons!!

  • Your DLL was not correctly installed (not installed or missing from GAC).
  • Misunderstanding in framework version that you used.
  • Forgetting to restart services so that it reflects the new changes

SOLUTION

Because this error can happen for several reasons you may have many solutions to this problem. These are some steps that you should take to resolve the issue:

  • Verify if the Assembly is correctly deployed (check if your DLL is in the BizTalk Management Console and in the Global Assembly Cache (GAC)). If the assembly was not found, you need to redeploy correctly the BizTalk Project or run gacutil to install the DLL in GAC.
  • Verify if the Application Pool (in case of Service) is running and correctly configured.
  • Verify the .NET Framework version of the Application Pool. If the application pool is running .NET Framework 2.0 and BizTalk solution is using other version of .NET Framework, at runtime it will not find the Assembly in GAC (.NET Framework version needs to be consistent.). In this case you need to change the .NET Framework version used in the BizTalk projects or change the Framework used in the App Pool.
  • Restart host instances

However, there is another step which usually is not referenced!

If you are using a Request-Response Port, normally using WCF or SOAP adapter, making restart only to Host Instances is not enough. This type of port is running over BizTalkServerIsolatedHost so you need to also restart App Pool associated with your services.

Read 2344 times Last modified on Friday, 10 February 2012 06:53
Tagged under
Sandro Pereira

Sandro Pereira lives in Portugal and works as a BizTalk consultant at DevScope. In the last few years has been working implementing integration scenarios and Cloud Provisioning at a major telecommunications service provider in Portugal. His main focus is on Integration Technologies where is been using .NET, BizTalk and SOAP/XML/XSLT since 2002.

He is an active blogger, member of BizTalk Brazil Community, member and moderator of MSDN BizTalk Server Forums, Code Gallery contributor and was awarded Most Valuable Professional (MVP) for BizTalk Server by Microsoft since 2011. He has certifications for BizTalk Server 2006 and BizTalk Server 2010.

twitterlinkedin

Website: sandroaspbiztalkblog.wordpress.com/

Latest from Sandro Pereira

More in this category: « General network TCP settings that can impact BizTalk Server BizTalk Server: List of available Service Packs and Cumulative Updates »

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.

back to top