Problem Note 70068: SAS® Deployment Tester is unable to read data from SAS® Operational Qualification Tool
When you run SAS Operational Qualification Tool (SASOQ) with SAS Deployment Tester in SAS® 9.4M8 (TS1M8), the following error might occur:
Error: Error showing report: ERROR: No report was found with ID reportID for this contract session
The issue is associated with invalid characters being added to the path in test XML files that the SAS Deployment Tester attempts to read while processing results from SASOQ.
Workaround:
Note: If using the workaround and the SAS® Installation Qualification (SAS IQ) tool is run on the same SAS 9.4 TS1M8 installation, a "Checksum does not match" error for the dtester.xsl file will occur, since it was altered in the workaround. This error can be considered a false positive and thus ignored. If you apply the hot fix, no "Checksum does not match" error should occur since the change was handled by the hot fix.
- Close SAS Deployment Tester.
- Navigate to the sashome/SASFoundation/9.4/dtest/sasoq/dtester.xsl file.
- Edit line 53 to ensure that all backslashes in the path are converted to forward slashes.
Line 53 before the edit:
<xsl:apply-templates select="document(concat('file:///', $result-root, '/Data/', ProductName, '/', TestName, '.xml'))/SASOQ/Test"/>
Line 53 after edit:
<xsl:apply-templates select="document(concat('file:///', translate($result-root, '\', '/'), '/Data/', ProductName, '/', TestName, '.xml'))/SASOQ/Test"/>
Click the Hot Fix tab in this note to access the hot fix for this issue.
Note that if this error has already been encountered on a 64-bit Windows installation before installing the hot fix, you must remove the incorrect data from the Results folder in SAS Management Console before the Deployment Tester plug-in will be available again.
Operating System and Release Information
SAS System | Base SAS | Microsoft® Windows® for x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8 Enterprise 32-bit | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8 Enterprise x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8 Pro 32-bit | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8 Pro x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Enterprise x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 8.1 Pro x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 10 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows 11 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 R2 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2008 for x64 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 Datacenter | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 R2 Std | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2012 Std | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2016 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2019 | 9.4_M8 | | 9.4 TS1M8 | |
Microsoft Windows Server 2022 | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Enterprise 32 bit | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Enterprise x64 | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Home Premium 32 bit | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Home Premium x64 | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Professional 32 bit | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Professional x64 | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Ultimate 32 bit | 9.4_M8 | | 9.4 TS1M8 | |
Windows 7 Ultimate x64 | 9.4_M8 | | 9.4 TS1M8 | |
64-bit Enabled AIX | 9.4_M8 | | 9.4 TS1M8 | |
64-bit Enabled Solaris | 9.4_M8 | | 9.4 TS1M8 | |
HP-UX IPF | 9.4_M8 | | 9.4 TS1M8 | |
Linux for x64 | 9.4_M8 | | 9.4 TS1M8 | |
Solaris for x64 | 9.4_M8 | | 9.4 TS1M8 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When running SAS Operational Qualification Tool (SAS OQ) with SAS Deployment Tester in SAS® 9.4M8, the following error has been observed: "Error: Error showing report: ERROR: No report was found with ID reportID for this contract session."
The problem occurs when invalid characters are added.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-11-03 15:40:17 |
Date Created: | 2023-05-03 15:37:56 |