ITrack/Crystal Reports Logon Failed - Revision history

Duff: Merging with ITrack/IDispatch error 31816 - Logon failed

2012-01-18T21:17:03Z

Merging with ITrack/IDispatch error 31816 - Logon failed

← Older revision		Revision as of 16:17, 18 January 2012
Line 1:		Line 1:
	~~This error occurs when printing a report.~~		#REDIRECT [[ITrack/IDispatch error 31816 - Logon failed]]

	~~==Cause==~~
	~~This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an~~ [[ITrack~~\ODBC\|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.~~

	~~[[Category:ITrack/Problems/Crystal Reports~~]]

Codeman: Category naming conventions again.

2009-07-13T21:37:09Z

Category naming conventions again.

← Older revision		Revision as of 16:37, 13 July 2009
Line 14:		Line 14:
	It is also possible that some sort of software firewall could be blocking ODBC, but not ITrack itself.		It is also possible that some sort of software firewall could be blocking ODBC, but not ITrack itself.

	[[Category:~~Error Messages (~~ITrack~~)]]~~		[[Category:ITrack/Problems/Crystal Reports]]
	~~[[Category:Printing Error Messages (ITrack)~~]]

Daytonlowell at 22:41, 6 July 2009

2009-07-06T22:41:05Z

← Older revision		Revision as of 17:41, 6 July 2009
Line 2:		Line 2:

	==Cause==		==Cause==
	This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an 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.

	==Solution==		==Solution==

Codeman: Crystal/Logon Failed moved to ITrack/Crystal Reports Logon Failed

2009-06-26T19:25:44Z

Crystal/Logon Failed moved to ITrack/Crystal Reports Logon Failed

New page

This error occurs when printing a report.

==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.

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

Duff: Login Failed moved to Logon Failed (Crystal): It's a crystal error, and it says Logon instead of Login

2009-02-25T16:10:15Z

← Older revision	Revision as of 11:10, 25 February 2009
(No difference)

Duff: Added more details

2009-02-25T16:09:50Z

Added more details

← Older revision		Revision as of 11:09, 25 February 2009
Line 1:		Line 1:
			This error occurs when printing a report.

	==Cause==		==Cause==
	This error probably means that ~~your computer~~ is trying and failing to log into the ~~MYSQL~~ server.		This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an ODBC connection.

	==Solution==		==Solution==
	~~If your PC connects~~ with the ~~server over a VPN~~, make sure ~~that the VPN software is running~~ properly ~~on both machines.~~ If ~~that's~~ not the problem~~, then it's usually a good idea~~ to ~~make sure~~ the ~~MYSQL service~~ is ~~actually running on the intended host and~~ that ~~there are no firewalls~~ blocking ~~any necessary ports~~.		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:Error Messages (ITrack)]]		[[Category:Error Messages (ITrack)]]
	[[Category:Printing Error Messages (ITrack)]]		[[Category:Printing Error Messages (ITrack)]]

192.168.5.1 at 15:05, 25 February 2009

2009-02-25T15:05:50Z

← Older revision		Revision as of 10:05, 25 February 2009
Line 1:		Line 1:
	This error probably means that your computer is trying and failing to log into the MYSQL server. If your PC connects with the server over a VPN, make sure that the VPN software is running properly on both machines. If that's not the problem, then it's usually a good idea to make sure the MYSQL service is actually running on the intended host and that there are no firewalls blocking any necessary ports.		==Cause==
			This error probably means that your computer is trying and failing to log into the MYSQL server.

			==Solution==
			If your PC connects with the server over a VPN, make sure that the VPN software is running properly on both machines. If that's not the problem, then it's usually a good idea to make sure the MYSQL service is actually running on the intended host and that there are no firewalls blocking any necessary ports.

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

192.168.5.1: New page: This error probably means that your computer is trying and failing to log into the MYSQL server. If your PC connects with the server over a VPN, make sure that the VPN software is running...

2009-02-25T15:04:04Z

New page: This error probably means that your computer is trying and failing to log into the MYSQL server. If your PC connects with the server over a VPN, make sure that the VPN software is running...

New page

This error probably means that your computer is trying and failing to log into the MYSQL server. If your PC connects with the server over a VPN, make sure that the VPN software is running properly on both machines. If that's not the problem, then it's usually a good idea to make sure the MYSQL service is actually running on the intended host and that there are no firewalls blocking any necessary ports.