A user encountered an AppV Client error 0600000011, with the Powershell cmdlet “Get-AppvClientpackages”.
(I used the “-all” property, because my admin user didn’t had the application published)
AppV Client error 0600000011
The AppV log shows all required information: Failed to load a manifest document from one particular package.
AppV failed to load manifest document
This package had two package-versions. If we browse the AppV cache and goto the package with Package GUID eadb7b20-d9d9-4e5f-b568-8312a090d9f8 we see two versions. But deleting the package with the well known pipe command wasn’t possible.
AppV cache shows two versions of one packge
Removing with “Get-AppvClientPackage | Remove-AppvClientPackage” doesn’t work out because the Get-AppvClientPackage throws the error 0600000011. Using Remove-AppvClientPackage with the appropriate package and version GUIDs however does the job.
AppV delete packages from cache
After deleting the faulty packages from cache, do a Sync-Publishing server and you’re back in business.
After sequencing HP iLO Integrated Remote Console with AppV 5.1, it crashes right after launching the application:
HPiLO Application Crash
- Sources: iLO_Integrated_Remote_Console_Installer.msi
- AppV Sequencer v220.127.116.11 (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
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
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 file
Because I cannot remember the AppV Sequencer PowerShell commands to convert a Softgrid (App-V 4.6 .sft) package to a App-V 5.x package (.appv). I dedicated to write it down at last, freed some memory for playing Commander Keen without using QEMM or whatever some cool memory management tool.
First import the cmdlet;
Do the converthingy:
ConvertFrom-AppvLegacyPackage -SourcePath “C:\temp\v4_pkg” -DestinationPath “C:\temp\new_v5_pkg”
Btw Better use the 5.1 Sequencer or newer, because the AppVPkgConverter was updated in the 5.1 release. Also don’t try to convert older Softgrid 4.1/4.2/4.5 packages. First convert them to the 4.6 format using the App-V 4.6 Sequencer.
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:
Or using a virtual process id:
Clearing the App-V cache is a common task for IT Pro’s, helpdesk have it in there toolbox. Back in the App-V 4.x days clearing the Softgrid cache could be done with sftmime.exe, the registry and some old fashion batch scripting, but things are different now in App-V 5 Powershell land.
Remove all packages from disk (AKA machine cache)
First remove all connection groups, because packages that are a member of any connection group couldn’t be removed:
Get-AppvClientConnectionGroup -All | Remove-AppvClientConnectionGroup
After that, remove all App-V 5 apps from the cache:
Get-AppvClientPackage -All | Remove-AppvClientPackage
Clear application settings (AKA user cache/user state)
Using the packageName:
Using the packageGUID and versionGUID:
Repair-AppvClientPackage -PackageId <packageGUID> -VersionId <versionGUID>
Pipe things (usefull in scripts or to target multiple applications using a wildcard):
Get-AppvClientPackage -PackageId <packageGUID> -VersionId <versionGUID> | Repair-AppvClientPackage
More on the Repair-AppvClientPackage cmdlet on Technet.
After sequencing an application using App-V 4.x, the client refuses to get the virtual app.
The sftlog.txt says:
The app manager could not create an application from ‘\\servername\contentshare\appname\osd filename.osd’ (rc xxxxxx45-00000107).
Most of the time this error is about the OS VALUE-tag in the OSD-file. I only had the Win764 value. As I’m only using a Windows 7 x64 client machine there is no problem to use this value.
Because I was out of possibilities to troubleshoot this issue, I removed this OS VALUE from my OSD file. After an AppV server refresh my sftlog.txt gives more info then before!
The client has encountered an XML parsing problem. The error code is 0xC00CE508. Reason: An invalid character was found in text content.
Source Text: Blah blah blah, (near line 35, character position 156).
AHA, I got the bastard!
I’m using the ABSTRACT-tag as a placeholder for some sequencing/packaging info. Apparently some unsupported character sneaked in!
The previous error message says enough, but opening the OSD file in Internet Explorer can give more information about the XML syntax.
After removing some brackets and colons from the ABSTRACT-tag, the client was able to load my sequenced application!
I like to have all my admin management tools grouped in one MMC Console (ADUC, ConfigMgr ..). But the Application Virtualization Management Console wasn’t listed in the available snap-ins. Although this was never a big issue to me, but couldn’t handle it anymore 🙂
The AppV Management Console Snap-in was listed on my AppV Server. After reading this blog post on the AppV Blog, I exported this registry key:
And imported it on my workstation .. but no luck, no App Virt Management Console in the Available Snap-ins list.
After digging arround I found out that it’s possible to launch MMC.EXE in a 32bit environment.
Now I’m able to use the AppV Management Console into my own custom console.
After importing a newly sequenced application I received this error when importing into the Management Server.
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.
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).
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.
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.
I needed to disable a service as a prereq to stream a virtual AppV Visual Studio 2010 Professional package.
When using sc with these parameters,I got a syntax error:
sc config FontCache18.104.22.168 start=disabled
You need to add a space after start= and disabled to get this working!
sc config FontCache22.214.171.124 start= disabled