Appboard/old/troubleshooting - Revision history

imported>Jason.nicholls: /* Issues With Starting the AppBoard Server */

2014-07-17T18:32:31Z

Issues With Starting the AppBoard Server

← Older revision		Revision as of 18:32, 17 July 2014
Line 11:		Line 11:
	*'''Issue:''' When executing the startup.bat or startup.sh command, AppBoard fails to start successfully and the URL does not return the AppBoard login page in the browser.		*'''Issue:''' When executing the startup.bat or startup.sh command, AppBoard fails to start successfully and the URL does not return the AppBoard login page in the browser.
	*'''Resolution:''' Review the following checklist to see if any of the items are preventing AppBoard from starting:		*'''Resolution:''' Review the following checklist to see if any of the items are preventing AppBoard from starting:
	**Validate that your server does not have applications already running on the port being used by AppBoard. For detailed instructions on troubleshooting this issue, see [[~~Port_Conflict_JVM_Bind_Error~~\|Port Conflict JVM Bind Error]].		**Validate that your server does not have applications already running on the port being used by AppBoard. For detailed instructions on troubleshooting this issue, see [[appboard/old/port_conflict\|Port Conflict JVM Bind Error]].
	**Check to see if there is a problem with the AppBoard license file.		**Check to see if there is a problem with the AppBoard license file.
	***Make sure there is a file called license.properties in [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/config/license.properties.		***Make sure there is a file called license.properties in [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/config/license.properties.

imported>Jason.nicholls: /* Issues With Starting the AppBoard Server */

2014-07-17T17:14:14Z

Issues With Starting the AppBoard Server

← Older revision		Revision as of 17:14, 17 July 2014
Line 21:		Line 21:
	***Run the following command:		***Run the following command:
	***: <tt>>catalina.bat run</tt>		***: <tt>>catalina.bat run</tt>
	**Check for [[Tomcat_Troubleshooting\|other issues with Tomcat]].

imported>Jason.nicholls: /* Issues With Starting the AppBoard Server */

2014-07-17T10:37:07Z

Issues With Starting the AppBoard Server

← Older revision		Revision as of 10:37, 17 July 2014
Line 15:		Line 15:
	***Make sure there is a file called license.properties in [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/config/license.properties.		***Make sure there is a file called license.properties in [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/config/license.properties.
	***Open the license.properties file and check the expiration date.		***Open the license.properties file and check the expiration date.
	**Look in the system log files and console output for errors. For more information about the log files, see [[~~Log_Files~~\|Log Files]].		**Look in the system log files and console output for errors. For more information about the log files, see [[appboard/old/log_files\|Log Files]].
	**In Windows, if you do not see any error messages in the console, or the console is closing before you can see anything, you can try to run Catalina directly instead of using the startup script. This will sometimes provide additional feedback in the console. To run Catalina directly, do the following:		**In Windows, if you do not see any error messages in the console, or the console is closing before you can see anything, you can try to run Catalina directly instead of using the startup script. This will sometimes provide additional feedback in the console. To run Catalina directly, do the following:
	***Go to the command line in a console.		***Go to the command line in a console.
Line 37:		Line 37:
	** The license may have been corrupted through FTP transfer or editing. Try re-saving the original license file and re-trying. I have attached the file if you want to try this.		** The license may have been corrupted through FTP transfer or editing. Try re-saving the original license file and re-trying. I have attached the file if you want to try this.
	** (less common) The date on the server is set forward to a date later than the license expiration date.		** (less common) The date on the server is set forward to a date later than the license expiration date.


	==Memory Issues==		==Memory Issues==

imported>Jason.nicholls: /* Memory Issues */

2014-07-17T05:10:10Z

Memory Issues

← Older revision		Revision as of 05:10, 17 July 2014
Line 45:		Line 45:
	*'''Resolution:''' Review the following checklist to see where performance can be improved:		*'''Resolution:''' Review the following checklist to see where performance can be improved:
	**Consider any latency that exists between the client and the AppBoard server. Run AppBoard in a browser on the server and evaluate whether it performs better than from other locations.		**Consider any latency that exists between the client and the AppBoard server. Run AppBoard in a browser on the server and evaluate whether it performs better than from other locations.
	**Allocate more memory to AppBoard. For more information on allocating additional memory, see [[~~Memory_Configuration~~\|Memory Configuration]].		**Allocate more memory to AppBoard. For more information on allocating additional memory, see [[appboard/old/memory configuration\|Memory Configuration]].


Line 53:		Line 53:
	*: "Error: Could not create the Java Virtual Machine."		*: "Error: Could not create the Java Virtual Machine."
	*: "Error: A fatal excepion has occurred. Program will exit."		*: "Error: A fatal excepion has occurred. Program will exit."
	*'''Resolution:''' You may not have too much memory allocated to the Java VM for your operating system. For example, you will get this error if you use the default Java Virtual Machine maximum heap size (-Xmx1536m) when running on a 32-bit Windows system. Lower the maximum heap size to an amount that can be handled by the operating system (for example, -Xmx1024m). For more information on this setting, see [[~~Memory_Configuration~~\|Memory Configuration]].		*'''Resolution:''' You may not have too much memory allocated to the Java VM for your operating system. For example, you will get this error if you use the default Java Virtual Machine maximum heap size (-Xmx1536m) when running on a 32-bit Windows system. Lower the maximum heap size to an amount that can be handled by the operating system (for example, -Xmx1024m). For more information on this setting, see [[appboard/old/memory configuration\|Memory Configuration]].


Line 63:		Line 63:
	*## tcnative-1.dll		*## tcnative-1.dll
	*## tomcat7.exe		*## tomcat7.exe


	==Viewing the Console Output==		==Viewing the Console Output==

imported>Jason.nicholls at 17:18, 16 July 2014

2014-07-16T17:18:59Z

← Older revision		Revision as of 17:18, 16 July 2014
Line 4:		Line 4:


	{{Note\|This page addresses troubleshooting issues on the AppBoard server. For any issues that take place in the web browser, see the page for [[~~AppBoard_Client_Troubleshooting~~\|AppBoard client troubleshooting]].}}		{{Note\|This page addresses troubleshooting issues on the AppBoard server. For any issues that take place in the web browser, see the page for [[appboard/old/client_troubleshooting\|AppBoard client troubleshooting]].}}

imported>Jason.nicholls: moved AppBoard Troubleshooting to appboard/old/troubleshooting

2014-07-16T17:17:31Z

moved AppBoard Troubleshooting to appboard/old/troubleshooting

← Older revision	Revision as of 17:17, 16 July 2014
(No difference)

imported>Jason.nicholls at 17:17, 16 July 2014

2014-07-16T17:17:16Z

← Older revision		Revision as of 17:17, 16 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:AppBoard Troubleshooting}}
			[[Category:AppBoard old]]
	This page identifies issues that you may encounter when running AppBoard/enPortal, and recommends possible solutions where applicable.		This page identifies issues that you may encounter when running AppBoard/enPortal, and recommends possible solutions where applicable.

imported>Mike.berman at 22:07, 16 January 2014

2014-01-16T22:07:23Z

← Older revision		Revision as of 22:07, 16 January 2014
Line 77:		Line 77:
	#Run the following command:		#Run the following command:
	#: <tt>>catalina.bat run > c:\tempdir\consoleOutput.txt</tt>		#: <tt>>catalina.bat run > c:\tempdir\consoleOutput.txt</tt>


			==Data Sources==
			*<b>Issue:</b>: Java cannot manage '00-00-00 00:00:00' in MySQL datetime fields. Even if this kind of datetime value is not supported within MySQL operations, values are allowed in general and used by some implementations as default for empty datetime values. The issue can result in many messages in Appboard error.log.
			*<b>Resolution</b>: Convert the zero values to NULL values within the data-source. Example url: <tt>jdbc:mysql://yourserver:3306/yourdatabase?zeroDateTimeBehavior=convertToNull</tt>

imported>Mike.berman: add licensing item

2012-12-06T17:51:48Z

add licensing item

← Older revision		Revision as of 17:51, 6 December 2012
Line 20:		Line 20:
	***: <tt>>catalina.bat run</tt>		***: <tt>>catalina.bat run</tt>
	**Check for [[Tomcat_Troubleshooting\|other issues with Tomcat]].		**Check for [[Tomcat_Troubleshooting\|other issues with Tomcat]].


			*<b>Issue:</b> When running Tomcat under HTTPS, you see the error message in your browser when accessing the login URL: <tt>SSL connection error. Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have. Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.</tt>
			* <b>Resolution</b>: Some applications, such as Skype, run on port 443. Check to make sure you do not have any other applications running on port 443 prior to starting Tomcat with the startup command


	{{Tip\|When starting AppBoard, always allow enough time for the Tomcat process to fully start up before accessing the login URL in a browser. This may take 1-2 minutes. When re-starting the system, always allow sufficient time for the system to stop before running the start command.}}		{{Tip\|When starting AppBoard, always allow enough time for the Tomcat process to fully start up before accessing the login URL in a browser. This may take 1-2 minutes. When re-starting the system, always allow sufficient time for the system to stop before running the start command.}}


			*<b>Issue:</b> When attempting to start the server, you receive the following message in the Tomcat console: <tt>Product is not licensed. Obtain a license.properties file from your product distributor and place in the config folder.</tt>
			* <b>Possible Causes</b>:
			** The license file is expired. View the license file in a text editor and examine the expiration date. The file is located in <tt>/server/webapps/enportal/WEB-INF/config/license.properties</tt>.
			** Due to a clerical mismatch, the directory where you placed the license.properties file (/server/webapps/enportal/WEB-INF/config/) is not under the same filesystem as where you started the application (/server/bin/). This is often caused by confusion due to having multiple versions of enPortal/AppBoard installed on the same server.
			** The license may have been corrupted through FTP transfer or editing. Try re-saving the original license file and re-trying. I have attached the file if you want to try this.
			** (less common) The date on the server is set forward to a date later than the license expiration date.

imported>Cmace: copied from internalwiki

2012-03-08T21:01:12Z

copied from internalwiki

New page

This page identifies issues that you may encounter when running AppBoard/enPortal, and recommends possible solutions where applicable.

{{Note|This page addresses troubleshooting issues on the AppBoard server. For any issues that take place in the web browser, see the page for [[AppBoard_Client_Troubleshooting|AppBoard client troubleshooting]].}}

==Issues With Starting the AppBoard Server==

*'''Issue:''' When executing the startup.bat or startup.sh command, AppBoard fails to start successfully and the URL does not return the AppBoard login page in the browser.
*'''Resolution:''' Review the following checklist to see if any of the items are preventing AppBoard from starting:
**Validate that your server does not have applications already running on the port being used by AppBoard. For detailed instructions on troubleshooting this issue, see [[Port_Conflict_JVM_Bind_Error|Port Conflict JVM Bind Error]].
**Check to see if there is a problem with the AppBoard license file.
***Make sure there is a file called license.properties in [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/config/license.properties.
***Open the license.properties file and check the expiration date.
**Look in the system log files and console output for errors. For more information about the log files, see [[Log_Files|Log Files]].
**In Windows, if you do not see any error messages in the console, or the console is closing before you can see anything, you can try to run Catalina directly instead of using the startup script. This will sometimes provide additional feedback in the console. To run Catalina directly, do the following:
***Go to the command line in a console.
***Navigate to [APPBOARD_HOME]/server/bin
***Run the following command:
***: <tt>>catalina.bat run</tt>
**Check for [[Tomcat_Troubleshooting|other issues with Tomcat]].

{{Tip|When starting AppBoard, always allow enough time for the Tomcat process to fully start up before accessing the login URL in a browser. This may take 1-2 minutes. When re-starting the system, always allow sufficient time for the system to stop before running the start command.}}

==Memory Issues==

*'''Issue:''' Your system is experiencing lags or performance issues
*'''Issue:''' You received the error message “Out of heap space”
*'''Resolution:''' Review the following checklist to see where performance can be improved:
**Consider any latency that exists between the client and the AppBoard server. Run AppBoard in a browser on the server and evaluate whether it performs better than from other locations.
**Allocate more memory to AppBoard. For more information on allocating additional memory, see [[Memory_Configuration|Memory Configuration]].

*'''Issue:''' You received one of the following error messages:
*: "Error occurred during initialization of VM"
*: "Could not reserve enough space for object heap"
*: "Error: Could not create the Java Virtual Machine."
*: "Error: A fatal excepion has occurred. Program will exit."
*'''Resolution:''' You may not have too much memory allocated to the Java VM for your operating system. For example, you will get this error if you use the default Java Virtual Machine maximum heap size (-Xmx1536m) when running on a 32-bit Windows system. Lower the maximum heap size to an amount that can be handled by the operating system (for example, -Xmx1024m). For more information on this setting, see [[Memory_Configuration|Memory Configuration]].

*'''Issue:''' You received the following error message:
*: "Can't load AMD 64-bit .dll on a IA 32-bit platform"
*'''Resolution:''' You are running the 64-bit Tomcat executable on a 32-bit Windows system. For example, you will get this error if you use the default installation on a 32-bit system. Perform the following steps to fix this issue:
*# Navigate to [APPBOARD_HOME]/server/bin/windows-x86
*# Copy the 32-bit Tomcat files from the /windows-x86 folder up one level to the /bin folder:
*## tcnative-1.dll
*## tomcat7.exe

==Viewing the Console Output==

A helpful technique for troubleshooting Windows server issues in AppBoard is being able to save the console output to a file. This is helpful for the following scenarios:

* You want to examine the console output, but the console is closing down quickly when an error occurs
* You want to submit the console output to technical support for review

Perform the following steps to start up AppBoard and save the console output to a file:
#Create a temporary folder, such as c:\tempdir
#Go to the command line in a console.
#Navigate to [APPBOARD_HOME]/server/bin
#Run the following command:
#: <tt>>catalina.bat run > c:\tempdir\consoleOutput.txt</tt>