Crystal report error Details: DAO Error Code: 0xbe3

[Former Member]

The error users are getting when they run a Crystal Report from a VB 2005 program we wrote and deployed with click once and is as follows:

Logon failed.

Details: DAO Error Code: 0xbe3

Source: DAO.Workspace

Description:Disk or network error.

Error in File

C:\Users\Johnson\Appdata\Temp\temp_a4d1-4c50-aslkjasjkjfsd-{5ED96F71-B12D-441D-9266-DDFD2408B2E6}.rpt:

Unable to connect: incorrect log on parameters

This error does not occur in our development environment, nor has it occurred in the many times it has previously been deployed in what we believe wea the same manner.

Any thoughts?

Thanks,

[former_member183750 · Accepted solution]

Enable the option "Verify database..." on the report(s).

See the article [Troubleshooting Guide to Database Connectivity Issues with Crystal Reports in Visual Studio .NET Applications|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0225775-88c4-2c10-bd80-8298769293de].

Use the search box in the top right corner of this web page.

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

[Former Member · Accepted solution]

I can do a 'verify database' on the report while I'm on the development license, but where do I set the 'verify database...' on the deployed license?

[former_member183750 · Accepted solution]

Not sure I understand the "development license" v.s. "deployed license"...

But in any case. If you are using CRVS2010 and the reports are in the project, open the report in the .NET IDE designer. Right click on any empty space. From the pop-up menu select database. Enable the option "Verify on Every Print". Save.

You can also do this at runtime - after you logon to the database. See the [SAP Crystal Reports .NET API Guide|http://help.sap.com/businessobject/product_guides/sapCRVS2010/en/crnet_api_2010_en.zip]

- Ludek

[Former Member · Accepted solution]

We are using Visual Studio 2005 with the Crystal Report version that originally came with visual studio. I Believe it is a hybrid version 9 or 8.5+. Would the solution be different for this older version of Crystal? I'm having difficulty understanding why the reports work flawlessly on our development system but we get intermittant errors when the system is deployed on another system. The company using the deployed system is using the access database file we designed on our system and our reports are only addressing data from that mdb file.

[former_member183750 · Accepted solution]

Yup. Same applies. You are using CR 10.2.

Why the difficulties? Some possibilities:

1) DB differences - even a small difference may cause issues (thus the verify)

2) DB Client differences

3) CR runtime differences

To check on (2) and (3), use the [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] utility.

On line help for CR 10.2 is here:

http://msdn.microsoft.com/en-us/library/ms225270(VS.80).aspx

- Ludek