HP

HP Version Control Agent

English
  Troubleshooting   

Troubleshooting

»Table of Contents
»Index
»Product overview
»Getting started
»Navigating the software
»The Home page
»The Log page
»The Help page
Troubleshooting
»Service and support
»Windows events
»Legal notices
»Glossary
»Using Help
» HP Version Control Agent
» Miscellaneous problems

HP Version Control Agent

Access problems

My [Install] buttons are grayed out in the HP VCA when I configure the HP VCA with administrator, operator or even invalid credentials to connect to the HP VCRM.

Solution: The HP VCRM's HP SMH has anonymous access enabled.

HP recommends that you upgrade the HP VCRM with the version from the 7.50 HP Management CD.

Systems Insight Manager problems

How do I recover from a failed update when the software repository becomes unavailable while the update is performed in Systems Insight Manager (HP SIM )?

Solution: If the update task uses a software version criteria, execute the task again. The update starts over and the Smart Components that are deployed are only installed if supported by the target servers.

Use the task log to examine the target systems and determine where the update failed.

The software update feature in HP SIM does not locate any repositories. How can this be corrected?

Solution: Verify the Discovery settings and ensure that the IP range specified does not exclude the selection of available repositories. Also, for a repository to announce itself as such to HP SIM, ensure that the repository is managed by the HP Version Control Repository Manager (HP VCRM). While it is not necessary, it is useful to set up a HP VCRM on a system before you run Discovery in HP SIM for the first time. Make sure that the HP VCRM trusts HP SIM.

One of the three items I was trying to install from HP SIM failed to download from the repository, yet the other two items, which downloaded properly, did not install.

Solution: If any items fail to download from the repository, the HP VCA will not attempt to install any of the items.

I set up a task to notify me using email when a software update task completed in HP SIM, but when the event arrived, not all of the software was completely installed.

Solution: The software update task sends the HP VCA on each target system a command to install the specified components. After the install command has been sent to the last system, the software update task completes, and the completion event is sent. However, at this time, some of the systems might still be in the process of downloading components and installing them.

Why can't I install or update the HP VCRM using the HP VCA? I receive an Unable to install the Microsoft XML Parser 3.0 (1603) error.

Solution: You are attempting to install the HP VCRM with the HP VCA, whose service does not have administrative privileges.

Perform the recommended changes only on servers running both the HP VCA and HP VCRM:

  1. Launch the Services program.

  2. Right-click the HP VCA service.

  3. Select [Properties].

  4. Click the Log On tab.

  5. Click This account.

  6. Enter the name of or browse to a user with administrative privileges using [Browse.]

  7. Click [OK] to save the changes.

You will now be able to install and upgrade the HP VCRM using the HP VCA.

Log problems

Why do I see a reboot required, Status 2 in the HP VCA Log but not in the Install Log?

Solution: The HP VCA Log page contains information logged by the HP VCA during its operation. The HP VCA Log is often informational when you are trying to troubleshoot a problem, such as why a specific task failed. In this specific case, the component setup program detected that the installation succeeded, but will not be complete until the system is rebooted. The HP VCA does not reboot the system after each component install, but at the end of all installations, to avoid unnecessary restarts. If the installation task was started without the reboot automatically option selected, you must restart the server manually to ensure proper installation of all software.

The Log page contains information logged by the component setup program.

After installing the HP SMH from the installation icon in the HP VCA, the HP VCA log disappeared and indicated that the page cannot be displayed. What happened to the log?

Solution: The HP SMH is restarted during the installation which disrupts the connection between the client browser application and the system. To resolve this issue, HP recommends that you login to the HP SMH again and view the HP VCA log directly to determine the status of the installation task.

Print problems

When I try to print from a Mozilla browser, a dialog box displays indicating there is an Unknown Error. Why is this happening?

Solution: A default printer has not been configured. HP recommends that you configure a default printer to resolve this issue.

HP Service Pack for ProLiant, ProLiant Support Pack problems

After initiating the PSP installation on a server, a message displays indicating XML PARSING ERROR and the log details display The xml file was tainted. The PSP installation is terminated.

Solution: The PSP installation is terminating due to low disk space.

To resolve this issue, ensure the server has at least 200 MB or more of free disk space so the installation can complete successfully.

Replicate Agent Settings problems

The Replicate Agent Settings feature in HP SIM denies access to the source system for security reasons. How is this corrected?

Solution: HP SIM implements security to ensure that access to management information is available only to authorized users. This security relies on security settings between HP SIM with managed systems. HP SIM will deny access if the trust relationship between HP SIM and the source system's HP SMH is not configured correctly. To correct this problem, HP suggests the following procedure:

  1. Navigate to https://hostname:2381.

  2. From HP SMH, click Settings ⇒ Security ⇒ Trust Mode.

  3. Correct the configuration.

Note: For more information regarding Trust Relationships, refer to Setting up Trust Relationships in the Systems Insight Manager User Guide.

Complete information on the security implemented by the management system, where the HP VCRM is installed, and the managed systems, or HP SMH, are available in the Security white paper. To download the Security white paper, go to http://www.hp.com/servers/manage.

Repository problems

The job of the Software Version Status Polling tasks in HP SIM is to retrieve a list of installed software and firmware from systems and obtain the software status from the HP Version Control Agent (HP VCA) on those systems. Why do I need to specify a repository when setting up this task? Does it matter which repository I choose?

Solution: HP SIM sends the selected HP VCRM a list of all the software versions in sorted order. This is necessary so that HP SIM can properly handle searches that include software version comparisons. The HP VCRM can return a sorted list of versions for a component even if that component does not exist in the repository. However, it is generally a good idea to choose a repository with the most complete set of software.

I cannot seem to configure the HP VCA settings to access the HP VCRM using the administrator credentials. Why is this happening?

Solution: When HP SMH is installed, the HP VCA cannot be configured to access a HP VCRM 2.1 or later using the administrator login credentials. A feature in the HP VCA prevents you from using the administrator credentials to ensure that the administrator OS Account for the HP VCRM is not locked out when the HP VCA retries the login to the HP VCRM several times.

HP recommends that you create an account with administrator privileges to be used specifically by the HP VCA, for example, vcadmin.

Miscellaneous problems

Should the HP VCRM be installed before running Discovery in HP SIM, and if so, why?

Solution: While it is not essential, it is a good idea to install a HP VCRM before running Discovery. Be sure that this repository trusts HP SIM. Refer to Setting up Trust Relationships in the HP SIM User Guide for more information on trust relationships. It is a good idea to install a HP VCRM is so that the Software Version Status Polling task can properly sort the versions of software retrieved from systems. If you do not set up a repository before running Discovery, then the versions are sorted when a software criteria search is set up for the first time.

Why is it that when I search for systems with Foundation Agents for Windows in HP SIM, I get only the Windows 2000 systems back and not Windows NT?

Solution: Even though you choose a component that is supported for both Windows NT and Windows 2000, the search only returns the systems that match the operating system tree from which you chose the component when you created the search. In this example, if you chose the Foundation Agents for Windows from the Windows 2000 branch of the criteria tree, then only Windows 2000 systems are returned. If you want systems from both Windows 2000 and Windows NT, choose the Foundation Agents for Windows from the Windows 2000 and Windows NT branch.

What capabilities do I get from the HP VCA alone?

Solution: The HP VCA provides a list of the HP Web-enabled System Management Software and firmware installed on the local server. For the HP VCA to provide version control and software distribution functionality, it must be configured to refer to a HP VCRM.

The HP VCA or HP VCRM display as links under the Integrated Agents list on the HP SMH, but the application is missing from the HP Version Control category on the HP SMH's Home tab, or the category does not display at all. When I click the link under the Integrated Agents, a page displays indicating The application is not available.

Solution: On Windows, the associated service is stopped. You must restart the HP Version Control Agent or HP Version Control Repository Manager's service on the server. If the service is not set for automatic startup, then configure the service to start automatically. If the service stopped unexpectedly, check the Windows Event Log as well as the application's log for additional information.

On Linux, the associated HP VCA daemon process is stopped, and the HP VCA daemon can be restarted by the root user running /etc/init.d/hpvca restart.