Error when creating a new CrystalReport.rpt file.

[Former Member]

I get the following error when attempting to add a new CrystalReport to my project:

Database Connection Error: ‘ADO Error Code: 0x80040e14

Source: Microsoft SQL Server Native Client 11.0

Description: Line 1: invalid procedure number (0). Must be between 1 and 32767.

SQL State: 42000

Native Error: 1005 [Database Vendor Code: 1005 ]’

This is happening as soon as I select the database:

It asks me to enter the database password, then crashed out with this error, without giving me the chance to even select any procedures.

There are procedures there, and the user account used to log in has access to them.

I'm using Visual Studio 2010.

[former_member188030 · Accepted solution]

What version of Crystal Reports and service pack are you using?

Does this happen when you try to connect to some other database?

Does this happen with all reports?

Thanks,

Bhushan

[Former Member · Accepted solution]

There are two Crystal Reports Engine Versions, 10.5.3700.0 and 13.0.2000.0

Yes, I tried and I can't connect (for anything new) to any database.

Existing reports are fine, but I can't add any new reports - even to the same database as the 'working' existing ones.

I can't even change a working report to look at the test database instead of the live one, or vice versa.

I've no idea what is happening.

p.s.

     Other people can do this, so it doesn't appear to be a problem with the database(s).

[former_member183750 · Accepted solution]

Database Vendor Code: 1005 is being passed from the database client through the report engine - unmodified. E.g.; look for the error in your database documentation.

See:

Failed to retrieve data from the database. Details: [Database Vendor Code: <vendor code numbe...

Failed to open the connection. Details: [Database Vendor Code: <vendor code number>].

Compare the version of the client you are using and "other people" are using.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter