Difference between revisions of "ITrack/IDispatch error 31816 - Logon failed"
Daytonlowell (talk | contribs) |
(→Cause) |
||
| Line 5: | Line 5: | ||
==Cause== | ==Cause== | ||
This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an [[ITrack\ODBC|ODBC]] connection. | This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an [[ITrack\ODBC|ODBC]] connection. | ||
This error can also occur when a report is saved with an invalid (for the customer) database connection. | |||
==Solution== | ==Solution== | ||
Revision as of 10:52, 24 May 2013
Logon failed.
Cause
This error probably means that Crystal Reports is trying and failing to log into the MySQL server using an ODBC connection.
This error can also occur when a report is saved with an invalid (for the customer) database connection.
Solution
In the ODBC configuration, make sure these settings are properly configured:
- Host
- Port
If the computer is running 64bit Windows, make sure you configure the 32bit version of the ODBC driver, which is NOT found in Control Panel and is instead located at: %systemdrive%\Windows\SysWoW64\Odbcad32.exe
If ITrack can connect, but Crystal Reports (through the ODBC connection) can not, the problem almost always has to do with the settings for the ODBC connection.
It is also possible that some sort of software firewall could be blocking ODBC, but not ITrack itself.
