10-28-2014 06:34 AM
I am getting an error while opening sas base:
Error states that : NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.
I have recently recovered sas metadata server , i think i have some issues with the rights on the config files.
Can anyone help me on this ...Urgent reply requested ....
10-28-2014 06:41 AM
This is not critical. The first SAS process for a given user opens the SASUSER.PROFILE with exclusive access, so any following process for the same user has to work with a temporary PROFILE. PROFILE is mainly used to store settings for Base SAS (display manager, function keys etc), so it is unproblematic to discard this information at the end of the session.
10-28-2014 06:42 AM
PS This is a NOTE, not an ERROR, and will not cause an exit condition <> 0 at session end.
10-28-2014 07:21 AM
If this is part of the Metadata Server Log, it indicates that a SAS session is underway already under the same userid that is used to start the Metadata Server. Locate this process and kill it.
I still do not believe that this NOTE is the root cause for your problems, because SASUER.PROFILE is needed for interactive SAS and the SAS process for the Metadata Server runs in (more or less) batch mode without display manager or a terminal interface. If the Metadata Server does not start (or terminates immediately), you need to read through the whole log file.
10-28-2014 07:42 AM
It shows that the Metadata Server has correctly started and is handling requests. It also shows rejected attempts by user sastrust@saspw. This lets me think that other SAS processes (ie Object Spawner) have a wrong password for sastrust in their configuration and can therefore not communicate with the Metadata Server.
Look in the Lev1/ObjectSpawner/metadataConfig.xml file that you will find in your configuration tree
xxxxx is the user ID used to install SAS, context is something like ebiserver (Enterprise Business Intelligence Server)
10-28-2014 08:23 AM
10-28-2014 08:58 AM
Yes, it looks like all the passwords for internal accounts are wrong. That for the external sasadm account seems to be OK.
Question to the OP:
Was sasadm used for the installation of the SAS system?
10-29-2014 03:55 AM
Yes we have used the same id for the installation and other configurations.
What i feel is there is something wrong with the rights on the file storing these IDs, on starting the server the process is unable to read that file because of rights issue.
Any idea which file may have such access issues?? Especially in metadata server folder.
10-29-2014 04:03 AM
To clarify: the Metadata Server has no problems and works OK.
The subservers and object spawner also seem to be able to read their configuration files (or they would not try to contact the metadata server), but they most likely have incorrect entries for the sastrust user/password in the configuration.