Skip to main content

BizTalk Error The local, cached version of the BizTalk Server group configuration is out of date.

By




When we try to delete BizTalk application or Map from BizTalk Admin console, we might get this type of error and this error might occur on every environment from development machines to production servers.

Error :

"Error while removing application "BT Project name".
Schema referenced by Map ‘BTProject’ has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes."


By Mistake I deployed the BizTalk Map project before the BizTalk schema project. The BizTalk Map project were having reference to BizTalk Schema project. When I tried to delete the deployed BizTalk project it gave me above error.

And every time you refresh BizTalk Admin console you will get the above error.

Solution :
 To fix the  above error you need to manually delete entry from  table bt_mapspec, this table is located inside BizTalkMgmtDB,
You can refer following queries to delete the map

-- Locate the itemId of the map
Select * from bt_mapspec
-- Using the itemId retrieved above delete the map
Delete from bt_mapspec Where itemid = 'itemId_of_map'

Delete from bt_mapspec Where assemblyid = ‘id’

After executing above SQL query, just refresh the BizTalk admin console. It should work now.



Love BizTalk, Think BizTalk!!!
Labels:

Comments

  1. 21cssIndia20 March 2014 at 22:09

    Biztalk Server Online Training - Biztalk Admin Online Training
    http://www.21cssindia.com/courses/biztalk-server-online-training-213.html
    COURSE OUT LINE
    Introductions to Enterprise Application Patterns and BizTalk Server, Understanding BizTalk Framework, Setting up a BizTalk Server Environment, Messaging Architecture, Setting up a BizTalk Server Environment Engine, Business Activity Monitoring, WCF Services Schemas in BizTalk, Transformations in BizTalk, The BizTalk Messaging Engine and Pipelines, Adapters in BizTalk, Orchestrations, Advanced Orchestrations, Integration Patterns in BizTalkBizTalk Rules with BizTalk, Testing BizTalk Artifacts, BizTalk Server Instrumentation, Error Handling, and Deployment,Tracking and Deploying BizTalk Solutions, Monitoring and Maintenance, Administration, BizTalk Server Performance andTuning, BizTalk Tools, BizTalk 2013 Features, ESB Toolkit 2.
    If you are seeking training and support you can reach me on 91-9000444287. contact@21cssindia.com

    ReplyDelete
  2. 21st Century Software Solutions14 May 2014 at 20:29

    Biztalk Admin Online Training - http://www.21cssindia.com/courses/biztalk-admin-online-training-220.html
    Overview - What is Business Process? - Need to Integrate - What is Integration? - Challenges without Integration - Challenges in Business Integration - BizTalk Server - Other Products available in Market - Comparison of BizTalk with Tibco, Web methods & SAP PI - Comparison of BizTalk with SSIS and WPF - Employees to learn at their own pace and maintain control of learning “where, when and how” with boundless access 24/7by 21st Century Software Solutions. contact@21cssindia.com ---- Call Us +919000444287

    ReplyDelete

Post a Comment

Popular posts from this blog

WCF MaxReceivedMessageSize max value in .config

By
MaxReceivedMessageSize parameter in binding config   file:   For max file size in WCF, we need to set following parameter in binding files. <binding name="MyService"        maxReceivedMessageSize="2147483647"        maxBufferSize="2147483647" transferMode="Streamed" >        <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"      maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/> <!-- other binding info here, such as security --> </binding> Max possible size: MaxReceivedMessageSize to 2147483647 (i.e. Int32.MaxValue), which is 2GB For our case, as we are using WsHttpBinding. <wsHttpBinding>         <binding name="wsHttpBindingSettings" maxReceivedMessageSize="2147483647">      ...
Post a Comment
Read more

Deploying Custom Pipeline Component on BizTalk Server (PROD)

By
Deploying Custom Pipeline Component on BizTalk Server: ·         Deploying BizTalk Custom Pipeline Component   on BizTalk Server 2006 or Older Version : To deploy the custom Pipeline component on BizTalk server 2006 or older version. We need to add the Custom Pipeline component in GAC as well as “ C:\Program Files (x86)\Microsoft BizTalk Server 2006\Pipeline Components ” folder.   At design time it will access the Pipeline component dll located in “….. Microsoft   BizTalk Server 2006\Pipeline Components ” folder and show the component in pipeline toolbox. At runtime the BizTalk will use the Custom Pipeline component from GAC. ·         Deploying BizTalk Custom Pipeline Component   on BizTalk Server 2006 R2 or New Version : To deploy the custom Pipeline component on BizTalk server 2006 R2 or later version. We need to add the Custom Pipeline component only in “C:\Pr...
12 comments
Read more

biztalk schema remove ns0 prefix

By
We can remove ns0 prefix simply by set the schema elements property or both elements and attributes properties to be qualified. To do that follow my steps: 1-       Open your schema 2-       Right Click <Schema> and select properties 3-       Use schema property editior and Set [Element FromDefult] to Unqualified , and then set [Attribute FromDefault] to Unqualified if you are using attributes in your schema. After applying the steps above, both XML instances below will be valid: Instance 1 (with ns0) < ns0:Root xmlns:ns0 = " http://RandomBizTalkProject.Schema1 " >   < Field1 > Field1_0 </ Field1 >   < Field2 > Field2_0 </ Field2 > </ ns0:Root > Instance 2 (without ns0) < Root xmlns = " http://RandomBizTalkProject.Schema1 " >   < Field1 > Field1_0 </ Field1 >   < Field2 >...
Post a Comment
Read more