Difference between revisions of "ITrack/IDispatch error 31826"

From ISoft Wiki
Jump to navigationJump to search
(Sneaky sneaky)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
"Failed to retrieve data from the database."
[[Image:IDispatchError31826.png]]
[[Image:IDispatchError31826.JPG|400px|thumb|left]]
 
Failed to retrieve data from the database.


== Cause ==
== Cause ==
Line 8: Line 9:
Possible reasons the query would fail:
Possible reasons the query would fail:


* Something wrong with the report you are trying to print.
** Report isn't up-to-date
** User's database is not up to date
** Correct parameters were not passed in to the report.
* The ODBC driver is pointed at the wrong server.
* The ODBC driver is pointed at the wrong server.
* Correct parameters were not passed in to the report.
* The wrong report may be referenced in Edit > Options > Reports tab, causing ITrack to think that incorrect parameters are being passed in.
* Something wrong with the report you are trying to print (it is not up to date, or the user's database is not up to date).
* If you are able to successfully run the report query in SQLYog, but the report still won't print, try checking on the definers for the functions related to files/attachments.
* The wrong report my be referenced in Edit >> Options >> Reports, causing ITrack to think that incorrect parameters are being passed in.


[[Category:Printing Error Messages (ITrack)]]
[[Category:ITrack/Printing Error Messages]]


[[Category:ITrack/Support]]
[[Category:ITrack/Support]]

Latest revision as of 14:37, 12 May 2016

IDispatchError31826.png

Failed to retrieve data from the database.

Cause

This error occurs when Crystal was able to connect to a MySQL database, but the report query returned with an error.

Solution

Possible reasons the query would fail:

  • Something wrong with the report you are trying to print.
    • Report isn't up-to-date
    • User's database is not up to date
    • Correct parameters were not passed in to the report.
  • The ODBC driver is pointed at the wrong server.
  • The wrong report may be referenced in Edit > Options > Reports tab, causing ITrack to think that incorrect parameters are being passed in.
  • If you are able to successfully run the report query in SQLYog, but the report still won't print, try checking on the definers for the functions related to files/attachments.