SQL Database Troubleshooting - Revision history

Dina at 07:49, 13 January 2022

2022-01-13T07:49:14Z

← Older revision		Revision as of 07:49, 13 January 2022
Line 122:		Line 122:

	==Recurring issues after Rebooting the RangerMSP Server Machine==		==Recurring issues after Rebooting the RangerMSP Server Machine==
	The RangerMSP database chooses its database mode upon the first concurrent connection to the system. If a client application, or RangerMSP Addon Service (Such as '''~~CommmitCRM WebInterface~~''', '''~~RangerMSP~~ Server''' or '''~~RangerMSP RMMServer~~''') service is already loaded and connected to the server before the Advantage Database Server service finishes loading, then all subsequent connections will be rejected since the prior connection to the database would not allow the Advantage Database Server service full control over the database.		The RangerMSP database chooses its database mode upon the first concurrent connection to the system. If a client application, or RangerMSP Addon Service (Such as '''CRM Web Interface''', '''CRM Server''' or '''CRM RMM Server''') service is already loaded and connected to the server before the Advantage Database Server service finishes loading, then all subsequent connections will be rejected since the prior connection to the database would not allow the Advantage Database Server service full control over the database.

	Typical characteristics of this type of problem are repeated manual attention needed to properly connect Advantage Database Server to RangerMSP after rebooting, and restarting the Advantage Database Server service.		Typical characteristics of this type of problem are repeated manual attention needed to properly connect Advantage Database Server to RangerMSP after rebooting, and restarting the Advantage Database Server service.
Line 137:		Line 137:
	<br>		<br>
	===Adding Service Dependency Rules===		===Adding Service Dependency Rules===
	Now that RangerMSP depends on the Advantage Database Server Database service, the RangerMSP Services (~~RangerMSP WebInterface~~, ~~RangerMSP~~ Server and ~~RangerMSP RMMServer~~) also need the Advantage Database Server server to to be up before they try to load.		Now that RangerMSP depends on the Advantage Database Server Database service, the RangerMSP Services (CRM Web Interface, CRM Server and CRM RMM Server) also need the Advantage Database Server server to to be up before they try to load.
	To set these services to be dependent on the Advantage Database Server Service, follow these steps:		To set these services to be dependent on the Advantage Database Server Service, follow these steps:
	# Backup your current registry settings.		# Backup your current registry settings.
	# Run '''regedit''' to open your registry.		# Run '''regedit''' to open your registry.
	# Navigate to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services''' and locate the '''~~RangerMSP WebInterface~~''', '''~~RangerMSP~~ Server''' or '''~~RangerMSP RMMServer~~''' services that you need to set a dependency for.		# Navigate to '''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services''' and locate the '''CRM Web Interface''', '''CRM Server''' or '''CRM RMM Server''' services that you need to set a dependency for.
	# Open the '''DependOnService''' key on the right side. If the selected service does not have a '''DependOnService''' key, then create one by right-clicking and selecting '''New > Multi-String Value'''.		# Open the '''DependOnService''' key on the right side. If the selected service does not have a '''DependOnService''' key, then create one by right-clicking and selecting '''New > Multi-String Value'''.
	# In the '''value''' field, enter '''Advantage'''.		# In the '''value''' field, enter '''Advantage'''.

Dina at 13:42, 8 July 2020

2020-07-08T13:42:40Z

Show changes

Dina: Dina moved page Commit SQL Database Troubleshooting to SQL Database Troubleshooting

2020-03-21T20:16:27Z

Dina moved page Commit SQL Database Troubleshooting to SQL Database Troubleshooting

← Older revision	Revision as of 20:16, 21 March 2020
(No difference)

Dina at 20:12, 21 March 2020

2020-03-21T20:12:21Z

← Older revision		Revision as of 20:12, 21 March 2020
Line 26:		Line 26:

	===Advantage Server===		===Advantage Server===
	*Verify the Advantage Database Server service is started on your server. For installation instructions click [[~~Commit_SQL_Database_Installation_Guide~~\|here]] or [[~~Commit_SQL_Database_for_Trial_Users~~\|here]] if your are using a trial copy of SQL.		*Verify the Advantage Database Server service is started on your server. For installation instructions click [[SQL_Database_Installation_Guide\|here]] or [[SQL_Database_for_Trial_Users\|here]] if your are using a trial copy of SQL.

	*'''Please restart all CommitCRM services, and retest communications by loading a CommitCRM Client application from another computer.'''		*'''Please restart all CommitCRM services, and retest communications by loading a CommitCRM Client application from another computer.'''
Line 149:		Line 149:

	==See Also==		==See Also==
	*[[~~Commit_SQL_Database_Installation_Guide~~\|SQL Database Installation Guide]]		*[[SQL_Database_Installation_Guide\|SQL Database Installation Guide]]
	*[[~~Commit_SQL_Database_for_Trial_Users~~\|SQL Database for Trial Users]]		*[[SQL_Database_for_Trial_Users\|SQL Database for Trial Users]]
	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

Dina: /* ADS.ini – Server Locator */

2018-05-24T11:53:00Z

ADS.ini – Server Locator

← Older revision		Revision as of 11:53, 24 May 2018
Line 49:		Line 49:
	===ADS.ini – Server Locator===		===ADS.ini – Server Locator===
	*The CommitCRM client's way of finding the SQL Database Server fails. In order for the client to detect where the server is running it broadcasts a UDP message and asks for the server to answer. When the server answers the client knows the server IP and can communicate with it.		*The CommitCRM client's way of finding the SQL Database Server fails. In order for the client to detect where the server is running it broadcasts a UDP message and asks for the server to answer. When the server answers the client knows the server IP and can communicate with it.
	*On your server, you can run the Advantage Configuration Utility ('''Start Menu > Programs > Advantage Database Server 9.0 > Advantage Configuration Utility > Configuration Utility tab > Communications tab'''). Using it you can find the Port number which is used for communicating with the clients. When adjusting the SQL ports, you can use any port you like, as long as the port is not being used by any other software.		*On your server, you can run the Advantage Configuration Utility ('''Start Menu > Programs > Advantage Database Server 11.10 > Advantage Configuration Utility > Configuration Utility tab > Communications tab'''). Using it you can find the Port number which is used for communicating with the clients. When adjusting the SQL ports, you can use any port you like, as long as the port is not being used by any other software.

	<br>		<br>

Dina: /* ADS.ini – Server Locator (Supplemental) */

2018-05-24T10:26:57Z

ADS.ini – Server Locator (Supplemental)

← Older revision		Revision as of 10:26, 24 May 2018
Line 86:		Line 86:

	===ADS.ini – Server Locator (Supplemental)===		===ADS.ini – Server Locator (Supplemental)===
	*If the Ads.ini file does not correct the issue, then we suggest ~~that~~ '''~~changing the~~ Server hostname reference''' in ADS.ini ~~to the '''server IP address [192.168.x.x]''' will correct this behavior.~~ (Remember to restart Advantage Service each time ADS.ini is adjusted)		*If the Ads.ini file does not correct the issue, then we suggest adding additional section with the '''Server hostname reference''' in ADS.ini (Remember to restart Advantage Service each time ADS.ini is adjusted)
	For example:		For example:
	'''[192.168.0.1] <br>LAN_IP=192.168.0.1<br>LAN_PORT=2001 '''		'''[192.168.0.1] <br>LAN_IP=192.168.0.1<br>LAN_PORT=2001 '''<br><br>
			'''[Your-Server-Name] <br>LAN_IP=192.168.0.1<br>LAN_PORT=2001 '''
	''IMPORTANT NOTE:''		''IMPORTANT NOTE:''
	*Please replace the ServerName (between the brackets) with '''the servers IP address''', as displayed in the example above.		*Please replace the ServerName (between the brackets) with '''the servers IP address''', as displayed in the example above.

Dina: /* Important Note For Users that Use our ODBC API */

2018-05-24T10:21:24Z

Important Note For Users that Use our ODBC API

← Older revision		Revision as of 10:21, 24 May 2018
Line 102:		Line 102:
	* The ADS.ini file succeeded in logging in the CommitCRM Software Applications (Clients).		* The ADS.ini file succeeded in logging in the CommitCRM Software Applications (Clients).

	* When using applications you developed with ODBC you receive a message regarding Database Discovery Failure (Error code ~~6320~~).		* When using applications you developed with ODBC you receive a message regarding Database Discovery Failure (Error code 6420) or "No connected server was found for the given drive letter" (Error 5033).

	If all of the above prerequisites exist, you should copy the ADS.ini file you prepared from the CommitCRM server folder into the following folder on each the affected workstation:		If all of the above prerequisites exist, you should

			1. copy the ADS.ini file you prepared from the CommitCRM server folder into the following folder on each the affected workstation:

	* '''%Windir%\system32'''		* '''%Windir%\system32'''
Line 111:		Line 113:

	'''Note:''' To open these folders on your PC you can paste the paths listed above into a Windows Run dialog box, or into any Windows Explorer path.		'''Note:''' To open these folders on your PC you can paste the paths listed above into a Windows Run dialog box, or into any Windows Explorer path.

			2. Change the database path configured for ODBC connection to include the server IP address and port used by Advantage Database Server, for example:
			\\192.168.0.1:6262\CommitCRM\Db


	<br>		<br>

Dina: /* Recurring issues after Rebooting the CommitCRM Server Machine */

2017-11-28T14:11:04Z

Recurring issues after Rebooting the CommitCRM Server Machine

← Older revision		Revision as of 14:11, 28 November 2017
Line 126:		Line 126:
	#If successful, Start '''CommitCRM Services'''.		#If successful, Start '''CommitCRM Services'''.

	If this process was successful, this is because the '''CommitCRM Services loaded before Advantage Database Server did''', locking Advantage Database Server out of the CommitCRM database. To permanently resolve this behavior, ~~manual rules will~~''' ~~need to be created~~''' ~~in order to ensure that The CommitCRM Services~~ '~~''do not try to load without Advantage Database Server being started~~'''.		If this process was successful, this is because the '''CommitCRM Services loaded before Advantage Database Server did''', locking Advantage Database Server out of the CommitCRM database. To permanently resolve this behavior, use the Services Management window, to define all CommitCRM services to start automatically with a ''Delayed Start'' ('''Startup type > Automatic (Delayed Start)''') each time the server is restarted.

	<br>		<br>

Dina at 15:03, 21 July 2016

2016-07-21T15:03:58Z

Dina: /* DEP – Data Execution Prevention */

2016-07-21T15:01:06Z

DEP – Data Execution Prevention

← Older revision		Revision as of 15:01, 21 July 2016
Line 32:		Line 32:

	===DEP – Data Execution Prevention===		===DEP – Data Execution Prevention===
	*Please ensure that if using DEP on the server, where ~~CommitCRM~~ SQL ~~Database~~ (aka, Advantage Database Server) is installed, it should be configured to allow data execution for '''ADS.exe''', by default located in the following folder '''C:\Program Files\Extended Systems\Advantage 9007\Server'''. This file is the SQL Database for CommitCRM / Advantage Database Server Windows service executable file and therefore should be allowed, or else DEP may isolate the SQL software from communicating with the CommitCRM client applications.		*Please ensure that if using DEP on the server, where SQL (aka, Advantage Database Server) is installed, it should be configured to allow data execution for '''ADS.exe''', by default located in the following folder '''C:\Program Files\Extended Systems\Advantage 9007\Server'''. This file is the SQL Database for CommitCRM / Advantage Database Server Windows service executable file and therefore should be allowed, or else DEP may isolate the SQL software from communicating with the CommitCRM client applications.

	*'''Please restart the Advantage service & all CommitCRM services, and retest communications by loading a CommitCRM Client application from another computer.'''		*'''Please restart the Advantage service & all CommitCRM services, and retest communications by loading a CommitCRM Client application from another computer.'''

← Older revision		Revision as of 15:03, 21 July 2016
Line 48:		Line 48:

	===ADS.ini – Server Locator===		===ADS.ini – Server Locator===
	*The CommitCRM client's way of finding the ~~CommitCRM~~ SQL Database Server fails. In order for the client to detect where the server is running it broadcasts a UDP message and asks for the server to answer. When the server answers the client knows the server IP and can communicate with it.		*The CommitCRM client's way of finding the SQL Database Server fails. In order for the client to detect where the server is running it broadcasts a UDP message and asks for the server to answer. When the server answers the client knows the server IP and can communicate with it.
	*On your server, you can run the Advantage Configuration Utility ('''Start Menu > Programs > Advantage Database Server 9.0 > Advantage Configuration Utility > Configuration Utility tab > Communications tab'''). Using it you can find the Port number which is used for communicating with the clients. When adjusting the SQL ports, you can use any port you like, as long as the port is not being used by any other software.		*On your server, you can run the Advantage Configuration Utility ('''Start Menu > Programs > Advantage Database Server 9.0 > Advantage Configuration Utility > Configuration Utility tab > Communications tab'''). Using it you can find the Port number which is used for communicating with the clients. When adjusting the SQL ports, you can use any port you like, as long as the port is not being used by any other software.

Line 55:		Line 55:
	<br>		<br>
	<br>		<br>
	As explained in the previous steps, you should make sure that the Windows firewall on each client on your LAN allows communication with the server for this port. Verifying this will allow communication between the CommitCRM client and ~~CommitCRM~~ SQL ~~Database~~ on the server.		As explained in the previous steps, you should make sure that the Windows firewall on each client on your LAN allows communication with the server for this port. Verifying this will allow communication between the CommitCRM client and SQL on the server.
	<br>		<br>
	<br>		<br>
Line 72:		Line 72:
	*Replace '''MYSERVER''' with the name of '''YOUR server'''		*Replace '''MYSERVER''' with the name of '''YOUR server'''
	*Replace the '''192.168.0.1''' IP address with the '''LOCAL IP address of your server'''.		*Replace the '''192.168.0.1''' IP address with the '''LOCAL IP address of your server'''.
	*Replace the port number '''2001 '''to the one used for ~~CommitCRM~~ SQL ~~Database~~ in your setup ('''this can be viewed by running Advantage Configuration Utility on your server, look for the port in use for your LAN''').		*Replace the port number '''2001 '''to the one used for SQL in your setup ('''this can be viewed by running Advantage Configuration Utility on your server, look for the port in use for your LAN''').


Line 98:		Line 98:
	I some cases your system may still present an error message regarding failure of the Discovery process (Advantage Error 6320) when trying to access to the CommitCRM database using an ODBC connection, even after the ADS.ini file has resolved the issues with CommitCRM clients being able to discover the Advantage server. The following solution should resolve this issue as long as the following conditions are met:		I some cases your system may still present an error message regarding failure of the Discovery process (Advantage Error 6320) when trying to access to the CommitCRM database using an ODBC connection, even after the ADS.ini file has resolved the issues with CommitCRM clients being able to discover the Advantage server. The following solution should resolve this issue as long as the following conditions are met:

	* You use the ~~CommitCRM~~ SQL ~~Database~~ (aka, Advantage Database Server on your server) and ODBC.		* You use the SQL (aka, Advantage Database Server on your server) and ODBC.

	* The ADS.ini file succeeded in logging in the CommitCRM Software Applications (Clients).		* The ADS.ini file succeeded in logging in the CommitCRM Software Applications (Clients).