Application server setup

Reply
N/A
Posts: 0

Application server setup

Dear,

I tried to setup the configuration server using the SAS Management Console, by right-clicking Server Manager and choose 'New Server'. I need to use this server in order to startup with ETL studio and OLAP Cube Studio.

I go through the steps prompted by the Wizard, however, I never succeed to pass the connection test, it always prompts:

sam.S249.ex.msg: A connection to server host hostA 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.

Do anyone have any ideas what goes wrong? Are there any guidelines or steps to setup the application server (or any pre-requisites?).
SAS Employee
Posts: 3

Re: Application server setup

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
N/A
Posts: 0

Re: Application server setup

Dear,

Thanks for your detailed explanation for the reasons of the error. Though I am still not successful in resolving my problem after going through the checkings recommended, however, I discover that I may not fully go through all the steps required for configuration.

I have the following few questions in addition:

1) I just configure the workspace server in my previous configuration. I think I may miss out at least the object spawner configuration. Besides this one, are there any other servers I need to setup/configure? Is Stored Process Server necessary to setup? Are there any steps by steps guide to perform the application server setup? Where can I find this guideline?

2) What is 'SASMain' mentioned in previous response. Is it the object spawner?

2) What account should I use to login for connection testing? sastrust or sasadm? Are there any differences?

Thanks very much
SAS Employee
Posts: 3

Re: Application server setup

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
N/A
Posts: 0

Re: Application server setup

Dear,

I now solve the problem. This is due to the mis-configuration of the spawner. It has now been fixed. Thanks very much.

At present, I can successfully install and configure the backend Metadata server and OLAP server for cube building.

I am not trying to configure the components relating to the cube access components, including the OLAP viewer and Information Map.

However, when I invoke the 'SAS Information Map Studio 2.1', I always get the error 'The Metadata server could not associate an identity with your connection'. I am not sure whether there are any configuration not yet performed or due to other problems? Do you have any ideas?

Also, about using OLAP viewer to access the cubes or reports, what is the url to invoke through OLAP viewer?

Thanks
SAS Employee
Posts: 27

Re: Application server setup

Based on the ongoing nature of your questions, I'd like to suggest you open a track with Technical Support (http://support.sas.com/techsup/contact/submit_emits2.htm ). This way, the problem can be addressed more quickly and directly, without the ongoing 'back and forth' of this type of forum.

Thanks.
Dave
Post a Question
Discussion Stats
  • 5 replies
  • 646 views
  • 0 likes
  • 3 in conversation