Difference between revisions of "ITrack/IDispatch error 31816 - Logon failed"
From ISoft Wiki
< ITrack
Jump to navigationJump to search
(Adding some spicy info about this error) |
(Merging from ITrack/Crystal_Reports_Logon_Failed) |
||
| Line 3: | Line 3: | ||
Logon failed. | Logon failed. | ||
== | ==Cause== | ||
This error | This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an [[ITrack\ODBC|ODBC]] connection. | ||
== Solution | ==Solution== | ||
The first thing to do is check the ODBC connection on the computer with the error, and make sure these settings are properly configured: | |||
* | * Host | ||
* | * Username | ||
* Port | |||
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. | |||
[[Category:ITrack/Problems/Crystal Reports]] | |||
[[Category:ITrack/Printing Error Messages]] | [[Category:ITrack/Printing Error Messages]] | ||
[[Category:ITrack/Support]] | [[Category:ITrack/Support]] | ||
Revision as of 16:16, 18 January 2012
Logon failed.
Cause
This error probably means that Crystal Reports is trying and failing to log into the MySQL server using an ODBC connection.
Solution
The first thing to do is check the ODBC connection on the computer with the error, and make sure these settings are properly configured:
- Host
- Username
- Port
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.
