5.8

Table Of Contents
SQL Server errors might include resource, disk space, or authentication problems, among others. Poor
tuning of your SQL Server might also cause performance problems such as data bottlenecks. Evidence of
SQL Server trouble might appear in the user interface or the debug logs, but messages directly related to
SQL Server typically appear directly in the SQL Server logs:
INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'fk_vcm_
sysdat_role_rules_role_id'. The conflict occurred in database 'VCM', table
'vcm_sysdat_rules', column 'rule_id'.
VCM Agent Problems
The VCM Agent is the locally installed mechanism by which VCM collects information from a managed
machine. If the Agent is not functioning properly, collections from that machine might fail.
In the VCM Console, the Running Jobs display is the first place to check when looking for problems with
an Agent. A typical error message for an Agent that cannot start collecting might be:
There was a problem parsing the agent instructions document.
The message indicates that a conflict occurred in the instruction set sent to the Agent, the Agent could not
process its instructions, and collection failed as a result.
UNIX Agent Problems
UNIX operates differently from Windows. To accommodate the differences, VCM uses a separate Agent
for Linux or UNIX based managed machines.
Troubleshooting UNIX Agent problems might be easier than Windows, because certain operations
available for Windows Agents are not available on the UNIX side. For example, compliance enforcement is
not available for UNIX, so you do not need to investigate compliance messages when you troubleshoot on
UNIX.
Report Server Problems
The Report Server is responsible for the graphical display of information in VCM and for VCM scheduled
reports. A Report Server error usually appears in the user interface.
An error has occurred during report processing.
System.Web.Services.Protocols.SoapException: An error has occurred during
report processing -
Microsoft.Reporting.Services.Diagnostics.Utilities.RSException: An error has
occurred during report processing -
. . .
You can determine if a problem exists with the Report Server by navigating to the Report Server home
page to see if the native interface for the Report Server is working. The URL is usually the name or IP
address of the Report Server machine followed by Reports:
http://report-server-name-or-IP/Reports
If the same error seen in the VCM user interface also occurs directly in the Report Server interface, the
problem is almost certainly with the Report Server itself, and not with VCM. If the Report Server interface
does not show the error, the cause is likely in VCM.
Types of Problems
VMware, Inc.
15