Article ID: 2673264 - View products that this article applies to.
Consider the following scenario:
Change requests failed for some resources. (Microsoft.BizTalk.ApplicationDeployment.Engine)
BizTalkAssemblyResourceManager failed to complete end type change request. (Microsoft.BizTalk.ResourceManagers)
Failed to deploy map "<Map name>".
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present. (Microsoft.BizTalk.Deployment)
Note The issue also occurs in BizTalk Server 2009.
This issue occurs because BizTalk tries to deploy the MAPPER_ASSEMBLY assembly before the SCHEMA_ASSEMBLY assembly. However, the MAPPER_ASSEMBLY assembly uses schemas in the SCHEMA_ASSEMBLY assembly.
Cumulative update information
BizTalk Server 2009The hotfix that resolves this issue is included in cumulative update package 7 for BizTalk Server 2009.
For more information about how to obtain the cumulative update package, see Cumulative update package 7 for BizTalk Server 2009
BizTalk Server 2010The hotfix that resolves this issue is included in cumulative update package 4 for BizTalk Server 2010.
For more information about how to obtain the cumulative update package, see Cumulative update package 4 for BizTalk Server 2010
Important To resolve this issue, install this hotfix on the Visual Studio machine and rebuild the mapper or schema DLL that was failing to deploy. Deployment will be successful with the new mapper or schema DLL.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For information about the service packs and cumulative update list for BizTalk Server, see Service pack and cumulative update list for BizTalk Server
For more information about BizTalk hotfixes and service packs support, see Information about BizTalk hotfixes and service pack support
Article ID: 2673264 - Last Review: December 1, 2014 - Revision: 5.0