I can't open the production transport queue. Our production system crashed about 3 hours ago and since then I can't open the production queue. At the time of the system crash I was transporting a user role and now when I go to STMS and try to open the production transport queue the clock is displayed in the left hand corner with the hands going round and round and I get a message saying copying import queue PR3. This is going on now for about 3hrs since the system crashed.
I done what you suggested and now it lets me into the PR3 transport queue
Now I'm getting an error saying that the transport control program could not be started, RFC errror connection to partner broken. If I click on the X it allows me into the transport queue but there's absolutely nothing in the transport queue.
I think I know this error though cannot remember it what I did. I faced a long time back. However please do one thing. In STMS go to TMS alerts -
>TMS Alert Viewer. You will find this error there as well.
Click on it and a pop up will come. In this pop up on the right had side you will find three icons. First one will be a question mark, second will be clipbpoard kind of icon called tp output and third one for logs.
Click on the the first 2 icons-question mark and tp output and paste the contents for both of them.
The tp output contents will help you the best in finding out the root cause of the issue.
Additionally try to redistribute the TMS configuration from domain controller though it wont help you too much.
The best solution in this case is (this is something which I think we had to try eventually ) is restart of SAP.
I ran the programs RSTPTEST as suggested below and everything looks ok. I looked at the Gateway trace files but to be honest doesn't really mean anything to me. I've inserted the text from the tms alert file.. Have you seen this before?
Message no. TP 608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
If I remember correctly this is what happened in my case:
Dummy TP proceeses were still running at OS level even though no job was running at OS level. We cancelled those processes and also deleted dummy entires in import monitor. Next after ensuring no TP process was running at OS level we did an import using TP commands at OS level and the issue got solved.You can do any kind of import even that of a blank transport request so that production doesnot get changed.Create a blank TR and release it and then try to import it using TP imports.Also check if you can find any old TP log files for the import that was happening at the time of crash in the path usr/sap/trans/tmp.Please delete them.
Please do try this out. This should really work.If this also does not work then restart should be done.
I'd just like to thank you for all of your help. I did reboot but it didin't work. So i then deleted the tmp files as advised in your previsous email and it worked. Thanks again for getting me out of a major jam again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.