TMS error Troubleshooting

Owner:
Basis Admin
Purpose:
How to troubleshoot TMS errors when users are saying their transports are stuck in Import
Running status.
How to troubleshoot Hung transports
How to troubleshoot component version mismatch errors 1 out of 1 requests does not match
component version when importing transports.
Affected Parties:
TCM team
Policy:
The below steps can be done at any time. If there are CRB or emergency transports hung in
production it can be considered an urgent priority to fix, or if the user says it is holding up their
cycle testing in non-production systems.
Hung Transport Procedure:
Resources to check:
Transport Logs
Import Monitor
TP System Logs
RDDIMDPD job logs in SM37
TRBAT table
TRJOB table also though rarely this helps
1. Check the transport logs to verify it hasnt imported fully.
2. Check the import monitor for the system transports are stuck in.
a. STMS -> Import Overview -> click on the system -> GoTo -> Import Monitor
Check to see if there are multiple transports that look like they have been trying to
import (the status symbol is a truck). In order to re-import them you will have to
delete them from both the import queue and the import monitor.
Usually if there are transport problems there should look like there are several
transports trying to import but staying in that status for a long time. If there are a
lot of hung transports, or if they are still stuck upon re-import, continue with the
next steps to troubleshoot the issue.
3. If there doesnt seem to be any hanging transports or errors, try doing a test transport to
verify that transports really are or are not moving correctly. If you think its just an issue
with just 1 transport, you can try to manually import it. If you dont think the problem is

TMS related, do basic system checks to see if theres a performance issue with the system
not specific to transports.
4. Check TP System logs
a. STMS -> Import Overview -> click on the system -> GoTo -> TP System Logs
b. Look to see if there are any errors or warnings. A common error that can indicate
TMS problems is:
WARNING:
Background job RDDIMPDP could not be started or terminated
abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING:
(This warning is harmless if no further warnings follow.)
Proceed to step 5.
If theres an error that references a file access error like *.LOB it may mean Infra
team needs to clear the temp file.
An error similar to the following could be a result of a locked object on the OS side
WARNING: \\mnqas\sapmnt\trans\tmp\QMN.LOB is already in use (15950), I'm
waiting 3 sec (20140506071316). My name: pid 3336 on fsdesa
5. If you see TP system logs referencing an RDD* job (like RDDIMPDP), check the job logs in
SM37.

If you cant find any released or scheduled jobs in the system called RDDIMPDP, go to 000
and release the job from there as high priority (the TP system logs will tell you to do this
by running report RDDNEWPP, and it should ask when releasing the job if it should be high
priority).

In this example the RDDIMPD job was cancelling and the job logs had this error:

I logged onto SC1 000 client and saw the DDIC userID had been locked. Once I
unlocked it transports started moving again.

In another example, the RDDIMPDP job log says another process is already running:

Go to SE16 and view TRBAT table. Do this in the client that transports are stuck in,
not necessarily the config client.

See if there are old entries in this table. If there are, go back into the table in edit
mode and delete the entries. There may be entries called HEADER as well. If
theyre old, delete those too.

Then delete the hung transport from both import monitor and import queue.
To delete from import monitor, right click and delete entry.

If transports start importing normally again the problem could be fixed. If they
dont, re-check the TRBAT table to see if more entries need to be cleared and check
the RDDIMPDP job logs again to see if there are more runs of the job and if they are
trying to process a different process ID than before.

Then you have to manually re-import the transports you deleted from the import
monitor once transport errors are cleared.

For more info about RDD* jobs, use this link:

http://www.consolut.com/en/s/sap-ides-access/d/s/doc/D-RDDIMPDP

Component Version Mismatch Procedure:

If you receive errors while importing a transport or in the TP system logs saying 1 out of 1
requests does not match the component version
Option 1: Import manually in STMS with the import options Ignore Invalid Transport Type

Option 2: To prevent from receiving the error, add SP_TRANS_SYNC=OFF TP parameter to each
system in the transport path that is receiving this error.