AppV 5 Package convertor

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;

Import-Module AppVPkgConverter

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.

The app manager could not create an application from 44-00001007

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!

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.

Office 2010 Standard AND Access 2010 on the same machine with Office 2010 Deployment Kit for App-V

We needed to have Access 2010 delivered through App-V on the same computers where Office 2010 Standard was published to. Office 2010 needs the Office 2010 Deployment Kit for App-V to activate, this was already up and running on our client computers.

If we streamed Access 2010 next to Office 2010 Standard, Access launched and asks for a Product Key:

Microsoft Office - Enter your Product Key

I thought the Office Software Protection Platform must take action here, and contact our KMS Server to obtain a license, but it behaved not like that. The service Office Software Protection Platform (osppsvc) is responsible for the activation. This service is installed by the Office 2010 Deployment Kit for App-V.

Service: Office Software Protection Platform (osppsvc)

After going through Technet and some forums, I finally got it all together and found the solution:

The KMS activation is done when installing the Deployment kit for App-V. To use Access 2010 and Office 2010 Standard together, the Deployment Kit for App-V needs to be installed with the STANDARD and ACCESS parameters combined. These Licensing Flags can be used on the command line separated by a space:

OffVirt.msi ACCESS=1 STANDARD=1 /qb REBOOT=REALLYSUPPRESS

To verify which actions the OffVirt.msi installer exactly did, use the logfile parameter and check the logs:

OffVirt.msi ACCESS=1 STANDARD=1 /qb REBOOT=REALLYSUPPRESS /l*v c:\temp\OffVirt.log

If the ACCESS=1 parameter wasn’t set, you’ll get this in the logfile;

MSI (s) (E0:E0) [17:11:35:989]: Skipping action: Access_KMS_Client (condition is false)

When you did set the ACCESS=1 licensing flag;

MSI (s) (40:58) [17:29:32:699]: Doing action: Access_KMS_Client

OffVirt.msi log

Going through the logs makes everything clear. Combining the OffVirt.msi parameters makes sense!

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!

A remoting error occurred when opening the App-V management console (Error Code 0000C824)

Had this issue before, and had to reinstall my App-V server from cratch. Lucky enough it was a lab environment.

But today I had this error again!

A remoting error occurred. Error Code 0000C824

A remoting error occured 0000C824 App-V

Solution

Because App-V 4.5 Service Pack 2 is released some months ago, I upgraded my VAS server to SP2. After the SP2 update, the Application Virtualization Management Console could connect to my App-V server like before!

Probably reinstalling your current Management Server version should do the trick also!

App-V error 0A-20000194 after server upgrade

After an App-V Server upgrade from Application Virtualization Server 4.5.1.15580 to 4.5.2.17140 we encountered the following error:

The Application Virtualization Client could not launch ApplicationName.

The package requested could not be found in the system data store or the files associated with this package could not be found on the server. Report the following error code to your System Administrator.

Error code: XXXXXX-XXXXXX0A-20000194

After some deep digging we (Ali) found out that the App-V Management Server Installer set the CONTENT_DIR back to the default value! As we don’t use the default content dir C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\content we found our problem.

Solve this by manually change the registry key  SOFTGRID_CONTENT_DIR (in HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\Server) to your current Content location (for example \\servername\contentdir).