Unexpected error from external database driver

[Former Member]

SAP Crystal Reports 16.

Standalone Windows 10 PC

Data saved as xls but in Office 365.

Since an update to Office yesterday, I get the error -

Logon failed - Details DAD Error Code 0xccb - Source DAO Workspace - Unexpected error from external database driver (1).

Access files work OK, but I need to use the spreadsheets.

[Former Member]

I am seeing this too. I tracked it down to an update KB4041676; after uninstalling this update my CR worked fine. I hope someone at SAP can help or a new Microsoft Update fixes this issue.

[Former Member]

Thank you - I will try to uninstall the update.

[Former Member]

I am having identical problems however with different program versions as noted below. Also began after Microsoft updates on 10/10/17.

Crystal Reports 11

Office 2010

Windows 7 32 bit

I believe KB4041676 is Windows 10 related as it is not installed on my system. Hopefully a fix is on the way...

[Former Member]

Yes, this KB4041676 is for Windows 10. I would try to narrow it down for your windows 7 machine on which update is causing the issue. I would talk to your system administrator though just in case.

[Former Member]

I uninstalled the update KB4041676, and I could run my reports correctly.

But, the same update has automatically downloaded and prompted for a restart to finish installation. I have have uninstalled it again, I assume in it's wisdom Microsoft will continue to try to install. Assuming it is the same update as before, I will have the same problem.

I don not want to keep unistalling the update (which I assume contains stuff I need), so do any of you much cleverer users than me, know of a permament solution?

It's a standalone PC - on 24/7

[Former Member]

Does this happen on the newer versions of Crystal? I am thinking of just biting the bullet and upgrading...

[Former Member]

A slightly newer Windows security update, KB4041691, was the culprit. The update was downloaded and installed automatically on October 10, and that's when the trouble started. The KB4041691 was uninstalled and Crystal Reports returned to normal. I didn't turn the automatic update feature off, and of course the KB4041691 reinstalled itself, starting the problem all over again. Uninstalling the update (again) and turning the automatic update feature off cured the problem, and after turning the computer off and starting again today the problem continued to be cured.

Bottom line: if you are running a Windows 10 operating system, 64 bit, look either for the original culprit, KB4041676 or the one released on October 10, KB4041691, and uninstall it. Be sure to turn the automatic update feature off in the System Administration folder so you aren't gifted with another automatic update of the culprit file.