Jump to content


English
hp.com home
HP Version Control Agent  |  Troubleshooting

HP Version Control Agent
Troubleshooting

» HP Version Control Agent

»table of contents
»index
»Product Overview
»Getting Started
»Navigating the Software
Troubleshooting
»Service and Support
»Windows 2000/NT Events
»printable version
»glossary
»using help
Content starts here
» HP Version Control Agent
» HP Version Control Repository Manager
» Miscellaneous Problems

HP Version Control Agent

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

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 install 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 Systems Insight Manager 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 Systems Insight Manager, ensure that the repository is managed by the HP Version Control Repository Manager. While it is not necessary, it is useful to set up a Version Control Repository Manager on a system before you run Discovery in HP Systems Insight Manager for the first time. Make sure that the Version Control Repository Manager trusts HP Systems Insight Manager.

One of the three items I was trying to install from HP Systems Insight Manager failed to download from the repository, yet the other two items, which downloaded properly, didn’t install.

Solution: If any items fail to download from the repository, the Version Control Agent 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 Systems Insight Manager, but when the event arrived, not all of the software was completely installed.

Solution: The software update task sends the Version Control Agent 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 Version Control Repository Manager using the Version Control Agent? I receive an Unable to install the Microsoft XML Parser 3.0 (1603) error.

Solution: You are attempting to install the Version Control Repository Manager with the Version Control Agent, whose service does not have administrative privileges.

Perform the recommended changes only on servers running both the Version Control Agent and Version Control Repository Manager:

  1. Launch the Services program.

  2. Right click the Version Control Agent service.

  3. Select [Properties].

  4. Select 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 Version Control Repository Manager using the Version Control Agent.

Why do I see a reboot required, Status 2 in the Version Control Agent Log but not in the Install Log?

Solution: The Version Control Agent Log page contains information logged by the Version Control Agent during its operation. The Version Control Agent 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 Version Control Agent 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.

Why do some of my components not install and report in the log as failed, although the hardware exists on my server and requires the update?

Solution: Some HP components are not written to support silent installation, such as HP NIC drivers for Windows NT, which is an installation that requires user intervention. The Version Control Agent can only install components that are written for silent installation. The following components currently do not support silent installation:

  • NetFlex/Netelligent Adapter Driver for Windows NT 4.0

  • Ethernet/Fast Ethernet or Gigabit NIC Driver for Windows NT 4.0

  • Array Redundancy Software for Windows 2000

In the event silent installation is not supported, HP recommends the following procedure

  1. View the Version Control Agent log and determine which component failed.

  2. Access the failed system, and browse to the Version Control Repository Manager repository from that system.

  3. Browse to the Catalog and identify the component.

  4. Click the component. The Component Details page appears.

  5. Click the link associated with the component at the top of the Component Details page to download the failed component.

  6. Save the component to the system.

  7. Install the component manually.

In the event components fail because they are not signed by Authenticode technology or have not cleared the Microsoft Windows logo testing, check the target system for messages.

If these components do not or will not install without user intervention or silently, why does the Version Control Agent report Failed to Install?

Solution: At the current time, the Version Control Agent does not differentiate between silent and non-silent components.

I am unable to save the log entries in a file and following Microsoft Internet Explorer message appears, "Internet Explorer cannot download clrlogwiz&logsave=true from the local host". What is happening?

Solution: A browser setting is preventing you from writing to the log file.

HP recommends the following actions:

  1. From Microsoft Windows Explorer, click ToolsInternet OptionsAdvanced.

  2. Under the Security section, deselect Do not save encrypted pages to disk.

  3. Click [OK]. The settings are saved.

After installing the System Management Homepage from the installation icon in the Version Control Agent, the Version Control Agent log disappeared and indicated that the page cannot be displayed. What happened to the log?

Solution: The System Management Homepage 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 System Management Homepage again and view the Version Control Agent log directly to determine the status of the installation task.

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

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

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

  2. From System Management Homepage, click SettingsSecurityTrust Mode.

  3. Correct the configuration.

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

Complete information on the security implemented by the management system, where the Version Control Repository Manager is installed, and the managed systems, or System Management Homepage, are available in the Security white paper. To download the Security white paper, go to http://www.hp.com/servers/manage.

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.

The job of the Software Version Status Polling tasks in HP Systems Insight Manager is to retrieve a list of installed software and firmware from systems and obtain the software status from the HP Version Control Agent 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 Systems Insight Manager sends the selected Version Control Repository Manager a list of all the software versions in sorted order. This is necessary so that HP Systems Insight Manager can properly handle searches that include software version comparisons. The Version Control Repository Manager 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 Version Control Agent settings to access the Version Control Repository Manager using the administrator credentials. Why is this happening?

Solution: When System Management Homepage is installed, the Version Control Agent cannot be configured to access a Version Control Repository Manager 2.1 or later using the administrator login credentials. A feature in the Version Control Agent prevents you from using the administrator credentials to ensure that the administrator OS Account for the Version Control Repository Manager is not locked out when the Version Control Agent retries the login to the Version Control Repository Manager several times.

HP recommends that you create an account with administrator privileges to be used specifically by the Version Control Agent. For example, vcadmin.

Why do some of the components display in the inventory for hardware that is not physically located on my server?

Solution: This issue is caused by a conflict between SmartStart and the Version Control Agent and might display with Yellow status icons in the Latest Version and Support Pack columns.

SmartStart installs all components, specifically storage components, for hardware, regardless of the physical location of hardware on the server, for example:

  • 32-Bit SCSI Controller Driver for Windows NT 4.0

  • Drive Array Driver for Windows NT 4.0

  • Smart Array-2 Controllers Driver for Windows NT 4.0

  • 64-Bit/66Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for Windows NT 4.0

  • Smart Array 5x Controller Driver for Windows NT.40

The inventory for these components might display with Yellow status icons, stating an upgrade is needed and available, which occurs when the Version Control Repository Manager configured on the Version Control Agent is cataloged with newer versions of these components.

For example, if your server is configured with components from HP SmartStart CD 5.2 and the Catalog of your Version Control Repository Manager contains new HP SmartStart CD 5.3 components, the inventory of the Version Control Agent displays the previously mentioned items with Yellow status icons. You cannot upgrade these components because the physical hardware does not exist on the system or allow the status icons to display with a Green icon reporting the components are current. The Overall Status also continues to display with a Yellow icon because the Version Control Agent is reporting components that need updating.

You can create a Custom Software Baseline excluding these components and configure your Version Control Agent to use it as its Reference Support Pack. This option enables the Support Pack Version column to exclude these components during its version comparison, which allows your Overall Status to display with a Green icon stating the inventory is current. However, the Latest Version column will continue to display with Yellow icons for these components.

This solution should only be applied to those systems without the storage hardware physically installed.

This problem will be corrected in future releases of the Version Control Agent.

Some of the software installed on the system shown in the Software Inventory of the Version Control Agent is not shown. Why?

Solution: The following components do not appear if you have HP Insight Management Agents 5.20 or earlier installed on the system:

  • Drive Array Notification for Windows 2000

  • PCI Hot Plug Controller Driver for Windows 2000

  • Integrated Management Log Display Utility for Windows 2000

  • Integrated Management Log Viewer for Windows 2000

  • Power Supply Viewer for Windows 2000

  • Power Down Manager for Windows 2000

  • Enhanced Integrated Management Display Service for Windows 2000

  • ATI RAGE IIC Video Controller Driver for Windows 2000

  • Array Redundancy Software for Windows 2000

  • Integrated ATA RAID Management Utility

  • Network Teaming and Configuration for Windows 2000

  • Remote Insight Board Wide Area Network Driver for Windows NT 4.0

  • Integrated Management Log Display Utility for Windows NT 4.0

  • Integrated Management Log Viewer for Windows NT 4.0

  • Power Supply Viewer for Windows NT 4.0

  • PCI Hot Plug Utility for Windows NT 4.0

  • Array Redundancy Software for Windows NT 4.0

  • Power Down Manager for Windows NT 4.0

  • Enhanced Integrated Management Display Service for Windows NT 4.0

  • ATI RAGE IIC Video Controller Driver for Windows NT 4.0

  • ATI RAGE XL Video Controller Driver for Windows NT 4.0

  • Integrated ATA RAID Management Utility

These components are displayed in the Software Inventory of the Version Control Agent if you install HP Insight Management Agents 5.30 or later.

HP Version Control Repository Manager

After updating my Windows XP system with Service Pack 2, I am unable to access the HP Version Control Repository Manager. What happened?

Solution: The Windows XP Service Pack 2 implements a software firewall that prevents browsers or other clients from accessing the ports required for access to the Version Control Repository Manager. To resolve this issue, you must configure the firewall with exceptions to allow access through the ports used by HP Systems Insight Manager, Version Control Agent and other Version Control Repository Managers.

HP recommends the following actions:

  1. Select StartSettingsControl Panel.

  2. Double-click Windows Firewall to configure the firewall settings.

  3. Select Exceptions.

  4. Click [Add Port].

    You must enter the product name and the port number.

    Add the following exceptions to the firewall protection:

    ProductPort Number
    HP SMH Insecure Port:2301
    HP SMH Secure Port:2381

    Note: For more information regarding HP Systems Insight Manager secure and insecure ports, refer to the HP Systems Insight Manager User Guide, Troubleshooting, Login Problems section.

  5. Click [OK] to save your settings and close the Add a Port dialog box.

  6. Click [OK] to save your settings and close the Windows Firewall dialog box.

This configuration leaves the default SP2 security enhancements in tact, but will allow traffic over the ports previously indicated. The secure and insecure ports must be added to enable proper communication from your browser and other clients that access the Version Control Repository Manager.

When I try to configure a component using the latest ProLiant Support Pack, the component configuration wizard appears in my Mozilla browser with a screen that has all configuration screens included in one individual screen. I am unable to save any configuration, and a blank screen appears in the wizard when I click [Save]. Why is this happening?

Solution: The component configuration included in ProLiant Support Pack 7.10 and earlier might not succeed when using the Mozilla browser because there are dependencies contained in the component's configuration HTML.

To resolve this issue, use Internet Explorer 6.0 SP1 or later, or HP Remote Deployment Utility to configure components.

The Upload Support Pack task does not work. What is happening?

Solution: The browser settings to download and run ActiveX controls must be enabled for the Upload ProLiant Support Pack task to work.

To configure the Microsoft Internet Explorer security settings

  1. From the Microsoft Internet Explorer toolbar, click Tools and select Internet Options. The Internet Options dialog box appears.

  2. Click [Custom Level]. The Security Settings dialog box appears.

  3. Under ActiveX controls and plug-ins, Download signed ActiveX controls, select [Enable].

  4. Under Run ActiveX controls and plug-ins, select [Enable].

  5. Under Script ActiveX controls marked safe for scripting, select [Enable].

  6. Click [OK] to save your settings. You are returned to the browser.

When I copy the files from a ProLiant and Integrity Support Pack into the repository manually, I might not see all of the new components listed on the Catalog page. What can I do to see these files?

Solution: When you copy files into the repository manually without using the Version Control Repository Manager, the repository might need to be rescanned and the catalog rebuilt. For more information regarding copying files into the repository manually, refer to the Version Control Repository Manager help files, Updating the Repository Manually from the HP SmartStart CD (for ProLiant servers) or HP SmartSetup CD (for Integrity servers). For more information regarding rescanning the repository, refer to Version Control Repository Manager help files, Rescanning the Repository and Rebuilding the Catalog.

The rescan functionality does not seem to work on my Version Control Repository Manager Why is this happening?

Solution: The rescan functionality does not work when the Auto Update is in progress. After the Auto Update is complete, the repository rescans itself, and all the components and ProLiant Support Packs downloaded during the Auto Update are displayed in the catalog.

During the automatic update, I received the following error, The automatic update failed because an error occurred while retrieving the download site catalog. The error message referenced an error for the catalog.xml file and an error code 12007, 12015, and etc. What does this mean?

Solution: While the automatic update process was in progress, the Version Control Repository Manager was unable to connect to the website.

HP recommends the following actions:

  • Verify that the hardware connection for the Internet is secure, for example, phone line or cable, to the machine where the Version Control Repository Manager is installed.

  • Verify the domain name server (DNS) settings are correct.

  • Verify that the proxy server, port, and proxy user authentication settings are correct.

After I use the 'Upload a Support Pack' feature, why are some of the new Support Packs marked invalid and other files missing, even though the upload appeared to complete successfully?

Solution: The upload completes once all files have been transferred from the local system to the Version Control Repository Manager. For performance reasons, transferred files are queued for cataloging as a separate activity at the Version Control Repository Manager server, meaning that upon completion of the upload, not all of the files will immediately appear in the catalog, and uploaded Support Packs may be marked as invalid until all files have been cataloged, usually within a few minutes.

Why are there multiple log entries in the Version Control Repository Manager log about components being modified or added after a ProLiant and Integrity Support Pack is uploaded?

Solution: The Version Control Repository Manager logs the specific additions that it receives from the upload control, but it also monitors the repository directory as a separate activity. The operating system provides separate notifications about changes in the repository directory, and these can result in multiple log entries, which can be ignored.

After setting the repository directory with the encryption attribute and restarting the Version Control Repository Manager service, none of the ProLiant Support Packs are displayed in the Version Control Repository Manager Catalog page. In addition, the Log page indicates that a component has been deleted from the repository. Why aren't the ProLiant Support Packs displaying?

Solution: This problem is usually caused by a change in security permissions or encryption of the repository directory. Always check that the repository directory permissions are set so that the Version Control Repository Manager Windows Service has full access to the repository directory. Additionally, the Version Control Repository Manager does not support the encryption attribute. If you encrypt the repository directory, the ProLiant Support Packs are not deleted, but they will not display on the Version Control Repository Manager Catalog page.

HP recommends the following actions:

  1. Stop the Version Control Repository Manager service.

  2. Double-click My Computer. Windows Explorer appears.

  3. Right-click on the repository directory and select Properties.

  4. Select the General tab.

  5. Click [Advanced].

  6. Deselect Encrypt contents to secure data.

  7. Click [OK].

  8. Click [OK] again. Your settings are saved.

  9. Start the Version Control Repository Manager service. The ProLiant Support Packs are displayed on the Catalog page.

Can I use the software or firmware criteria in HP Systems Insight Manager to tell which version of a Support Pack is installed?

Solution: Generally, ProLiant Support Packs cannot be used for comparison when developing a software update search. However, if you must compare ProLiant Support Packs, use the following guidelines when selecting ProLiant Support Packs to compare:

  • The only comparison you can use with a ProLiant Support Pack is Equal To.

  • HP Systems Insight Manager cannot determine whether a ProLiant Support Pack was installed on a system, only whether all of the components in a ProLiant Support Pack are installed on a system. A targeted system is returned by a search that compares ProLiant Support Packs only if every component in the ProLiant Support Pack is present on the targeted system.

It is unlikely that all of the components in a ProLiant Support Pack will be installed on any system. This causes most searches that include Support Pack software criteria to return no systems.

Miscellaneous Problems

Should the Version Control Repository Manager be installed before running Discovery in HP Systems Insight Manager, and if so, why?

Solution: While it is not essential, it is a good idea to install a Version Control Repository Manager before running Discovery. Be sure that this repository trusts HP Systems Insight Manager. Refer to Setting up Trust Relationships in the HP Systems Insight Manager User Guide for more information on trust relationships. It is a good idea to install a Version Control Repository Manager 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 did the Version Control Agent encounter an error while obtaining the software and firmware inventory?

Solution: The Version Control Agent requires the Windows Foundation Agents 5.30 or later. You must install SNMP and the Windows Foundation Agents. For Version Control Agent for Linux, you must install HP Server Management Application and Agents (hpasm RPM 7.00 or later. To download the agent, go to http://www.hp.com/servers/swdrivers. You must also ensure that you have configured at least a read-only community string in the SNMP security settings.

Why is it that when I search for systems with Foundation Agents for Windows in HP Systems Insight Manager, 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 Version Control Agent alone?

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

Does HP have any intention of disabling the Install icon on those components that do not install silently or without user intervention in future releases?

Solution: Yes.

The Version Control Agent or Version Control Repository Manager display as links under the Integrated Agents list on the System Management Homepage, but the application is missing from the version control category on the System Management Homepage's Home tab, or the category does not display at all. When I click on the link under the Integrated Agents, a page displays indicating The application is not available.

Solution: On Windows, the associated Win32 service is stopped. You must restart the HP Version Control Agent or HP Version Control Repository Manager's Win32 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 NT Event Log as well as the application's log for additional information.

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