Usage Note 42271: How to run all of the test suites in the Deployment Tester Server in SAS® Management Console
 |  |  |  |
When you right-click and select Run All Test Suites from the Deployment Tester Server in SAS Management Console, a Credentials Required dialog box might appear. Clicking the Help button within the dialog box provides the information. As of SAS® 9.2 11w03, this is the information from the Help dialog box:
To correct this problem, rerun the test and enter sasadm@saspw and the password for this user.
*
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.
Credentials Required Dialog Box Specify the user ID and password needed to run the test suite. If you are running the OLAP Server test suite, you must specify an administrator account (such as sasadm@saspw). If you are running the Workspace Server test suite, you must specify an external account (such as sasdemo). If you are running the Stored Process Server, Pooled Workspace Server, or Remote Services test suites, you can use either an internal account (such as sasadm@saspw) or an external account (such as sasdemo). If you are running the SAS Foundation test suite, no credentials are required.
Important: To test Remote Services, select the internal account sasadm@saspw. Or, if you did not set up internal accounts during the installation process, select the Administrator account (for example: sasadm).
If you do not do so, you might receive the following error:
Could not deploy/find services: Unable to attempt a lookup since
a remote discovery service metadata configuration was not found
in the metadata source.
OMRMetadataSource {software component: "Remote Services"host:
"foo.xx.xxx.com"port: "8561"repository: "Foundation"} at
junit.framework.Assert.fail(Assert.java:47) at
com.sas.services.test.FoundationServicesFramework.setUp
(FoundationServicesFramework.java:352) at
com.sas.services.test.TestServicesBuild.setUp(TestServicesBuild.java:122)
at junit.framework.TestCase.runBare(TestCase.java:125) at
junit.framework.TestResult$1.protect(TestResult.java:106) at
junit.framework.TestResult.runProtected(TestResult.java:124) at
junit.framework.TestResult.run(TestResult.java:109) at
junit.framework.TestCase.run(TestCase.java:118) at
com.sas.testutil.BaseTest.run(BaseTest.java:119) at
junit.framework.TestSuite.runTest(TestSuite.java:208) at
junit.framework.TestSuite.run(TestSuite.java:203) at
com.sas.trun.junitdriver.JUnitDriver.runTestSuite(JUnitDriver.java:487) at
com.sas.trun.junitdriver.JUnitDriver.main(JUnitDriver.java:696)
For the specific details for this test on your machine, see the Instructions.html file that is located in SAS_Config_dir\Lev1\Documents (for example: C:\SAS\EBIEDIEG\Lev1\Documents\Instructions.html).
Search for "SAS Deployment Tester Server." Here is an example of the information that you might see:
| Validation steps |
|
| Notes: | The Deployment Tester Server is used to validate functionality and proper operation of SAS products and servers. The Deployment Tester Server, in conjunction with the Deployment Tester SAS Management Console plug-in, allows for tests to be executed on remote systems from a single SAS Management Console instance. Click Help for the Deployment Tester in the SAS Management Console Help menu for more information. |
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Management Console | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2_M2 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows XP 64-bit Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft® Windows® for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2003 Enterprise Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2003 Standard Edition | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2003 for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2008 | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows Server 2008 for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Microsoft Windows XP Professional | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Enterprise 32 bit | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Enterprise x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Home Premium 32 bit | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Home Premium x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Professional 32 bit | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Professional x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Ultimate 32 bit | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows 7 Ultimate x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows Vista | 9.2_M2 | 9.2 TS2M3 | ||||
| Windows Vista for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| 64-bit Enabled AIX | 9.2_M2 | 9.2 TS2M3 | ||||
| 64-bit Enabled HP-UX | 9.2_M2 | 9.2 TS2M3 | ||||
| 64-bit Enabled Solaris | 9.2_M2 | 9.2 TS2M3 | ||||
| HP-UX IPF | 9.2_M2 | 9.2 TS2M3 | ||||
| Linux | 9.2_M2 | 9.2 TS2M3 | ||||
| Linux for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Solaris for x64 | 9.2_M2 | 9.2 TS2M3 | ||||
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2012-04-30 12:55:49 |
| Date Created: | 2011-02-02 14:43:14 |