Hello,

Any Help Plz.......

Mohannad

The upgrade path for Sage CRM 7.1 to Sage CRM 2017R1 needs to go through Sage CRM 7.2. The install wizard upgrades from 7.2 or 7.3 to 2017 R1. You should make a full backup of your data before upgrading.

The Calendar feature in Sage CRM 2017 R1 makes use of new JavaScript libraries which make REST calls to Sage CRM using SData 2.0. This provides insert and update abilities.

Both the old SData 1.1 (ReadOnly) web service used by the Dashboards and SData 2.0 are delivered from the Tomcat side of the application.

Are other Tomcat features working? Do the logs give an indication?

The first basic test is to see whether SData is working

http://localhost/sdata/crmj/

This assumes that your install is called 'crm'.

The two example usages of the end points for SData 1.1 and SData 2.0 are

localhost/.../company('28')

and

localhost/.../company('28')

SData 1.1 returns XML and SData 2.0 returns JSON.

Jeff;
Certainly when upgrade to CRM 2017 R1 go through Sage CRM 7.2. 7.3.
When Run (http://localhost/sdata/crmj/), Return the error bellow.

Mohannad

I think there is something wrong with the JRE being used. I can't find a previous discussion of this issue on the community.

When you request

http://localhost/sdata/crmj/

This actually is directed to the physical file

C:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmj\index.jsp

Which contains a 'Hello World' response in plain HTML.

The error "HTTP Status 500 - Unable to compile class for JSP" therefore originates at this point as the JSP page is being compiled.

Are there any errors in the logs that may shed additional light?

And have you logged a case with you local Sage office?

Hi Mohannad,

Not sure if you have managed to fix this issue or not. But here is KB from NA on this support.na.sage.com/.../viewdocument.do. This has fixed issue for one of our Business Patner.

Hope that helps

Thanks

Ravi