次の方法で共有

Handling Issues with the ESB Toolkit 2.0 Samples on 64 Bit Systems

  • [アーティクル]

If you’re trying to install the ESB Toolkit 2.0 samples on a 64 bit environment, then you have likely seen an error similar to the following.

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:07.87
New-Object : Exception calling ".ctor" with "0" argument(s): "Explorer OM is no
t supported in a 64bit process."
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
656 char:19
+     $exp = New-Object  <<<< Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer
Property 'ConnectionString' cannot be found on this object; make sure it exists
and is settable.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
657 char:7
+     $exp.C <<<< onnectionString = $btsConnectionString
Cannot index into a null array.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
658 char:27
+     $app = $exp.Applications[$ <<<< appName]
Application  Microsoft.Practices.ESB  not found
New-Object : Exception calling ".ctor" with "0" argument(s): "Explorer OM is no
t supported in a 64bit process."
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
656 char:19
+     $exp = New-Object  <<<< Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer
Property 'ConnectionString' cannot be found on this object; make sure it exists
and is settable.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
657 char:7
+     $exp.C <<<< onnectionString = $btsConnectionString
Cannot index into a null array.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
658 char:27
+     $app = $exp.Applications[$ <<<< appName]
Application  GlobalBank.ESB  not found
Stopping BizTalk Services
New-Object : Exception calling ".ctor" with "0" argument(s): "Explorer OM is no
t supported in a 64bit process."
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
718 char:19
+     $exp = New-Object  <<<< Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer
Property 'ConnectionString' cannot be found on this object; make sure it exists
and is settable.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
719 char:7
+     $exp.C <<<< onnectionString = $btsConnectionString
Cannot index into a null array.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
720 char:27
+     $app = $exp.Applications[$ <<<< appName]
Cannot index into a null array.
At C:\Projects\Microsoft.Practices.ESB\Source\Install\Scripts\ESBFunctions.ps1:
721 char:36
+     $referenceApp = $exp.Applications[$ <<<< referencedAppName]
Application  GlobalBank.ESB  or  Microsoft.Practices.ESB not found
Microsoft (R) BizTalk Application Deployment Utility Version 3.8.368.0

This is caused by the fact that the install scripts are leveraging BizTalk’s BTSCatalogExplorer Object Model which is only available in 32 bit mode. Don’t worry, you can still install the samples. What you have to do is to manually launch a 32 bit version of the powershell console and then run the powershell script from there. This will allow the script to access the BTSCatalogExplorer OM without problem.

Cheers and keep on BizTalking…

Peter

Comments

  • Anonymous
    June 02, 2010
    To good information.....

  • Anonymous
    January 15, 2015
    Peter, Off this topic, sorry. Could you please post the video for CRM 2011 Integration How to Video #1: BizTalk On-Premise to CRM 2011 one more time. Several individuals have requested it and we will all appreciate it. (Sorry agian to posit my request here). Kind Regards.