Microsoft KB Archive/930707

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 08:32, 21 July 2020 by X010 (talk | contribs) (Text replacement - "<" to "<")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Error message when you refresh a Desktop Configuration Server in the Microsoft SoftGrid Client Management MMC snap-in: "Error code: xxxxxx-xxxxxx2A-00002AF9"

Article ID: 930707

Article Last Modified on 5/4/2007



APPLIES TO

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



SYMPTOMS

When you refresh a Desktop Configuration Server in the Microsoft SoftGrid Client Management Microsoft Management Console (MMC) snap-in, you receive the following error message:

The SoftGrid Client could not update desktop configuration information from the server ServerName.
No such host is known.
Error code: xxxxxx-xxxxxx2A-00002AF9

CAUSE

This problem occurs because the SoftGrid Client cannot communicate with the Desktop Configuration Server.

MORE INFORMATION

The Desktop Configuration Server can be specified by the host name, the DNS name, or the IP address of the server or the load-balancing device.

To verify the server, follow these steps:

  1. In Administrative Tools, open the SoftGrid Client Management MMC snap-in.
  2. Click Desktop Configuration Servers.
  3. Right-click the server that reports the error code, and then click Properties.
  4. Verify that the server is specified in the Host Name box.

    If the server is invalid, the refresh operation fails.

    If the server is valid, determine whether the client can ping the host name, the DNS name, or the IP address. To do this, follow these steps:
    1. At a command prompt, type ping ServerName, and then press ENTER. For example, type the following command:

      ping SGSERVER01

    2. If the ping operation succeeds, you receive the following mssage:

      Pinging ServerName xxx.xxx.xxx.xxx with 32 bytes of date:
      Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=128

      If the ping is unsuccessful, you receive the following error message:

      Ping request could not find host ServerName. Please check the name and try again.

If the client cannot ping the server, a network-related issue is preventing the client from communicating with the server. You must correct the network-related issue before you can start an application. For more information, contact the network administrator.

Keywords: kbexpertiseinter kbtshoot KB930707