Transactions STRUST and STRUSTSSO2 are failing in PI

[ashok_oleti]

Hello All,

The transaction codes STRUST and STRUSTSSO2 are failing in our PI Pre-Prod system with error both in 000 client and test client. It shows the message "Start of application ; Trust Manager for Logon Ticket" in status bar for sometime and then terminates with below error.

We don't have any problem with any other transaction codes. Can anyone please let me know how this can be fixed.

Below is our System Environment

Netweaver/PI Version : 7.11 SP12

Kernel Version : 720_REL ; Patch 500

Database : SQL Server 2008 R2

OS : Windows Server 2008 R2

Regards,

Ashok Oleti

[ashok_oleti · Accepted solution]

Hi All,

Thanks everyone for your time and suggestions.

The problem is fixed by changing the owner of the SAP services from SAPService<SID> to <SID>adm on the Windows server OS (2008 R2)

Now we are investigating what went wrong with the SAPService<SID> user, any suggestions?

Regards,

Ashok Oleti

[Former Member]

Hi,

Please check if the error is only in your system. Trying using others system and try the tcode.

It might be an issue with the GUI also.

Regards,

Ambarish.

[ashok_oleti]

All the recommendations/suggestions are leading to the cases where the problem is with import/export of certificates and the solution is Kernel upgrade. But in our case the transactions STRUSTSSO2/STRUST are not at all getting opened, should we still consider it as a Kernel problem?

We don't find any errors in SM21 or trace file of the work processes and also there no any dumps in ST22.

There was a windows OS security patch update a day before the problem has started, could it be the reason for this behaviour?

[Former Member]

Ashok,

Are you able to interrogate the PSE with sapgenpse ?

eg: sapgenpse maintain_pk -l -p <PSE filename with full path>

https://help.sap.com/saphelp_nw70ehp1/helpdata/en/0a/2aa63a2719f539e10000000a11402f/content.htm

KR,

Amerjit

[Johan_sapbasis]

Hi,

According to your screenshot it lists Work process restarted, session terminated so try open the tcode and directly afterward check in sm21 which is the work process that was terminated from your user then go and check the dev_w* trace file of this specific work process, and list the details here.

To rule out variables:

1. Can no user open strust/strustsso2 ?

2. Have you run a trace to see what is written in trace perhaps when you try to reproduce the issue st12/st01/st05?

3. Can you try open it from a different sapgui?

We do not more information to assist you.

Kind Regards,

Johan

[manumohandas82]

Hi Ashok ,

Follow as suggested by Nicolaas  .  Get the work process trace (dev_w* ) where the termination occurs  . You may increase the trace level as well .

This could be  because of the kernel / security patch but need more details , Otherwise we would be just beating around the bush

Thanks ,

Manu

[Former Member]

Hello Ashok,

Please check your system log (SM21) and also check the WP trace file (SM50). You should get some meaningful information from there as a starting point.

KR,

Amerjit

[Former Member]

Oops,

I should have noticed Johan had asked the same thing.

Mea culpa.

[Former Member]

Hi Ashok,

check following parameters:

ztta/roll_area  ( set it to 1)

ztta/short_area ( suggeted 4000000).

Regards,

Ambarish.

[Johan_sapbasis]

Hi,

Tcode smicm ->Goto-> Trace level -> increase

Check the dev_w* file of your process that died when you were busy with the error please check the logs/sm21/st22 and additional information here please.

Check the ICM log as well directly after reproducing the issue.

Tcode smicm ->Goto->Trace file -> display all

Kind Regards,

Johan

[manumohandas82]

Hi

Check SAP Note 2094861 - Workprocess restarts during PSE creation

Also check the following link

Thanks ,

Manu

[Former Member]

Hi,

There might be a case where work process consume all the available memory and thus gets restarted, please check the work process trace file for more information on this.

Check for any dump during the time of restart.

Also check the sap note:

2073392 - Memory leak in SSF API of ABAP Kernel

Regards,

Prithviraj.