Crystal Reports error after Windows update

[Former Member]

Hello,

I have a customer who is using Crystal Reports version 9.2.0.448. After a windows update they started receiving the following errors when trying to run any Crystal report. The error occurs when the reports attempts to refernce an excel file .

Logon failed.

Details: DAO Errror Code: 0xccb

Source: DAO.Workspace

Description: Unexpected error from external database driver (1).

[vitaly_izmaylov · Accepted solution]

The following solution approved by Developers:

Uninstall the following Microsoft KBs:

KB4041681 on Windows 7

KB4041676 on Windows 10

[Former Member · Accepted solution]

Hi there,

I have a client that is getting the same error but they are using Windows 8.1 64Bit.

Any idea what the Windows 8.1 update to uninstall is? I have searched for the updates listed but as suspected they are not available to uninstall.

Any help would be appreciated.

Many thanks

Ben

[Former Member]

Hello,

I am unable to uninstall the Microsoft Updates. I took a simple approach. I resaved the file to a different folder on my drive. This solved my issue.

[Former Member]

HELP!! I am having the same problem, and it is 100% mission-critical to be able to connect Crystal to Excel. I have uninstalled every Windows update in October and still get this error. If I don't reconnect Crystal to Excel soon, I'm out of business. Who knows what will work?

[former_member398199]

Did you have any luck Stephen??
We have started using the OLEDB drivers and it's working for us if the reports are run through Crystal Reports, however if they are run through the BO Server then they fail.

[former_member398199]

I am having the same issue and I can't resolve it!! This is absolutely vital that we resolve this - any help is appreciated 🙂

The oledb connection works if the excel data file is on the same server as Business Objects, but in production this is not the case, the Excel data file being used as a source is on a network server.

I create a new connection using the OLEDB (ADO) section, I was told to use the Microsoft Office 16.0 Access Database Engine OLEDB Provider.

I create a connection to the xls file

• Choose Excel as the Office Database Type
• and leave the User Id as Admin

I can refresh the data through Crystal on my laptop and I can access the data without issues.

I then save the report to Enterprise.

I go to CMC and change the Database Configuration to Use the same database logon as when report is run.

There are two options for Database logon information:

1. Use original fatabase logon information from the report
2. Use custom database logon information specified here. This option has the crdb_ado custom drivers set - I am not sure if this is correct

The default username of Admin is assigned but there is no password.

(Regardless of which options I choose here I seem to get the same error messages.)

When I log into the Launchpad I see the report I can open it, as I saved it with data but if I click refresh, I get the following error:

The viewer could not process an event. The database logon information for this report is either incomplete or incorrect. []
---- Error code:0 [CRWEB00000119]

I suspect the issue is connecting from the BO server to the server where the xls file is, however I don't know how to overcome the issue??

[former_member11696]

Use OLE DB:

link for step by step instructions to configure OLE DB connection:

https://blogs.sap.com/2013/06/21/steps-to-extract-data-from-an-excel-file-to-crystal-report-2011/

First, try to create a brand new report with OLE DB connection.

If it works, then open existing report, go to Database > Set Datasource connection and update the existing connection with new one.

Vitaly

[Former Member]

HELP!! I am having the same problem, and it is 100% mission-critical to be able to connect Crystal to Excel. I have uninstalled every Windows update in October and still get this error. If I don't reconnect Crystal to Excel soon, I'm out of business. Who knows what will work?

[Former Member]

I manage to refresh the report by left the connected Excel sheet open during refreshing the report. But the refreshing speed was too slow.

[former_member11696]

The fix is to Stop using the legacy DAO engine and move to ODBC or OLE DB to connect CR to your data sources.

Upgrade to current versions of Crystal Reports, CR 9 is 10+ years old.

You can upgrade here:

https://www.sap.com/products/crystal-reports.html

Don

[Former Member]

Same problem - have had to ask IT to un-install but this needs to be resolved for the long-term as we now have 2 machines without the latest security features

Is there any news on when a new upgrade is available from MS?

IS there a way to be notified so that we can re-activate upgrades on affected machines

Thanks

[vitaly_izmaylov]

The best long term suggestion for now is to change DAO connectivity to OLE DB.

“Unexpected error from external database driver (1). (Microsoft JET Database Engine)” after applying...

Microsoft is working on a resolution and will provide an update in an upcoming release.

October 10, 2017—KB4041678 (Security-only update)

[Former Member]

We have had the same problem - have had to ask IT to un-install but this needs to be resolved for the long-term as we now have 2 machines without the latest security features

Is there any news on when a new upgrade is available from MS?

Is there a way to be notified so that we can re-activate upgrades on affected machines

Thanks

[Former Member]

Hi there,

I have a client that is getting the same error but they are using Windows 8.1 64Bit.

Any idea what the Windows 8.1 update to uninstall is? I have searched for the updates listed but as suspected they are not available to uninstall.

Any help would be appreciated.

Many thanks

Ben

RE ADDED THIS TO SEE IF SOMEONE HAD AN ANSWER!?

[Former Member]

Uninstalling KB4041681 did not work for us.

The problem patch updated the Excel Jet connector from V4.00.9801.0 to 4.00.9801.1

We restored the old dll file "msexcl40.dll" to a new directory C:\Windows\SysWOW64\exceldriver\ and then updated the registry key HKLM\Software\Wow6432Node\Microsift\Jet\4.0\Engines\ExcelWin32 value from C:\Windows\SysWOW64\ to C:\Windows\SysWow64\exceldriver\

[vitaly_izmaylov]

The Update affected not only Crystal Reports, but all the applications connecting to Excel with the same engine, see:

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/kb4041681-and-microsoftodbc-excel...

I expect Microsoft to fix the Update soon.

[Former Member]

Hi,

Thanks for the response but this is not a long term solution. They already rolled back the update.

Will they need to upgrade to the latest version?