| Defect No |
Details |
| 13982 |
Problem: When you run a report that has relationships in the results, such as the Installed Packages report, the New Packages discovered on Hosts report, and the New Patches discovered on Hosts report, the Query Builder is not displayed.
Workaround: None. |
| 13881 |
Problem: When saving queries in the Reports Builder, if you specify a name that already exists, the save button is disabled, though no reason for this is shown in the user interface.
Workaround: None. |
| 13281 |
Problem: The date selector in the Report Builder does not honor the user's date preference setting.
Workaround: None. |
| 13049 |
Problem: ADDM created BMC_Impact relationships to classes in the CMDB that were not SIM-enabled. When SIM encountered such relationships a NullPointerException was seen in SIM.
Workaround: Updated mapping files are available here |
| 13007 |
Problem: Certain BMC_Dependency relationships in the CMDB are populated with the incorrect direction
The following BMC_Dependency relationships were being populated with the Source and Destination classes the wrong way round:
- Name=HOSTEDVIRTUALSYSTEM
- Name=DEPLOYEDAPPLICATION
- Name=APPLICATIONSYSTEMPRODUCT
- Name=APPLICATIONSYSTEMHIERARCHY
- Name=MOUNTS
- Name=APPLICATIONSYSTEMCOMPUTER
- Name=ENDPOINTDEPENDENCY
Workaround: Updated mapping files are available here
|
| 12892 |
Problem: Retrieving Files from 64-bit Windows systems. This impacts discovery of files that are under C:\Windows\System32 directory when running the slave on 2008. When the slave is running on a 2008 system and there is a request to discover a file beneath the C:\Windows\System32 directory it will fail. The IIS, HyperV and DB2 patterns are impacted by this.
Workaround: Run the slave on a Windows 2003 system. |
| 12704 |
Problem: You cannot filter using the third column of the Installed Packages report.
Workaround: None. |
| 12700 |
Problem: The PROCESSWITH ordering in the search and reporting service is unreliable.
Workaround: None. |
| 12692 |
Problem: A leading space in the host field or username of a adapter prevents the adapter from working. You cannot test the adapter or use it to export data.
Workaround: Ensure that leading spaces have not been inadvertently added in these fields. |
| 12608 |
Problem: When discovering Oracle instances, Discovery currently only attempts to log into the IP that the host was discovered on.
Workaround: None. |
| 12385 |
Problem: The datastore can crash when compacting the datastore using the new online compaction tool.
Workaround: Although the crash does not corrupt data and the online compaction can be re-run and it will continue where it left off, it is recommended that you continue to use the offline compaction utility. |
| 12382 |
Problem: Visualizations cannot display manual groups with the '$' character in their name.
Workaround: Do not use the '$' character in manual group names. |
| 12330 |
Problem: graph-definition.txt handling has regressed.
- Errors in the file are reported in the log file less clearly
- The Tideway services must be restarted to re-read the file (previously it was automatically picked up the next time a visualization was viewed)
Workaround: None.
|
| 12297 |
Problem: If the "Only show working set in visualizations" menu option is used while viewing a visualization, the visualization does not always redraw correctly to honor the new option state.
Workaround: Manually refresh the browser page. |
| 12296 |
Problem: Hiding nodes in a visualization such that no nodes remain in the visualization can cause IE 6 to crash with the message "R6025 - pure virtual function call".
Workaround: Do not hide all nodes in a visualization. |
| 11665 |
Problem: Registry queries against 64-bit Windows
- Package discovery: The package list for a 64-bit system will always be incomplete. When running the slave on a 32-bit platform only the 64-bit packages are discovered. When running the slave on a 64-bit system only the 32-bit packages are discovered.
- Registry queries: Registry queries will succeed when the slave is running on a 32-bit system. The result of registry queries for a slave running on a 64-bit system will vary depending on the Operating System version. For slaves running on XP_64 or 2003_64 the queries will succeed. For slaves running on 2008_64 the queries are likely to fail - it is not predictable.
Workaround: To minimise the impact of this defect wherever possible run the slave on a 32-bit OS, or if running on a 64-bit OS Windows avoid 2008. In all cases the package list will be incomplete.
|
| 9670 |
Problem: If a snapshot is created whilst there is an incomplete scheduled scan, the scan scheduled will be deleted if the snapshot is restored without restoring the discovery run state. This means that the user will need to recreate those scheduled scans after restoring the snapshot.
Workaround: Ensure there are no scheduled scans in progress at the time the snapshot is created, or restore the discovery run state. |
| 9179 |
Problem: When doing an snmpGet in a pattern, it is possible that some SNMP agents for certain OIDs will return data for a different OID than the one requested. Because the OID for the data retrieved doesn't match the OID that the request was for, the corresponding attribute will not be set.
Workaround: The mapping can be set to include the requested OID and the OID that will actually be returned. For example:
|
| 7848 |
Problem: On Windows hosts there is overlap between what is returned as packages and what is returned as patches. The WMI getPackageList code retrieves everything that is uninstallable which will include all the patches. The pstools version does the same, but filters out hot fixes.
• The data returned by getPackageList will be different depending on the access method used.
• Duplicate Patch and Package nodes will be created, with potential impact on performance and disk usage.
• Queries for patch/package information will have to be more complex or may return duplicate results.
Workaround: None. |
| 4400 |
Problem: The Credential External slave may sometimes fail to retrieve uptime from Windows XP or Windows 2003 target hosts.
Workaround: Use a different discovery method, such as WMI, rcmd or local commands. Alternatively, you can use the Active Directory or Workgroup slaves with pstools. |
| 3859, 4345, 4529 |
Problem: Credential slave discovery using pstools fails where the user name specified in the discovery credential is not a fully qualified user name for the discovery target, that is, of the form <domain>|<hostname>\<username>. This means that discovery using pstools will fail for local users unless a credential is created for each machine with the user name specified as <hostname>\<username>.
Workaround: Either a credential needs to be specified in a correct format for pstools for every target host (note that the user name format differs between pstools and rcmd), or a different discovery method or slave (e.g. AD slave) used.
Customer Case Number: C5047. |
| 3534 |
Problem: An Appscan Auto test revealed several XSS vulnerabilities in the RelationshipSearch and ReleationshipMultisearch widgets.
Workaround: None, though these have now been identified as false positives. |
| 3151, 4456. |
Problem: When discovering Windows NT hosts with a Credential External Slave, this Discovery fails although a valid credential is defined. The credential should be localhost\username.
Workaround: Ensure that the credentials for these hosts are entered as localhost\username.
In these examples, replace user name with the correct user name for Discovery.
Customer Case Number: C5293. |
Tideway Blog