5.8

Table Of Contents
Internet Information Services Problems
The VCM user interface is hosted on Microsoft Internet Information Server (IIS), which might be
incorrectly configured.
Sometimes the VCM user interface displays an error similar to what you see when you fail to connect to a
Web page. Error messages such as 404 File Not Found or 403 Forbidden are typical IIS messages,
and indicate improper configuration of IIS in relation to VCM or Report Server pages. You might also see
ASP.NET errors:
Server object error 'ASP 0177:8007007e'
Server.CreateObject Failed
/vcm5/L1033/SumAdminDeployment.asp, line 68
8007007e
Network Connectivity Problems
The VCM Collector must have a network connection to all the Agents that send data. In addition, split
installations require network connections between the separate VCM servers: Collector, SQL database,
and Web server.
Failed network connections do not usually occur between all systems at the same time, so network issues
are often easier to diagnose. A failed connection typically appears in the user interface as a failure of a
VCM or VCM Patching job on a single or subset of managed machines. In the Jobs Detail display, a
PingFailed message indicates connectivity problems.
A way to test network connectivity is to ping the Agent from the Collector. From the Collector, it might
be necessary to connect to the HTTP port of an Agent if any of the following are true:
n The environment contains a firewall.
n The Agent is a UNIX Agent.
n The Agent machine is using HTTP instead of the DCOM protocol for its primary communication
method.
To connect to the HTTP port, type telnet
agent-machine-name-or-IP
26542 at the command prompt.
A successful command returns only a blank screen, which indicates that the managed machine has
answered the connection request and awaits further instructions. You can break the connection and exit
telnet by typing Ctrl+] and then quit.
If you send the telnet command and receive any other message (such as Connection refused or
Connection timeout) that is a good indication of a network problem. Failed network connections must
be resolved with the help of local support before further VCM troubleshooting. Otherwise, you cannot
know whether or not the problems you are seeing are network related.
Hardware and Performance Problems
Hardware and performance problemsare among the most difficult to diagnose because they are often
intermittent and random.
Sometimes, the only common denominator is that the problem is random. When that happens, look for
possible hardware or performance evidence.
Running out of disk space is the most common hardware problem.On the VCM servers, use the
operating system file or disk management tools to check that enough disk space is available for the
database and for the VCM application itself.
VCM Troubleshooting Guide
16
VMware, Inc.