Release Notes

Symptom:

During the installation process the product upgrades a previous version of the SPI without problem, but does not remove references to the previous version from the registry. This causes an error message to occur during the removal of the previous SPI when you are doing a removal of the OVO for Windows product.

Solution:

The upgraded SPI needs to be removed first using Add/Remove Programs before doing a complete removal of OVO for Windows. Because the previous version's uninstall tries to run again during the removal of the OVO for Windows product, error messages occur because files needed during the uninstall have already been removed. This is only an issue when the SPI has been run separately from the installer to upgrade a version of the SPI installed as part of OVO for Windows 7.0. If the SPI has been installed by the installer, it will function correctly.

QXCR1000220982

Summary: OVO Windows Management Server unable to start up on first cluster node after moving the group from node two to node one.

Symptom:

When installing OVO on a cluster, moving the OVO Windows Management Server cluster group after install from node two to node one makes OVO unable to start on node one.

Solution:

During the install the named pipe alias in the SQL Server Client network configuration utility was not removed, causing the failure of the OVO management server on node one. Remove the SQL Server alias in the client network configuration utility and reboot the first cluster node. Following this, switching the OVO management server between the two cluster nodes works properly.

Reporter and Reporting Component

QXCR1000127876

Summary: Reporter cannot be installed. An error message appears.

Symptom:

After several error messages, the system reports that the installation completed successfully. However OpenView Reporter is not installed.

Solution:

1. From the Start menu, select Run.
2. Enter RegEdt32.exe to run that utility.
3. Find the HKEY_LOCALMACHINE window.
4. Find the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Reporter key and select it.
5. From the Security menu, select Permissions.
6. Add the user group CREATOR OWNER and give it "Full Control" access.
7. Try to install Reporter.

If this does not succeed, make sure that the current login is covered by the CREATOR OWNER group; add the current login user account if it is not. If this still does not work, attempt this for the Administrator account, delete the registry key, and allow the installer to recreate it on the install.

QXCR1000157078

Summary: Unable to read reporter.xml.

Symptom:

The console is unable to display the reports tree and the message ""The xml page cannot be displayed" appears in the browser.

Solution:

The xml file may contain the "&"sign from the OVO groupings. Change the groups and remove the "&" sign from the group name.

Minimize security risk from system administrator password being written to the installation log file.

During the install of the reporting component, the Reporter database passwords are written into the installation log file.

Solution:

The installation file is in your default OpenView directory:

\data\HPOVInstall\reporter_install.log

You may want to minimize this potential security risk by taking one of the following actions:

1. Remove the passwords from the file. Look for the following keywords: "DBADMINPASSWORD," "GetDataBaseConnection," and "PASSWORDCLEAR". Remove the passwords or the entire line containing the keywords.
2. Increase the security on the file.
3. Remove the install.log file from your system (this is the least preferred solution).

QXCR1000048890

Summary: Cannot modify passwords after encryption.

Symptom:

Cannot modify passwords for reporting component database logins or the openview password in the registry after encryption.

Solution:

With the new utility OvrPwdEncrpt.exe you can change these passwords after encryption:

• The openview password into the registry
• The ovdb_user's password stored into the reporting component database.

Usage:

OvrPwdEncrpt <-R|-O> <New Password>
where:

-R = will change the openview's password.
-O = will change the ovdb_user's password.
<New Password> = The new password which is to be encrypted.
Examples:

OvrPwdEncrpt -R phoenix
This will change the openview's password to phoenix

OvrPwdEncrpt -O phoenix
This will change the ovdb_user's password to phoenix

The OvrPwdEncrpt.exe file is located in this directory:

<OvInstallDir>\bin

Patches and Fixes

http://support.openview.hp.com/cpe/patches

After installing the software, please check the web site to view the latest available patches. Patches should be installed before you do any configuration.

Required Patches for the AIX.4.3.1 agent include the following:

• bos.up version 4.3.1.1
  Base Operating System Uniprocessor Runtime
  PTF: U455996
  
• bos.mp version 4.3.1.1
  Base Operating System Multiprocessor Runtime
  PTF: U453884
  

Patches can be downloaded from the IBM web site at this location:

http://www.ibm.com/support/us/

Before uninstalling OVO 7.0, install the following patch:

Install the OVOW_00003 patch on your OVO 7 management server prior to uninstalling OVO for Windows 7.0 to prepare for upgrade. You can find this patch on the HP OpenView web site, www.openview.hp.com. From this web site select Support. Then select the Software Patches link in the Using Products section. In the pulldown menu for selecting products, choose Operations for Windows --> Release A.07.00. The OVOW_0003 patch will be listed. Instructions for installation are available with the patch.

Self Management Policies

All policies delivered with the OVO for Windows 7.5 Self Management module have the version 6.0.

New Policies

The following policies have been added to this release:

• VP_SM_OVOWServices (Monitors the following services)
  • OvAutoDiscoveryServer
  • OvDnsDscr
  • OvEpMessageActionServer
  • OvMsmAccessManager
  • OvPmad
  • OvSecurityServer
  • OvOWReqCheckSrv
  • Windows Management Instrumentation
• WP_SM_DeleteNodeFromReporterDB

  This policy listens for NodeDeletion events on WMI and deletes the respective nodes from the Reporter database.

• VP_SM_Cluster Consistency Check

  This policy is installed only in a clustered installation and checks the sanity of a clustered OVO for Windows installation.

Changed Policies

The following policies have changed in this release:

• VP_SM-Server_EventLogEntries

  Additional rules have been added.

• OvSvcDiscErrorLog

  Additional rules have been added.

• OvSvcDiscServerLog

  Additional rules have been added.

Obsolete Policies

The following policies have been replaced by the policy VP_SM_OVOWServices:

• VP_SM-OV AutoDiscoveryServer
• VP_SM-OVDnsDscvryService
• VP_SM-OVEpMsgActionServer
• VP_SM-OVEpStatusEngine
• VP_SM-OVMsmAccessManager
• VP_SM-OvSecurityServer
• VP_SM-WMI

Changes in the Sample Policies

The following sample policies have changed in this release:

New Policies

• OvOWSubmitNSByFlag
• OvOWopcmsgTTNS
• OvOWSubmitNSByRule
• OvOWUpdateTTStateChange
• OvOWSubmitTTByFlag
• OvOWUpdateTT
• OvOWSubmitTTByRule

Changed Policies

The following policies have changed in this release:

• FwdMsgAsEmail

  Added rules to prevent endless loops.

• FwdMsgAsHtmlEmail

  Added rules to prevent endless loops.

• Synchronize state changes with target server

  Shortened name. The policy was previously named "Synchronize state changes with target management server. "

• Synchronize state changes with source server(s)

  Shortened name. The policy was previously named "Synchronize state changes with corresponding source server(s)".

Known Problems, Limitations, and Workarounds

Vantage Point References

Occasionally the previous VantagePoint product name or its VP abbreviation may appear as an application name in a message browser message, in error messages, or in a policy name. This is not a cause for concern.

Disk Space Management for Graph Output Files

Summary:To manage disk space, you may want to do periodic cleanup of generated graph output files.

Symptom:

When graphs are generated, the HTML and GIF files are written to a directory based on the parameters used to generate the graph. All files will be located in this directory:

<installation_directory>\data\webpages\VPI_All_Customers\

Solution:

Periodically clean out old files from the subdirectories under <installation_directory>\data\webpages\VPI_All_Customers\ for disk space management.

Additional Backup Steps for Disaster Recovery of a Hard Drive Crash

Summary: To recover from a crash of your management server's hard drive you may want to back up additional files onto another media to be used in disaster recovery.

Solution:

After the usual backup is completed, two files are generated:
c:\Program Files\HP Openview\Data\Databases\Backup\openview.dat_bak
C:\Program Files\HP Openview\Data\Databases\Backup\openview.log_bak

These files, along with all the files in the following folder, should be either copied to a share or included in a backup process to another media (such as tape):

C:\Program Files\HP Openview\Policies\*

It is important that this copy/backup of additional files be done after the usual backup is complete, to ensure that the files have been regenerated and are consistent.

In case of a crash of the management server hard drive, the recovery is to reinstall the OS, reinstall OVO for Windows, get the files above from the backup media/share and continue with the recovery as described in the online help.

Using logfile policies in non-English environments

By default, all OpenView-supplied logfile policies are set to monitor English-language managed nodes. If you want to monitor logfiles on nodes that have a different language environment, you must change the logfile character set for each policy to match the character set of the node where it is deployed. Such policies will also function only if the monitored logfiles have not been translated into a non-English language.

Using eventlog policies in non-English environments

By default, all OpenView-supplied eventlog policies are set to monitor English or Japanese language managed nodes. If you want to monitor eventlogs on nodes that have a different language environment, simply open each eventlog policy and save it again. This automatically sets the logfile character set to the one appropriate for the node's language environment.

Possible problem with RedHat 6.2J and 7.0J

The deployment of some policies using certain Japanese characters might fail on RedHat 6.2J/7.0J with the following error message:

Cannot read template file.

The error occurs because certain character conversions on RedHat 6.2J and 7.0J are experiencing problems due to a problem in the iconv function embedded in the OS. Because RedHat has officially obsoleted those versions, it is not possible for HP to fix this problem or to get a patch from RedHat to resolve this issue.

The only policy shipping with OVO for Windows 7.20 and its SPIs that is affected by this problem is "OvSvcDiscErrorLog_jp." As a workaround, you can do one of these things:

• Use the English equivalent "\"OvSvdDiscErrorLog."'
• Update to RedHat 7.1J or higher, which does not appear to have this problem.

Existing Crystal 8.5 Templates Known Problems and Workarounds

The templates of Crystal 8.5 (or earlier version) when used with Reporter 3.6 (which uses Crystal 10 binaries), may break the HTML files created by the "Repcrys" module. You may have to change the 8.5 templates based on the issues encountered. Please note that all the out-of-the-box Crystal Reports templates that accompany Reporter 3.6 Full are properly converted and should work without any issues.

NOTE:The following changes are applicable for users who want to use their customized Crystal 8.5 templates with Reporter 3.6.

All the reports can be edited with CR 8.5 with the following modifications, to be able to support Crystal 8.5 and Crystal 10 from the same templates. If it is required to support text fields longer than 254 characters (or 127 Japanese characters), the reports must be edited using Crystal 10, as there is no way to do this with Crystal 8.5. Any reports that are edited using Crystal 10 will not work on the Reporter 3.5 system.

Summary: Crystal 10 does not truncate fields based on the field length defined in the report template. So in the exported HTML files, if the data in the database is longer than the field length defined in the report template, the data will overlap with the neighboring field.

Solution: Modify the templates to validate all of the fields to make sure the field defined in the report template is at least the same size as the field in the Reporter database. It might not always be possible to have the full length of the database fields displayed. For example, object or application fields with 254 characters would not leave any further space in the same line to display further information. If possible, the according field should be configured with the "Can Grow" option, so that the field automatically extends vertically. If this interferes with the report design, it is possible to set the "Can Grow " option with the maximum number of lines=1. In this case, CR10 truncates data again, but only for formula fields and with a different mechanism. Plain database field objects must be placed into a formula and it must be checked if the new truncation mechanism does not truncate important information.

Summary: Exported HTML reports will not have space in the left-hand side.

Solution: Modify templates for left-hand space manually by setting the margin for the report. Adding an additional 0.25 inch margin should solve the problem.

Summary: The hyperlink used to display banners is not parsed and so becomes visible text. The "less than" and "greater than" symbols are translated to character entities, which prevent the text being recognized as HTML.

Solution: The solution is to use OLE object linking to get some minimal linking of banners working with CR 8.5 and CR 10. Instead of embedding the banner in the report, insert an OLE link to the banner graphic in the report. This requires a fixed location and size in the banner files; you can only exchange with banners of an equal size. If you want to include your own banners in the reports, you will need to purchase Crystal Reports 10 and modify the reports to include the banners. As you include the banner, you can size it properly inside the report.

Summary: Boolean or single bit flag fields in the database (such as the SYSTEMS table's EXCLUDE column) might not migrate correctly to Crystal Reports 10. The template seems to expect a numeric value in a selection formula that should evaluate to a Boolean.

Solution:

Bit flags cannot be used with CR 10 and Oracle. Oracle knows only the numeric data type and accordingly, CR 10's data type checking will cause an error if true/false checks are used. Therefore, such fields must be implemented as Integer across all databases and the reports should use "field=0" checking. Using "=0"will work for both Oracle (numeric field) and SQL Server (bit field).

Summary: Crystal Queries are no longer supported with CR 10.

Solution:

The reports have to be changed to work without queries. If this is not possible (for example, if a UNION must be used without any other leading table) you might be forced to create views in the database to cover this functionality.

Summary: Every run of Repcrys binary creates a set of files with distinct GUIDs as filename and .png as extension in the directories that have the generated HTML files. You would need only the latest set of .png files to view the generated HTML files.

Solution:

Schedule "Repmaint -clean" so that the unwanted .png files can be removed. It should be scheduled well after RepCrys has finished generating reports.

Summary: When Crystal 8.5 templates are exported using Reporter 3.6 with the "Page Break" option set, the navigational links in them will be broken. This happens because there is a difference in the name of .html files that are generated when exported using Crystal 8.5 and Crystal 10.

Solution: Reporter 3.6 uses Crystal 10 and on exporting with page break, the html are named as default.html, where n=1,2,3..k. In the previous version of Reporter, which uses Crystal 8.5, the generated html files used to be named as default.htm and default.htm where n=1,2,3...k. The Crystal Reports designer needs to be used to make the appropriate changes to the links in the report template.

Summary:Formulas with the global variables and running total fields cannot be used in charts, maps, or cross-tabs.

Solution:

In Crystal 10, this is no longer possible. To solve this problem, the report needs to be redesigned to work without the use of global variables in charts.

Summary:Crystal Reports 10 aligns, but does not correctly align, fields with borders.

Solution:

Remove the border from the field formatting and place an empty field with border on top of the value field.

Summary:Crystal Reports 10 cuts the blank spaces or adds empty sections at the bottom of the report.

Solution:

If the last line of the exported report is not completely visible in Internet Explorer, insert a blank text field in the report footer section. Crystal Reports 10 will export the blank section at the end of the report according to the height of the inserted text field.

Graphing Known Problems and Workarounds

The following section contains information on the graphing component.

Data not shown in graph.

Summary: It is possible to draw a graph that shows no data when you expect that data should be shown.

Symptom:

If you get an error message indicating "Could not make connection to agent" or "The metrics in graph <graphname> were not found on this data source" then that indicates that either the grapher could not contact the system or data source requested, or that it contacted it but the list of classes and metrics do not match those required in the graph definition. Please check the graph definition and data source you selected to ensure they are compatible.

Solution: If you are drawing a graph, but that graph is empty, try the following resolutions:

• Verify that the Data Range is not selecting a time when no data exists. Change Date Range to the maximum number and redraw the graph. If you get a graph this time, examine it to determine what dates and times have data available.
• If it appears that the date and time range you selected have data now, but not when you draw a smaller date range, or if you still get a blank graph, you may have the situation where data is present sporadically, or at intervals less than your Points Every setting.

  Change the graph type to Table, and set the Points Every to Unsummarized. When you draw this graph, you should see each data point from the data source. If this table is blank, then there truly doesn't appear to be any data in the data range you selected; try date range All again.

• When data from the data source is present less frequently than your Points Every setting, then you can graph data that appears invisible. Actually it is a graph that is trying to draw a line between one data point (can't be done). You can:
  • Change your graph settings to select a marker for each data point.
  • Change the Missing setting to Previous or zero
  • Change your Points Every setting to be equal or greater than the distance between each data point.

Graphing component cannot connect to agent

Summary: Sometimes the graphing component cannot connect to the agent on a system.

Symptom:

When drawing a graph, you may get a message similar to "Coda not found on "XYZ" (Socket connection was refused)." This indicates that the graphing component was not able to connect to the agent running on that system.

Solution:

1. Check to be sure that the agent is actually running on that system (it may not be installed, or it may have been stopped).
2. Check to be sure that the network between the management server and the selected system is functioning properly.

Configure Microsoft IIS Lockdown Tool security settings for HP Graphing Component to execute

Summary: You must configure the IIS Lockdown tool to enable the execution of the HP Graphing Component.

Symptom:

Microsoft provides the "Internet Information Service Lockdown Tool" (IISLockdown) to help you configure your IIS web server security settings. When using this tool, take care to choose settings that allow the HP Graphing Component to execute. These recommended settings should not significantly compromise your web server security, but you should review them to ensure that they meet your security needs. The HP Graphing Component cannot be used without these settings.

Solution:

The parameter settings are presented based on IIS Lockdown version 2.5. You may have to make adjustments if you are using a different version. The following recommendations are for the HP Graphing Component only. If you have other web applications, they may have additional requirements that should be considered.

Internet Services: The HP Graphing Component uses the Web Service (HTTP). It does not require File Transfer Service (FTP), requirements-mailservice (SMTP), or News Service (NNTP) so these services can be disabled if none of your other applications require them.

Script Maps: The HP Graphing Component does not use any script maps. All can be disabled unless required by another application.

Additional Security: Virtual directories for IIS Samples, MSADC, IISHelp, Scripts, and IISAdmin are not used by the HP Graphing Component. File permissions may be set to prevent the anonymous IIS user from running system utilities, but they must not prevent the anonymous IIS user from writing to content directories. Web Distributed Authoring and Versioning (WebDAV) is not required by the HP Graphing Component and can be disabled.

URLScan: the URLScan filter prevents web server requests that match certain patterns from reaching the web server for processing. If used, the URLScan filter must have its parameters set to allow the HP Graphing Component requests through. These settings are changed by editing the urlscan.ini file.See Microsoft's documentation for more information on using URLScan.

• AllowHighBitCharacters=1: This setting is required if you are running on a system that uses a wide or multi-byte character set such as Japanese. It should be set on all systems because the communications to the Java interface are using the UTF8 character set.
• Verbs: Depending on the setting of the UseAllowVerbs parameter, the verbs will be controlled through either the [AllowVerbs] or [DenyVerbs] sections of the .ini file. The following verbs must be allowed ( or not denied): GET, POST.
• Extensions: Depending on the setting of the UseAllowExtensions parameter, the file extensions will be controlled through either the [AllowExtensions] or [DenyExtensions] sections of the .ini file. The following extensions must be allowed (or not denied): .htm, .jpg, .gif, .xml, .exe.
• URL Sequences: The [DenyUrlSequences] section of the .ini file will disallow URL requests that contain special characters. The following characters must not be denied: \ (backslash), % (percent).

QXCR1000151643

Summary: Closing a graph before granting security access to Java applet causes abort.

Symptom:

When you open a graph or a report, if you close the new window before the graph or report is fully displayed, a C runtime error occurs, and MMC aborts. Closing the graph or report before granting security access to the Java applet (via the Java dialog) is the same situation. In some cases the MMC process is not stopped and must be killed via the Task Manager.

Solution:

To avoid this problem, always allow time for the graph or report to fully display before closing the window. If it seems that it is taking too long to display, close MMC, instead of the single child window. An alternative solution is to draw HTML graphs, which are more quickly displayed.

QXCR1000042889

Summary: Sometimes the symbol in a Java graph legend becomes visible when it has been deselected.

Symptom:

There is a colored symbol on the right side of the graph that can be clicked to hide/show a metric. The symbol and the metric should go away when the symbol is clicked, and come back if that spot is clicked again. Sometimes the symbol becomes visible when it should not.

Solution:

None.

QXCR1000043595

Summary: Graph customizations are lost when using auto refresh on a Java Graph.

Symptom:

If you draw a Java Graph and then change something in the properties (for example, metric color), and then turn Auto Refresh on, the metric color reverts its original color when the graph refreshes.

Solution:

Open the graph in the Design tab, make the customizations you want to see and then save the graph with a new name and redraw it.

QXCR1000153002

Summary: Drawing a Java Graph causes mmc.exe process to become a zombie on exit. A zombie process is one that appears in a list of processes but is not really running.

Symptom:

If a Java graph is launched from the console for display, the console's MMC process will not be properly terminated upon exit and MMC will remain as a zombie process. You may see several MMC processes in Task Manager if you have exited and restarted the console multiple times.

Solution:

Kill the zombie processes to free memory. If you exit and restart the console often in your day-to-day activities, you may want to draw HTML graphs instead of Java graphs to avoid this situation.

QXCR1000043906

Summary: Duplicate graph family names are not allowed in the OVO for Windows Graphs tree.

Symptom:

If a graph family name is manually entered in a graph definition file, and this graph family already exists in another graph definition file used by OVO for Windows, an error window will appear when the console is opened. The error is:

"Missing or invalid graph definition XML stream. This key is already associated with an element of this collection (457)."

Solution:

Edit the graph definition file to use a unique graph family name. If the graph definitions are always edited from the Graph Configuration editor, this problem will not occur. The editor will properly manage the graph family names.

QXCR1000301370

Summary: The generation of different OVO for Windows reports fails because the ServiceReports views were not created.

Symptom:

When you try to open some OVO graphs on an OVO for Windows system using SQL Server 2005 as the underlying database, you will see a "page cannot be displayed" error message and will find some "failed to open rowset" error messages in the status.Reporter log file.

Solution:

If you are running an SQL Server 2005 as the database for OVO 7.5 for Windows, follow these steps:

1. Save a copy of <Install-Dir>\install\OvServiceReports\inst_service_report_db.vbs.
2. Change the line:

   Const REG_KEY_SQLPATH="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\Clientsetup\SQLPath"

   to read as follows:

   Const REG_KEY_SQLPATH="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\Clientsetup\SQLPath"

3. Execute the script from the command line.

After the next report generation, you will be able to see all the OVO for Windows reports.

Console Known Problems and Workarounds

Summary: Performance can vary.

Symptom:

Performance can vary running the remote console on a Wide Area Network (WAN) connection.

Solution:

If performance is unsatisfactory, use the Web console instead.

QXCR1000232377

Summary: The license report incorrectly reports full non-InstantOn OVO for Windows server license as an expired InstantOn licence, even though it is a valid license.

Symptom:

The license report for the "HP OpenView Operations for Windows Manager" product reports a valid, full, permanent or temporary OVO for Windows server license as an expired InstantOn license.

Even though the license report indicates that the license has expired, the OVO server and console work because the license is valid.

Limited edition licenses and full InstantOn licenses are not affected.

Solution:

Install OVOW_00188 or superseding server patch to resolve this problem.

QXCR1000232840

Summary: After you reboot the management server, graphs are no longer available.

Symptom:

No graphs are accessible in the console tree. This can occur if the following sequence of actions is performed:

1. An OVO for Windows management server is installed.
2. Windows system updates are installed through the Microsoft Update Service.
3. The system is rebooted.

Solution:

Copy the file Analyzer.exe, located on the OVO for Windows release media under the folder "install\AnalyzerChanges" to the installed management server folder "HPOV_IOPS\cgi-bin." Restart the OVO console.

QXCR1000153317

Summary: Node deleted improperly if folders are created with the same name as OpenView Defined Groups folders.

Symptom:

A node will be deleted from its OpenView Defined Group even though there are still instances of it managed. This happens if folders with identical names to the OpenView Defined Groups are created anywhere.

Solution:

Do not create folders with identical names as the OpenView Defined Groups. To add the node back into the OpenView Defined Group, open the nodes properties and click OK.

QXCR1000107287

Summary: It is not possible to launch help for Reports or Graphs.

Symptom:

It is not possible to launch help for Reports or Graphs via the toolbar button, context menu or F1 key. Help does not display when any of these choices are selected.

Solution:

Start help elsewhere and look up the information in the index, table of contents, or through search. Make sure you have selected the OVO for Windows help and not the MMC help system.

QXCR1000105435

Summary: Managed node reappears under Unmanaged Nodes with Agents list.

Symptom:

After moving a node from the Unmanaged Nodes with Agents list into managed nodes, it may reappear in the Unmanaged Nodes with Agents list, even though it is also listed as managed.

Solution:

If listed as a managed node, the node is being managed. To remove the node from the Unmanaged Nodes with Agents list, right-click the node name and select Delete from the resulting context menu. You do not have to clean up the list for correct product operation. This is for convenience only.

QXCR1000106863

Summary: Different unique IDs for the same node.

Symptom:

Dragging one node from either of these locations:

Discovered Nodes / Directory or DNS and the same node from
-Discovered Nodes / Microsoft Windows Network

to the managed nodes list in the Configure Nodes dialog box produces two different managed nodes with different unique IDs.

Solution:

None. From the console perspective, a NetBIOS name and a DNS name are different and may or may not represent the same node. NetBIOS names do not have to be the same as the short DNS name, for example. It is also possible that a managed node has multiple IP addresses with DNS records associated with it, which makes it impossible for the console to distinguish that one node in DNS or NetBIOS are one and the same until an agent is installed.

QXCR1000153346

Summary: Selecting the Services tab for a predefined role in the User Roles configuration editor returns an error.

Symptom:

The error message "Database could not return the instance" displays when the Services tab is selected on a predefined role in the User Roles configuration editor when one of the services assigned the role does not exist on the management server. This can happen when a SPI is installed and the service discovery policy installed with the SPI has not yet been deployed to any of the managed nodes.

Solution:

The error message can be ignored and will no longer appear after the service discovery policy has been run.

WARNING: Any changes made to the Services tab of the User Roles configuration editor upon getting the above described error will result in the loss of the predefined role's service assignments.

QXCR1000152865

Summary: Well-known groups cannot be assigned to a user role.

Symptom:

If a well-known group is assigned to HP-OVE-OPERATORS group, it will not be available for assignment to a user role in the User Roles configuration editor.

Solution:

Users contained in the well-known groups will need to be assigned to the HP-OVE-OPERATORS group individually or assigned to a domain group that has been assigned to HP-OVE-OPERATORS group.

Manually removing an agent from a node does not update the node inventory on the management server

Symptom:

If an agent is manually removed from a node (as opposed to removing it by using the OVO console), the node inventory on the management server will not be updated. The "synchronize packages task" cannot update the inventory because the management server has no way of knowing whether or not the agent has been removed or simply cannot communicate with the server.

Solution:

You must manually update the node inventory by removing all packages from the node. Use the instructions found in the online help under the topic "Remove package from node."

QXCR1000153366

Symptom:

Upon launching a tool after it had been stopped because it appeared to be stuck in the "starting" state, an error message appears which reads:

(SC1504) Failed to save Action Request.

Solution:

Launch the specific tool again.

QXCR1000125776

• Tool output received from agents on non-English operating systems does not display correctly.
• Errors result when an event log policy is deployed to a non-English node.

• Deploy a nodeinfo policy to the non-English node. The policy must set the parameters OPC_MGMTSV_CHARSET and OPC_NODE_CHARSET to values that are correct for the node's language. Valid character sets can be found in the manual agent installation instructions for each node OS type.
• This problem is caused by older versions of logfile policies that include a reference to a particular character set. The problem can be corrected by opening the policy in a version 7.0 or later policy editor, then saving the policy and redeploying it.

Addendum

Integrated Service Assurance for Windows, which uses HP OpenView Operations for Windows 7.0, has localized versions available for English and Japanese. While significant effort has been applied to ensure that HP OpenView Operations for Windows 7.0 functions correctly on non-English, non-Japanese localized systems (either management server or managed node), some SPI policies may not work correctly when monitoring applications or Operating Systems localized to other languages.

One area known to be affected by this limitation is the nodeinfo file. The nodeinfo file uses utf8 as the default character set. On some non-English localized platforms, utf8 may be the incorrect character set and will lead to data being displayed incorrectly in the nodeinfo policies. The following table indicates which character set should be used for different languages.

The following table lists the possible nodeinfo character sets and locales that should be used on non-English managed nodes reporting to an OVO for Windows management server.

NOTE: As long as you do NOT use utf8 as codeset on the agent, you can use the same value in a mixed OVO for Windows and OVO for UNIX environment. If you do run in such a mixed environment, you have to use ASCII instead of utf8.

NOTE: If you use utf8 or ASCII as codeset in nodeinfo, there is NO conversion done. All data is taken raw and expected to be in the codeset the management server can handle.

LANG must be set to one of the locales supported by the operating system for the desired language and code set combination, for example Japanese EUC, Simplified Chinese Big5, and so on.

On UNIX managed nodes: LANG is the preferred environment variable used by the OVO agents. If any one of the LC_* variables (LC_ALL, LC_TIME, LC_COLLATE, LC_MONETARY, LC_CTYPE, LC_NUMERIC, LC_MESSAGES) are also set, they must be consistent with the value used for LANG.

Cannot create a service with the same name as a just-deleted service

Symptom:

It is not possible to create a service with the same name as a service which has just been deleted. The service editor denies the creation with an error message that says the service already exists.

Solution:

After deleting the service, close the service editor. When you restart the service editor, you can use the service name again to create a new service.

QXCR1000154371

Summary: Error message occurs incorrectly.

Symptom: The "DLL Versions and Dependencies" report shows the following message:

File OvNtKill.exe has missing dependencies. Cannot find libopc.dll (needed by OvNtKill.exe)

Explanation: OvNTkill is a utility which allows you to emulate the UX kill command on Windows, strictly for agents only.

Solution:

Ignore the error on the report.

QXCR1000152850

Summary: Virtual memory grows.

Symptom:

The virtual memory and the handle count of the monitor agent opsmona.exe grows.

Solution:

The problem is a bad performance counter in the Symantec pcAnywhere product. To solve the problem, it is necessary to remove the performance counter from the registry. The process is described in the Symantec document:

The Windows Event Log fills with error messages after installing pcAnywhere.

document id: 2000083013004512

To access the document:

1. Open the web page www.symantec.com.
2. Go to service and support.
3. Press search and enter the document id.
4. Press search again to display the document.

QXCR1000159846

Summary: MOM: policy editor from remote console does not repaint well.

Symptom:

When the policy editor is hidden and then refocused, it may happen that the policy editor is not refreshed completely.

Solution:

Resize the policy editor window.

QXCR1000152147

Summary: On Japanese systems, the editing area may not refresh correctly.

Symptom:

It may happen that some part of the policy editor area is dimmed (that is, it is not refreshed correctly). That may happen in all policy editors occasionally.

Solution:

1. Minimize and maximize the policy editor window.
2. Resize the window a little bit.
3. Pull some other window on top of the policy editor and then remove it.

QXCR1000129735

Summary: The progress bar in the message browser does not disappear and shows only partial completion of messages loading.

Symptom:

This can happen when messages are being processed (acknowledged) on the server at the same time a server query for (active) messages is being requested by the MMC console.

For example, when the operator selects a service on which to view an active message browser, the MMC Console queries for the count of messages associated with the service before the actual query for messages. This is done to be able to calculate the percentage of messages loaded in the progress bar.

During the time these queries are being requested of the server by the MMC Console, it is possible that some of the messages contained in the queries are acknowledged by another operator or policy. If this happens, then the number of active messages actually returned to the console will be less than the count that was originally expected and the progress bar will not disappear.

Solution:

Simply select a different item in the scope pane and then reselect the previously selected scope pane item on which a browser was displayed. The message browser will reload and the progress bar should behave as expected.

QXCR1000218105

Summary: Message browser fails to receive or fails to properly handle removal of messages from the browser list.

Symptom: When clicking on a service, node group, or node item in the scope pane with a message browser view, one or both of the following errors appear:

"(SC1087) Newly created messages will not be displayed. __InstanceCreation event query failed."' "(SC1349) Message removed from the server will not be removed from the browser. __InstanceDeletionEvent query failed."

Solution: The error messages are appearing because Windows Management cannot handle long notification query strings required by the OVO console to receive new messages from the server or message deletion notifications. This problem is fixed in Windows Server 2003 Service Pack 2. If the service pack is not yet available, install Microsoft hotfix 828653:

http://support.microsoft.com/default.aspx?scid=kb;en-us;828653

QXCR1000125519

Summary: High CPU usage.

Symptom:

While Performance Monitoring on Windows NT 4 systems you might see a high CPU usage of the opcmona.exe.

Solution:

The problem could be caused by the usage of the pdh.dll (Performance Data Helper) version 4. In case this version is used, the monitor agent has to handle it differently, because this dll doesn't offer the functions provided with version 5. This may lead to a higher CPU usage on the system. Check which version of the pdh.dll is on the system in case there is a version 4 or earlier in \system32.

QXCR1000125345

Summary: OVO for Windows policy name cannot contain these special characters.

Symptom:

In OVOW the name of a policy may not contain the following special characters: "%", "*", ">", "<", "|", ":", "\", "/", "?", ",", "'", ";". Some of them, however, are allowed in OVO for UNIX. If you have such a policy on the UNIX server and want to upload it on the Windows server, the tool ovpmutil will fail with an error message telling you that the policy name contains invalid characters.

Solution:

Before you download the policy on the UNIX system, rename it so that the name does not contain the characters shown above.

QXCR100012546

Summary: Cannot copy policies directly to a mounted network drive.

Symptom:

It is not possible to download policies directly into a directory of a mounted network drive. For example, ovpmutil cfg pol dnl o:\policies /p \Samples will fail if the drive 'o' is not a local disk.

Solution:

Download the policies into a directory of a local disk first and later copy the files to the network drive.

QXCR1000106751

Summary: Opening a new window from a report window will create a view that is unusable for Policy Management.

Symptom:

If a new window is created while the top window is showing a report, and that new windows is used to navigate to policy management, an exception dialog is displayed and the console will close down.

Solution:

Option 1: If possible do not create a new window with the report view as the top window. Always create a new window by right clicking on a console tree item and select New Window From Here in the context menu.

Option 2: If a new window has been created from a report view, right click on the item in the new window (Operations Manager:machinename) and select New Window From Here to create a new window. The new window can now be used to navigate the policy management hierarchy.

QXCR1000125625

Summary: Must use OVO for Windows 7.0 to use RMV ovpmutil option.

Symptom:

The option "RMV" of ovpmutil does not work.

Solution:

The option "RMV" works only for *.mm files that have been created with OVOW 7 or later. Thus, please download the policies with OVOW 7 and not with a previous release.

QXCR1000125775

Summary: Recreated logfiles not processed properly.

Symptom:

If a logfile policy is created with the option "close after reading" disabled, there is misleading behavior. If you remove the logfile which is processed by the logfile encapsulator and create a new one with the same name, the logfile encapsulator does not determine that new file until 20 intervals have passed.

Solution:

If you want to use such a procedure to store a logfile with a different name and create a new one instead, it is strongly recommended that you enable the option Close after reading.

QXCR1000125936

Summary: Do not use package names with non-ASCII characters for cluster support.

Symptom:

Cluster support does not work with software package names containing non-ASCII characters.

Solution;

Rename packages.

QXCR1000231091

Summary: Tracemon cannot be launched due to an error when trying to connect to the local configuration server.

Symptom:

The following issue was found with certain OVO/OVIS co-installations. The OVTrace.exe file is still on the system but no longer registered as Service. Therefore, when the user calls tracemon, the following error is displayed:

"Error trying to connect to local configuration server" - "Cannot use tracemon "

This problem can be reproduced in the following test setup:

1. Install OVIS 5.20
2. Install OVOW 7.5
3. Install OVIS 6.0

After the final upgrade, vpstat will show that the OVTrace service is missing.

Solution:

To restore the OVO trace service, start the old trace server manually using the following command:
<OvInstalldir>\lbin\xpl\trc\trcinst /ccl

QXCR1000231281

Summary: Linux agent OS attributes reported do not match the OVO server's OS attributes.

Symptom:

Adding Linux OVO agents either via direct Add Node or via Drag-Drop from the "Unmanaged Node with Agents" list might potentially configure invalid OS attributes to the Node Properties and cause a deployment failure with the following error message:

"(PMD183) One or more attributes of node {917C....} are not valid. Check the system type, the OS type, and the OS version."

Solution: To solve this issue, manually open the Node Editor and select the proper platform type, OS, and version.

QXCR1000229087

Summary: The AutoPass user interface causes the calling OVIS application to hang when closed.

Symptom:

When you close the AutoPass 5 interface using a method other than clicking on File -->Close, it can cause the parent application to hang or to receive an application error.

Solution:

When using the AutoPass 5 interface from any OV application, close it using the File -->Close menu option.

Web Console Known Problems and Workarounds

QXCR1000232876

Summary: Cannot cancel a job in the web console.

Symptom:

When a job is canceled in the web console, it can happen that the results are not displayed you see a generic "This page cannot be displayed" message in the resultsl pane. In this case, the job is deleted but because of an internal exception, the result page is not displayed.

Solution:

Install OVOW_00188 or superseding server patch to resolve this problem.

QXCR1000232884

Summary: Canceling the same job twice in the web console causes an error.

Symptom:

If a job is deleted in the native console, the web console is not updated immediately, so it is possible that you could delete a job in the web console that has already been deleted. In this case, the web console displays a generic "This page cannot be dislayed" message in the result pane.

Solution:

Install OVOW_00188 or superseding server patch to resolve this problem.

Documentation Errata and Corrections

The HP OpenView Operations for Windows product provides printed installation and upgrade guides, electronic manuals, and online help to assist you with licensing, using, and configuring OVO to meet your needs. Manuals are available in .pdf format and are located on the product media disk labeled HP OpenView OV Operations 7.5 for Windows Startup, in the Documentation directory.

You may experience some difficulty in opening and viewing .pdf files if you are using Internet Explorer 5.5. If so, try opening the Acrobat Reader before opening the pdf file you want to view. You can open and print any .pdf file by starting the Acrobat Reader and navigating to the directory that contains the file you want to view.

QXCR1000232106

Summary: Online help for the topic "ovowconfigexchange" uses the name "node group" in a misleading way.

Symptom:

The online help topic "ovowconfigexchange" states that for OVO for UNIX you cannot have a node within several node groups.

Solution: This documentation is incorrect. It is possible to have a node within several node groups. The term "node group" in this context is used to mean the node layout groups (hierarchy groups) of OVO for UNIX.

QXCR1000232143

Summary: The help topic "Configure using registry keys" is incomplete.

Symptom:

The text says "A prerequisite for message forwarding is that on each management server all nodes are known from which messages may be forwarded".

Solution:

The following additional information should be included:

Alternatively, on OVO for UNIX you can add nodes for external events that match the message nodes. If you do so, however, the OVO for UNIX user will not be able to start or restart automatic and operator-initiated actions. A node for external events is a pattern that can match a range of node names or IP addresses.

QXCR1000108188

Summary: Unwanted policies left on nodes.

Symptom:

If a managed node is down or disconnected from the management server during an uninstallation, unwanted policies remain on the node.

Solution:

Remove a "ghost" policy following these steps, which are also documented in the "New and Upgraded Smart Plug-ins CD Installation Guide." Disregard the instructions contained in the help topic "Delete policies manually on the node."

1. At the managed node, stop the OpenView subagent (select Control Panel-->Administrative Tools-->Services-->HP ITO Agent; right-click and select Stop.
2. Manually delete policies by opening directories, selecting them, right-clicking, and choosing Delete. Locations for policy types are folders: <agent>\<file folder>\<File_GUID>. Specific folders are: Nodeinfo, Service Discovery, Flexible Management, and Config File.
3. For remaining policy types, remove corresponding files from: <agent_directory>/conf/OpC/vpwin/<file folder>.
4. Restart the OpenView subagent by selecting Control Panel-->Administrative Tools-->Services-->HP ITO Agent; right-click and select Start.

ovowconfigexchange does not support codeset conversion for ISO 8859-15

Symptom:

It is not possible to choose ISO 8859-15 for codeset conversion with the ovowconfigexchange tool.

Solution:

Use codeset ISO81 (a keyword for ISO 8859-1), which is similar to ISO 8859-15, but does not include the Euro symbol. Support for the ISO 8859-15 codeset will be added in an upcoming patch.

QXCR1000231785

Summary: Help topic Configure MsgForwarding.ini contains incorrect rule name.

Symptom:

The help topic states that only the first "MESSAGETARGETRULE" that matches is evaluated. This is incorrect.

Solution:

The topic should say "MESSAGETARGETRULE"

Typographical error in help topic "ovowconfigexchange"

The text ISO82 (for ISO88591) is incorrect. The text should be ISO82 (for ISO88592)

Internationalization and Localization

Refer to the HP OpenView Operations Installation Guide for more details on using OVO for Windows in other countries.

OVExtract Utility

The output file path and file name must be in ASCII format. POV Auto Pass Licensing Program: You will see only English text for all installations, even if your locale is set to German (or any non-English OS). Please note:

1. Licensing screens on any OS other than the ones supported by the product will default to the default locale specified by the product. Supported locales and the default locale are specified in the .pdf file for the product.
2. If the default locale of the product is not supported by HPOV Auto Pass, or if the resource files corresponding to this locale are missing, then licensing screens are shown in English (the default locale of HPOV Auto Pass).
3. If the report, import, and export screens are launched by the product via SM API calls, the above two scenarios apply.
4. If the report, import, and export screens are launched via the executable programs provided in HPOV AutoPass software, they will show in the locale supported by HPOV Auto Pass and will default to English under exceptional cases.

System and input locale settings

Be sure that the system default locale setting and any input locale settings are set to Japanese. OVO for Windows does not support configurations that mix locales.

QXCR1000231728

(Applicable to the English release only)

Summary: Script file cannot be found on Japanese/Korean/Simplified Chinese system.

Symptom:

The following command line tools fail on Japanese/Korean/Simplified Chinese sytems with the error message that the needed script cannot be found.
-opcragt
-ovownodeutil
-OvOWRAgtS
-ovowreqcheck
-ovowtoolutil

Error message:

Input Error: Cannot find script file "<OVOW_install_dir>\nls\<1041|1042|2052>\scripts\command_name>.vbs"

Solution:

Install OVOW_00188 or superseding patch to resolve this problem.

QXCR1000153277

Summary: Change logfile policies to ASCII character set.

Symptom:

When deploying logfile policies to systems in which the language has been set to non-Latin languages (Polish, Chinese, Korean, etc.) the following error occurs:

EventID: 0x00000400 (1024) - (FM) Error: OvEpItoAdapter: 
    (MS194)RPC call failed ((NUL16389E) Unsufficiant error ) 
    Can't read template file 'HPCTLMH'.

(PMD36) Error: Unable to install policy
    WINOSSPI-ADS_ADCFwdAllWarnErrorMSADC on node with Primary Node
    Name or Communication Path HPCTLMH
    (NUL16389E) Unsufficient error (0x80004005). ...

The problem does not occur on systems set to Italian, English, Spanish, German, and French.

Solution:

To work around this problem, change all logfile policies to the ASCII character set and redeploy the policy to the node.

Trademark Notices

Adobe(TM) and Adobe Acrobat(TM) are trademarks of Adobe Systems Incorporated.
Microsoft is a U.S. registered trademark of Microsoft Corporation.
Windows NT Windows 2000 are U.S. registered trademarks of Microsoft Corporation.
Windows and MS Windows are U.S. registered trademarks of Microsoft Corporation.
Pentium is a U.S. registered trademark of Intel Corporation.
UNIX is a registered trademark of The Open Group.
All other product names are the property of their respective trademark or service mark holders.

Support

Please visit the HP OpenView web site at:

http://managementsoftware.hp.com/

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

You can also go directly to the support web site at:

http://support.openview.hp.com/support

HP OpenView online software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valuable support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

NOTE: Most of the support areas require that you register as an HP Passport user and log in. Many also require an active support contract. To find more information about support access levels, go to the following URL:

http://support.openview.hp.com/access_level.jsp

To register for an HP Passport ID, go to the following URL:

https://passport.hp.com/hpp2/newuser.do

To view release notes and other documentation, go to the following URL:

http://ovweb.external.hp.com/lpe/doc_serv/

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL:

http://www.adobe.com

Legal Notices

The information contained herein is subject to change without notice.

The only warranties for HP products and services are set forth in the express warranty statement accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.