Microsoft KB Archive/939920

= FIX: Error message when you try to generate a schema for an adapter in BizTalk Server 2006: &quot;Error reading WSDL file.[System.InvalidOperationException] There is an error in XML document (190, 41).[System.Xml.XmlException]&quot; =

Article ID: 939920

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Standard Edition
 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 R2 Standard Edition
 * Microsoft BizTalk Server 2006 R2 Developer Edition
 * Microsoft BizTalk Server 2006 R2 Enterprise Edition
 * Microsoft BizTalk Server 2006 R2 Branch Edition
 * Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne
 * Microsoft BizTalk Adapter for J.D. Edwards OneWorld
 * Microsoft BizTalk Adapter for Siebel eBusiness Applications

-



SYMPTOMS
In Microsoft BizTalk Server 2006, you try to generate a schema at design time for one of the following adapters:
 * Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne
 * Microsoft BizTalk Adapter for J.D. Edwards OneWorld
 * Microsoft BizTalk Adapter for Siebel eBusiness Applications

When you do this, the schema generation fails. When this problem occurs, you receive the following error messages:

Error message 1

--

Microsoft.BizTalk.Adapter.Framework.CannotProceedException

--

Error reading WSDL file.[System.InvalidOperationException] There is an error in XML document (190, 41).[System.Xml.XmlException]

Name cannot begin with the '=' character, hexadecimal value 0x3D. Line 190, position 41.

---

OK

---

Error message 2

---

System.Runtime.InteropServices.COMException

---

An error occurred during wizard execution.Cannot find file &quot;C:\Lab\BizTalk Orchestration_1.odx&quot;.

---

OK

---



CAUSE
This problem occurs because some XML characters are not allowed as a part of a field name for the schema or as a part of an element name for the schema in BizTalk Server 2006. For example, the following XML characters are not allowed:
 * &quot;
 * ]
 * &quot;
 * ]
 * &quot;
 * ]
 * &quot;
 * ]
 * ]
 * ]



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server 2006 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You must have BizTalk Server 2006 installed to apply this hotfix.

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The 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.

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.



WORKAROUND
To work around this problem, change the field name for the schema or the element name for the schema on the server. Change the name so that the name no longer contains these XML characters.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB939920

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.