Problem transport requests remain in queue

Hello
I have problem as transport requests remain in queue of QAS and does not advance in approwal list. Problem began after /usr/sap/trans was full
Now trnasport are imported correcly but remain in queue of QAS and does not advance in approwal list. Problem began

Hi Jan,
Talk to your Basis team as this is basic config.This is happening because import queue is inconsistant. Check this thread - STMS: Transport Requests Forever Stuck to Running
Regards,
Sen

Similar Messages

Need TP command for Add Transport Request to import Queue all at a time

Hi SAP gurus,
Can you tell the o/s or TP command to Add Transport Request to import Queue all at a time which are available in co files directory ,
Because I have to add 500- 600 request . For every request I canu2019t do like this STMS_IMPORT -- Extras=> other requests -add--
Thanks and regards
babu

Hi,
You can export list of all transport requests from your DEV system in one shot, from SE09-> Display (provide your required selection criteria) -> Goto -> "Display as List"
You can export these all Transport Requests as Spreadsheet. Then Filter out all your required 400 to 500 Transport Requests.
Now,use another excel sheet to create a file with the list of required transport request Nos only, then concatenate all of them to generate the required TP commands as mentioned below.
The syntax will become as follows:
column1 column2 column3
tp addtobuffer DEVK900123 <SID> pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp addtobuffer DEVK900124 <SID> pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp addtobuffer DEVK900125 <SID> pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp addtobuffer DEVK900126 <SID> pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp addtobuffer DEVK900127 <SID> pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp import DEVK900123 <SID> client=### pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp import DEVK900124 <SID> client=### pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp import DEVK900125 <SID> client=### pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp import DEVK900126 <SID> client=### pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
tp import DEVK900127 <SID> client=### pf=<Drive>:\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL
-> Open Notepad and Copy+Paste these three columns & save the text file in the <Drive>:\usr\sap\trans\bin\ folder.
-> Then rename this .txt file to *.bat.
-> open a command prompt and change to the <Drive>:\usr\sap\trans\bin\ folder and run the .bat batch file.
Make sure that object lists of all the Trans. Requests are checked and confirmed for the transport to avoid data incosistency in target system. (e.g. Number Range Object)
Regards,
Bhavik G. Shroff

Problem transporting Request from Development to Quality Assurance Server

Hi All,
I m facing a problem of Transporting requests from one System to other.
When adjusting the Request ,the error message reads as follows :
RFC system error in system/destination
[email protected]_HSE
Now,when I check the RFC Connection for [email protected]_HSE,,
i get the message :
" License Check required "
Please respond to this query urgently.....
Thanks in advance

Hi!
I think it's better to call SAP support, if you have problems with the licenses...
Maybe your company forget to pay their fees since a while
Regards
Tamá

STMS: Add a great number of transport requests to the queue

Hi everybody!
we make a system copy and I have two questions regarding this.
1. After the system has been copied, we have to add a great number of transport requests to the transport queue (transaction STMS). Is there a report to to this?
2. Of course, the transport requests added to the queue have to be imported. Is it possible to mark them all at a time and then start the import? I mean, if one specific object (for instance a reportsource) is part of several transport requests, does the STMS ensure that they are imported in the correct order, so that the following won't happen: a imported object is overwritten by a older version.
Thanks for your help in advance.
Regards
CHRIS

As Sunny said you can do it from OS as there is no SAP program. Create a file with the all transports no. that you want to add to the buffer at the OS level. Here is the script that we use:
for i in `cat file_name`
do
tp addtobuffer $i SID client=xxx pf=TP_DOMAIN_SID.PFL
done
For you second question, the sequence of import into the system will be based on how they are listed in the STMS queue. So first transports goes first then the second, third and so on.
Hope this helps.
Thanks,
Naveed

Problem Transporting Request

Dear Experts,
I am facing a problem in transporting the request, 2 days back it was working fine, but from last day is having problem.
When i import the request the truck shows but it doesnot finishes. after sometime if i goes to tms alert i find a message comming:
Function:-TMS_WBO_READ_REQUEST.......
MESSAGE:- "READ_DOCU_FAILED".
It doesnot transport the request.
can anybody help me out.........waiting for a response.
Thanks and Regards
Bhaskar.

Dear Hariprasad,
Thanks for your reply....
This is working fine I have deleted the entry from those tables....now it has started the transport.
Thanks onces again.........
bhaskar

Mailbox move requests remain in Queued status

My server is part of a two member DAG. DAG shows to be healthy. I have turned logging up to Expert level but no useful data is generated (only shows that the move request was created; no problems are indicated)
Server is Exchange 2010 SP 3

Hi,
Please check the database copy status under management tab on source database and target database. This can be that one or more of those databases you are moving mailboxes to has a failed or suspended copy and its failing the DataMoveReplicationConstraint
check.
Refer to this blog about Exchange 2010 Mailbox Moves and Mailbox Resiliency
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
In addition, please check the event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
Best Regards.

Importing a transport request

Hi Expert,
In our Transport landscape some one has released a transport for QA system but the request is not reflecting in Import Queue of QA system.
Can some one advise how to import the request in QA.
Thanks
Kundan

Hi,
There might be some problems at OS level of Dev/Qua system and check the Co and Datafiles. Now execute Tcode STMS_IMPORT in Qua system. and goto following location from menu bar:
Extras-> Other Requests -> Add
Now give the Transport Request No. and Target Client.
This will add the Transport request into Import Queue of Qua system, now u can import the request.
Hope this will solve your query.
Regards
Lokendra

Re-transport the transport request to NQA server after system refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

Amar,
Depending on how many tarnsports you have and also if this is one time, what you can do is ask Basis guys to write a small script which adds to the buffer to your NQA system.
Steps:
1) under /usr/sap/trans/buffer rename the NQA buffer file.
2) create a new empty file NQA (make sure permissions are identical)
3) Provide the list of transports and ask Basis team to put it in a file at Unix level
4) Run a script which will add to the buffer from the source file.
5) From STMS refresh the NQA queue and you should see all the transports ready for import.
Hope this helps.
Thanks,
Naveed
Edited by: Naveed Qureshi on Dec 4, 2008 8:52 AM

Transport request deleted from buffer how to retain it?

Hi geeks please help me.
As the support package upload,i have found that some transport request request are blocking the support package upload.The error issued was Queue_not_empty .I went to command prompt to get the list of transport request with status "will not be import because it is tagged".
then to remove them from the buffer I executed commands
tp addtobuffer <tr.request> <SID> pf=<path of tp profile> U1 tag=SPAM
tp delfrombuffer <tr.request> <SID> pf=<path of tp profile> tag=SPAM
.But now I see the transport request in the queue is in "RED" status.
I need to retain the transport request and reimport it.Is there any way to do that?
I have both K-file and R-file corresponding to this requests in cofile and data directories respectively.
Regards
Syamkrishnan

Hi Syamkrishnan,
just copy the cofile and data file in the transport directory, then go to STMS click on Extras -> Other requests -> Add and add the transport to the queue.. then just reimport.
Hope this help
Juan
Please reward with points if helpful

Re-transport the transport request in Quality server after System refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

No cross posting
Read the "Rules of Engagement"
Regards
Juan

What checkbox "import again" when adding an transport request to import que

Hello
I wander what checkbox "import again" when adding an transport request to import queue means?
Thank you in advance

Hello Jan,
Well you should have searched in help.sap.com before posting here for basic concepts. Anyways, import again means after successful import also you can reimport that particular request.. Please see the below link for other options as well.
http://help.sap.com/saphelp_nw04/helpdata/en/5c/d21880fe3c11d2b461006094b9ea64/content.htm
Thanks,
Siva Kumar

RFC error when trying to add transport request in queue in STMS..

Hi,
When I try to add a Transport request in queue in STMS transaction. I get RFC error saying some problem with tp program.
But when I go and check the RFC connection through STMS in system overview -> Communication -> RFC setting, it says RFC connection Ok.
What may be the issue ? I really need some light on this..
Regards,
Rajesh.

Hi Rajesh,
At times when u try to add the TR to a queue there would be 2 reasons.
1. If u have imported a TR into a system say QTY and it needs to be re imported, then we delete it fromthe STMS queue and add it again to re import it.
2. If u have some transport from external sap system to be imported here we place the data and Co files in the trans directory and then add the TR to this queue.
A TP failure happens if the data and co files does not exist in the TP directory or else, the TR target system is incorrectly mentioned.
Hope it helps.
Br,
Sri
Award points for helpful answers

Transport request main task releasing problem

Hi friends,
Environment is Linux, ECC5.0, Two system landscape,
I have problem with Transport Request task releasing when I am going to release the subtask that willbe released success fully when I am trying to releasing the main task that task is not released and at that time the system wil hang( mesg on the status bar is tp is connected success fully) thats it we wait for long time then also that looks thats only no log will be generating in usr/sap/trans/log there will be a log on this one that log is
WARNING:/usr/sap/trans/tmp/<username.LOS>is already in use (10), I'm waiting 3 sec(20070326124305). My name:pid 7265 on test(sd1adm)
after saw the this mesg I kill the 7265 pid then also same proablem.
I change the ownet of the request then the request is released but not uppeard in the import que. whn i am trying to import in que as manually that will appear in que but not importing when i press the import button the error is tp error 0203.
I check the both users authorizations also bothe authorizations also same then why it wil happening ???
then I check the nfc also that service also running ok the six services are 1.off 2.off 3.on 4. on 5.on 6.off.
I mount the trans dir also the mounting points also ok tms configuration is also ok
wt can i do plz help me with ur valuable suggessions
Thankyou
Ranjith

Hello Ranjith,
This is usually because the tp transport buffer lock file remains locked by the
operating system (OS).
You should be able to move or delete this file from the DIR_TRANS/tmp dir.
After that the tp should run fine after.
Thanks,
George

CRM Support Package Manager - Add transport request to queue

Hi,
I'm applying CRM Support Packages with SP_MANAGER on the production system.
I already applied these SP on the development system, I performed an SPAU adjustment, selected the corresponding transport request to use it on the production system, but SP_MANAGER didn't asked for this transport on the production system.
How can I add the SPAU adjustment to the queue with SP_MANAGER ?
Kind regards,
Christophe

Hi,
That's why I opened this message: in step 1 of the procedure described by the link (http://help.sap.com/saphelp_nw04s/helpdata/EN/de/151042f664e12ce10000000a1550b0/content.htm), the system should ask for a transport request. This is not the case here, despite the fact that the correct setting is set in SPAM.
Any other idea ?
That's not a problem since I can use a workaround (import via STMS when the system asks to perform the adjustment), but I wonder why the system doesn't ask for a transport request in the case of a CRM system.
Kind regards,
Christophe

Transport Request is disappearing from the import queue

Hi everybody,
I am facing a problem with the transport import queue.When I exported a transport request and entered the STMS transaction,initially it is showing the request.But when I double click on the system(like DEV or PRD) it is saying "there are no requests in the import queue".
Please help in resolving this issue.
Thanks in advance,
Sreeharsha Singuru

Goto transaction SE01 and enter the transport number and put the cursor on the Transport number ans click Transport Logs (CtrlShiftF2) and see the structure .
This will give u the details of the Development , Quality , and Production Status for that request.
Like whether this request is moved to quality or production . This you can make out from the Tree Node Structure of that Log .
Check this .
If this is not there in the Quality then it is not imported from queue .
regards,
vijay

Problem transport requests remain in queue

Similar Messages

Maybe you are looking for