topic Re: Libname error with excel engine in SAS Programming

Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 08:53:04 GMT

Hi,

We have installed SAS 9.3 in our server, right from the day we upgraded from 9.1 to 9.3 we hare facing problem in using libname with Excel engine. we are getting the error message as

ERROR: Connect: Class not registered

ERROR: Error in the LIBNAME statement.

Our server is windows server 2008 R2 64 bit. "NOTE: This session is executing on the X64_S08R2 platform." and we are using Office 2010 with 32 bit.

We have license for the below products

Product expiration dates:

---Base SAS Software 31JUL2013

---SAS/STAT 31JUL2013

---SAS/GRAPH 31JUL2013

---SAS/ACCESS Interface to PC Files 31JUL2013

---SAS Workspace Server for Local Access 31JUL2013

But still we cant able to use the libname with excel engine. Please help me to solve the issue.

Thanks

Sudhakar

Re: Libname error with excel engine

allurai0412 — Mon, 08 Apr 2013 10:57:34 GMT

hi,

please check in the below link... i guess it will help...

https://communities.sas.com/message/123860

Regards

ALLU

Re: Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 12:05:17 GMT

Hi,

thanks for the link,

I tried this code.

libname xf Excel "F:\share\check.xls"; am getting the same error as above.

Sudhakar

Re: Libname error with excel engine

esjackso — Mon, 08 Apr 2013 12:08:29 GMT

I believe we were directed by SAS support to install 64 bit office on our server before the libname would work.

Re: Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 12:15:00 GMT

Is that so, is there any other way to make them work ?

Re: Libname error with excel engine

Florent — Mon, 08 Apr 2013 12:15:07 GMT

Does the following still give an error ?

libname xf Excel path="F:\share\check.xls";

Re: Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 12:21:14 GMT

Yes even if i do with Userinterface to create a libname am getting this error:

ERROR: Connect: Class not registered

ERROR: Error in the LIBNAME statement.

Re: Libname error with excel engine

esjackso — Mon, 08 Apr 2013 12:23:51 GMT

We have a complete 64 bit setup so we had to match that with office. This was a switch from local sas 9.3 to remote Server SAS 9.3 so I dont know if this was a 9.3 issue or not.

Re: Libname error with excel engine

esjackso — Mon, 08 Apr 2013 12:24:20 GMT

I believe we had problems even with proc import and import wizard.

Re: Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 12:28:28 GMT

true even import wizard and export wizard is not working.

Re: Libname error with excel engine

esjackso — Mon, 08 Apr 2013 12:31:56 GMT

We didnt ask a lot of question since we had licenses for both versions of Office 2010 so we tried it and stopped our problems.

Re: Libname error with excel engine

Sudhakar_A — Mon, 08 Apr 2013 12:45:23 GMT

Thanks for your help. But i want this to executed in 32 bit version Office in 64 SAS bit server.

Re: Libname error with excel engine

esjackso — Mon, 08 Apr 2013 12:49:57 GMT

Sounds like you need to submit a support ticket and let SAS Support answer.

Re: Libname error with excel engine

Linlin — Mon, 08 Apr 2013 14:31:08 GMT

I had a similar problem when I installed 9.3 some time ago. a type of HP printer as my default printer caused the problem.

Re: Libname error with excel engine

sas4ml — Mon, 08 Apr 2013 19:30:36 GMT

Hi, Not sure if your issue has been resolved. You may have compatibility issues meaning if SAS is 64 bit and the Office that you are running is 32 bit. I know in such a situation you normally receive "Class not registered" or Excel engine not found" messages.

Try checking the Excel version and if different from SAS version try Installing 64 bit Office 2010 to match your version of SAS .

Try the following links in the order given

http://www.office.com/office64setup

The following links involve more steps using PC Server Files with Import Wizard

http://support.sas.com/kb/44197

Iinstalling a SAS PC File server which provides a bridge between 32 bit Office and 64 bit SAS.

http://support.sas.com/kb/43802

Thanks,

Re: Libname error with excel engine

SandyH — Tue, 09 Apr 2013 00:48:54 GMT

dose not work in 64 bit

Re: Libname error with excel engine

Cynthia_sas — Tue, 09 Apr 2013 02:00:09 GMT

Hi: When your "bitness" does not match, such as having 64 bit SAS and 32 bit Office, you CAN use the PC file server to use the LIBNAME engine. However, the form of the LIBNAME engine statement changes. I use this all the time on my machine, which has the bitness difference described above (64 bit SAS/32 bit Office). Here's a sample LIBNAME engine statement that I use:

libname myxls pcfiles path='c:\temp\myexceldata.xls' ;

Note that this form of the LIBNAME statement does require the PC File Server component to work.

cynthia

Re: Libname error with excel engine

Sudhakar_A — Tue, 09 Apr 2013 03:39:29 GMT

Hi Cynthia,

I tried using the PCfiles engine to excel files. It is working fine in User interface method of creating lib name. But if i use the below code, i am getting this error.

libname ex pcfiles "d:\Users\sanbazhagan\Desktop\System Details.xls";

ERROR: Incorrect syntax for this LIBNAME statement. This engine does not accept a physical name.

ERROR: Error in the LIBNAME statement.

It is strange for me now, how it is working in userinterface method of creating libname and not in program way.

Sudhakar

Re: Libname error with excel engine

Sudhakar_A — Tue, 09 Apr 2013 03:42:00 GMT

Hi Cynthia,

I tried using the following code for the libname statement now it is working. I have added Path= option.

libname ex pcfiles path="d:\Users\sanbazhagan\Desktop\System Details.xls";

thanks for your answer. But Libname with excel engine will not work? I am just trying to find why it is not working whether i need to change any settings in my server to do that?

Sudhakar

Re: Libname error with excel engine

Norman21 — Thu, 09 Jun 2016 09:22:57 GMT

Although this is an old thread, I can confirm that Cynthia's solution works with SAS 9.4 64 bit and Microsoft Office 32 bit.

Specifically, use

LIBNAME XLSLIB pcfiles path="C:\My SAS\myfile.XLS"

instead of

LIBNAME XLSLIB "C:\My SAS\myfile.XLS"