The SAS Intelligence Platform: Administration Documentation is found at: http://support.sas.com/documentation/configuration/913admin.html If you are going to be configuring a Business Intelligence platform, you **really** should be familiar with the information available in these references. Most of your questions will be answered there. Yes, you need to configure the Object Spawner & Workspace Server. No, you do not necessarily need a Stored Process Server. You must have the Object Spawner running. "sastrust" is used to run some server processes. "sasadm" is used as the "administrator" account. Yes, they are different. For instance, you can verify that the Metadata Server is running by successfully connecting to the Metadata Server from the SAS Management Console by using the "sasadm" account. If you continue to have a problem, your best bet would be to "open" a *new* Track with Technical Support, which you can always do from this page: http://support.sas.com/techsup/contact/submit_emits2.html --GlenG@sas ... View more

re Error: sam.S249.ex.msg: A connection to server host xxxx could not be established on port 8591 Either there is no server listening for connections or the server is too busy to accept any new connections. Make sure that the server has started and that the values provided for host and port are correct. Explanation: This error might be encountered if any one of the following conditions are true: A. Object Spawner is not started: This error might be seen when you did not start your Object Spawner, before testing the Workspace Server. To start your Object Spawner, perform the following: => Start => Programs => SAS => => => "Start SAS Object Spawner" B. Missing Server definition: When you test the Workspace server connection in the SAS Management Console (SMC), this error message might also appear if the Workspace server has not been added to the SASMain - Spawner definition when you configured the Object Spawner in the New Server Wizard. Likewise, if the Stored Process server has been omitted, the same error message might appear when testing its connection. If so, add the Workspace server to the SASMain - Spawner definition: 1. Open the SAS Management Console and expand Server Manager. 2. Locate SASMain - Spawner, right click, and select Properties. 3. Select the Servers tab (notice what is in 'Selected Servers': you should see SASMain - Workspace server and SASMain - Stored Process server). 4. If either is not listed in 'Selected Servers', choose the missing one from 'Available servers', move it to 'Selected Servers', and choose OK. 5. Then close the Object Spawner, stop and restart your Metadata server, start the Object Spawner and test the connections. Server connections can be tested by using Server Manager in the SMC. 1. Expand Server Manager and expand SASMain. 2. Expand SASMain - Logical Workspace server. 3. Click SASMain - Workspace server. 4. In the right pane, right-click on Connection: SASMain - Workspace server. 5. Choose Test Connection (log in, if necessary). 6. If successful, this message appears: "Test Connection Successful!" C: Metadata permissions: The SAS System Services group is not granted ReadMetadata in the Workspace server definition. To verify, within the SAS Management Console go to Server Manager and click on SASMain - Logical Workspace Server. Expanded Properties and go to the Authorization Tab. Make sure the SAS System Services Group has been granted ReadMetadata. By default, these permissions are inherited by from the Default Act definition. D: sastrust not in SAS Services Group: The SAS Trusted User is not a member of the SAS Services Group. To verify, within the SAS Management Console to go User Manager. Select the SAS System Services group. View Properties and select the Members Tab. Verify the SAS Trusted User is part of this group. E: Hostname conflict: The Object Spawner and Workspace Server have different hostnames. For example, the Workspace server is on the 'hostname' server and the Object Spawner is on the hostname.domain server. The hostname must be represented the same. To verify the name of the Workspace server, go to Server Manager. Expand the SASMain Logical Workspace Server entry. The Connection Definition will show how the hostname is defined under the Host column. To verify the name of the Object Spawner, go to Server Manager and expand SASMain - Spawner. The Connection Definition will show how the hostname is defined under the Host column. If the hostnames are represented differently, the Result Entry for the SASMain - Logical Workspace Server will contain no information. If you continue to have a problem, your best bet would be to "open" a *new* Track with Technical Support, which you can always do from this page: http://support.sas.com/techsup/contact/submit_emits2.html ... View more

Perhaps this explanation might help.... When you get an error message about invalid userid credentials similer to: Could not log on to the server Then there are usually (3) areas to examine for consistency in the credentials: 1. Userid Definition: When you defined the Userid [e.g. "sastrust"] whose credentials are used for running SAS tasks, if the Server machine was Windows, you were supposed to have checked these boxes: **Deselect** => "User must change password at next logon" Select => "User cannot change password" Select => "Password never expires" Please review the following settings: => Settings => Control Panel => Administrative Tools => Computer Management => => "Expand +" Local Users & Groups (in Left Panel) => Select => "Users" (in Left Panel) Then in Right Panel => => R/Click on Userid [e.g. "sastrust"] => Properties => Examine: **Deselect** => "User must change password at next logon" Select => "User cannot change password" Select => "Password never expires" If any of these "password" properties were not set properly, then the password for *this* Userid is out of synch with how it is defined elsewhere 😞 2. Validate Windows Password: verify that the user ID and password that you defined in the operating system matches what you specified in your Metadata login information. You can check this by verifying that you can log in to your local machine by using the user ID and password that you stored in the metadata login. Here is how you check what Windows is using for the password for *this* Userid [e.g. "sastrust"] Start up a Command Window => Programs => Accessories => "Command Prompt" Then, in the Command Window: >runas /user:sastrust "notepad" It will prompt for the password for *this* Userid and if you enter the correct Windows password for *this* Userid, then it will allow "Notepad" to come up. If Notepad fails to come up then you know that the password for that Userid was not correct and needs to be changed. 3. Password in SMC: Next, use the *same* password which you just validated with Windows authentication for *this* Userid [e.g. "sastrust"] and using SMC compare the Metadata Server's value listed for that Userid in the User's Properties. Next, search your "c:\" drive and find the file: "OmrConfig.xml" which shows the encrypted password for *this* Userid as originally provided to the Configuration Wizard. Next, compare the password you just validated with Windows authentication and compare with the encrypted password in "OmrConfig.xml". For each password, use this code to get the encrypted value: proc pwencode in=" "; run; For example: proc pwencode in="UserUser1"; run; If none of this helps you, then please Open a "Track" with SAS Technical support describing your problem 🙂 See: http://support.sas.com/techsup/contact/submit_emits2.html Good luck! -- GlenG@sas ... View more