AppV Sequencing HP iLO Integrated Remote Console and .NET Runtime application crashes

After sequencing HP iLO Integrated Remote Console with AppV 5.1, it crashes right after launching the application:

HPiLO Application Crash

HPiLO Application Crash

Environment:

  • Sources: iLO_Integrated_Remote_Console_Installer.msi
  • AppV Sequencer v5.1.85.0 (OS: Win7 x64 SP1)
  • Endpoint: Win7 x64 SP1

Sequencer and endpoint where the same in terms of .NET Framework version and installed VC++ redistributions.

All prereqs where installed one both sequencer and endpoint.

The application logs:

Event ID 1000 Faulting application name: HPLOCONS.exe

Event ID 1000 Faulting application name: HPLOCONS.exe

Event ID 1026 Application: HPLOCONS.exe terminated due to an unhandled exception.

After spending some time and anguishing my eyes on ProcMon logs I decided to delete the “HPLOCONS.exe.config” application manifest file from within the App-V bubble. First launch a DOS-box in the virtual environment (VE) of our AppV package. From within that DOS-BOX delete the manifest file and try to launch the application .exe. (or just re-sequence the application, and delete the manifest file. Or edit your package .. whatever).

Start-AppvVirtualProcess -AppvClientObject (Get-AppvClientPackage "hp ilo pvadinstall") cmd.exe

appv-hpilo-netframework-crash-on-hplocons-exe

After deleting the application manifest file the application launches like it should.

Added March 1 (2017); Vigneshwaran, here’s the contents of the HPLOCONS.exe.config manifest file:

HP iLO manifest

HP iLO manifest file

2 thoughts on “AppV Sequencing HP iLO Integrated Remote Console and .NET Runtime application crashes

  1. Good find. Did you find anything inside the manifest file like this?

  2. Hello Vigneshwaran,

    That manifest file contains:

    can’t post images here, I’ll add it to the post.

    I suppose that these two .Net Framework versions are used by the .exe. But we have newer .Net Framework versions installed, so it couldn’t find that particular version. Without manifest file the .exe uses the native installed .Net Framework 4.6.2.

Leave a Reply