BookmarkSubscribeRSS Feed
pkatapally
Calcite | Level 5

When we addedd sas users to prod, not sure why they were not able to connect SASAPP workspace server.

 

Error we got in EG:-

Error] Failed to start the server.

[Error] The launch of server SASApp - Workspace Server for user nmester failed.

 

 

-------------------------- Technical Information Follows --------------------------

 

Exception Details:

----------------------------------------

Exception type:  SAS.EG.SDS.SDSException

SAS Message:     [Error] Failed to start the server.

[Error] The launch of server SASApp - Workspace Server for user nmester failed.

 

Raw Message:     <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Failed to start the server.</SASMessage></Exception><Exception><SASMessage severity="Error">The launch of server SASApp - Workspace Server for user nmester failed.</SASMessage></Exception></Exceptions>

Source:          SAS.EG.SDS.Model

Target Site:     SASWorkspace

 

Stack Trace:

   at SAS.EG.SDS.Model.Server.SASWorkspace(Boolean checkWorkspace)

   at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)

 

Inner Exception Details:

----------------------------------------

Exception type:  SAS.EC.Directory.Model.SDSException

SAS Message:     [Error] Failed to start the server.

[Error] The launch of server SASApp - Workspace Server for user nmester failed.

 

Raw Message:     <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Failed to start the server.</SASMessage></Exception><Exception><SASMessage severity="Error">The launch of server SASApp - Workspace Server for user nmester failed.</SASMessage></Exception></Exceptions>

Source:          EC.Directory

Target Site:     Connect

 

Inner Exception Details:

----------------------------------------

Exception type:  System.Runtime.InteropServices.COMException

SAS Message:     [Error] Failed to start the server.

[Error] The launch of server SASApp - Workspace Server for user nmester failed.

 

Raw Message:     <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Failed to start the server.</SASMessage></Exception><Exception><SASMessage severity="Error">The launch of server SASApp - Workspace Server for user nmester failed.</SASMessage></Exception></Exceptions>

Source:          SASObjectManager

Target Site:     CreateObjectByLogicalNameAndLogins

 

Stack Trace:

   at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByLogicalNameAndLogins(String Name, Boolean synchronous, Object pIOMI, String LogicalName, LoginDef pOMRLoginDef, LoginDef pSASLoginDef, String nameValuePairs)

   at SAS.EC.Directory.Model.Server.Connect(ConnectionInfo connInfo)

 

 

 

Object Spawner Log:-

2017-07-13T15:39:42,622 INFO  [00000868] :nancha - New client connection (54) accepted from server port 8591 for user nancha. Encryption level is Everything using encryption algorithm AES. Peer IP address and port are [10.3.51.221]:59532 for APPNAME=SAS Enterprise Guide.

2017-07-13T15:39:42,642 INFO  [00000868] :nancha - New out call client connection (55) for user sastrust@saspw.  Encryption level is Everything using encryption algorithm AES.  Peer IP address and port are [10.18.129.105]:8561.

2017-07-13T15:39:42,652 INFO  [00000868] :nancha - There are no grid option sets defined for SAS application server "SASApp".

2017-07-13T15:39:42,658 INFO  [00000009] :sas - Client connection 55 for user sastrust@saspw closed.

2017-07-13T15:39:42,659 INFO  [00000868] :nancha - New out call client connection (56) for user sastrust@saspw.  Encryption level is Everything using encryption algorithm AES.  Peer IP address and port are [10.18.129.105]:8561.

2017-07-13T15:39:42,670 INFO  [00000868] :nancha - Client connection 56 for user sastrust@saspw closed.

2017-07-13T15:39:42,860 INFO  [00000868] :nancha - Created grid job 1734 using credentials nancha (child id 1).

2017-07-13T15:39:50,873 INFO  [00000818] :sas - Grid job 1734 owned by user nancha (child id 1) has ended.

2017-07-13T15:39:50,873 ERROR [00000868] :nancha - The launch of server SASApp - Workspace Server for user nancha failed.

2017-07-13T15:39:50,873 ERROR [00000818] :sas - The specified uuid 9E6BAAD3-7C2C-1244-BB21-8524BB61C620 did not match any process managed by this spawner.

2017-07-13T15:39:50,874 INFO  [00000868] :sas - Client connection 54 for user nancha closed.

7 REPLIES 7
ChrisHemedinger
Community Manager

Windows server? Your user account needs "Log on as a batch job" privileges -- that's a Windows user setting.

It's time to register for SAS Innovate! Join your SAS user peers in Las Vegas on April 16-19 2024.
pkatapally
Calcite | Level 5

Actually we have a grid environment, Server on Linux and EG client on Windows. We did the same thing in Dev and its working fine.

ChrisHemedinger
Community Manager

Your error message and spawner log seem mismatched.  The error message references one ID (nmester) but the log refers to nancho.  Are you sure you captured/shared the proper segment of the log?

It's time to register for SAS Innovate! Join your SAS user peers in Las Vegas on April 16-19 2024.
pkatapally
Calcite | Level 5

Actually both are having same issue.

alexal
SAS Employee

@pkatapally,

 

There is not a way to tell you exactly what happened without some diagnostic logging turned on when the failure occurred.
 
Usually, the failure is due to file permission errors.  If logging for the WorkspaceServer sessions has been enabled, this is a common source of failure if the users are not able to create the logs due to permissions on the directory holding the logs.
 
Other sources would be incorrect permissions to create the WORK library, or, especially in the case of new users, their Unix $HOME directories do not have the correct permissions.
 
One last cause would be that the permissions on the directories in the <SASConfig> path have been set so that the users are not able to access and execute the WorkspaceServer.sh script.

Kurt_Bremser
Super User

Are those users coming from LDAP? They might need to logon once to the servers in question (SSH or similar) so their HOME directories are created. AFAIK, that's one thing that does not work out of the box with the spawner.

JuanS_OCS
Amethyst | Level 16

Hello @pkatapally,

 

are you using a Grid environment with a Hadoop cluster on SAS 9.4 M3?

 

Please check this Hot Fix, perhaps it can help you. http://support.sas.com/kb/60/250.html

 

Kind regards,

 

Juan

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 7 replies
  • 3942 views
  • 1 like
  • 5 in conversation