Tomcat - Revision history

Crmtogetherkb at 09:49, 29 March 2016

2016-03-29T09:49:14Z

@@ Line 1: / Line 1: @@
 Easiest option here is to re-install (actually select the upgrade option) a patch and this usually works.
@@ Line 7: / Line 27: @@
 ----
 Java versions later than

Crmtogetherkb at 08:10, 5 August 2015

2015-08-05T08:10:41Z

← Older revision		Revision as of 09:10, 5 August 2015
Line 1:		Line 1:
	Easiest option here is to re-install (actually select the upgrade option) a patch and this usually works.		Easiest option here is to re-install (actually select the upgrade option) a patch and this usually works.

			Latest guide (7.3)

			https://community.sagecrm.com/knowledgebase/w/onpremisekba/1074.632-17360-sage-crm-interactive-dashboard-support-guide.aspx#CommonErrors


	----		----

Crmtogetherkb at 08:04, 2 April 2014

2014-04-02T08:04:54Z

← Older revision		Revision as of 09:04, 2 April 2014
Line 98:		Line 98:
	com.sage.crm.web.exception.SageAsyncProcessException: Mailmerge generation failed		com.sage.crm.web.exception.SageAsyncProcessException: Mailmerge generation failed
	Caused by: com.sage.crm.core.exception.SageEndpointException: java.io.IOException: Cannot run program		Caused by: com.sage.crm.core.exception.SageEndpointException: java.io.IOException: Cannot run program

			----
			7.2b seems to need port 11009 (used to be 10009) to be open for external ips to get access to the dashboard

Crmtogetherkb at 13:18, 27 February 2014

2014-02-27T13:18:12Z

← Older revision		Revision as of 14:18, 27 February 2014
Line 91:		Line 91:

	update custom_sysparams		update custom_sysparams
	set parm_value='C:\Program Files (x86)\Sage\CRM\Services\JRE\jre7\bin'		set parm_value='C:\Program Files (x86)\Sage\CRM\Services\JRE\jre7\bin\'
	where parm_name='javapath'		where parm_name='javapath'

Crmtogetherkb at 13:08, 27 February 2014

2014-02-27T13:08:13Z

← Older revision		Revision as of 14:08, 27 February 2014
Line 79:		Line 79:

	Ref: https://community.sagecrm.com/user_community/f/84/t/9983.aspx		Ref: https://community.sagecrm.com/user_community/f/84/t/9983.aspx



			----

			Seen on 7.2

			If you move installs you can get issues with the mail merge (dashboard might still work) if you dont have the same 'javapath' set in custom_sysparams

			Sample code to fix this

			update custom_sysparams
			set parm_value='C:\Program Files (x86)\Sage\CRM\Services\JRE\jre7\bin'
			where parm_name='javapath'

			The error might be reported as

			com.sage.crm.web.exception.SageAsyncProcessException: Mailmerge generation failed
			Caused by: com.sage.crm.core.exception.SageEndpointException: java.io.IOException: Cannot run program

Crmtogetherkb at 14:47, 31 October 2013

2013-10-31T14:47:08Z

← Older revision		Revision as of 15:47, 31 October 2013
Line 61:		Line 61:
	Dashboard not working outside of intranet		Dashboard not working outside of intranet

	The rewriter's probably trying to send the request to Tomcat to the external IP. In v7.1, It will look something like this, for a static IP of 50.57.215.216:		The rewriter's probably trying to send the request to Tomcat to the external IP.

			In v7.1, It will look something like this, for a static IP of 50.57.215.216:

	Initial request:		Initial request:
	http:// 50.57.215.216/sdata/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1
			http:// 50.57.215.216/sdata/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1

	This is rewritten to:		This is rewritten to:
	http:// 50.57.215.216:10009/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1
	The Tomcat port is unlikely to be accessible using the static IP. The usual way I'd suggest working around this is to use a fully-qualified name, and add an entry to the server's hosts file so that the FQDN will resolve to 127.0.0.1. I would not suggest opening the Tomcat port for requests using the static IP.		http:// 50.57.215.216:10009/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1

			The Tomcat port is unlikely to be accessible using the static IP.
			The usual way I'd suggest working around this is to use a fully-qualified name, and add an entry to the server's hosts file so that the FQDN will resolve to 127.0.0.1.
			I would not suggest opening the Tomcat port for requests using the static IP.


	Ref: https://community.sagecrm.com/user_community/f/84/t/9983.aspx		Ref: https://community.sagecrm.com/user_community/f/84/t/9983.aspx

Crmtogetherkb at 14:46, 31 October 2013

2013-10-31T14:46:30Z

← Older revision		Revision as of 15:46, 31 October 2013
Line 54:		Line 54:

	http://aspnet.4guysfromrolla.com/articles/011404-1.aspx		http://aspnet.4guysfromrolla.com/articles/011404-1.aspx



			----

			Dashboard not working outside of intranet

			The rewriter's probably trying to send the request to Tomcat to the external IP. In v7.1, It will look something like this, for a static IP of 50.57.215.216:
			Initial request:
			http:// 50.57.215.216/sdata/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1
			This is rewritten to:
			http:// 50.57.215.216:10009/crmj/layout/-/$service/lockrecord?tableName=LPLayout&id=6010&SID=47373617139422&contextEntityId=-1&contextRecordId=-1
			The Tomcat port is unlikely to be accessible using the static IP. The usual way I'd suggest working around this is to use a fully-qualified name, and add an entry to the server's hosts file so that the FQDN will resolve to 127.0.0.1. I would not suggest opening the Tomcat port for requests using the static IP.

			Ref: https://community.sagecrm.com/user_community/f/84/t/9983.aspx

Crmtogetherkb at 11:19, 3 September 2013

2013-09-03T11:19:35Z

← Older revision		Revision as of 12:19, 3 September 2013
Line 1:		Line 1:
	Easiest option here is to re-install a patch and this usually works.		Easiest option here is to re-install (actually select the upgrade option) a patch and this usually works.

	----		----

Crmtogetherkb at 10:08, 7 February 2013

2013-02-07T10:08:08Z

← Older revision		Revision as of 11:08, 7 February 2013
Line 1:		Line 1:
			Easiest option here is to re-install a patch and this usually works.

			----
	Java versions later than		Java versions later than

Crmtogetherkb at 13:44, 7 December 2012

2012-12-07T13:44:25Z

← Older revision		Revision as of 14:44, 7 December 2012
Line 3:		Line 3:
	version 6 update 27		version 6 update 27

	will cause issues (tomcat wont work)		will cause issues (tomcat wont work and the report export might error out with "win 32 code 1 incorrect function")

	use this too test the version of java on the machine		use this too test the version of java on the machine