logon error (index.html) Application Server Java in SolMan 7.1 SP12

[Former Member]

Hi,

Our customer has a Test-SolMan and a Prod-SolMan.

We have patched the Test-SolMan a few weeks before from SP10 to SP12. => all was fine after this project

Last weekend we´ve patched the Prod-SolMan to SP12. => all was fine except one thing.

When I want to access http://<fully-qualified-hostname>:50100/index.html this leads to following error (see screenshot below and attached)

I´ve found nothing in SCN or regarding any SAP notes.

In /usr/sap/<SID>/DVEBMGS01/j2ee/cluster/server0/log/defaultxxx.trc i found the following (see attached screenshot of default tracefile).

But in this default trace file path of main.jsp I haven´t seen any error or missing files or wrong permissions etc.

Also the input of the file is the same as on the Test-SolMan. On Test-SolMan all is fine. Files etc. are the same.

Restart of Java Instance or whole SolMan instance doesn´t bring any success...

Please assist & help me in this case.

Thanks & Regards,
Manuel

[manumohandas82]

Hi Manuel ,

try the following Note

1291202 - SystemInfo application does not open

Thanks ,

Manu

[Former Member]

Hi Manu,

Thanks for the SAP-Note.

I haven´t tried this but I´ve seen the note yesterday and I think this will only solve the /systeminfo issue, but what is with the other sites like /nwa or /useradmin etc.? This won´t be covered by this note...

The thing is: The URL is correct on Test-SolMan after the upgrade and all works fine. I haven´t implemented the note on Test-SolMan and the /systeminfo and all other sites work fine!

But on Prod-SolMan after the Upgrade the Java-Processes are started the same than on Test-SolMan but the sites don´t work....

Regards,
Manuel

[hemanth2]

Please try the force bootstrap option..

[Former Member]

Hi Guys,

Problem was solved.

First we tried the bootstrap Option but this doesn´t help. (But it was a good hint)

Solution:

I´ve found some wrong permissions in JAVA_HOME Directory. Seems this Directory or some files of this Directory were copied and the permissions were wrong.

I checked permissions of the JAVA_HOME files and compared with the files of Test Solution Manager - After Setting the right permissions, the logon error doesn´t appear anymore

Regards,
Manuel

[hemanth2]

Hi Manuel,
 

Hope you are doing good.

Nice to hear from you again.

Are you able to login to links like /useradmin or /nwa?

There is a possibility that the issue is due to the J2EE default page settings in

\usr\sap\<SID>\JC<nr>\j2ee\cluster\server0\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root.

Also is the SP stack consistent?

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth
SAP AGS
_ _ _ _ _ _ _ _ _
 

[Former Member]

Hi Hemanth,

Thanks for your reply!

I´m fine thanks for asking Hope you´re doing also good?

1. No, I´m not able to login to other sites like /nwa, /useradmin etc.

2. yes, in my screenshot attached you can see the error-message regarding this default page settings, but as you said: It could be the issue - but what could I do to solve this??

3. Yes, the SP-stack should be consistent, otherwise SUM has told me, that the XML-file is wrong or anything else. And the stack was the same than on Test-SolutionManager and on this Test-SolMan all is fine!

Regards,

Manuel

[hemanth2]

Hi Manuel,

If none of the links are working, then it looks like the whole server is affected.

Such an issue can be caused due to inconsistencies and it will be worthwhile to run the force bootstrap once (perhaps when you are scheduling the next offline backup on the server).

1)

Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename
the bootstrap folder as this is needed for the sync process.
2)

Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.

3)

Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.

4)

Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.

If the issue persists, you will need to redeploy the core patches; but first try the above.

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth
SAP AGS
_ _ _ _ _ _ _ _ _

[Former Member]

Hi Hemanth,

Thanks for your description and points!! Very helpful - I will try this as soon as this could be arranged with the customer.

And then I will come back to you if this is OK?

Regards,

Manuel

[hemanth2]

No problem manuel, please keep us posted.

regards,
Hemanth