If you upgraded to Service Pack 2 automatically using Automatic Updates or Windows Server Update Services (WSUS) you may have the following happen after the update:
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
We recently had two blog articles that were much related but not specifically in this context:
How to Fix Microsoft Management Console Error Code: 0000C824: http://blogs.technet.com/b/appv/archive/2011/04/20/how-to-fix-microsoft-management-console-error-code-0000c824.aspx
Microsoft Update/WSUS will not offer the App-V 4.5 SP2 update if you do not have Microsoft Application Error Reporting installed: http://blogs.technet.com/b/appv/archive/2010/08/11/microsoft-update-wsus-will-not-offer-the-app-v-4-5-sp2-update-if-you-do-not-have-microsoft-application-error-reporting-installed.aspx
Where this particular scenario is different is it involves the App-V management server instead of the client upgrading to Service Pack 2. What is likely happening is a variation of the issue outlined in the following KB article:
KB221140 - Error 25100 or 25122 when installing the Microsoft Application Virtualization Management service
If .NET 4 is installed on the machine and the installation fails, it could leave the AppVirt management Service (formerly called the management web service.) in a partially installed state.
How to Tell
When you get the 0000C824 error, determine if the App-V Management Service is still in place by verifying the presence of the SoftgridManagement virtual directory in the web site’s configuration within IIS.
The current work around is to:
1. Remove the .NET 4.0 (temporarily as it will be re-added later.)
2. Restart the server.
3. Manually uninstall ONLY the AppVirt Management Service (Service - not server.)
4. Restart the server.
5. Reinstall AppVirt Management Service component from SP2 media (MDOP 2011 Media0 or upgrade media found here:
6. Reinstall the .NET 4.0 Framework.
If .NET 4.0 is not installed, please follow the abbreviated steps to restore the management service.
1. Manually uninstall ONLY the AppVirt Management Service (Service - not server.)
2. Restart the server.
3. Reinstall AppVirt Management Service component from SP2 media.
Steve Thomas | Senior Support Escalation Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
In my case, this happened after a failed App-V 4.5 SP2 update on the App-V server. Event: "Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft Application Virtualization 4.5 Service Pack 2.", possibly from a missing dependency, I haven't checked it out yet.
During that update, it somehow replaced or altered the file C:\Windows\System32\inetsrv\config\applicationHost.config. This file was altered at the exact time our server got rebooted from a scheduled WSUS update. What puzzles me, is why it didn't roll back all the changes it made when the failure occurred.
Restoration of said "applicationHost.config" file from backup solved our problem. If you have this problem, you can test quickly using a browser, url: http://appvservername/SoftGridManagement/Authorization.rem?wsdl
(it should give you a credentials check, followed by "Object reference not set to an instance of an object" messages). If failed, it should give you "Internal server error".