It sounds like there's something the matter with the Operating System. I have seen this behavior in Windows 2000 and Office 2000 applications. The application is closed but the process remains. Have you installed the latest service pack for W2K? If you cannot end the process in Task Manager, get the KILL.exe utility from the W2K Support Tools (located on the W2K CD). KILL.exe is more powerful than the "end process" button in Task Manager. Since rebooting the entire system is time consuming, I suggest you use one of the following workarounds while you determine the cause of the orphan process:
1. Log off Windows and log back on. Then, you should be able to launch SAPlogon again.
2. Kill the process with KILL.exe (c:>kill saplogon.exe or kill <pid>)
3. Log on directly to SAPGUI bypassing SAPLogon.exe. To do this you need to run:
sapgui <systemname> <instance_number>
Example: sapgui myprd 00
Keep in mind that SAPGUI might not be in the path. Therefore, you need to go to the directory where SAPGUI.exe resides or put the folder in the system path. This is a very fast way to log on to SAP.
4. Create shortcuts for the different SAP systems you log on. This way, you also bypass SAPlogon.
5. Use "LogonX" a free product from Basis Technologies that allows you to quickly launch SAP sessions. You can download it at:
Dig Deeper on SAP Basis administration and NetWeaver administration
Related Q&A from Giovanni Davila
Learn how to transfer a client from one server to another in this administration tip from Basis guru Giovanni Davila. Continue Reading
Learn how to return a list of 1,000 transport requests in SAP R/3 PRD in this tip from SearchSAP.com's Basis expert. Continue Reading
Learn fundamentals of transport management and STMS from Basis guru Giovanni Davila in this expert tip. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.