Error with Object Spawner

Reply
Occasional Contributor
Posts: 15

Error with Object Spawner

We were facing an issue with reports in Portal and with SAS Pooled workspace server. Over the analysis made out there was an error with the WORK Library location in the SASv9 confg file.

Now after the change finding the following errors with Object Spwaner which i nturn affected the portal which went offline.

ERROR: Library WORK does not exist.
NOTE: Unable to initialize the options subsystem.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

ERROR: Library WORK does not exist.
NOTE: Unable to initialize the options subsystem.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

....

....

....

....

20140905:05.10.51.51: 00000004:

20140905:05.10.51.51: 00000004:NOTE: SAS initialization used:

20140905:05.10.51.51: 00000004:NOTE: real time           0.05 seconds

20140905:05.10.51.51: 00000004:NOTE: cpu time            0.01 seconds

20140905:05.10.51.51: 00000004:NOTE:      

20140905:05.10.51.66: 00000004:ERROR: Failed to retrieve login credential from the authentication domain.

20140905:05.10.51.66: 00000004:ERROR: User does not have appropriate authorization level for library ADM.

20140905:05.10.51.66: 00000004:ERROR: Failed to retrieve login credential from the authentication domain.

20140905:05.10.51.66: 00000004:ERROR: Failed to retrieve login credential from the authentication domain.

20140905:05.10.51.66: 00000004:ERROR: Failed to retrieve login credential from the authentication domain.

20140905:05.10.51.66: 00000004:ERROR: User does not have appropriate authorization level for library ANDRO.

20140905:05.10.51.66: 00000004:WARNING: NOTE: Libref shared successfully assigned from logical server.

20140905:05.10.51.66: 00000004:WARNING: NOTE: Libref wrstemp successfully assigned from logical server.

20140905:05.10.51.66: 00000004:WARNING: NOTE: Libref wrsdist successfully assigned from logical server.

20140905:05.10.51.66: 00000004:WARNING: NOTE: Libref stpsamp successfully assigned from logical server.

20140905:05.10.51.66: 00000004:WARNING: NOTE: Libref SASDATA successfully assigned from logical server.

Could anyone help on this.

Sriram

Valued Guide
Posts: 3,208

Re: Error with Object Spawner

Siriam, (back again).  

SASwork:

There is no "the sasv9.cfg" anymore. In fact there is whole bunch of them at all kind of locations.
These are (install) /Foundation/-  1/ a default installed and a 2/ usermods  (with language encoding being duplicated)

For each  ( ! )  appserver (config) /levx/-   3a/  for the environment 3a1/ for appservercontext an installed and 4a1/ usermods

                                                                  5a1a/ each server (WS SP PW ) an installed and 6a1a/ an usermods version.

The leveling 6a1a as it can possible repeating. There is a SASmeta appserver and SASapp appserver by default.  That is you to view at 10 of those 

 

The error on the SAS Work is an indication something did not secceed with your saswork setting or the saswork is inaccessible for the used groupaccount.

Authentication domain:
In the SAS code prolably generated there can be a reference to an authentication domain in the SAS metadata.

That one can be used to make connections  to external RDBMS systems. As you are using a Pooled workspace server the authentication in the sas-metadata is possible done by the pooled workspace server (libnames). In that case there must be the login defined for the DBNS for that Pooled WS server account.  

---->-- ja karman --<-----
Frequent Contributor
Posts: 97

Re: Error with Object Spawner

Sriram,

Definitely a typo in one of your config files, like Jaap says above. Assuming you're on Linux, do this:

1) Navigate to your context (SASApp) base directory, so something like


cd /opt/sas93/config/Lev1/SASApp

Then use this command to search for any files where a specific saswork directory has been defined:

find -name "*.cfg" | xargs grep -ni '\-work '

This will give you a list of all the config files where a custom -WORK has been set. What you need to ensure is that a) all of those directories exist, and b) they are all writeable by your sassrv user at the operating system level. You'll get a different error message if they exist but are not accessible by your sassrv user. 99% chance that you've got a typo in there somewhere. Ensure that any directories with spaces in are quoted, or better don't use spaces in directory names.

The authentication domain errors are probably a result of your sastrust@saspw user not having metadata permissions to access the credentials to those preassigned libraries. You can fix this by granting your SAS Trusted User permissions to those libraries in metadata if you want them preassigned.

hope this helps

Nik

Ask a Question
Discussion stats
  • 2 replies
  • 846 views
  • 0 likes
  • 3 in conversation