Network Issues Troubleshooting - Revision history

Dina at 13:15, 8 July 2020

2020-07-08T13:15:38Z

Dina at 18:26, 18 June 2020

2020-06-18T18:26:10Z

← Older revision		Revision as of 18:26, 18 June 2020
Line 37:		Line 37:
	<br>		<br>
	===SQL Database Users===		===SQL Database Users===
	*Customers that utilize the various features that the [http://~~www.commitcrm.com~~/~~sql_database_server.htm~~ SQL Database for CommitCRM] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.		*Customers that utilize the various features that the [http://{{SERVERNAME}}//products/sql-database/ SQL Database for CommitCRM] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.
	<br>		<br>
	*'''For more information regarding SQL Database troubleshooting, [[SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding SQL Database troubleshooting, [[SQL_Database_Troubleshooting\|please click here]].'''

Dina at 20:15, 21 March 2020

2020-03-21T20:15:38Z

← Older revision		Revision as of 20:15, 21 March 2020
Line 39:		Line 39:
	*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm SQL Database for CommitCRM] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.		*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm SQL Database for CommitCRM] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.
	<br>		<br>
	*'''For more information regarding SQL Database troubleshooting, [[~~Commit_SQL_Database_Troubleshooting~~\|please click here]].'''		*'''For more information regarding SQL Database troubleshooting, [[SQL_Database_Troubleshooting\|please click here]].'''

	<br>		<br>

	==See Also==		==See Also==
	*'''[[~~Commit_SQL_Database_Troubleshooting~~\|SQL Database Troubleshooting]]'''		*'''[[SQL_Database_Troubleshooting\|SQL Database Troubleshooting]]'''

	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

Dina: /* See Also */

2016-07-24T07:55:29Z

Dina: /* SQL Database Users */

2016-07-24T07:55:05Z

SQL Database Users

← Older revision		Revision as of 07:55, 24 July 2016
Line 36:		Line 36:

	<br>		<br>
	===~~CommitCRM~~ SQL Database Users===		===SQL Database Users===
	*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm ~~CommitCRM~~ SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the ~~CommitCRM~~ SQL Database.		*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm SQL Database for CommitCRM] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.
	<br>		<br>
	*'''For more information regarding ~~CommitCRM~~ SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''

	<br>		<br>

Robert at 10:58, 1 September 2013

2013-09-01T10:58:07Z

← Older revision		Revision as of 10:58, 1 September 2013
Line 36:		Line 36:

	<br>		<br>
	===~~Commit~~ SQL Database Users===		===CommitCRM SQL Database Users===
	*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm ~~Commit~~ SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the ~~Commit~~ SQL Database.		*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm CommitCRM SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the CommitCRM SQL Database.
	<br>		<br>
	*'''For more information regarding ~~Commit~~ SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding CommitCRM SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''

	<br>		<br>

	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|~~Commit~~ SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|CommitCRM SQL Database Troubleshooting]]'''

	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

Reno: /* See Also */

2009-12-24T17:19:21Z

Reno: /* Commit SQL Database Users */

2009-12-24T17:18:27Z

Commit SQL Database Users

← Older revision		Revision as of 17:18, 24 December 2009
Line 37:		Line 37:
	<br>		<br>
	===Commit SQL Database Users===		===Commit SQL Database Users===
	*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm Commit SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur.		*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm Commit SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.
	*The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.		<br>
	*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''

	<br>		<br>

	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''
	[[Category:KB\|Troubleshooting]]		[[Category:KB\|Troubleshooting]]

Reno: /* Commit SQL Database Users */

2009-12-24T17:17:34Z

Commit SQL Database Users

← Older revision		Revision as of 17:17, 24 December 2009
Line 4:		Line 4:
	__TOC__		__TOC__

			<br>
	==How do I know that I have Network Issues?==		==How do I know that I have Network Issues?==
	Network issues are rather difficult to diagnose, since the problem can be caused by hardware as well as software. If you think you have network issues or any other unexplained issues, then the best way to find out the lingering issue is to send us the CommitCRM log files. Once we determine the specific issue, we'll reply with the specific cause of the problem, and suggested steps to resolve the issue.		Network issues are rather difficult to diagnose, since the problem can be caused by hardware as well as software. If you think you have network issues or any other unexplained issues, then the best way to find out the lingering issue is to send us the CommitCRM log files. Once we determine the specific issue, we'll reply with the specific cause of the problem, and suggested steps to resolve the issue.

	<br>		<br>

	==Assessment==		==Assessment==
	When dealing with network communications traffic issues for CommitCRM, the issue can be Software based, Socket based, or Network based. The following information can greatly ease the diagnosis flow:		When dealing with network communications traffic issues for CommitCRM, the issue can be Software based, Socket based, or Network based. The following information can greatly ease the diagnosis flow:
Line 17:		Line 16:
	*Does this happen with all computers?		*Does this happen with all computers?

			<br>
	==Network Troubleshooting==		==Network Troubleshooting==
			<br>
	===System based network issues===		===System based network issues===
	When the problem is restricted to 1 computer, the problem is usually caused by certain configuration options, and protective solutions; however, it is always good practice to '''make sure that the network card on the computer in question is fully functional, with up to date drivers'''.		When the problem is restricted to 1 computer, the problem is usually caused by certain configuration options, and protective solutions; however, it is always good practice to '''make sure that the network card on the computer in question is fully functional, with up to date drivers'''.
Line 25:		Line 26:

	<br>		<br>

	===Socket Based network issues===		===Socket Based network issues===
	If the issue is limited to a group of network sockets, then this is usually due to a bandwidth overload in the routing switch (This would mean that the group of sockets share the same switch), and therefore must be investigated, treated, and possibly replaced as quickly as possible. If this is the case, the issue may be temporary; however, this must be treated since overload issues may repeat easily. This theory can be easily tested by benchmarking the network traffic capabilities on the affected servers, and measuring if the ping is fast enough, and if the speed is normal.		*If the issue is limited to a group of network sockets, then this is usually due to a bandwidth overload in the routing switch (This would mean that the group of sockets share the same switch), and therefore must be investigated, treated, and possibly replaced as quickly as possible.
			*If this is the case, the issue may be temporary; however, this must be treated since overload issues may repeat easily. This theory can be easily tested by benchmarking the network traffic capabilities on the affected servers, and measuring if the ping is fast enough, and if the speed is normal.

			<br>
	===Network-Wide issues===		===Network-Wide issues===
	Network wide traffic issues could mean that there’s a problem with a main network junction; however, if the network wide issues are only related to CommitCRM, then this means that the network wide CommitCRM issues are due to system based problem localized to the server CommitCRM is installed on. The best way to test this is to run through all the steps in the System based Network issues chapter; and if unsuccessful, transferring the CommitCRM system to another computer would be the next step which will allow you to quickly resume your CRM duties while you troubleshoot the system wide issue on the previous server.		*Network wide traffic issues could mean that there’s a problem with a main network junction; however, if the network wide issues are only related to CommitCRM, then this means that the network wide CommitCRM issues are due to system based problem localized to the server CommitCRM is installed on.
			*The best way to test this is to run through all the steps in the System based Network issues chapter; and if unsuccessful, transferring the CommitCRM system to another computer would be the next step which will allow you to quickly resume your CRM duties while you troubleshoot the system wide issue on the previous server.

			<br>
	===Commit SQL Database Users===		===Commit SQL Database Users===
	Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm Commit SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur.		*Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm Commit SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur.
	~~rThe~~ troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.		*The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.
	*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''

	<br>		<br>

	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''
	[[Category:KB\|Troubleshooting]]		[[Category:KB\|Troubleshooting]]

Reno: /* Commit SQL Database Users */

2009-12-24T17:15:19Z

Commit SQL Database Users

← Older revision		Revision as of 17:15, 24 December 2009
Line 35:		Line 35:

	===Commit SQL Database Users===		===Commit SQL Database Users===
	~~The~~ troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.		Customers that utilize the various features that the [http://www.commitcrm.com/sql_database_server.htm Commit SQL Database] also benefit from increased network performance and security, so these types of errors are much less likely to occur.
			rThe troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the Commit SQL Database.
	*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding Commit SQL Database troubleshooting, [[Commit_SQL_Database_Troubleshooting\|please click here]].'''

			<br>

	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''
	[[Category:KB\|Troubleshooting]]		[[Category:KB\|Troubleshooting]]

← Older revision		Revision as of 17:19, 24 December 2009
Line 45:		Line 45:
	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|Commit SQL Database Troubleshooting]]'''
	[[Category:~~KB\|~~Troubleshooting]]
			[[Category:Troubleshooting]]

← Older revision		Revision as of 13:15, 8 July 2020
Line 1:		Line 1:
	==Introduction==		==Introduction==
	Since ~~CommitCRM~~ is a network based application, it is highly dependent on continuous network communication traffic. For this reason, some computers may be configured or used in a way that could temporarily stop network traffic. When diagnosing network traffic issues, it is important to properly assess the situation and gather as much information as possible, in order to quickly identify the problem.		Since RangerMSP is a network based application, it is highly dependent on continuous network communication traffic. For this reason, some computers may be configured or used in a way that could temporarily stop network traffic. When diagnosing network traffic issues, it is important to properly assess the situation and gather as much information as possible, in order to quickly identify the problem.

	__TOC__		__TOC__
Line 6:		Line 6:
	<br>		<br>
	==How do I know that I have Network Issues?==		==How do I know that I have Network Issues?==
	Network issues are rather difficult to diagnose, since the problem can be caused by hardware as well as software. If you think you have network issues or any other unexplained issues, then the best way to find out the lingering issue is to send us the ~~CommitCRM~~ log files. Once we determine the specific issue, we'll reply with the specific cause of the problem, and suggested steps to resolve the issue.		Network issues are rather difficult to diagnose, since the problem can be caused by hardware as well as software. If you think you have network issues or any other unexplained issues, then the best way to find out the lingering issue is to send us the RangerMSP log files. Once we determine the specific issue, we'll reply with the specific cause of the problem, and suggested steps to resolve the issue.

	<br>		<br>
	==Assessment==		==Assessment==
	When dealing with network communications traffic issues for ~~CommitCRM~~, the issue can be Software based, Socket based, or Network based. The following information can greatly ease the diagnosis flow:		When dealing with network communications traffic issues for RangerMSP, the issue can be Software based, Socket based, or Network based. The following information can greatly ease the diagnosis flow:
	*Does the problem only show in 1 computer?		*Does the problem only show in 1 computer?
	*If the one computer network cable is conntected to a different network socket, does the issue persist?		*If the one computer network cable is conntected to a different network socket, does the issue persist?
Line 21:		Line 21:
	===System based network issues===		===System based network issues===
	When the problem is restricted to 1 computer, the problem is usually caused by certain configuration options, and protective solutions; however, it is always good practice to '''make sure that the network card on the computer in question is fully functional, with up to date drivers'''.		When the problem is restricted to 1 computer, the problem is usually caused by certain configuration options, and protective solutions; however, it is always good practice to '''make sure that the network card on the computer in question is fully functional, with up to date drivers'''.
	*The only software that would hinder communications with the ~~CommitCRM~~ server enough to cause an error to be sent out is a Firewall. If you have any active software firewalls, it is suggested to temporarily disable all firewalls installed on the computer, and restarting the ~~CommitCRM~~ client. If the ~~CommitCRM~~ client works as it should, then you should re-activate each firewall you’ve disabled while restarting the ~~CommitCRM~~ client, to see which firewall needs an exception set for ~~CommitCRM~~.		*The only software that would hinder communications with the RangerMSP server enough to cause an error to be sent out is a Firewall. If you have any active software firewalls, it is suggested to temporarily disable all firewalls installed on the computer, and restarting the RangerMSP client. If the RangerMSP client works as it should, then you should re-activate each firewall you’ve disabled while restarting the RangerMSP client, to see which firewall needs an exception set for RangerMSP.
	*If the Network issues only present itself while the computer is idle for long periods of time, then we suggest checking the power settings for the computer to make sure that the computer does not hibernate/sleep/power down the hard disks, as well as automated shutdown mechanisms that put the computer to sleep once the lid has been closed. Actions like these can stop network communication, causing the system to lose the connection by the time the network has reacquired the connection.		*If the Network issues only present itself while the computer is idle for long periods of time, then we suggest checking the power settings for the computer to make sure that the computer does not hibernate/sleep/power down the hard disks, as well as automated shutdown mechanisms that put the computer to sleep once the lid has been closed. Actions like these can stop network communication, causing the system to lose the connection by the time the network has reacquired the connection.
	*Laptops also have an automatic mechanism that can shut the hard disks down if the laptop has been moved abruptly. Also, all MS Windows operating systems come with a default hardware setting that powers down the Network Interface (Network Card), in the event that the computer is idle for extended periods of time. These types of protective software configurations can also cause network instability; however, only in extreme rare cases.		*Laptops also have an automatic mechanism that can shut the hard disks down if the laptop has been moved abruptly. Also, all MS Windows operating systems come with a default hardware setting that powers down the Network Interface (Network Card), in the event that the computer is idle for extended periods of time. These types of protective software configurations can also cause network instability; however, only in extreme rare cases.
Line 32:		Line 32:
	<br>		<br>
	===Network-Wide issues===		===Network-Wide issues===
	*Network wide traffic issues could mean that there’s a problem with a main network junction; however, if the network wide issues are only related to ~~CommitCRM~~, then this means that the network wide ~~CommitCRM~~ issues are due to system based problem localized to the server ~~CommitCRM~~ is installed on.		*Network wide traffic issues could mean that there’s a problem with a main network junction; however, if the network wide issues are only related to RangerMSP, then this means that the network wide RangerMSP issues are due to system based problem localized to the server RangerMSP is installed on.
	*The best way to test this is to run through all the steps in the System based Network issues chapter; and if unsuccessful, transferring the ~~CommitCRM~~ system to another computer would be the next step which will allow you to quickly resume your CRM duties while you troubleshoot the system wide issue on the previous server.		*The best way to test this is to run through all the steps in the System based Network issues chapter; and if unsuccessful, transferring the RangerMSP system to another computer would be the next step which will allow you to quickly resume your CRM duties while you troubleshoot the system wide issue on the previous server.

	<br>		<br>
	===SQL Database Users===		===SQL Database Users===
	*Customers that utilize the various features that the [http://{{SERVERNAME}}//products/sql-database/ SQL Database for ~~CommitCRM~~] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.		*Customers that utilize the various features that the [http://{{SERVERNAME}}//products/sql-database/ SQL Database for RangerMSP] also benefit from increased network performance and security, so these types of errors are much less likely to occur. The troubleshooting steps are basically the same; however, the following document is specialized in troubleshooting all types of communication issues with the SQL Database.
	<br>		<br>
	*'''For more information regarding SQL Database troubleshooting, [[SQL_Database_Troubleshooting\|please click here]].'''		*'''For more information regarding SQL Database troubleshooting, [[SQL_Database_Troubleshooting\|please click here]].'''

← Older revision		Revision as of 07:55, 24 July 2016
Line 44:		Line 44:

	==See Also==		==See Also==
	*'''[[Commit_SQL_Database_Troubleshooting\|~~CommitCRM~~ SQL Database Troubleshooting]]'''		*'''[[Commit_SQL_Database_Troubleshooting\|SQL Database Troubleshooting]]'''

	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]