Browse By Tags

  • Wiki Page: 492-16647 - Error creating bean with name 'sdataServiceMetaDataStore'

    Summary: Following an upgrade to v7.1 SP1, an error displayed on interactive dashboard: The Dashboard has experienced a problem. Please contact your system administrator. Browsing to the SDATA schema URL will result in a 404 error page being returned from the Tomcat web server. The following error appears...
  • Wiki Page: 492-16447 - Error 400 accessing the SDATA schema URL

    Summary: All requests to the SDATA schema URL using the hostname return an error 400 (Bad Request). Requests to localhost work correctly: • http://localhost/sdata/default.aspx?r=/sdata/test.html • http://localhost:[Tomcat Port]/[CRM Install Name]j/sagecrm/-/$schema • http://localhost/sdata...
  • Wiki Page: 492-17112 - Mail merge error with IIS autologin

    Summary: An issue with mail merges may arise when IIS autologin is enabled. Symptoms: The following error message is displayed in the Sage CRM logs: "User with a username xxxx not found in CRM" "User not logged" This issue is caused by Tomcat attempting to check for an active user...
  • Wiki Page: 593-16538 - Unable to make JDBC connection to Oracle 11 DB

    Summary: On testing the connection with JaySQL No suitable driver found for jdbc.url=jdbc:log4jdbc:oracle:thin:@oracleserver:port:crmdatabase jdbc.driver=net.sf.log4jdbc.DriverSpy jdbc.url=jdbc:log4jdbc:oracle:thin:@oracleserver:port:crmdatabase jdbc.username=username jdbc.password=password jdbc.minpoolsize...
  • Wiki Page: 605-16691 - Modifying Sage CRM database settings causes Tomcat to lose SQL connection

    Summary: Modifying Sage CRM database settings causes Tomcat to lose SQL connection. Symptoms: If the database name is changed, Tomcat services stop for that install. Cause: This is happening because the format of the database is showing up incorrectly in the jdbc.properties file. If the database name...
  • Wiki Page: 632-17296 - After updating to Java 7, the Tomcat service no longer starts for version 7.1

    Summary: After a Java update occurs - java 6 updated to Java 7 - the Apache Tomcat service (Tomcat6) fails to start after the upgrade. Symptoms: The following error message is displayed if the user tries to start the Tomcat service manually: Cause: The cause of this is that when Tomcat goes to start...
  • Wiki Page: 632-17645 - Mail Merge failing but other tomcat features are available

    Summary: Mail Merge was not working in CRM but the Interactive Dashboards were working as expected. Symptoms: When trying to perfom a Mail Merge it was failing even though other Tomcat features were working as expected, ie: the Interactive Dashboard. Cause: The cause of this issue was that a line in...
  • Wiki Page: 492-17909 - HOWTO: Deploy psi-probe on a v7.1 Tomcat install

    Summary: Psi-probe is an intended replacement for Tomcat Monitor, and provides advanced monitoring options for a Tomcat install. We do not support deploying additional webapps along with a CRM install, however there may be cases where this is useful, such as troubleshooting thread waits and suspected...