Application streaming failing when using SCCM 2012 with App-V integration

UPDATE: Hotfix 4 released. Download it from HERE.

And yet another Microsoft bug...

If you were pulling your hair off as I was a few hours ago then you understand the frustration of spending hours of troubleshooting and knowing that everything looks fine and finding that the problem you were experiencing was actually a bug.

Well luck for you if you have found this blog and this fix.

You can identify the problem by looking into the AppEnforce.log and finding the following:

Publish-AppvClientPackage : Failure to communicate with Application Virtualization Service. Operation attempted: Publish AppV Package. HRESULT: 800706BE

Now look in the event viewer and find the following:

The Microsoft App-V Client service terminated unexpectedly.  It has done this 2 time(s).

Faulting application name: AppVClient.exe, version: 5.0.3361.0, time stamp: 0x52781536Faulting module name: AppVEntStreamingManager.dll, version: 5.0.3361.0, time stamp: 0x52781643

If you monitor the App-V Service you will see that it stops every time SCCM start caching the initial files for streaming.

If you are experiencing the above then there are 2 workaround. The manual and the automated:

Manual:

Open powershell as admin and type:

Import-Module AppvClient; Set-AppvClientConfiguration –IgnoreLocationProvider 1

Automated:

Create a GPP registry item with the following:

HKLM\SOFTWARE\Microsoft\AppV\Client\StreamingName: IgnoreLocationProvider Value: 1 Type: DWORD

Happy streaming!