Can't export file anymore to excel (from SAS E-guide)

[kumargupt]

Hi,

We are not able to Export SASDataset anymore to excel (from SAS E-guide) .

SAS DAtaset to .xls (Microsoft excel 97-2003)

Error Message:

Export job

The open data operation failed. The following error occurred.

Could not open the data source.

Environment Details:

Eguide Version:4.3 (4.3.0.13063) Hot fix 32
SAS Version: 9.3

OS: Linux 64

All of Sudden Export is not working .
Servers are up and running and File System was having enough/sufficient disk space..
Please Help to fix the problem.

Thanks.

[Reeza]

You should contact SAS tech support. 

But, what exactly is your SAS version?
And what changed from before it ran to now it doesn't run? 

[kumargupt]

version: 9.04.01M3P06242015

Export task is Creating the XLS File in Destination location.
But couldn't able to open the file.

Refer the attachment for the .xls file and Document with the screenshot of Messages while opening in xls.

Thanks,
Kiran

[ChrisHemedinger]

You would get that message if the data source you're exporting isn't able to be read.  Could be the data set was removed or something as simple as a LIBNAME was unassigned along the way.  Can you open the data in the data grid before the export step?

[kumargupt]

Tried with sample sashelp dataset .
Export task is creating the .xls file in the specified location

But could nt able to open the file . Refer the attachment for the .xls file and the document with the messages that were generated while opening the xls file.

 We  could open and view the data before start of export task.

[Reeza]

This shows SAS version 9.4 TS1M3 whereas you stated before you were running SAS 9.3, is that correct?

Is the PCFILE server running?

[kumargupt]

Hello Reeza,

The SAS Version is : 9.0301M0

Sorry for the Confusion.

Thanks,
Kiran.

[Reeza]

version: 9.04.01M3P06242015

Are you sure? That's a pretty different than above...sounds like you're working on multiple systems. And what has changed between when it did run and when it didn't? That's what you need to figure out.

[CaseySmith · Accepted solution]

It sounds like you may be encountering an issue that was introduced with this recent (10/10/2017) Microsoft update:

https://support.microsoft.com/en-us/help/4041691/windows-10-update-kb4041691

In the Known Issues section...

Installing this update may cause applications based on the Microsoft JET Database Engine (Microsoft Access 2007 and older or non-Microsoft applications) to fail when creating or opening Microsoft Excel .xls files. The error message is, “Unexpected error from external database driver (1). (Microsoft JET Database Engine)".

Download and install the Microsoft Access Database Engine 2010 Redistributable, and then modify the DB connection strings in Microsoft Excel to use ACE as a provider. Example: Change Provider=Microsoft.Jet.OLEDB.4.0 to Provider=Microsoft.ACE.OLEDB.12.0. Microsoft is working on a resolution and will provide an update in an upcoming release.

(If you wish to confirm this is the issue, turn on EG logging (in Tools->Options->Application Logging), reproduce the problem, then search your EG log for the error message, "Unexpected error from external database driver".)

Microsoft has not provided a resolution at this time.  Also, EG users can't make use of the Microsoft suggested workaround (above), since the EG application would have to be changed to implement the workaround.  We plan to contact Microsoft regarding this issue.

For now, there are some workarounds in EG (ex. export to another format, such as xlsx, csv; use proc export, etc.).

UPDATE: We contacted Microsoft.  They pointed out the blog post below which contains more details, and indicated a fix is forthcoming in their November update:

https://blogs.msdn.microsoft.com/dataaccesstechnologies/2017/10/18/unexpected-error-from-external-da...

Casey

[kumargupt]

Thank You Very much for the information.
The Issue is due to the Windows Security Updates that you mentioned in the Mail.

As A temporary workaround : We have requested our Systems team to Uninstall the Updates on Implacted PC's.

Thanks,
Kiran.