ITrack/IDispatch error 31816 - Logon failed - Revision history

Nenjin: /* Cause */

2013-05-24T15:57:15Z

Cause

← Older revision		Revision as of 10:57, 24 May 2013
Line 6:		Line 6:
	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.		The error can also occur when a report is saved with an invalid (for the customer) database connection.

	==Solution==		==Solution==

Nenjin: /* Solution */

2013-05-24T15:56:31Z

Solution

← Older revision		Revision as of 10:56, 24 May 2013
Line 23:		Line 23:
	* Run the report.		* Run the report.
	* Where you're asked to put in your username/password, check the "database" field at the bottom of the window. Make sure it's pointed to 'itrackpro' or 'itrackenterprise' and not one of our testing databases.		* Where you're asked to put in your username/password, check the "database" field at the bottom of the window. Make sure it's pointed to 'itrackpro' or 'itrackenterprise' and not one of our testing databases.
	* Save the report after you've put in the right database and run it. Then deploy it to the customer.		* Save the report after you've put in the right database connection and run it. Then deploy it to the customer.

	[[Category:ITrack/Problems/Crystal Reports]]		[[Category:ITrack/Problems/Crystal Reports]]
	[[Category:ITrack/Printing Error Messages]]		[[Category:ITrack/Printing Error Messages]]
	[[Category:ITrack/Support]]		[[Category:ITrack/Support]]

Nenjin: /* Solution */

2013-05-24T15:55:11Z

Solution

← Older revision		Revision as of 10:55, 24 May 2013
Line 18:		Line 18:

	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.

			If you've eliminated ODBC errors as an issue:
			* Open the report using Crystal Reports.
			* Run the report.
			* Where you're asked to put in your username/password, check the "database" field at the bottom of the window. Make sure it's pointed to 'itrackpro' or 'itrackenterprise' and not one of our testing databases.
			* Save the report after you've put in the right database and run it. Then deploy it to the customer.

	[[Category:ITrack/Problems/Crystal Reports]]		[[Category:ITrack/Problems/Crystal Reports]]
	[[Category:ITrack/Printing Error Messages]]		[[Category:ITrack/Printing Error Messages]]
	[[Category:ITrack/Support]]		[[Category:ITrack/Support]]

Nenjin: /* Cause */

2013-05-24T15:52:08Z

Cause

← Older revision		Revision as of 10:52, 24 May 2013
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==

Daytonlowell at 21:22, 3 January 2013

2013-01-03T21:22:28Z

← Older revision		Revision as of 16:22, 3 January 2013
Line 11:		Line 11:
	* Port		* Port

	If the computer is running 64bit Windows, make sure you configure the 32bit version of the ODBC ~~drive~~, which is '''NOT''' found in Control Panel and is instead located at: %systemdrive%\Windows\SysWoW64\Odbcad32.exe		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.		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.

Daytonlowell at 21:21, 3 January 2013

2013-01-03T21:21:54Z

← Older revision		Revision as of 16:21, 3 January 2013
Line 7:		Line 7:

	==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:		In the ODBC configuration, make sure these settings are properly configured:
	* Host		* Host
	* Username
	* Port		* Port

			If the computer is running 64bit Windows, make sure you configure the 32bit version of the ODBC drive, 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.		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.

Duff: Merging from ITrack/Crystal_Reports_Logon_Failed

2012-01-18T21:16:27Z

Merging from ITrack/Crystal_Reports_Logon_Failed

← Older revision		Revision as of 16:16, 18 January 2012
Line 3:		Line 3:
	Logon failed.		Logon failed.

	== ~~Problem~~ ==		==Cause==
	This error ~~occurs because~~ the ~~login information in~~ ODBC ~~is incorrect~~.		This error probably means that [[Crystal Reports]] is trying and failing to log into the MySQL server using an [[ITrack\ODBC\|ODBC]] connection.

	== Solution~~(s)~~ ==		==Solution==
	* Open up ODBC~~, enter~~ the ~~correct information~~, and ~~hit "Test" to confirm that you have a connection.~~		The first thing to do is check the ODBC connection on the computer with the error, and make sure these settings are properly configured:
	* ~~If an ODBC entry exists for ITrack in the 'User DSN' tab, you should delete that out. The ODBC connections should be set up in the 'System DSN' tab.~~		* Host
	* ~~Try navigating to the reports directory and printing again.~~		* 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]]

Codeman: Adding some spicy info about this error

2012-01-12T18:21:00Z

Adding some spicy info about this error

← Older revision		Revision as of 13:21, 12 January 2012
Line 8:		Line 8:
	== Solution(s) ==		== Solution(s) ==
	* Open up ODBC, enter the correct information, and hit "Test" to confirm that you have a connection.		* Open up ODBC, enter the correct information, and hit "Test" to confirm that you have a connection.
			* If an ODBC entry exists for ITrack in the 'User DSN' tab, you should delete that out. The ODBC connections should be set up in the 'System DSN' tab.
	* Try navigating to the reports directory and printing again.		* Try navigating to the reports directory and printing again.

Codeman: Huh, I guess the new option I added worked. Not entirely sure why, but I figure it should be added to the wiki.

2011-12-07T14:50:31Z

Huh, I guess the new option I added worked. Not entirely sure why, but I figure it should be added to the wiki.

← Older revision		Revision as of 09:50, 7 December 2011
Line 6:		Line 6:
	This error occurs because the login information in ODBC is incorrect.		This error occurs because the login information in ODBC is incorrect.

	== Solution ==		== Solution(s) ==
	Open up ODBC, enter the correct information, and hit "Test" to confirm that you have a connection.		* Open up ODBC, enter the correct information, and hit "Test" to confirm that you have a connection.
			* Try navigating to the reports directory and printing again.

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

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

Duff: moved ITrack/IDispatch error 31816 to ITrack/IDispatch error 31816 - Logon failed: Now with error message

2011-10-31T17:37:08Z

moved ITrack/IDispatch error 31816 to ITrack/IDispatch error 31816 - Logon failed: Now with error message

← Older revision	Revision as of 12:37, 31 October 2011
(No difference)