topic Error: Procedure NLIN not found in SAS Procedures

Error: Procedure NLIN not found

SKR — Wed, 23 Mar 2016 15:34:30 GMT

Hi Experts,

we are using SAS NLIN procedure in a stored process and it executes fine in Solaris 10 / Oracle 11g client.

However in Solaris 11, we receive the following error

ERROR: Could not load /sas/SAS94/SASFoundation/9.4/sasexe/sasnlin (98 images loaded)
ERROR: ld.so.1: sas: fatal: libmtsk.so.1: open failed: No such file or directory
ERROR: Procedure NLIN not found.

we have checked and confirmed that the SASNLIN library exists under the above SAS root folder (sas/SAS94/SASFoundation/9.4/sasexe/) and necc access rights are granted.

Can anybody advise?

Re: Error: Procedure NLIN not found

ChrisHemedinger — Wed, 23 Mar 2016 15:43:28 GMT

Hi,

It looks like you have a tech support track on this already, but for the benefit of the community -- possible causes are:

1. SAS/STAT is not licensed on the server

2. SAS/STAT is licensed by not installed on the server

3. LD_LIBRARY_PATH_64 has been set incorrectly (see this SAS Note)

To check these, you would run (from the "problem" environment):

PROC SETINIT;RUN;
PROC PRODUCT_STATUS;RUN;
 
data temp7;
length result $2000;
result=sysget('LD_LIBRARY_PATH_64');
put result;
run;

Re: Error: Procedure NLIN not found

SKR — Wed, 23 Mar 2016 16:02:33 GMT

Hi Chris, thanks for the feedback. Yes. we have raised tech support and i am merely trying my luck to get it resolved asap, while waitinf for TS response

we have verified and the license is valid and we dont have LD_LIBRARY_PATH64 and only have LD_LIBRARY_PATH. Could this be a problem?

Re: Error: Procedure NLIN not found

ChrisHemedinger — Wed, 23 Mar 2016 16:07:08 GMT

Reading the SAS note, I think that's likely. You could try a test to define it per the note and see if that helps.

Re: Error: Procedure NLIN not found

SKR — Sun, 10 Apr 2016 11:27:19 GMT

Hi Chris, we managed to find the root cause.

One of the package file in solaris 11 was missing. The corresponding package was installed by default in solaris 10 and hence the issues happened only for solaris 11 OS.

thanks a lot for your help