Previous Topic: No New Host UUID for Microsoft Hyper-V CloneNext Topic: Erratic Communication Between CAM Servers

Diagnostics and Troubleshooting › vDisk Record Is Not Found in the DSM Explorer

vDisk Record Is Not Found in the DSM Explorer

The vDisk record is not found in the DSM explorer, due to the following reasons:

In all the cases, CAF shuts down.

To fix, perform the following steps:

Follow these steps:

  1. Log in to the vDisk with administrator privileges.
  2. Verify the personality data provisioning services information.
  3. Troubleshoot the connection to the provisioning server.

    On success, CAF starts and the vDisk registration happens.

Processor Throttle Displays a Different Value in CA ITCM

The inventory item Processor Throttle displays a different value in CA ITCM when compared to the output of the powercfg.exe utility. This value is read using a 64-bit version of powerprof.dll.

This value matches the output of the powercfg.exe utility available in the ..\windows\SysWOW64 folder on the Windows platform. The 32-bit version of the same powercfg.exe utility available at the
..\ windows\system32 folder displays a different output.

Citrix XenServer Guest Virtual Machines Are not Shown in Virtualization Inventory

Symptom:

When I collect the virtualization inventory for a Citrix XenServer platform using RVI Agent plug-in, some of the guest Virtual Machines are not shown under Inventory, Virtualization, Citrix XenServer Virtual Machines.

Solution:

A solution to this problem is being worked-out. For more information, see support.ca.com to check if the solution is available.

Tenant ID Not Updated When an Asset Moves to New Tenant

When an asset moves to a new tenant, the tenant ID is not updated. The workaround is to delete the asset first and then reregister it with the new tenant.

Content Download Fails

Symptom:

If I download content when a CIC process runs in the background and another instance is launched by the engine, a detached CIC instance occurs.

Solution:

Do the following:

  1. Terminate the wrapper.exe process.
  2. Terminate java.exe that is used by CIC.
  3. Delete anchor files and loc files if any from C:\Program Files (x86)\CA\SC\CIC\bin.
  4. Initiate the content download job again from Engine tasks.

Software Job History Behavior after the Uninstall Job

When the time period specified in the Job history cleanup time setting elapses, the software job history of an agent is cleaned up. The cleanup task runs daily at the time specified in the configuration policy Start Time. Based on the Job history cleanup time setting, the cleanup task checks every day for install jobs that are older than the number of hours specified in the configuration policy. The default period is 4320 hours or 180 days.

The cleanup task attempts to remove all the procedures of a package together. This means that the task searches for the uninstall job history of the package before deleting the install job history. So, even if the install job history is more than 180 days, the task cannot remove the job history until the uninstall job history is available. After you deploy the uninstall procedure, the software job history contains the uninstall job too. When the cleanup task runs at the next scheduled time, it looks for the install jobs that are older than the time specified in the configuration policy and have the corresponding uninstall job in the history. When a match is found, the complete job history of the package (including the install, activate, and uninstall procedures) is deleted from the software job history of the agent. This results in the removal of the history soon after uninstallation.

With the Release 12.8, the comstore setting is changed such that the software job history is deleted when the uninstall job exceeds the time specified in the configuration policy. For example, if you have set the Job history cleanup time parameter to 10 days, the complete job history of the package upto ten days, from the time the uninstall procedure was installed on the computer, is deleted.