BI2025 installation ends up with http:500 error

I downloaded BO 2025 yesterday and setup a new bo install; went up quick but ended with an Http Status 500-Internal Server Error…

any ideas?

  • Wobi

Hi Wobi,
Take a look at https://me.sap.com/notes/3559381
Cheers,
Tom

1 Like

Thank you Tom for your response - actually I had this issues updating my 4.3.4 900 test to patch 1000 in January - nothing worked … and the documentation or the KB was not published at that moment… took me a while to find the cause for this troubles - but since this is a standalone 2025 installation with no prev. trusted authentication and no https I expected it ready for testing after this fresh install…

Wobi

to be more precise - cmc and bi are giving an Http Status 500-Internal Server Error

interrestingly the stdout.log of tomcat is not filling with input - it stays empty…

so sg. is wrong there…

Hi Wobi,
We ‘only’ encountered the HTTP:500 Error after updating to SP04 Patch 800. After stumbling across Note 3559381 I decided to uninstall SP04.800 and update to SP04.1100 instead. This fixed the issue for us.
Getting the same error / similar behaviour as outlined in the KBA after a maiden installation of BI 2025 sounds worrying. I guess you have already tried reinstalling?
Kind regards,
Tom

Yep repair redeploy uninstall reinstall - same result… stdout.log of tomcat stays empty… -
new downloaded installer files - same results -first the stdout.log had a line with something about framework…
and after reboot it stays empty…
-wobi

Hi,
it is the same situation for us.
SAP Support Trouble Ticket has ben created.
Kind Regards
Jeno

1 Like

Ok, so I will wait for your results :wink:

Hi,
After an SAP Support Call, it works already for us.
We get Tomcat 9 Options Params.( Tomcat Config – Tomcat 9 Options)
And CMS Reset. ( In Test Environment OK, in PROD No :wink: )
I think they make an SAP Note about it.
Regards,

1 Like

Can you share the tomcat 9 options? - otherwise we have to wait for the kb… no time to chat with sap support at the moment :wink:

  • Wobbi

We have got these Options from SAP Support.
I don know, if it works for you too.
They should add to Tomcat Config – Java – Java9 Options.

–add-opens=java.base/java.lang=ALL-UNNAMED

–add-opens=java.base/java.io=ALL-UNNAMED

–add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED

–add-opens=java.base/java.net=ALL-UNNAMED

–add-opens=java.management/com.sun.jmx.remote.internal=ALL-UNNAMED

–add-opens=java.management/com.sun.jmx.remote.security=ALL-UNNAMED

–add-opens=java.management/com.sun.jmx.remote.util=ALL-UNNAMED

–add-opens=java.base/sun.security.internal.spec=ALL-UNNAMED

–add-opens=java.base/sun.security.x509=ALL-UNNAMED

Maybe you should then reset the CMS (CCM – Initialize CMS DB) too.
I can’t see in our trouble Ticket the SAP Note Nr, maybe come soon.
Regards,

1 Like

Hi,
SAP Note is arrived
3586047 - HTTP 500 Internal Server Error accessing BILP / CMC - SAP for Me
Regards,
Jenő

2 Likes

Thanks for sharing, Jenő. Seems to be a common issue… :frowning:

Well now I applied the KB entries - redeployed - deleted old cache - and now it works…
2025 is alive! Viva la evoluzcion!

Wobi

–add - it seems the correct beginning ist with - - !!! two single - !

  • Wobi

… yes, it is always important to follow the exact syntax and the official support page :laughing:

358604