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

App-V 5 Inside the bubble (AKA break into the Virtual Environment)

As App-V grows up, this old post “Softgrid/App-V: Inside the bubble” became outdated. With App-V 5.x we have Powershell to break into the bubble.

Launch a cmd.exe processes inside the App-V 5 virtualized environment:

$AppVName = Get-AppvClientPackage <Package>
Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe

Or as a oneliner:

Start-AppvVirtualProcess -AppvClientObject (Get-AppvClientPackage “<AppVApplicationName>”) cmd.exe

Change “cmd.exe” to your needs, and of course change AppVApplicationName to the application name you would break into..

Another approach is the /appvve switch:

cmd.exe /appvve:<PACKAGEGUID_VERSIONGUID>

Or using a virtual process id:

cmd.exe /appvpid:8108

 

 

App-V The version lineage specified for package xxx is invalid, error code 0000BD39

After importing a newly sequenced application I received this error when importing into the Management Server.

AppV Error code 0000BD39

While saving my sequence an I/O File Error showed up. Some log file couldn’t be read or write. I deleted the log file from the sequence and saved the sequence again, with success this time. Probably this was the cause of the issue.

Solved this by opening the package for upgrade and saving the sequence As New Package, this way the Package GUID is regenerated.

AppV Save As New Package

App-V Error: Cannot create file when that file already exists (2C-000000B7)

I needed to make an empty application, which calls an external batch file. No problem for the batch file, but you cannot create a sequence whithout shortcuts right?

So I sequenced the local notepad and changed FILENAME from NOTEPAD.EXE to CMD.EXE (with “/C” as parameter to hide the DOS Box).

PARAMETERS=”/C” FILENAME=”%CSIDL_SYSTEM%\cmd.exe”

When the shortcut was launched, the App-V client throws this error:

App-V Error: Cannot create file when that file already exists (2C-000000B7)

After changing the SUBSYSTEM from windows to console this error was solved.

UPDATE 23/03/2012

Using CMD.EXE with PARAMETER /C in de CODEBASE tag makes SFTTRAY.EXE to load my application multiple times! So I changed the design; I don’t use a PRE or POST LAUNCH script but places the batch file in de FILENAME property of the CODEBASE tag. This way the batch file is the application.

Old:

PARAMETERS=”/C” FILENAME=”%CSIDL_SYSTEM%\cmd.exe”

New:

FILENAME=”\\server\share\batchfile.cmd”

AppV Error 19-00001003 Error while waiting for the application to be ready to interact with the user

My colleague couldn’t get an App-V application launched properly.

The app throws the following error:

The Application Virtualization Client encountered a problem while waiting for the application to be ready to interact with the user.

Error code: 19-00001003

AppV - Error while waiting for the application to be ready to interact with the user

Because the app launches a VBScript we changed the SUBSYSTEM Value from windows to console, and the app launched like it should!

 <IMPLEMENTATION>
  
  <VM VALUE=”Win32″>
   <SUBSYSTEM VALUE=”console”/>
  </VM>
  
 </IMPLEMENTATION>

Sometimes you must change this setting in the OSD file yourself. Because the AppV Sequencer doesn’t know if a particular application is a Windows (value=windows) or a DOS (value=console) program.

 

AppV Error: 44-00001004 The app manager could not create an application

I just had an issue with an App-V shortcut not picked up by the client. In the SFTLOG.TXT file the following errors exist:

[xx/xx/2011 xx:24:42:784 OMGR ERR] {tid=C10:usr=xxx}

The Application Virtualization Client cannot use the OSD file specified because the GUID attribute for the CODEBASE element changed (rc xxxxxx04-00001004).

[xx/xx/2011 xx:24:42:799 SWAP WRN] {tid=C10:usr=xxx}

Could not load OSD file \\xxx\xxx\xxx.003\xxx.osd

[xx/xx/2011 xx:24:42:799 AMGR INF] {tid=C10:usr=xxx}

The app manager could not create an application from ‘\\xxx\xxx\xxx.003\xxx.osd’ (rc xxxxxx44-00001004).

According to the last log file entries this is a typical issue where the OS VALUE tag in the OSD file is missing. But this wasn’t the case because I cleared all OS VALUE’s from the OSD file.

My second thought was a legacy OSD file floating around the Softgrid cache. But after setting the State key to zero and rebooting the machine the issue still exists. But I kept walking this path, because the first log entry was about GUID attributes that has been changed (04-00001004). But especially because the issue started after performing an Active Upgrade of the sequence.

So I decided to clear all caches using these methods:

  • Removed the App-V user cache (%appdata%\SoftGrid Client)
  • Cleared the system cache again with the State key
  • Removed the registry folder from Microsoft\SoftGrid\4.5\Client\Applications\<ApplicationName>

Rebooted the machine and BAM, I got my long awaited shortcut! Probably a previous OSD version was floating around in the AppV User Cache.

App-V package slow first launch

We had serious performance issues with our sequenced Office 2010. First launch could take up to 6 minutes, while Feature Block 1 was only about 100MB!

Because only Office 2010 was having this slow first start (and autoload), we blame our sequence, the App-V infrastructure or the application itself. But neither of these were the cause of the problem.

What got our attention was the Network utilization, it only reaches 2%. While this wasn’t an issue at all with other App-V applications. Streaming other applications goes fast and uses up to 95% of the available network bandwidth. But Office 2010 was sequenced with the 4.6 RTM version of the Application Virtualization Sequencer. Most other applications were sequenced with App-V sequencer 4.5.

Since version 4.6 the blocksize is fixed at 64KB, there is no way to change this with the GUI sequencer.

I managed to change the blocksize with the trail version of SFT Encoder. Once the blocksize was changed from 64 to 32K, Office 2010 launches ten times faster! However this isn’t a permanent solution for the slow launch. We don’t want to convert all newly sequenced packages with SFT Encoder!

So the reason why only Office 2010 suffered form this slow first start was because it was the only large package sequenced with version 4.6. Other packages made with sequencer 4.6 where to small to notice the slow launch.

A colleague of mine changed the network card speed from 1GBit/Full Duplex to 100Mbit/Full Duplex. With this setting changed, packages created with sequencer 4.6 are streaming fast like it should.

Maybe it’s a networking issue (switches?), maybe a network card setting misconfiguration (teaming?) .. to be investigated. But at least our 4.6 sequences are streaming fast again!

Thanks to Madelinde Walraven for the help with this issue!

To be continued!

Softgrid: Clear the AppV cache

Many AppV client issue’s are solved by clearing the virtual application cache.  Also while troubleshooting sequenced applications whipping the cache is a common task.  Here are several possibilities to clear the Softgrid cache.

First, get a list of all AppV applications:

sftmime query obj:app /short

Remove all applications from the cache:

sftmime.exe remove obj:app /global /complete

Remove a specific application from the cache:

sftmime.exe remove app:”applicationName” /complete

 

Or if you need to wipe the complete cache, set the Registry State key to zero:

Changing the State key to zero, and reboot the machine. This will completely clear the file system cache.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS\

Clear the Softgrid AppV cache via the State registry key

Update: I had to clear the User Cache for a specific application only, let’s call it “MyApp v1.0”. Using some batch- and OSD-scripting I was getting there.

Batch-script (Softgrid_clear_userCache_myApp.cmd);

SET _Path=C:\Users\%username%\AppData\Roaming\SoftGrid Client\%appDir%

SET _logfile=%systemroot%\_SOMEFOLDER_\MyAPP_cleanup.log

:: ### CHECK ###

If exist “%_logfile%” goto SKIP

:: ### REMOVE MyApp USER CACHE ###

If exist “%_Path%” rd “%_Path%” /S /Q

echo MyApp v1.0 AppV user cache cleared >> “%_logfile%”

goto END

:SKIP

echo Script already did his job before, quitting ..

goto END

:END

echo End script

OSD-script (to launch the batch script);

<DEPENDENCY>

<SCRIPT EVENT=”LAUNCH” TIMING=”PRE” PROTECT=”FALSE” WAIT=”TRUE” TIMEOUT=”0″>

<SCRIPTBODY>

@CALL \\\\server\\contentShare\MyApp1.0\\Softgrid_clear_userCache_myApp.cmd \n

..