Microsoft KB Archive/923733

= FIX: You receive an &quot;Import Error&quot; error message when you try to import an .msi file for a BizTalk application =

Article ID: 923733

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Adapter for Oracle Database
 * Microsoft BizTalk Adapter for PeopleSoft Enterprise
 * Microsoft BizTalk Adapter for Siebel eBusiness Applications
 * Microsoft BizTalk Adapter for J.D. Edwards EnterpriseOne
 * Microsoft BizTalk Adapter for J.D. Edwards OneWorld
 * Microsoft BizTalk Adapter for TIBCO Enterprise Message Service
 * Microsoft BizTalk Adapter for TIBCO Rendezvous

-



SYMPTOMS
In Microsoft BizTalk Server 2006, you receive an error message that resembles the following when you try to import an .msi file for a BizTalk application:

TITLE: Import Error

Failed to import &quot; &quot;.

Location of the log file is provided in the Results page.

ADDITIONAL INFORMATION:

Change requests failed for some resources. (mscorlib)

Unable to process create change request for BizTalk binding &quot;BindingInfo.xml&quot;. Import bindings (overwrite) failed. (Microsoft.BizTalk.ResourceManagers)

Failed to update binding information. (mscorlib)

Could not validate configuration of Primary Transport of Send Port ' ' with SSO server.

Specify user name and password (Microsoft.BizTalk.ExplorerOM)

Specify user name and password (Microsoft.BizTalk.ExplorerOM)

This issue occurs when the .msi file includes binding information for any of the Enterprise Application adapters.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
There are no prerequisites to install this hotfix.

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

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

File information
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.

Hotfix installation instructions
Install this hotfix on the computer to which you want to import the .msi file. After you install the hotfix, you must manually register the Microsoft.biztalk.adapters.bizutil.dll file in the Global Assembly Cache. To manually register the Microsoft.biztalk.adapters.bizutil.dll file in the Global Assembly Cache, use the appropriate method.

Method 1: Use the Visual Studio command prompt
If Microsoft Visual Studio is installed, follow these steps to manually register the Microsoft.biztalk.adapters.bizutil.dll file in the Global Assembly Cache:
 * 1) Open a Visual Studio command prompt. To do this, do one of the following:
 * 2) * Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.
 * 3) * Click Start, point to Programs, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.
 * 4) At the Visual Studio command prompt, use the CD command to move to the &quot;Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin&quot; folder.
 * 5) Type gacutil /i Microsoft.BizTalk.Adapters.BizUtil.dll, and then press ENTER.

Method 2: Use the command prompt
If Microsoft Visual Studio is not installed, follow these steps to manually register the Microsoft.biztalk.adapters.bizutil.dll file in the Global Assembly Cache:
 * 1) Click Start, click Run, type cmd, and then click OK.
 * 2) At the command prompt, use the CD command to move to the folder in which the Microsoft .NET Framework 1.1 is installed. For example, type cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322, and then press ENTER.
 * 3) At the command prompt, type gacutil /i &quot; :\Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications\Bin\Microsoft.BizTalk.Adapters.BizUtil.dll&quot;, and then press ENTER.

Note  is the hard disk on which the &quot;Program Files\Common Files\Microsoft BizTalk Adapters for Enterprise Applications&quot; folder is located.



WORKAROUND
To work around this issue, export the BizTalk application and the binding files separately. After you export the binding file, edit the binding file, and then type a password.

Note The password is stored in the binding file as clear text. We recommend that you do not type the actual password in the binding file. After you import the binding file, edit the port configuration in the BizTalk Administration Console, and then type the password that you want to use.



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
When a binding file for an Enterprise Application adapter is exported, the password is inserted into the export file by using asterisks (*). This behavior increases security. However, an Enterprise Application adapter will not validate a port configuration that does not include a valid user name and password. Therefore, you may experience the issue that is described in the &quot;Symptoms&quot; section.

When this issue occurs, you may receive an error message that resembles the following in the log file that is generated when you try to import the .msi file for the BizTalk application:

Import Wizard[3/26/2007 3:53:00 PM]: Error in Importing Application

Import Wizard[3/26/2007 3:53:00 PM]: Change requests failed for some resources.

Unable to process create change request for BizTalk binding &quot;BindingInfo.xml&quot;. Import bindings (overwrite) failed. Failed to update binding information.

Could not validate configuration of Primary Transport of Send Port ' ' with SSO server.

Specify user name and password

Specify user name and password

