When releasing a transport it stays constantly in 'export' status

Hi
We've recently done a refresh of our BI QA system. Now, whenever we create a new transport in the DEV environment, when we try to release it the status stays as 'Export' and says 'In process: Requires update'. If you refresh then the timestamp updates but it never comes out of this export status. Also the transport never appears in the QA queue/buffer (you can manually add it however using 'extras->other requests->add').
We can see tp processes hanging on the UNIX server. We have killed these and checked tables TRBAT and TRJOB - these are empty. There were however entries in TPSTAT, so we also deleted these. We also ran 'tp getprots <SID> pf=<profile>'. We have done this tidy up process several times and ONCE the transport actually appeared in the QA queue - but not other times. Always, the status stays in 'export'.
I have also ran RDDNEWPP in client 000 to reschedule RDDIMPDP - not helped.
We have removed the QA system from the domain controller and added back in. We have checked all the parameters match up between DEV and QA (CTC is set to 0). There is nothing in the tp log until we issue a tp getprots command manually.
SAP would probably advise us to upgrade tp (we are on version This is tp version 372.04.36 (release 700, unicode enabled) patch 165) - but before we have to resort to this, does anyone else have any ideas?
Thanks
Ross

HI
Seven Steps When you get stuck with Truck ICON.
1. Kill any TP processes at the OS level, if you do not have an import actively running. Then in STMS -> Import Queue -> Import Monitor -> Delete the entries related to this transport request. You can see the requests are in running status. To delete right click and delete.
2. While being logged in as DDIC in client 000, run report RDDNEWPP in trx se38. You will also need to do this for all client that you transport to or from in accordance of note 11677 Kindly goto SE38, use RDDNEWPP to schedule RDDIMPDP on client 000 and other client with DDIC user(refer note 71353 and 11677).
3. Check and delete any entries found in the following tables:
TMSTLOCKR
TMSTLOCKP
TPSTAT
TRJOB
TRBAT
Before starting a transport, these tables must be empty.Delete the entry using SM30/SM31.
5. In transaction Al11, Directory: /usr/sap/trans/tmp, check for semaphore with file extension .LOC/.LOB, try to rename or move this files to another directory. Refer to note: 12746.
6. If the Import Monitor or table TPSTAT does not contain entries any more, you can delete the entries of tables TMSTLOCKR and TMSTLOCKP.
7. Update your R3trans and your tp to latest available.
Then restart the import.
Also delete entry from usr/sap/trans/tmp
Regards
Uday

Similar Messages

  • Error when releasing a transport

    Hello experts,
    I am getting an error when releasing a transport. The error message is telling me that
    Object DTPA DTP_009C8T81IIB6H4UFC7FQUVRFL was set to 'inactive'   
    The detailed error message isnt very helpful. The performance assistant gives the error message RSO 407.
    I found another thread,  scn.sap.com/thread/3428031
    The answer in this thread appears to be very close to a solution for me, I just need a little more information I think. As it says, I have looked in the table RSTRAN for the transformation that this DTP processes. There are three rows, with a different OBJVERS. A and M are both set to ACT, but OBJVERS = D is set to OBJSTAT = INA.
    I suspect that this is the problem with the releasing of my transport. Do you agree?
    If so, how do I go about getting this activated?
    Many thanks.

    Hi Simon,
    The D version will be always inactive as it indicate SAP Delivered version of the transformation.
    I will suggest just have a look at any existing transformation, you will find same status i.e D version INA also check last change it will be SAP also under content column you will find info for D version.
    I still say, just go ahead and release your transport by ignoring the message, it should work. You are all set to move your transport.
    Rest upto you.
    I have tried releasing transport by ignoring messages many times.....and worked all time
    Thank-You.
    Regards,
    VB

  • Error when releasing a transportation order

    Good morning.
    I am trying to release a transportation order that contains a nonstandard table which has been added two fields, and the corresponding data elements and dominions of the new fields.
    When releasing the order, dumps an error and cancels the export.
    The status of the order now is "Initiated liberation".
    The error code is:
    "Error SQL 932 when accesing SPROXDAT: ORA-00932: inconsistent datatypes: expected %s got." And makes reference to data elements, but i think they are OK.
    Please,  ¿someone can help me?
    Thanks a lot.
    Regards.

    well the problem is very likeley that the table has enhancement options which allow only character and NUMC append fields.
    you most probably violated those preferences.

  • Error 12 when releasing a transport

    I am trying to release a transport, but get an error 12 "The request's target VBQ.500 is client dependant but the target system cannot handle that". VBQ.500 is a virtual system. Anyone have any suggestions for me to check out? I'm at a loss.
    Thanks,
    -- Jackie

    Hello Jackie
    I cannot tell you the reason for the error code. Somehow the CTS "believes" that the target system cannot handle clients and client-dependent objects.
    For the moment I think your main problem is to release your customizing request (or is it a workbench request containing client-dependent repository objects?). Try to change the target of your request. Perhaps the CTS can handle that. It might be necessary to adjust transport routes (transaction STMS) in order to get a "decent" target.
    Is your virtual system VBQ.500 a <b>consolidation system</b>? If not then try to change this (Note: this is a critical SAP basis activity).
    As soon as the request is released you can try to import it into your VBQ.500 system.
    Regards
      Uwe

  • Error when releasing Transports in ChaRM

    Good Day;
    When releasing a transport thru ChaRM I get the following error
    "Release of system could not be determined. The error message is "/TMWFLOW/CRIT_OBJ061"
    Any ideas?
    Thanks
    Don

    Good Day Farzan;
    We have the following systems
    Solution Manager      (Netweaver)
    Development System (Client 100 SAP 4.7)
    Quality System      (Client 100 SAP 4.7)
    Production System      (Client 100 SAP 4.7)      
    Regards
    Don

  • Error while Releasing a transport request - DSO 0SD_O03: Active version

    Hi all,
    I am getting below error when I am trying to release a transport request.
    Object ODSO 0SD_O03: Active version differs from modified version.
    I activated DSO again,but I was not successful to correct the error.Please help me correcting this error.
    Regards,
    Bob

    check
    match and copy while installing the business content
    Match (X) or Copy
    If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.With the most important object types, the active version and the SAP delivery version can be matched.
    When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually.
    A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.
    When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
    The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Installindicator separately.
    The active version is overwritten with the delivery version if
     the match indicator is not set and
     the install indicator is set.
    check following thread
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
    Thanks and regards
    Kiran

  • Error "TK287" when releasing a request - Special character "_" is invalid.

    I have some tables in Solution Manager and having some warnings:
    Table: CRM_SVY_DB_ST
    Field value:CRM_SVY_GENERATE_BSP_TEMPLATE.XSLT
    Field: TRANSFORMATIONID
    It doesn´t accept the special character "_"
    Below the error when releasing and the explanation of the error in the sequence.
    Key messages: TABU CRM_SVY_DB_ST 300DSWPCI_ISSUE_FDBCK 0000000000DCRM_               
    Special character "_" in generic key                                                                               
    Key messages: TABU CRM_SVY_DB_ST 300DSWPCI_ISSUE_FDBCK 0000000000DCRM_               
    Special character "_" in generic key                                                                               
    Key messages: TABU CRM_SVY_DB_ST 300DSWPCI_ISSUE_FDBCK 0000000000DCRM_               
    Special character "_" in generic key                                                                               
    Key messages: TABU CRM_SVY_DB_ST 300DSWPCI_SERVICE_FDBCK 0000000000DCRM_             
    Special character "_" in generic key                                                                               
    Key messages: TABU CRM_SVY_DB_ST 300DSWPCI_SERVICE_FDBCK 0000000000DCRM_             
    Special character "_" in generic key                                                 
    Explanation of the error:
    Special character "_" in generic key
    Message no. TK287
    Diagnosis
    The generic key 300DSWPCI_ISSUE_FDBCK 0000000000DCRM_ was entered for the object CRM_SVY_DB_ST. All keys that match up to the asterisk are to be transported.
    The key cannot have any special characters before the asterisk, since they are interpreted in different ways by different database systems.
    The key contains the special character _.
    System Response
    The entry is rejected.
    Procedure
    Extend the generic entry, or specify all keys individually.

    Hi,
    Go through SAP note 711103 & 688363.
    Regards,
    Sachin Rane.
    Edited by: Sachin Rane on Mar 12, 2009 2:48 PM

  • Releasing a Transport Request ends with error code 0012.

    Hi,
    We have a Development system and a Production System (both running on separate windows machine) but they are not connected in STMS. We perform transporting of Requests at o.s level and NOT through STMS.
    We are facing this new problem - We are trying to release a Transport Request in SE01 and it ends with error code 0012. The task inside the Request is released without any error. There is no Notes in SAP Marketplace for this.
    Test call of transport control program (tp) ended with return code 0012
    Message no. TK094
    Diagnosis
    Your transport request could not be exported, since all requirements were not fulfilled.
    Calling the transport control program tp
       "tp EXPCHK EFIK900025 pf=E:\usr\sap\trans\bin\TP_DOMAIN_EFI.PFL -Dtransdir=E:\usr\sa"
    which checks the export requirements, returned the following information:
    Return code from tp: 0012
    Error text from tp: ERROR: Buffer check failed.
    System Response
    Further processing is terminated.
    Procedure
    Check the following points:
    Feasibility of the transport control program tp
    Parameter settings in the transport profile
    Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
    Write authorization for the subdirectories
    Write authorization for the files of the subdirectories cofiles, data, log, sapnames
    Release the request again when the error has been removed
    Please help.
    Regards,
    Mohan.

    Hi Mohan,
    Nice to hear that that your problem is resolved.
    For Pamater CTC, please check the below links:
    Automatic transport between DEV clients ?
    http://sapsolutions.searchsap.com/kw;ExtendedTransportControl/content-sap.htm
    Regards,
    Hari Kishan

  • When releasing a transp. req.not all object in the request could  be locked

    When trying to release a transport request I get error message that "not all object in the request could  be locked. Do you want to release them anyway"
    I found an unreleased request (from someone else) containing few objects from my request. However I do not know the owner of that request (and I can not felete it). What to do?
    If I release the transport anyway what could happen?

    Hi Tina,
    If ur sure that u only want to release object which u have created and not the other objects then proceed in following way.
    1. Go to SE10 and click on create button
    2. u will get a popup select the 3rd radio button(ToC)
    3 Give the decsription of the Tp
    4. u will get  anext screen here in menu select request
    task->object lise ->Include object (new screen) here u select radio button freely selet obkect -> then new screen then selected the radio button selected objet. Here u give ur object and those object will be store in the created request then u can transport
    Regard
    Anees Ahned

  • How to release a transport request with warnings using a function module?

    Hi,
    I want to release a transport request(which has some warnings) using some function module .
    The warnign that i get when i try to release the Transport Request manually is "not all objects could be locked..."
    Which function module can I use so i can release such a transport request?
    I am currently using TR_RELEASE_REQUEST but I am unable to release the TR, it throws an exception.
    Also i wouls assume that the function module mentioned would take care of releasing all the unreleased task
    under the request.
    Regards,
    Bikash.

    Hello Bikash
    As an alternative (to cope with the warnings) you may use TRINT_RELEASE_REQUEST.
    However, since this fm offers only a single task/request as IMPORTING parameter you need to take care about unreleased tasks yourself. Looking at SE09/SE10 even there you do not have the option the release a request including all its tasks.
    Regards
      Uwe

  • How to retire/archive/status a released workbench transport for an OSS note

    My Question:  Is there a best practice for the "retiring" or "archiving" or "statusing" of released workbench transports for OSS notes that have been imported into the quality environment, but should never be imported into the production environment? 
    For example an OSS note is applied and imported into QS1, but then a CRT Hotpack is applied as an entire patch upgrade, so that the prior individual transport is no longer needed.  Best Business practice indicates to not delete a released transport, but unless there is a way to permanently segregate them from the remaining legitimately viable transports, there is always a risk that the "stale" code could inadvertently slip through thus overwriting good code.

    Hello.
    Well, you have confirmed what I suspected when I read the descriptions - wrong forum. 
    I chuckled and couldn't stop a broad smile from creeping across my face when I read your response though:  "the old BASIS type questions".  I knew we were a bit behind the times here; you have definitely confirmed this suspicion.
    Thank you again.  I'll try another search of the OSS notes or put in a customer message just for the heck of it.

  • Problem releasing workbench transports

    We had created a number of changelists in our workbench and are trying to release these to transport them into out test system.  When we release the transports which are created without issue in the development workbench we get the following message:
    Preparation for export                                                        
    Transport request   : CRDK903862                                              
    System              : CRD                                                     
    tp path             : tp                                                      
    Version and release: 372.04.57 700                                                                               
    Execution of the export pre-processing methods for request CRDK903862                                                                               
    Start: Execution of object-specific export pre-processing methods             
    Changelist C647D7C9CCE64307AFC4F46272840107 is not complete in this system    
    Request CRDK903862 is modifiable after error during release                   
    Preparation for export                                                        
    End date and time : 20090925164345                                            
    Ended with return code:  ===> 8 <===                                          
    The Transport Agent Service is  already activated.
    Has anyone any idea what the problem could be
    Thanks in advance

    Hi,
    You need to first check which TranportOrder ID was not getting released on the server .
    Then fire the below query to find the changelists associated with that TransportOrder in the ARS database-
    select * from changelist where state <>0 and transportorderid ='<Name of that Transport Order ID>'
    Then follow these steps -
    1. Stop the Transport Agent in Source repository.
    2. Cleanup the blobs from WBTRCL, WBTRBLOB, WBTRBSEG tables
       in ars repository for the changelists, which were associated with
    that specific transport order.
    DELETE FROM WBTRCL WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
    DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
    DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
    3. Use the transaction SMOBDELCL to remove details of this
       changelist from the CRM server. This transaction
       would require you to enter the id of the changelist.
       The id should be entered without 0x.
    4. Create a new change request in the CRM server and add these
    changelists to the change request.
    5. Steps 1-5 of Note 568624 can be followed for this but NOT steps
       6 and 7.DO NOT release the change request. There is no need to modify
       the TransportOrderId field in changelist table in ARS repository to
       reflect the new change request id.The field is there for
       documentation purpose only.
    6. Update the state of the changelist in ARS repository to 1 so that
       Transport Agent can pickup the changelist and send it to server as
       soon as it is started.
    Eg:
    UPDATE CHANGELIST SET STATE = 1 WHERE CHANGELISTID = <0XChangelistID>
    (GIVE WITH 0X)
    7. Start the Transport Agent on both Source repository.
    Also, you need to make sure that whenever you release a changelist from Mobile Application Studio then
    you should not chose this transport Order(which was not getting released earlier) while choosing the transport
    Order.

  • What happen if I change a role after I released the transport?

    Here is my Scenerio:
    1) Assuming I've created a role : ROLE1 in DEV
    2) I create a transport TR1 with that ROLE1, NOT yet released.
    3) Then I added ME21 txn to ROLE1.
    4) Then I released the transport TR1
    5) Then I remove ME21 txn from ROLE1.
    6) Then I transport role from DEV to QA.
    Q1) I would expect In QA, ROLE1 will still has ME21. - True?
    Q2) TR1 will be the snapshot of the ROLE1 when I release the transport TR1 - True?
    Now, I want to delete the ROLE1,
    A) I would need to create another Transport TR2 first with ROLE1 in DEV
    B) Then delete ROLE1 in DEV
    C) Then release Transport TR2
    D) Then I decided that I still need ROLE1. (oops)
    Q3 I should not transport TR2 so that it won't delete it in QA. - True?

    Hi Dominick,
    >
    > 1) Assuming I've created a role : ROLE1 in DEV
    >
    > 2) I create a transport TR1 with that ROLE1, NOT yet released.
    >
    > 3) Then I added ME21 txn to ROLE1.
    You should add the role again to the Transport to avoid inconsistency
    > 4) Then I released the transport TR1
    >
    > 5) Then I remove ME21 txn from ROLE1.
    >
    > 6) Then I transport role from DEV to QA.
    > -
    >
    > Q1) I would expect In QA, ROLE1 will still has ME21. - True?
    Answer: If you reassign the role to the TR then you will get.
    > Q2) TR1 will be the snapshot of the ROLE1 when I release the transport TR1 - True?
    Answer:  TRUE (but without ME21 if you don't add the change to the CR - see below for detail discussion)
    > -
    >
    >
    > Now, I want to delete the ROLE1,
    > 
    > A) I would need to create another Transport TR2 first with ROLE1 in DEV
    >
    > B) Then delete ROLE1 in DEV
    >
    > C) Then release Transport TR2
    >
    > D) Then I decided that I still need ROLE1. (oops)
    > -
    > Q3 I should not transport TR2 so that it won't delete it in QA. - True?
    Answer:  TRUE. And if you want the role again back to DEV without recreating it, please download the role from QAS or PROD and then Upload it to DEV. After that you need to generate the Profile of the role.
    > -
    FYI:   When a Change is Included into a request to send in other systems, then this request is called "Change Request" (CR). After Releasing, the CR called as "Transport request".
    CRs are basically (in layman language) the Pointers to the DB changes performed. These are included into a CR as "Task". A CR can contain multiple Tasks created by different users.
    Please note if this is a Workbench CR then it is ONLY editable by that particular user(owner of the Task). Also the Object captured in a Task of a WCR possesses a Lock till it gets released and thus can't be added to any other Task of a different CR. The Objects are unlocked when the Tasks and the CR is released respectively.
    There are no Object Lock for Customizing CRs ... like your TR1 which contains Creation / Deletion of roles.
    After the release of each Task, all Objects contained into every Task are transferred to the Change Request. After release of all Tasks, the CR owner can release the CR and thus the Transport Request has been initiated. Technically, at this time, a copy of Data from the Database of DEV captured under the headers of each Tasks are written to Data Files in Central Transport Directory.
    Now coming to your queries..... there are no such synchronization happens for a Task if the Objects are edited in different time frames before Release.  So, when you added ME21, again you need to assign this change to the same CR. (_Answer to your Q1_)
    Please let me know if you have any confusion / query.
    Regards,
    Dipanjan

  • Code inspector - Release of transport

    Hi,
    When we release the transport request, default variant of code inspector is executed.
    Is there any customization for this ? If yes, were do we do setting for this? I need to use own created variant instead of default.
    Regards,,,
    Sunil Joyous

    Hi,
    You can create your own default variant in transaction SCI.  If you create a local variant instead of a global one and call it DEFAULT it will be used instead of the standard one.
    Regards,
    Nick

  • Problems when releasing transpots

    Hi,
    I get the following error message when releasing transports in my SLOG file:
    FATAL No stdout redirectio <SID> 0000 20070810145629              TMSADM       <hostname>.
    this causes the export to fail.
    Does anyone know what the cause might be.
    thanks.

    Within TMS, tp via RFC redirects all standard output into file dev_tp.
    Please change the permissions of /usr/sap/PRD/DVEBMGS00/work/dev_tp
    file, at least it must have 666
    Also check that user <sid>adm has the correct authorization/ownerships.
    In addition, please download from SAP Service Marketplace, alias
    /patches  the latest versions of TP, R3trans, R/3 kernel patch and
    database library.

Maybe you are looking for