Poblem in Transport Queue

whenever I import transport request in Qulaity Assurance transport
Queue, it successfully imports but when transporting the specific
request number to different QA Clients it starts importing and
showing "transport symbol i.e. TRUCK" on the the particular request but
it does not turn to "symbol yellow". I leave the system System for that
particular screen for hour but it doen not transport successfully in
the system.
I have some important transport request which are to be transported to
the PRD after tesing the scenario in Quality Assurance Server.
Kindly help me in resolving this issue.
Regards,
Majid Khan

Hi,
1. Check the TMS configuration and the transport route and the tp connection in STMS.
2. Check wthr the problem is for a particular trasport request or for all..
3.Check wthr your transport request is local or transportable request bcecause local request are not transportable.
4.Check SE10 to see wthr the import request is in green in the quality to which you wanna transfer.
5.Check the status of RDDIMPDP program and also kill the tp programs at OS level which are hung up.
You can also transport the request throudg OS level but it is not recommended by SAP
Please let me know wthr the issue is resolved or not.
Rakesh

Similar Messages

Delete change request in transport queue

hi,
is there a possibility to delete change requests in the transport queue (stms)?
thanks
mike

hi,
Yes, you can delete change requests in transport queue.
You can do it in SE10. Place the cursor on the item and press delete button on application tool bar. If it dint get deleted. Then right click on request and press Sort/Compress . Then try deleting again.
Regards,
Sailaja.

Transport queue gets closed very often

We found out transport queue gets closed very often on QAS system. We open it.
However what is the reason. Could it be because of an job is sheduled to import every 15 minutes. or is it something wrong

Hello Jan,
Yes, its expected behavior because when import runs, TMS lock the import queue for avoiding incosistency.
As long as the import is running or is scheduled, you see this status is displayed in the Import Overview with either This graphic is explained in the accompanying text or This graphic is explained in the accompanying text. After the import, the import queue is opened again automatically by the transport control program.
http://help.sap.com/saphelp_nw04/helpdata/en/c6/ea253715dfb808e10000009b38f889/frameset.htm
Regards,
Debasis.

About the automation of "Adjust Transport Queue"

Hi, Experts.
I want to know about the automation of "Adjust Transport Queue".
Concretly, I want to copy Transport Data&cofiles
from Transport Domain Controler(DEV) to PRD System.
[Environment]
DEV -- Location A, Domain Controler
QAS -- Location A
PRD -- Location B ** different Location from Domain Controler **
Therefore when I execute Transport to PRD,
"Adjust Transport Queue " is necessary to do.
I know the JOB to refresh Transport List,
but I don't know the JOB to Modify transport Queue.
If you know it , please tell me the way.
Best Regards.
Toshikazu Takahashi.

Hi Pavan,
Thanks for your post.
What’s the version of your TFS?
How did you specific the file path in InvokeProcess activity? Where you stored this batch file, under a local path in your build agent machine?
As the TFS Build will running on build agent machine, so you can create the batch file under a local path in your build agent machine, for example C:\BAT\test.bat, then specific in this “C:\BAT\test.bat” as the
FileName in your InvokeProcess activity. You can refer to Hari’s reply in this similar post:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/b8bcb19f-1296-441c-8356-e701b949445a/tfs-2010-how-to-execute-a-batch-file-after-build?forum=tfsbuild.
Each TFS build’s drop location copied from binaries folder, you can find the binaries folder from
C:\Builds\ID\teamprojectname\builddefinitionname\bin on build agent machine, so you can write your batch script to copy latest files form this binaries folder for each TFS Build.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Transport queue is not updating?

Hi Gurus,
We have a 4 system landscape Dev->Test->Quality->PRD. After a transport is released from SE03 why the import queues are not update with the released request, except the "Test" Enviornment not the other systems in my landscapre (Quality & PRD)? but once the request has been imported into the "Test" enviornment, the Quality import queue and PRD import queue are updated? why not, once its released in "Dev" in the first place?
Thanks in Advance
Ahamed

Dear Guru,
According to setup in my landscape, my Test system is the source system for the "Quality" & "Production". from this source system a delivery route is configured for the other two systems ( Quality & Production)
Note from: help.sap.com
When you set up a delivery route, you are making sure that all change requests that are imported into the routeu2019s source system are automatically flagged for import into the routeu2019s target system.
Thanks for your support, I appreaciate it.
Ahamed

SCOM 2012 SP1 exchange edge transport queue is showing as not monitored state.

Hi,
We have exchange servers which is being monitored by both SCOM 2007 and SCOM2012 SP1, in SCOM 2007 R2 exchange edge queue is getting discovered, but in SCOM 2012 SP1 it is showing as not monitored state.
Please help me in resolving this issue.

Hi,
What kind of MP did you import on SCOM 2012? Meanwhile, please try the following suggestions.
1. Start the Remote Registry service.
2. Enable File and Printer Sharing
3. Check the network connectivity between the management server and the Exchange Server and ensure the FQDN of the Exchange Server can be resolved.
4. Clear the HealthService queue on the Exchange Server:
a. Stop System Center Management service.
b. Go to C:\Program Files\System Center Operations Manager 2007\, and rename the “Health Service State” folder.
c. Restart System Center Management service.
Niki Han
TechNet Community Support

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

Consumers from for wlsb.internal.transport.task.queue.ftp Queue on OSB

Hi All,
Can anyone tell me where do I get the Consumers for Queue:
wlsb.internal.transport.task.queue.ftp_auto_1
wlsb.internal.transport.task.queue.ftp_auto_2
I have consumers in my 1st Queue but not in my 2nd Queue for any of the Internal Transport Queues.
Please let me know how do I solve this Issue.
Thanks !

You might be better of asking this in the SOA/OSB forum. Also please add version, OS etc.
The ftp poller from OSB is always targeted to exactly one server, but at least in theory both servers should pick up the messages from the distributed Q.
What behaviour exactly are you seeing? Does it relate to the ftp poller target?
best wishes!
Blog: Oracle Fusion Middleware and Cloud Computing

Error while Transporting Request

Hi All,
we have ECC 6.0 on Unix environment.
we had copied a production client with group selection, as we wanted all the three system PRD,DEV,QLT in sync.
the export was succesfully done.i copied Cofiles & Datafiles which are generated in DEV & Quality server,then i add request no in transport queue. the time when i copied transport request was not releasing from development.we checked the destination it was full so we removed the old request. then req is releasing.
after that i deleted the Cofile & datafile from OS level of DEV & QLT & trying to delete the reques from request queue. it is deleted but when im refreshing the queue its coming back in the queue.
while transporting other request its giving me error.
please help out me.

Hi Aasmi Gawas,
Please could you post the error?
We don't have a crystal ball to see the errors in your system...
Best Regards,
Erick ILarraza

CTS+ : Error while importing transport into Portal QA system

Hi All,
we have configured CTS+ for Portal systesms, then we have created a
test transport in Portal Development system (PD5). SOlution manager is the communication systesm. We are also able to release this transport from transport organizer web UI.
This tranpsort is available in transport queue of Portal Qua system , but on importing this transport in PQ7 we are getting following
error
Problem during file access, stopping. Error is:'The file (/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa) does
not exist on the filesystem.'.
We have checked in /usr/sap/trans_SM/data/PD5K900003/ file
Test_CTS_20110215_031956.epa exist.
CTSDEPLOY and sap.com/com.sap.tc.di.CTSserver connection are working fine.
Kindly suggest.
Regards,
Akhilesh

Error is
puhi078:sp5adm 54> more PD5T900003.PQ7
59y0C1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "PD5K900003"
1 ETP102 system              : "PQ7"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "372.04.71" "701"
1 ETP198
2 EPU601X"CTS Import Service - Version 0.94" "04.04.2008" " " " "
2 ETW000 ========================================================================
2 EPU601 "Deploy web service destination =" "CTSDEPLOY" " " " "
2 EPU601 "Directory =" "/usr/sap/trans_SM/data" " " " "
2 EPU601 "SDM Deploy URL =" "http://cqhepad1.contact-energy.co.nz:50018" " " " "
2 EPU601 "SLD Deploy URL =" " " " " " "
2 EPU601 "XI Deploy URL =" " " " " " "
4 EPU607 Non-ABAP system "PQ7" (communication system "SP5")
1 ETW000 Start import with id:4D5ADEC1C8D6540AE10000000ACE01D3
4 ETW000 DeployProxy (patch level:0) called with following parameters:
4 ETW000 Deployable(0)
4 ETW000 Deployable-Type:0
4 ETW000 Deployable-Id:4D5A0D6A05111633E10000000ACE01D3
4 ETW000 Deployable-TransportContainerId:PD5K900003
4 ETW000 Deployable-ContentLocator:/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa
1EETW000 Problem during file access, stopping. Error is:'The file (/usr/sap/trans_SM/data/PD5K900003/Test_CTS_20110215_031956.epa) does not
1EETW000 exist on the filesystem.'.
3 ETW000 End import with returncode:'12'
4AEPU601 "Highest Return Code =" "12" " " " "
1 ETP189 DEPLOYMENT

Transport control program tp ended with error code 0208

Hello
I installed minisap NW2004s on XP/SP2 VMWARE 4.5. The installation it self's works fine, but have some problems in the stms. when i call the transport queue there appears an error as follow:
System   NSP              Command TMS_MGR_READ_TRANSPORT_QUEUE
Client   000              Service Transport Service
User     TMSADM           Start    Online
Date     12.10.2006       Function TMS_TP_SHOW_BUFFER
Time     07:13:13         Message TP_REPORTED_ERROR
Transport control program tp ended with error code 0208
Errors: error in transportprofil (param missing
unknown,.
Any Idea? Thanks for your help.
Regards, George

Hi
You can edit the parameter profile using RZ10 and RZ11. You should not copy but manually edit the parameters. Also you need to make a consistency check so that the parameters will be copied to the database from the OS level. You will find an option to perform consistency check in RZ11.
Hope that helps.

Transport control program tp ended with error code 0247

Hi,
Our landscape is such that any transport request once released, gets imported to Q system immediately. However there is another system (another box REG - regression testing) to which I would like to import a request but the transport queue of REG system does not show the request. So I tried to explicitly add it to the queue but I get the following error message, 'Transport control program tp ended with error code 0247.
There doesn't seem to be a problem with data & CO files as the same request is in Q system and the changes are all transported successfully.
This request is a transport of copy that contains some ABAP code. (changes to the relevant package can be saved only in local requests therefore transport of copy is recommended to transport the changes).
The changes appear correctly in Q system but for REG system the request neither appears in the queue nor be added to it.
Can someone advise where the problem is.
Cheers,
KC

Hi
When the REG system is not in the system landscape, probably you may not have Data & Co files in that system & you need to have those files separately in the REG system path & then import it.
Do consult Basis team on this issue.
Thanks,
Murali.

Transport control program tp ended with error code 0203

when i import queue and transport queue from dev to prd ,error show:
Transport control program tp ended with error code 0203
Message no. XT200
Diagnosis
An error occurred when executing a tp command.
Command: IMPORT DEVK900298 P01 clientP01 U0 pf=/usr/sap/tra
Return code: 0203
Error text: wrong syntax in tp call
Request: DEVK900298
System Response
The function terminates.
Procedure
Correct the error and execute the command again if necessary.

Dear Allen,
The transport control program tp collects all return codes that occur when a tp command is executed. From all of these single return codes, a combined return code is calculated that tp outputs as a result at the end the command. During an import, for example, all return codes for individual import steps are handled. If a special return code does not occur, then the combined return code at the end is the maximum of individual return codes that occur. In addition to the value of the return code, tp also gives a short description of this return code. You can display this short description using the command explainrc.
Normally, all return codes that occur originate from individual transport steps. Since these individual return codes can only have the following values 0, 4, 6, 8, 12, 13, 14, 16, the combined return code also has one of these values. However, if a general error occurs, a single return code over 200 is generated. For example, this could arise if tp cannot establish a connection to the database. The maximum return code for all single transport steps is output in a separate message before specifying the combined returned code. In this case, the combined return code is always the return code of the general error message.
<b>tp Commands:</b>
tp addtobuffer <request> <sapsid>
As of Release 4.6A, an explicit addtobuffer command leaves the position of the entry unchanged, if the relevant transport request is already in the buffer. Only the status of the entry is changed:
Unconditional modes appearing in the command line are added to the unconditional modes in the buffer.
All the steps of the entry are re-initialized.
If the entry found is not an initial entry, the import step for the command file is set to *4000 .
Before you call this command and its options, consider the effects of changing the import sequence.
tp cleanbuffer <sapsid>
This deletes successfully imported change requests from the list of requests that are marked for import into the SAP System <SAPSID>. This function is contained in the commands tp import all <sapsid> and tp put <sapsid> .
tp delfrombuffer <request> <sapsid>
If the specified request is marked for import into the specified SAP System, this flag is deleted from the import list.
Before you call this command, consider the effects of changing the import sequence.
As of Release 4.6A: If a transport request was only partially imported, you can delete this type of transport request from the buffer. However, if a deleted transport request is placed in the buffer (without having been initially or completely imported), the attributes of the old entry are reactivated. This means the return codes, the unconditional modes and tags of the deleted entry appear in the new entry.
tp delstopmark <sapsid>
If the list of requests marked for import into the specified SAP System contains a STOP mark, the mark is deleted.
tp export <request>
This exports the complete request from the source system. This command starts the export of a request from the operating system level. Only use this command in exceptional cases. The SAP System uses the command expwbo to release requests from CTS transactions.
tp reformatbuffer <sapsid> [options]
This automatically reformats the entire buffer.
As of Release 4.5A, there are 2 different formats for buffer entries. (As of Release 4.5A, tp can work with both formats, and with a puffer containing heterogeneous entries. As of Release 4.6A, tp can work with 3 formats.)
However, in certain cases entries with the old formatting have to be reformatted during the normal run of tp . In this case, the entire buffer is automatically reformatted.
If you use the options downtorelease and Iagree for command reformatbuffer , you can format the buffer so that its formatting is compatible with an older release:
Option downtorelease <Release>
The command reformatbuffer with this option formats the buffer so that the formatting corresponds to the one used in an old release. This is necessary if tp writes buffer entries to the buffer of another system, but uses a buffer format that the transport control programs does not understand in this system.
Since older formats cannot store the same amount of information as the newer ones, some information contained in the original buffer may not be stored in the unformatted buffer. This may lead to data loss.
To avoid data loss, the original buffer is stored. In addition, you have the following functions:
Displaying the unformatted buffer (using showbuffer <SID> )
Displaying the original buffer (using showbuffer buffer=<SID>SAV )
Accepting the unformatted buffer (using reformatbuffer and the option Iagree yes )
Resetting the changes (using reformatpuffer and the option Iagree no )
If you call reformatpuffer using downtorelease , tp displays in detail if information was lost by reformatting, and what that information was. tp also names the commands that is has to execute to accept or reject the changes.
If you use the option downtorelease , you must also specify the option Iagree with yes or no . You cannot use the transport system until you decide to accept or reject the changes.
Option Iagree
Here are the following values for this option:
yes ( true )
Accept the change made by tp reformatbuffer <SID> downtorelease <rel>
In this case, tp deleted the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
no ( false )
Reject the change made by tp reformatbuffer <SID> downtorelease <rel> In this case, tp copies the backup of the original buffer back and deletes the buffer semaphore file that was lifted for security reasons at the first call of reformatbuffer
tp setstopmark <sapsid>
A special STOP mark is added to the list of requests registered for import into the specified SAP System. The commands tp import all <sapsid> and tp put <sapsid> only process the requests in front of this stop mark.
If there is no stop mark, it is automatically generated by the commands
tp import all <sapsid> and tp put <sapsid> .
When all the requests in front of the stop mark have been imported successfully, at the end of all the calls the related marks and the mark itself are deleted.
A STOP mark can only be placed at the end of the change requests that have already been marked. In addition, it can only be set if no other mark of the same kind already exists.
tp showparams <sapsid>
This tp function displays which values the individual parameters of the transport profile have for the current SAP System.
tp verse <request>
This creates versions of the objects in the specified request. This transport step is contained in command export .
As of Release 4.5A, more actions that prepare the export are performed in this step.
Thanks and Regards,
Naveen.

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

R/3 Transport requests

HI,
i raised a transport request for install & activate data source in R/3.I released the request in development system,But it is not showing in the transport queue
stms_import
What am i missing.....what is the tcode for transport queue.
Thanks

there is a possibility if there is filter in the list you see in stms_import transaction.click on the filter icon and view if there is any userid specifically given..
But there shouldnt be any problem in transport if it is in se09..ask your basis to import to QA..and check if they have the transport path setup form dev to QA properly then it should not be problem in transport..

Poblem in Transport Queue

Similar Messages

Maybe you are looking for