Failure of export dataset to excel under window 10 environment

[herbman]

Hi,

I am running SAS 9.4 32 bit in pc window environment. After the windows updated to win 10, the export procedure has shown some dysfunctions: 

ERROR: Connect: Class not registered
ERROR: Error in the LIBNAME statement.
ERROR: Connection Failed. See log for details.

Wish help to fix this problem.

Thank you!

Herb

[ballardw]

---

@herbman wrote:

Hi,

I am running SAS 9.4 32 bit in pc window environment. After the windows updated to win 10, the export procedure has shown some dysfunctions: 

ERROR: Connect: Class not registered
ERROR: Error in the LIBNAME statement.
ERROR: Connection Failed. See log for details.

Wish help to fix this problem.

Thank you!

Herb

---

Please show the code you used.

Also is your Excel 32 or 64 bit?

[herbman]

Hi Bakkardw,

Thank you.

The code for export would be most regular and it was working in window 7 environment:

PROC EXPORT DATA= WORK.Doset
OUTFILE= "D:\Documents\MCs\AFP.xlsx"
DBMS=EXCEL REPLACE;
SHEET="Doset";
RUN;

The excel is also 32 bit, but it is Office 365 version:

Microsoft Excel for Office 365 MSO 32-bit.

Herb

[ballardw · Accepted solution]

Try

DBMS=XLSX

[herbman]

Hi ballardw,

It is the solution! Thank you so much! 

I would like follow this a little bit, when I tried to export the file using window interface, I used "Microsoft Excel Workbook(*xls' 'xlsb''xlsm''xlsx)" as data source, and I got similar error message:

ERROR: Connect: Class not registered
ERROR: Error in the LIBNAME statement.

In this case, any correction to make the export happen?

Herb

[ballardw]

Excel and to a lesser extent, probably because fewer people use it, Access have datebase engine issues.

The "bitness" of SAS, 32 or 64 and the bitness of the Microsoft install alone create 4 combinations of engines. And some just don't talk to others in the correct manner. Then which Office version can have other issues. Since Office 365 doesn't quite have the same executable presence that the older office editions did, I suspect that as another issue cause.

The Wizards are making some assumptions about which combinations of engines may work and apparently not matching your install. You are not the only one with that particular issue.

Note that the actual file formats behind XLS and XLSX are dramatically different. I don't know why any of the menus would actually include both on the same option where binary (or pseudo-binary in the case of XLSX) files are concerned. If code works, use code.

If you want to use wizards look at the Microsoft Excel Workbook on PC Files Server. Which goes though another window but should work if PC Files Server was installed.

[herbman]

Hi ballardw, Thanks so much for the clarification!

Herb