Custom Crystal Report Was Working and Now crw32.exe ver 14.2.6.2839 Crashes with c000041d error

[former_member967101]

I purchased Crystal 2016 in mid Dec 2018 and have been running an upgraded CR 2008 custom report every other week since then. This week it started crashing upon startup. I did have a Win 10 update recently. I ran the install program and did a repair which uninstalled and reinstalled most of the Crystal dll's. Still crashes,

Any ideas on how to debug this would be appreciated.

Below are the details from the Windows Report.wer dump:

Version=1
( removed for clarity )
AppName=Crystal Reports
AppPath=C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\crw32.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=96F44089A709BCC066C81EE56CA92F33
MetadataHash=-894723385

[former_member11696 · Accepted solution]

It could be your firewall or AV software is blocking access to the home page.

See this KBA to stop it from trying to get home and see if that works:

https://launchpad.support.sap.com/#/notes/1368945

Don

[former_member967101 · Accepted solution]

Don - Thank you for the quick reply.

I had a pending Windows 10 Update, so I rebooted my PC and let the update finish. I then retried my Crystal Report and it worked fine! My video editing software was acting funny tonight, so that is what prompted me to see if I had any pending Windows Update. I really HATE how these forced Windows updates mess up things.

As an aside, when I click on the link you gave, I get the following error:

"You are signed in with a P-user ID. Visitors with an S-user ID will benefit from more tools and enhanced functionality. If you are an SAP customer, contact a user administrator in your company to request such an ID. Your SAP Local Support Centercan help you identify your administrators. If you already own an S-user ID, log out now and log in with your S-user ID."

Any ideas on how to access the link you gave?

Brad

[former_member11696]

Sorry about that -

https://apps.support.sap.com/sap/support/knowledge/public/en/1368945

Will work, for any KBA just replace the last number.

Don