Could not kill the existing SAP User session

Basis (Basis Technology Modules: Basis Component/System Administration, GUIs)

Moderators: Snowy, thx4allthefish

Post Reply
adminbasis
Posts: 22
Joined: Mon Jul 06, 2009 2:30 am

Could not kill the existing SAP User session

Post by adminbasis » Sat Jul 11, 2009 12:49 am

Dear All,

There is one SAP FI user who was working on transaction "FBL1N - Vendor line items" & suddenly his system got stuck & he restarted his PC from that time onwards it was showing already logged in like 'multiple logons' & even i tried to kill that session from SM04 -user list but its not deleting, is there any other way to kill that hang session???? could you please help me to delete that existing session....

Thanks in advance....

dnedev
Posts: 6
Joined: Sun Jul 12, 2009 1:47 pm
Contact:

Re: Could not kill the existing SAP User session

Post by dnedev » Sun Jul 12, 2009 2:02 pm

Hello adminbasis,

You could try to check if there is any connection from this user in gateway monitor SMGW transaction as well as from SM50 to cancel the process of this user if there is any.

Best regards,
Detelin

adminbasis
Posts: 22
Joined: Mon Jul 06, 2009 2:30 am

Re: Could not kill the existing SAP User session

Post by adminbasis » Mon Jul 13, 2009 12:48 am

Dear Detelin,

I already checked there is no connection from this user in gateway monitor SMGW & SM50 to cancel the process.

Any other way to kill that existing session of the user orelse if i restart the Production server that will be ok please advice.

Thanks

hoinz
Posts: 151
Joined: Tue Jan 15, 2008 5:56 am

Re: Could not kill the existing SAP User session

Post by hoinz » Mon Jul 13, 2009 6:11 am

What is your operating system system?
You may have to use OS tools on the SAP server, like 'kill -9' for Unix.

adminbasis
Posts: 22
Joined: Mon Jul 06, 2009 2:30 am

Re: Could not kill the existing SAP User session

Post by adminbasis » Mon Jul 13, 2009 7:40 am

We have OS- win2003
SAP version - 4.7 x200
Database -Oracle - 10.2.0.2.0

The Prince Of Darkness
Posts: 3080
Joined: Fri Jun 20, 2003 10:10 am
Location: Either on a train or in a pub (if neither, arguing with an Eastern Block work colleague)

Re: Could not kill the existing SAP User session

Post by The Prince Of Darkness » Mon Jul 13, 2009 9:19 am

Open Task Manager, select process tab and End Process.

Make sure you can see the PID column and select the right one.
Former SAP PM, looking to move in Lawn Mower business

adminbasis
Posts: 22
Joined: Mon Jul 06, 2009 2:30 am

Re: Could not kill the existing SAP User session

Post by adminbasis » Tue Jul 14, 2009 3:43 am

I have already tried to kill the session form task manager but the PID was not displaying for that perticuler user anyways I have restarted the server & now its ok all old existing sessions are gone but i know this is not the best solutuion anyways there was no other option.

please close the call.

Thanks

jrcygcm
Posts: 154
Joined: Tue Dec 05, 2006 2:18 pm
Location: Juárez, México

Re: Could not kill the existing SAP User session

Post by jrcygcm » Tue Jul 14, 2009 11:02 am

Next time, you can check the PID via SM66

Tinuviel
Posts: 1069
Joined: Fri Sep 09, 2005 8:05 pm

Re: Could not kill the existing SAP User session

Post by Tinuviel » Sun Jul 19, 2009 8:48 am

SM50 shows the PID. If it it can't be killed in the Task Manager, use the OS program SAPNTKILL.

TattooDave
Posts: 188
Joined: Mon Aug 23, 2004 12:26 am
Location: Brisbane, Australia

Re: Could not kill the existing SAP User session

Post by TattooDave » Mon Jul 20, 2009 6:03 pm

I already checked there is no connection from this user in gateway monitor SMGW & SM50 to cancel the process.
The OP States that there is nothing in SM50.

Brumhilda
Posts: 17
Joined: Sat Jul 25, 2009 9:48 am

Re: Could not kill the existing SAP User session

Post by Brumhilda » Sat Jul 25, 2009 10:01 am

TattooDave wrote:
I already checked there is no connection from this user in gateway monitor SMGW & SM50 to cancel the process.
The OP States that there is nothing in SM50.
There can't be nothing in SM50 - there has to at least be several inactive dialog and background threads.

Post Reply