Proc Export causes instant crash of SAS

[rickpaulos]

Same program I've run before (months ago),  this time with a smaller input data set. All works fine until the final Proc Export.

Instant crash.  No messages, no log to read, SAS just gone.

SAS Temporary Files still in place in the designated work folder.

I tried using the Export Data wizard in the menus and got the same crash.

I tried a different target drive and a short filename x.xlsx, same crash.  I have access rights to the folders.

restarted the computer. tried again. Same crash.

the data set isn't very large: The data set WORK.CONSENTEDAGED has 7830 observations and 51 variables

Windows 10 Education 64 bit version 20H2  build 19042.1110

SAS  9.4 TS level 1M6 X64_10Pro  platform.

My proc export code:

PROC EXPORT
DATA = consentedAged
OUTFILE = "c:\temp\x.xlsx"
DBMS = EXCEL
LABEL
REPLACE;
SHEET = "Crouter";
RUN;

Using the Wizard SAS crashes when I click on okay to create the xlsx file. 

The target file (x.xlsx) is created (9kb) but is empty. 

The sheet name is A266FF2A662E84b639DA not Crouter

Submitting the code above creates an identical empty file.

Any suggestions? 

Is there a way to capture any error message as sas is crashing?

[SASKiwi]

Does PROC EXPORT fail for ANY SAS dataset or just the one you are having problems with?

Try one of the SASHELP datasets like CLASS. Are there any errors in the SAS log? If so please post them.

Try also DBMS = XLSX - same behaviour? 

[zhanghaipo]

DBMS = xlsx，try

[ChrisNZ]

This looks like a defect. I'd try isolating the record(s) and even the variable(s) whose values cause the defect.

I'd then contact Tech Support to ask them the replicate the problem using your data.

[andreas_lds]

If the crash occurs for all datasets, even sashelp.class, than you should check if a hotfix exists. Instead of searching manually, using SAS Hot Fix Analysis, Download and Deployment Tool is recommended.

[Kurt_Bremser]

A recent action on Windows or Office could be the trigger.

Use DBMS=XLSX to avoid the usage of external modules.

[Alan68022]

I had the same problem. Using DBMS=XLSX worked for me. Thanks!