Difference between revisions of "ITrack/Crystal Reports Failed to retrieve from the database"
From ISoft Wiki
< ITrack
Jump to navigationJump to search
Daytonlowell (talk | contribs) |
Daytonlowell (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
* In most cases, this error is caused by the specific report. | * In most cases, this error is caused by the specific report. | ||
** Most likely, the internal query of the report failed when it was run. The report (or database structure) may be out of date. | ** Most likely, the internal query of the report failed when it was run. The report (or database structure) may be out of date. | ||
* Check ODBC, if its pointed to an actual server with a valid username and password but the database/table/field doesn't exist on this server(most likely because its not the correct server), you'll get this error. | * Check [[ITrack/ODBC|ODBC]], if its pointed to an actual server with a valid username and password but the database/table/field doesn't exist on this server(most likely because its not the correct server), you'll get this error. | ||
==Database Vendor Code: 506== | |||
This is caused by the MySQL ODBC driver incorrectly parsing comments. The bug is fixed as of version 5.2.4. | |||
* http://bugs.mysql.com/bug.php?id=53891 | |||
[[Category:ITrack/Problems/Crystal Reports]] | [[Category:ITrack/Problems/Crystal Reports]] | ||
Latest revision as of 16:20, 10 February 2015
Cause
Crystal Reports failed to get information to fill out the report, even though it did connect before the failure.
Solution
- In most cases, this error is caused by the specific report.
- Most likely, the internal query of the report failed when it was run. The report (or database structure) may be out of date.
- Check ODBC, if its pointed to an actual server with a valid username and password but the database/table/field doesn't exist on this server(most likely because its not the correct server), you'll get this error.
Database Vendor Code: 506
This is caused by the MySQL ODBC driver incorrectly parsing comments. The bug is fixed as of version 5.2.4.
