App-V and Console protocol mismatches

Ive recently been building out some awesome Microsoft and Citrix demos for our internal field organization running the full stack of XenDesktop 5, XenApp6, Hyper-V, App-V 4.6 and AppSense. Ive been having these weird problems with App-V and the App-V management console that I couldnt work out. Mysteriously, after a period of time and without any changes by me I would get these odd remote protocol errors.

A remoting error occurred.
Make sure the Management Console is properly configured and it has the same version as the Management Service.
Error code: 0000C824

I searched and searched for answers. It got to the point where I had tried everything so I reinstalled the whole App-V instance. The problem went away for a period of time, but then jsut as mysteriously, it reappeared. Weird.

Luckily I have access to the App-V team and got the following troubleshooting steps. In my case, the first step fixed the issue. I post the following in the event that you too are having these issues. That said if you have any questions, dont direct them to me. Contact the App-V team! Internal kudos to Steve Thomas. Enjoy!

1st: Clear the MMC XML Cache:



1. Navigate to Start-Run and type in %APPDATA%\Microsoft\MMC


2. Delete the SFTMMC file.


3. Restart the MMC console and reattempt.


2nd: Restart the Management Web Service



1. On the App-V Server, reset IIS and ASP.NET by running the following command from an elevated command prompt:




2. Restart the MMC console and reattempt.


3rd: Collect the SFTMMC Log file to get more specifics on the error:



The log file is here:


C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Console\sftmmc.log


This will need to be enabled.


1.            Start Registry Editor.


2.            In the Navigation pane, locate and then right-click the following subkey:


                HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Management Console (or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Management Console if x64)


3.            Click the App-V Management Console.


4.            Review the values that are listed for the LogLevel entry.


                a.            If the LogLevel entry does not exist, go to step 5.


                b.            If LogLevel entry exists, go to step 7.


5.            Right-click the App-V Management Console, point to New, and then click DWORD Value.


6.            For New Value #1 type LogLevel.


7.            Right-click LogLevel, and then click Modify.


8.            For Value data, type the appropriate Value from the table in the "Logging level values and description" section, and then click OK.



4th: Check for Duplicate SPNs



1. Use the SETSPN tool to check for duplicate or missing SPNs:


You will need to ensure the HTTP and SOFTGRID SPNs are in place as well as the SQL server SPNs.


5th: Verify the App-V Server has been trusted for delegation:



Please follow the procedures outlined in the following article:


6th: Verify UDL file access:



1. Application Virtualization administrators must have Read and Execute permissions to the SftMgmt.UDL file in folder %systemdrive%\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Service.


 7th: Verify FIPS settings


Check to see if you have enabled "System cryptography: Use FIPS compliant algorithms for encryption". That can screw it up too.


Comments (3)

  1. Thanks Doug. Though my name is Michael. It says so at the top of the blog 🙂

  2. Ken says:

    Thanks, great article.  For me it was a failed Windows update for App V.  Went to view update history and had repeated failures.  I re-ran the update, restarted the server and I was back in business.

  3. Doug says:

    Ken, you saved me 8 hours of frustration.  Thanks.

Skip to main content