cancel
Showing results for 
Search instead for 
Did you mean: 

SAP was not accessible

Former Member
0 Kudos

Dear all,

My SAP system was not accessible many time. When I found this error all user in the system can not log in to system.

If we can logon to system and check work process via SM66. We found many work process have status running (but it is waiting) in this instance until it show red color.

We solve this issue by kill process at OS level or Stop SAP and Start SAP again. Please tell me why this system has error like this. What is the permanent solution for this issues.

Regards,

Pannee

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

You can have the autologout. Most idle one is to increase your Dialog process depending on your server capacity

Regards

D.Mukunthan

Former Member
0 Kudos

Hi Pannee,

Is this a specific user related issue or all users are facing this issue?

Regards,

Pankaj

Former Member
0 Kudos

It sounds like you have a lot of long running dialog jobs running, which are using up all of the dialog work processes and preventing people from logging in. What User ID are these running as and what is shown in the "Report" column in SM66? Is the same thing showing as running in each process?

If this is correct, you'll need to find out what is running. Then you'll need to determine whether it is running correctly and whether or not it should be running at all. For example, there may be a problem with a regularly executed report that causes it to run for a long time.

If whatever is running is doing so correctly and needs to run, it may that additional work processes are required.

Former Member
0 Kudos

Hi Pankaj,

All user in my system have effect....

Regards,

Pannee

Former Member
0 Kudos

Hi,

Your analysis is correct. But I try to find the root cause of this error.

Because all work process which status runing in sm66 is normal process

Regards,

Pannee

JPReyes
Active Contributor
0 Kudos

If your dialog WP are taken by regular users... then you have a sizing problem.

You need to increase the amount of processes and set a timeout so users can't run long jobs in dialog

I still believe theres not enough information here... are you having performance problems?, any dumps or errors on the logs?

Regards

Juan

Former Member
0 Kudos

Hi,

You mentined earlier:

. If user logon to instance(02), user will get status waiting and can not logon. But if user logon to instance(06), user can logon some time but can not work

If users are trying to log in using instance numbers explicitily theuchit.n what logon load balancing are we talking about here?

In any case see if increasing number of dialog processes can help.

Also when you are having this issue check if you are having any activity running which involves parallel processing? Or may be things like large scale idoc processing is happening !

Regards.

Ruchit.

Former Member
0 Kudos

As per my understanding rdisp/gui_autologout parameter not set properly ,set it properly .If workprocess are being occupied by SAPSYS .then it might be becuase of kernel level , patch level issue. ensure these thing.

Regards

Yogesh

Former Member
0 Kudos

Hi Yanee,

Please explain the exact error that you are getting while trying to login into the system. Are you able to get into the system or not?

Regards,

Pankaj

Former Member
0 Kudos

Hi Pankaj,

My production system have 2 instance. One is the main instance (02) and another one is stand alone instance (06)

Two instance was set load balance by SMLG. If user logon to instance(02), user will get status waiting and can not logon. But if user logon to instance(06), user can logon some time but can not working. If we check work process in SM66, we found many work process with status runing in the instance (02) but this process can not finish. After we kill work process that pending in instance(02)at OS level, the system will allow another user to logon and working fine.

Thank you for your reply in advance.

Regards,

Pannee

JPReyes
Active Contributor
0 Kudos

Theres simply not enough information here...

if we check work process in SM66, we found many work process with status runing in the instance (02) but this process can not finish

Whos using the processes?.... SAPSYS??

Theres a note about this

Regards

Juan

Former Member
0 Kudos

Hi Juan,

The user for each process in normal user and SAPSYS.

But normal user more than SAPSYS.

Regards,

Pannee

Former Member
0 Kudos

You need to recruit the SAP Basis Administrator.

Regards.