We had problems with this particular error message "Delete session 001 after error 061" in our system this morning. It is the Monday after a maintenance weekend. We didn't find any notes that correctly addressed the above error message. The solution to our problem was from the system side. The two NICs on each App server were not grouped properly. Somehow they had become ungrouped and saw their address as already in use because each card was responding to the system request, which caused numerous network read errors. Once we contacted the NT Admins and had them synch (group) the cards, the problem went away. I hope this helps.
I just have this same problem and fix it. It has nothing to the locktable, this is due to a disconnection from the SAPGUI.
For some reason, the terminal when is the SAPGUI is causing disconnections, in my case, this was a security programs recently installed (firewall, anti-spyware, TuneUp, ncleaner, CCleaner, etc.)
Remove all these programs suspects, who handle or involved the Windows TCP parameters, this solves the problem.
you get these 'delete session' errors when the workprocess that has been handling the communication to a frontend is dying. this may be for various reasons. unfortunately it's not only due to firewall or other frontend software and not necessarily bound to happen on Windows-based frontends only. it can be the connection type (DSL, UTM ...) combined with any other of the components like firewall, SAPGui version and so on.
unfortunately error 061 is not documented and not specified (they are up to 23 but no more). i dearly would like to know, what 061 is about!
I suspect one of possible reasons to be enque table overflow. Watch ASCS logs or enque statistics (SM12->Extra) whether you encounter any errors at the same time you notice 'delete session...'.
Adjusting enque/table_size may resolve this problem. Search notes for "enque overflow".
error 061 means that the session has been canceled by the system. Usually this happens if some sort of error happens and the only way to resolve this situation is to delete the currently running user session. As stated before this can happen for a number of errors.
Unfortunately this "error" is also generated, if a user session is logged off due to a forbidden multiple logon. So you can simply generate this syslog message when you log on twice to one system (with two differen application servers) and confirm the license popup such that you terminate the foreign session. On the foreign server the syslog with error 061 will be generated.
This message appears in the log when a user starts another session to the sam SAP system from the logon pad. The user logs in and a pop window with the title "License Information for Multiple Logon" is displayed with the following:
User <USERNAME> is already logged on in client 000
Note that multiple logons to the production system using the same user
ID are not part of the SAP licence agreement.
You can:
- Continue with this Logon and end any other logons in system
When ending any existing logons to system, unsaved data is lost.
- Continue with this Logon, without ending any other logons in system
If you continue with this logon without ending any existing logons to
system, this will be logged in the system. SAP reserves the right to
view this information.
+- Terminate this logon +
The user selects the first option and a message box is displayed. The user select OK and the message Delete session 001 after error 061 is logged.
Did you ever get a response or solution for this. We have run into the same issue and cannot find any documentation on this. The only difference in our environment is 9206 and AIX.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.