topic Re: SAS Message Log Error in Administration and Deployment

SAS Message Log Error

Areksoo — Wed, 18 Apr 2012 19:14:33 GMT

Whenever I open SAS 9.2 or try to reinstall SAS 9.2, I'm getting this error message:

UNABLE TO OPEN/READ MESSAGE FILE USING THE -MSG PATHS

Anybody know what this means?

EDIT:

I should add... I did all sorts of searches online and found that it might be a config error with the SASV9 file. SAS 9.2 was inititally installed locally on my d: drive. However I checked all the paths in the config and they all do exist... Not sure if this helps.

Re: SAS Message Log Error

Doc_Duke — Thu, 19 Apr 2012 13:47:20 GMT

Areksoo,

I haven't seen that message, but might have a workaround. I'm assuming you are running local on a Windows machine. Before re-installing SAS 9.2, uninstall all the pieces with add-remove programs and then go into $SAShome and delete all the files. You might have a bad file that SAS is not overwriting in an effort to have a lighter re-installation footprint.

Doc Muhlbaier

Duke

Re: SAS Message Log Error

shivas — Thu, 19 Apr 2012 15:54:17 GMT

Hi..

Just check this SAS notes for older version of SAS.

http://support.sas.com/kb/1/567.html

http://support.sas.com/kb/8/536.html

Before installing SAS make sure that you completely uninstall SAS from control panel,Delete existing Configuration Directory(or un configure),remove Services and also delete any SAS related things from registry and from documents and settings.

Thanks,

Shiva

Re: SAS Message Log Error

Areksoo — Wed, 25 Apr 2012 15:26:37 GMT

Sorry for the late reply... lots of training sessions.

From your replies and further digging, it looks like I only have two options: Uninstall and reinstall SAS or reconfigure the config file (not recommended unless you know what you are doing).

I did a lot of tests and checking on the config file and permissions to the folders. Everything looks fine... except results in the same error.

I won't go into the details, but uninstalling SAS isn't working and doing things like re-imaging my computer is not an option at the current time.

At least SAS EG works... being an "old school" SAS programmer, I'm not fond of it, but it runs.