HTTP 500 INTERNAL ERROR When Opening a report

[Achraf_Ougdal]

Hello everyone,

We have an issue with SAS Visual Analytics. I am currently loading 24 Tables (5.5 Gb uncompressed) and a LASR Star Schema as a view (Total shown on LASR is 130 Gb).

The problem we have is when we create a report (with calculated items and graphs) it takes a while before it crashes and shows the HTTP 500 INTERNAL ERROR. When e restart the services and try to open the report, it crashes right away.

When we try to open the report, the CPU Utilization increase to 100%, also every time we try to create a calculated item, make changes etc… the CPU utilization raise to 100% (I think this is normal because the source is view) Then, when we refresh the page or try to access  any other application (SAS Studio, SAS Visual Data Builder, sas Environment Manager…) it shows the http 500 error.

When we try to create a new report, it acts the same way, it crashes at some point, and when we try to open it again it crashes right away.

We are using SAS Visual Anlaytics on SAS 9.4 for Windows. We have 42 GB or RAM and a x64 Processor with 24 VCPU.

Any Idea why this keeps happening ?

Thank you.

[Mickey_SAS · Accepted solution]

You are most likely running out of memory in the web application server.  You may just need to increase the available memory( -Xmx ) to the java process which is the web application server, or you may also need to tune some of the settings the protect the middle tier.

I would recommend that you open a Technical Support track for assistance with this.

https://www.sas.com/en_us/contact/technical-support.html

It would be a good idea to go ahead and provide the middle tier logs for SASServer1_1 and SASServer12_1( if you have that ) when you open the track, using the instructions in the first section of the note here: https://support.sas.com/kb/55/426.html

[Achraf_Ougdal]

Hello,

Can you please guide me on where to increase the available memory, I couldn't find where to do so.

Thank you

[Madelyn_SAS]

As @Mickey_SAS said, please contact technical support for assistance with this issue. 

----------------------------

I would recommend that you open a Technical Support track for assistance with this.

https://www.sas.com/en_us/contact/technical-support.html

It would be a good idea to go ahead and provide the middle tier logs for SASServer1_1 and SASServer12_1( if you have that ) when you open the track, using the instructions in the first section of the note here: https://support.sas.com/kb/55/426.html