There was a failure executing the receive pipeline: Microsoft.BizTalk.DefaultPipelines… failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache

  • Sandro Pereira
  • Apr 24, 2009
  • 2 min read

Sometimes, when we try to test our Visual Studio BizTalk Server solution that we deploy in the BizTalk Server environment, we get the following error message:

There was a failure executing the receive pipeline: Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML disassembler” Receive Port: “Port_Name” URI: Reason: The document specification <Schema_Name> from assembly <Schema_Name, Version=1.0.0.0, Culture=neutral, PublicKeyToken=…> failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache.

📝 One-Minute Brief

This post provides a quick-fix guide for the BizTalk error: “The document specification failed to load. Verify the schema… is deployed and is in the GAC.” The issue typically occurs when the BizTalk Runtime cannot locate the required schema in the Global Assembly Cache (GAC) or the BizTalk Management database. Sandro explains how to resolve this by ensuring the assembly is correctly GAC’ed and that the host instances are restarted to refresh the cache.

Cause

This error may happen for several reasons:

  • The DLL is not deployed in the environment.
  • Or for some reason, there is a misunderstanding by the BizTalk Server engine, which happens from time to time.

Solution

In my case, I was sure, and I validated that the DLL and that particular version were deployed… In these cases, changing the DLL version (for example, 1.0.0.1) and deploying the solution will solve it every time.

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son. 

Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

2 thoughts on “There was a failure executing the receive pipeline: Microsoft.BizTalk.DefaultPipelines… failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache”

  1. i have the same problem but this didin´t solved my problem…
    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: “RP_DB” URI: “C:BizTalk_WorkFolderreceive*.xml” Reason: The document specification from assembly failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache.

    1. There are a couple of things you need to do, when you run into this type of error in your case:
      – redeploy the assemblies (schema’s) you are using, my suggestion is to make a different dll version, and make sure you are restarting all the hosts.
      – In additional, you can stop the application and delete the assemblies from the application and GAC, and then redeploy the new assemblies.
      – use processmonitor or filemon to see where BizTalk is looking for the file can helped you.

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top