Microsoft App-V 5 Connectiongroups and errors

Edit: The issue is solved in App-V 5 SP2. The connectiongroups can’t be added with these conflicting settings

Microsoft App-V 5 Connectiongroups and errors

Error: This may be due to a network failure

After importing App-V 5 packages and setting up connectiongroups I was experiencing problems with starting up the applications. I got several errors:the may be due to a network failure

Error: this may be due to a network failure

Error code: 0x8e90060a-003000F

On a Windows 2008 R2 server i got a additional error.

error: MSVCR100.dll

MSVCR100.DLL missing from the system

The following error is in the eventviewer:

failed to start due to Virtual COM subsystem failure

Process 2744 failed to start due to Virtual COM subsystem failure. Package ID {715f39d8-1b48-4b9a-95e6-d33370564b33}. Version ID {9cdf46f3-6716-43d3-b533-5c697878f51f}. Error: 0x8E90060A-0x3000F

Research

With troubleshooting these errors i didn’t find a solution on the internet. There are some similar errors around with different solutions. My problem wasn’t about local rights, because I tried local administrator account and domain admin account. The application would startup correctly after removing the connectiongroup.

The connectiongroup was giving the problem with these applications. A new connectiongroup with different applications worked fine. My suspicion instantly went to “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. In Microsoft App-V 4.* this settings was “ALLOW LOCAL INTERACTION”.

Testing my suspicion

For my test I created two new applications:

  • A Link to notepad without any registry or files
  • A Link to odbcad32 without any registry or files with BOTH Com and Named objects allowed

Both applications worked fine as a single App-V package. I connected both App-V packages through a connectiongroup.

Connectiongroup

The connectiongroup imported without any errors or warnings. After the creation of the connectiongroup the applications started with the errors again.

Conslusion

The connectiongroups aren’t able to handle a choice between using or not using “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. The Microsoft App-V 5 client will generate several errors with startup, because it can’t make a choice between them.

Advertisements