Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you try to connect to the App-V (SoftGrid) Management Web Service from the App-V (SoftGrid) Management Console: "A remoting error occurred. Error code: 0000C824"


View products that this article applies to.

Symptoms

When you try to connect to the SoftGrid Management Web Service from the SoftGrid Management Console, the connection is unsuccessful. Additionally, you receive the following error message: 
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
Additionally, the following error message is logged in the SoftGrid Management Console log file (Sftmmc.log):
BinaryFormatter Version incompatibility.

↑ Back to the top


Cause

This issue may occur if one or more of the following conditions are true:
  • The NETWORK SERVICE account does not have Local Activation permissions to the Internet Information Services (IIS) Admin service.
  • The ASP.NET worker process account on the SoftGrid Management Web Service

    server does not have the correct file permissions.

  • Microsoft Windows SharePoint Services 2.0 is installed on the same website as the SoftGrid Management Web Service.
  • The NETWORK SERVICE account does not have access to the Web.config file in the C:\Program files\Softricity\SoftGrid Management Service directory.
  • The .NET Framework version 2.0 or the .NET Framework version 3.0 was installed after IIS was installed.
  • The LOCAL PATH in the default Web site of IIS is incorrect.

↑ Back to the top


Resolution

To resolve this issue, use one or more of the following methods, as appropriate for your situation.

Method 1: Make sure that the NETWORK SERVICE account has the correct permissions

The NETWORK SERVICE account may not have Local Activation permissions to the IIS Admin service. This condition can occur if the following conditions are true:
  • You add IIS to a server that is running Microsoft Windows Server 2003 Service Pack 1 (SP1).
  • You supply the Windows Server 2003 installation source when you are prompted for the Windows Server 2003 Service Pack 1 installation source.
When the NETWORK SERVICE account does not have Local Activation permissions to the IIS Admin service, the following events are logged in the System log:To make sure that the NETWORK SERVICE account has the correct permissions, follow these steps:

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services.
  2. Expand Component Services, expand Computers, expand My Computer, and then expand DCOM Config.
  3. Right-click IIS Admin Service, and then click Properties.
  4. Click the Security tab.
  5. Under Launch and Activation Permissions, click Edit.
  6. Click Add.
  7. In the Enter the object names to select box, type NETWORK SERVICE, and then click OK.
  8. Click NETWORK SERVICE, and then click to select the Local Activation check box in the Allow column.
  9. Click OK two times.
When the issue that is mentioned in the "Symptoms" section occurs, the IIS DefaultAppPool application pool is stopped. When you try to reconnect with the SoftGrid Management Console, the operation will fail. Additionally, you receive the following error message until the DefaultAppPool application pool is started:
Unable to contact the SoftGrid System.
An unexpected communication error has occurred. Please report the following error code to your system administrator.
Error code: 0000C809
To

start the DefaultAppPool application pool, follow these steps:
  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand server_name, expand Application Pools, and then click DefaultAppPool.
  3. Right-click DefaultAppPool, and then click Start.
Note If this method does not resolve the issue, you may have to reapply Windows Server 2003 SP1. Alternatively, you may have to uninstall and then reinstall IIS by using the Windows Server 2003 SP1

installation source.

Method 2: Make sure that the ASP.NET worker process account has the correct file permissions

The ASP.NET worker process account on the SoftGrid Management Web Service

server must have the file permissions that are described in the following table.

LocationPermission
%SystemRoot%\TempFull Control
%SystemRoot%\Microsoft.NET\Framework
\VERSION\Temporary ASP.NET Files
Full Control




The issue that is mentioned in the "Symptoms" section can occur when you install the Active Directory directory service on a member server that has IIS installed and then install the SoftGrid

Management Web Service on that server. We recommend that you do not install SoftGrid components on a domain controller.





The following table describes which Windows account is the default ASP.NET worker process account, depending on the operating system and on the role of the server on which the Web Service is installed.
Operating SystemRoleASP.NET work process account
Windows 2000 ServerMember ServerASP.NET Machine Account (computer name\ASPNET)
Windows Server 2003Member ServerASP.NET Machine Account (computer name\ASPNET)
Windows 2000 ServerDomain ControllerLaunch IIS Process Account (domain name\IWAM_computer name)
Windows Server 2003Domain ControllerNETWORK SERVICE
For more information about ASP.NET worker process account permissions and about Internet Information Services (IIS) 6.0, click the following article number to view the article in the Microsoft Knowledge Base:

812614 Default permissions and user rights for IIS 6.0

Method 3: Change the SoftGridManagement and SoftGridReporting application pool back to the DefaultAppPool application pool

When you install Windows SharePoint Services 2.0, it modifies the SoftGridManagement and SoftGridReporting application

pool from "DefaultAppPool" to "StsAppPool1."



To change the application pool back to "DefaultAppPool," follow these steps from the SoftGrid Management Web Service

server:
  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand server_name, expand Web Sites, and then click Default Web Site.
  3. Right-click SoftGridManagement, and then click Properties.
  4. Click the Virtual Directory tab.
  5. Under Application pool, select DefaultAppPool, and then click OK.
  6. Right-click SoftGridReporting, and then click Properties.
  7. Click the Virtual Directory tab.
  8. Under Application pool, select DefaultAppPool, and then click OK.

Method 4: Add the NETWORK SERVICE account to the folder that you want to access and grant the full control permission

Add the NETWORK SERVICE account to the security tab in the folder and grant the full control permission for the NETWORK SERVICE account and then restart IIS.

Method 5: Run the aspnet_regiis tool

  1. Click Start, click Run, type cmd, and then press ENTER.
  2. At the command prompt, type Drive:\WINDOWS\Microsoft.NET\Framework\version, and then press ENTER.
  3. Type aspnet_regiis.exe /R, and then press ENTER.

Method 6: Make sure that Local Path is set to <drive>:\Inetpub\Wwwroot

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand server_name, expand Web Sites, and then click Default Web Site.
  3. Right-click Default Web Site, and then click Properties.
  4. Click the Home Directory tab.
  5. Make sure Local Path is set to drive:\Inetpub\Wwwroot, and then click OK.

↑ Back to the top


Keywords: kbacqcompany, kbexpertiseinter, kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 930461
Revision : 2
Created on : 8/1/2019
Published on : 8/1/2019
Exists online : False
Views : 667