Microsoft KB Archive/930465

Knowledge Base

Error message when you try to connect to the SoftGrid Management Web Service server from the SoftGrid Management Console: "Error code: 0000C81B"

Article ID: 930465

Article Last Modified on 5/22/2007

---

APPLIES TO

• Microsoft SoftGrid for Terminal Services
• Microsoft SoftGrid for Windows Desktops

---

SYMPTOMS

When you try to connect to the SoftGrid Management Web Service server from the SoftGrid Management Console, you receive the following error message:

Unable to contact the SoftGrid system.
Please make sure that the hostname is correct and the SoftGrid Management Web Service is active.
Error code: 0000C81B

When this issue occurs, an entry that resembles the following is logged in the SoftGrid Management Console log file (Sftmmc.log):

No information is available at this time.

CAUSE

This issue may occur if one of the following conditions is true:

• The ASP.NET Web service extension is set to Prohibited.
• The ASP.NET Web service extension is set to Allow. However, ASP.NET is not installed under Application Server of Windows Components.

RESOLUTION

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

Method 1: Confirm that the ASP.NET Web service extension is set to Allow

The following steps apply to the SoftGrid Management Web Service being installed on the Microsoft Windows Server 2003 operating system:

1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand {server_name}, and then expand Web Service Extensions.
3. Right-click ASP.NET v.X.X.XXXX, and then click Allow.

If the ASP.NET Web service extension is not available, or if it already set to Allow, the Microsoft .NET Framework is installed. However, the ASP.NET Web service extension has not been installed to IIS. To install the ASP.NET Web service extension to IIS, follow these steps:

1. In Control Panel, double-click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click Application Server, and then click Details.
4. Click to select the ASP.NET check box, click OK, and then click Next.

Method 2: If the .NET Framework was installed before IIS

This following steps apply to the SoftGrid Management Web Service being installed on the Microsoft Windows Server 2000 operating system. Follow these steps to register the .NET Framework with IIS:

1. At the command prompt, change to the following directory:

   %SystemRoot%\Microsoft.NET\Framework\%VersionNumber%

2. Type the following command, and then press ENTER:

   aspnet_regiis.exe /i

Method 3: If Windows SharePoint Services is installed on the same Web site as the SoftGrid Management Web Service

When Microsoft Windows SharePoint Services 2.0 is installed, it adds the stsfltr ISAPI filter to the Web site. This causes the SoftGrid Management Console to fail to connect to the SoftGrid Management Web Service. If the ISAPI filter is removed, the SoftGrid Management Console will connect to the SoftGrid Management Web Service. However, you will be unable to connect to the Windows SharePoint Services site. To work around the issue, move the SoftGrid Management Web Service to a new Web site on the same server. For more information about how to move the SoftGrid Management Web Service to a new Web site on the same server, click the following article number to view the article in the Microsoft Knowledge Base:

931809 How to create a new Web site for the SoftGrid Management Web Service

Method 4: If the IIS UrlScan tool from the IIS Lockdown Tool is installed on the SoftGrid Management Web Service server and denies the POST verb

Review the effect of allowing the POST verb in your environment before you follow these steps:

1. Locate the Urlscan.ini file on the SoftGrid Management Web Service server.
2. Use a text editor to open the Urlscan.ini file.
3. Locate the following section in the Urlscan.ini file:

   [AllowVerbs]

4. Determine whether the POST verb exists. Then, perform one of the following actions as appropriate for your situation:
   1. If the POST verb exists, but it is commented out as in the following example, remove the semicolon:

      ;POST

   2. If the POST verb exists, but it is not commented out, do nothing.
   3. If the POST verb does not exist, add it.
5. Locate the following section in the URLscan.ini file:

   [DenyVerbs]

6. Determine whether the POST verb exists. Then, perform one of the following actions as appropriate for your situation:
   1. If the POST verb exists, comment it out by adding a semicolon before it as in the following example:

      ;POST

   2. If the POST verb does not exist, do nothing.
7. Save the changes to the Urlscan.ini file, and then close the file.
8. Stop the World Wide Web Publishing service, and then restart the World Wide Web Publishing service.

Keywords: kbtshoot kbexpertiseinter KB930465

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.