| Defect No |
Details |
| 11924 |
Problem: When upgrading from versions prior to 7.2 to 7.2 or 7.2.1 the upgrade script moves any taxonomy extension files into the default directory instead of the custom directory. This can cause the taxonomy extensions to be loaded before the base taxonomy.
Workaround: Move the taxonomy extension(s) from /usr/tideway/data/installed/taxonomy to /usr/tideway/data/custom/taxonomy. |
| 11406 |
Problem: In an appliance which is upgraded to version 7.2, all existing DiscoveryAccesses are listed as occurring on the upgrade date. The DiscoveryAccess list does not show any start or end times. This is due to renamed attributes in version 7.2.
Workaround: None, though the DiscoveryAccesses will age out and be replaced by DiscoveryAccesses with the correct attributes for display in version 7.2. |
| 11351 |
Problem: A traceback appears in the tw_svc_tomcat log with the exception "ArrayIndexOutOfBoundsException" when the user creates a new query associated with an IntegrationPoint or Software Credential Group. The exception is benign as it happens when Foundation attempts to generate an example TPL call for the new query in the UI. A warning associated with this exception is also logged in the tw_appserver log.
Workaround: None. |
| 9670 |
Problem: If a snapshot is created while 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. |
| 9326 |
Problem: Chart links and titles do not match for certain reports and some contain redundant information.
Workaround: None. |
| 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 username specified in the discovery credential is not a fully qualified username 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 username 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 username 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 username with the correct username for Discovery.
Customer Case Number: C5293. |
| 2875 |
Problem: If you place an updated reports.xml file on a system without stopping the tideway services, you may see a traceback in the UI.
Workaround: Stop the tideway services before adding a new or modifying the existing reports.xml file. |
| 2463 |
Problem: While migrating a large appliance snapshot to a target appliance, you cannot view the Database Snapshot page on the target appliance.
Workaround: None. |
Tideway Blog