Summary:

An incorrect parameter in your database connection string may prevent the CRMJ webapp from connecting to the database. The error given refers to an error connecting to the database - you may also get an error referring to CloneReportController.

The error has only been observed where the SQL Server instance used is something other than the default instance.

Issue:

The dashboard cannot be displayed. The schema URL will return an error 500.

Workaround:

Remove the language=english; string from the db.url in the CRMJ webapp's db.properties. Restart Tomcat, and it will work.

More info:

The CRM webapps can't connect the database. An error will be displayed in the Tomcat service logs. This issue was introduced in v7.2, and has been raised to the devlopment team for a fix.