none
issue with ESB Management Portal (ESB Toolkit 2.4 Installation) on BizTlk 2016 RRS feed

  • Question

  • I have followed all below steps in installation ESB Toolkit 2.4 but still I am not able to access ESB Management portal (http://localhost/ESB.Portal). What is different that I am doing ?
    For Management Portal you can follow below steps:

    1. Download and install Enterprise Library 5.0 from http://www.microsoft.com/en-us/download/details.aspx?id=15104
    2. Download and install Microsoft Report Viewer Redistributable 2008  fromhttp://www.microsoft.com/en-us/download/details.aspx?id=577
    3. In Visual Studio 2012, open ESB.Portal.sln found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
    4. When Visual Studio 2012 starts converting the solution to the current format, a dialog pops up that warns you about ESB.Portal.Setup.vdproj file not being supported in Visual Studio 2012. Click OK. Wait until the solution opens.
    5. In the Solution Explorer add Microsoft.Practices.ServiceLocation.dll as a reference to theESB.BAM.Service.Implementation project. This assembly is found in C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
    6. Open web.config file found in ESB.Portal project and remove (or comment out) "scripting"sectionGroup declaration that starts at line 12 and ends at line 20.
    7. Save all files in the solution.
    8. Rebuild ESB.Portal solution.
    9. Close Visual Studio.

    RH

    Monday, July 29, 2019 9:42 PM

All replies

  • I rebuild the ESB.Portal. sln and it got rebuild successfully.

    When I run the Management_Install.cmd as an Administrator i am receiving follow error :

    C:\Windows\system32>powershell .\Management_Install.ps1 "'Default Web Site'"
    .\Management_Install.ps1 : The term '.\Management_Install.ps1' is not recognized as the name of a cmdlet, function,
    script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
    correct and try again.
    At line:1 char:1
    + .\Management_Install.ps1 'Default Web Site'
    + ~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (.\Management_Install.ps1:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException


    C:\Windows\system32>pause
    Press any key to continue . . .

    Please advise


    RH

    Tuesday, July 30, 2019 3:56 PM
  • No one has worked on installing ESB Toolkit 2.4 on BizTalk 2016 server ?

    If anyone has done it please advise, I am stuck. Not able to access ESB Exception Management Portal


    RH

    Monday, August 5, 2019 12:35 AM
  • Is that PowerShell script sitting under C:\Windows\system32 ?

    Note, that if you run as an Administrator the current working directory can change, which is why you may be getting that error.  

    Monday, August 5, 2019 1:34 AM
  • so under which folder does Powershell script be ? for me to have the ESB Exception Management portal browsable ?

    Please advise


    RH

    Monday, August 5, 2019 1:43 AM
  • What happens if you try to run the Powershell scripts without escalating yourself as Admin?
    Monday, August 5, 2019 1:45 AM
  • Additionally when I run the Management_Install.cmd  (tried both as Admin mode and non admin mode)....receiving following errors :

    C:\Projects\Microsoft.Practises.ESB\Source\Samples\Management Portal\ESB.Portal\ESB.Portal.sln" (Rebuild target) (1) -
    >
    "C:\Projects\Microsoft.Practises.ESB\Source\Samples\Management Portal\ESB.Exceptions.Service\ESB.Exceptions.Service\ESB
    .Exceptions.Service.csproj" (Rebuild target) (5) ->
      C:\Projects\Microsoft.Practises.ESB\Source\Samples\Management Portal\ESB.Exceptions.Service\ESB.Exceptions.Service\ES
    B.Exceptions.Service.csproj(92,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\Visual
    Studio\v11.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the path in the <Import> dec
    laration is correct, and that the file exists on disk.

    New-Item : Cannot find drive. A drive with the name 'IIS' does not exist.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:231 char:17
    +         $pool = New-Item $appPoolPath
    +                 ~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (IIS:String) [New-Item], DriveNotFoundException
        + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.NewItemCommand

    The property 'identityType' cannot be found on this object. Verify that the property exists and can be set.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:233 char:9
    +         $pool.processModel.identityType = $identityType
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : PropertyNotFound

    The property 'managedPipelineMode' cannot be found on this object. Verify that the property exists and can be set.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:242 char:9
    +         $pool.managedPipelineMode = 0
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : PropertyNotFound

    The property 'managedRuntimeVersion' cannot be found on this object. Verify that the property exists and can be set.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:243 char:9
    +         $pool.managedRuntimeVersion = "v4.0.30319"
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : PropertyNotFound

    New-Item : A parameter cannot be found that matches parameter name 'physicalPath'.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:204 char:50
    + ...    New-Item "IIS:\Sites\$webSiteName\$vDirName" -physicalPath $path - ...
    +                                                     ~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [New-Item], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.NewItemCommand

    Set-WebConfigurationProperty : Cannot find a provider with the name 'WebAdministration'.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:206 char:5
    +     Set-WebConfigurationProperty -filter /system.webserver/handlers - ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (WebAdministration:String) [Set-WebConfigurationProperty], ProviderNotFoundException
        + FullyQualifiedErrorId : ProviderNotFound,Microsoft.IIs.PowerShell.Provider.SetConfigurationPropertyCommand

    et-ItemProperty : Cannot find drive. A drive with the name 'IIS' does not exist.
    At C:\Projects\Microsoft.Practises.ESB\Source\Install\Scripts\ESBFunctions.ps1:260 char:5
    +     Set-ItemProperty $vDirPath -Name applicationPool -value $appPoolN ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (IIS:String) [Set-ItemProperty], DriveNotFoundException
        + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.SetItemPropertyCommand


    RH

    Monday, August 5, 2019 8:25 PM
  • Run as Administrator for Power Shell.
    Set execution policy as mentioned in the below link

    https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-6

    Wednesday, August 7, 2019 5:03 AM