Article ID: 938567 - Last Review: October 18, 2007 - Revision: 1.3 FIX: Error message when you publish an orchestration that is converted from a BizTalk Server 2004 project in BizTalk Server 2006: Failed to create project
On This PageSYMPTOMSWhen you publish an orchestration from a Microsoft BizTalk Server 2004 project as a Web service on a computer that is running Microsoft BizTalk Server 2006, you receive the following error message: Failed to create project
http://localhost/MicrosoftTest. Failed to construct code for schema "". Object reference not set to an instance of an object. Object reference not set to an instance of an object. The error message does not occur when you publish the same orchestration in BizTalk Server 2004. CAUSEThe issue occurs because the null target namespace property
is allowed in BizTalk Server 2004. The null target namespace property is not
allowed in BizTalk Server 2006. When you convert a project that includes an
orchestration from BizTalk Server 2004, the target namespace property
in schemas may be null. Therefore, when you publish the orchestration as a Web
service on the BizTalk Server 2006 server, the Web publishing wizard may fail
because of a null namespace reference that is caused by the null target namespace
property in schemas. WORKAROUNDTo work around this issue, add the target namespace property
to the schemas manually before you publish the orchestration as a Web
service. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesYou must have the Microsoft BizTalk Server 2006 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. | Article Translations
|
Back to the top
