Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You may receive an unhandled exception error message when you try to consume a BizTalk Web service in BizTalk Server 2006 or in BizTalk Server 2004

You may receive an unhandled exception error message when you try to consume a BizTalk Web service in BizTalk Server 2006 or in BizTalk Server 2004

View products that this article applies to.

Symptoms

In Microsoft BizTalk Server 2006 or in Microsoft BizTalk Server 2004, when you try to consume a BizTalk Web service from the client application, you may receive an unhandled exception error message that is similar to one of the following:
Error message 1
An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll
Additional information: Server was unable to process request. --> File or assembly name PP5dap.dll, or one of its dependencies, was not found.
Error message 2
SOAP Fault: [Receiver]: Server was unable to process request. ---> Unable to generate a temporary class (result=1). error CS0029: Cannot implicitly convert type 'string' to 'string[]'
If you enabled the compile time XmlSerialization.Compilation switch in the Web.config file, you may receive an error message that is similar to the following:
vax07a.0.cs(219,125): error CS0030: Cannot convert type 'string[]' to 'string'
vax07a.0.cs(715,147): error CS0029: Cannot implicitly convert type 'string' to 'string[]'

↑ Back to the top

Cause

This problem occurs when the BizTalk Web Services Publishing Wizard uses the Web Services Description Language Tool (Wsdl.exe) to generate the client information. When you publish a schema that contains nested nodes that have the maxOccurs attribute set to the "unbounded" value, the Wsdl.exe tool creates multidimensional arrays in the generated datatypes.cs file. Therefore, the generated datatypes.cs file contains incorrect types for the nested nodes.

For example, in the generated datatypes.cs file, you notice generated data type declaration statements that are similar to the following. 
...
public class yourSchema
    {
     
        /// <remarks/>
        [System.Xml.Serialization.XmlElementAttribute("TextValue")]
        public string[] TextValue;
        
        /// <remarks/>
        [System.Xml.Serialization.XmlElementAttribute("NumValue")]
        public string[] NumValue;
        
       ....
    }
....
Note In this example, the data types are incorrectly declared as multidimensional arrays.

↑ Back to the top

Workaround

To work around this problem, modify the datatypes.cs file that is generated by the BizTalk Web Services Publishing Wizard by removing the bracket ([ ]) array characters from the data type declaration statements.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

For more information about the BizTalk Web Services Publishign Wizard in BizTalk Server 2006, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa578703.aspx
For more information about the BizTalk Web Services Publishing Wizard in BizTalk Server 2004, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms946997.aspx
For more information about how to enable the XmlSerialization.Compilation switch, click the following article number to view the article in the Microsoft Knowledge Base:
823196 You receive a "System.IO.FileNotFoundException" error when the client application calls a Web service

↑ Back to the top

Keywords: kbbiztalk2004sp2fix, kbtshoot, kbnofix, kbbug, kbprb, KB891386

↑ Back to the top

Article Info
Article ID : 891386
Revision : 5
Created on : 8/7/2007
Published on : 8/7/2007
Exists online : False
Views : 483