Process Chain Ended with Errors - cause unknown

I have had several instances of process chains stopping for no apparent reason.  The stops occur between 2 master data infopackage loads.  The last step is green and the next is grey.  The PSA table has been updated successfully for the last step.  All IDocs are in green status in both systems.  The monitor for the last successful step does say "Ended with Errors" although no errors are evident.  The process chain starts back up via Repeat at the next (grey) step and continues successfully.  There were no system problems or connection interruptions that occurred during the time the process chains failed.  There were no changes in the remote user profile.
This exact problem has occurred a half dozen times since our application of ECC Support Packs several months ago and had not occurred before.  The infopackages are different each time. Two different process chains have had this problem.  I have re-activated and re-scheduled the process chains without solving the problem.
Thanks for any ideas on why this may be occurring or what I can do to prevent it.
Patty Moffatt

Hi Des,
Here's my BW release info:
SAP_ABA        640       0019 SAPKA64019     Cross-Application
SAP_BASIS      640       0019 SAPKB64019     SAP Basis          
PI_BASIS       2005_1_6400009 SAPKIPYJ69     Basis Plug-In
ST-PI          2005_1_6400008 SAPKITLQH8     SAP Solution Tools Plug-
SAP_BW         350       0019 SAPKW35019   SAP_BW                      
ECC SPs 13-21 were applied before the BW problem started:
SAP_BASIS      640       0021 SAPKB64021    
SAP_ABA        640       0021 SAPKA64021    
PI_BASIS       2005_1_6400012 SAPKIPYJ6C   
ST-PI          2005_1_6400008 SAPKITLQH8    
SAP_BW         350       0021 SAPKW35021   
PI             2004_1_5000016 SAPKIPZI6G    
The process chain step and the monitor load both are green.  The Details tab shows all the processing is green, but the Process Chain itself is red with "Errors Occurred.  There have been no runtime dumps.
Patty

Similar Messages

  • Process chain failing with error 8 in BI 7.0

    Hi ,
    we have upgrade the dev to BI 7.0 and I am trying to execute the process chains but it is failing with a error 8 due to the step of the job BI_PROCESS is in the name of a old user. So i have changed in process chain -Attrbutes--Execution user --- current user.So the chain has started but it has so many chains inside the Meta chain it looks i need to go to each of them and change as cyurrent user.
    But is there some place where I can change globally to a Batch user/current user for these process chain in BI 7.0.If so pl let me know.

    Hi,
    user SM37 to identify all BI_PROCESS jobs and change the User of the step in the jobs (they all should only have one step).
    bye
    Frank

  • Process chain failed with Error-Status Change of Process ABAP ZL321NIMIMUUT

    Hi,
    process chain got failed with Error --**Status Change of Process ABAP ZL321NIMIMUUT
                                                                   Save Status and Trigger Events if Appropriate**

    Hi Neha,
    When we do the repeat after right click then we are getting this messege"--**Status Change of Process ABAP ZL321NIMIMUUT
    Save Status and Trigger Events if Appropriate**"
    I have come to know that there is one ABAP programe when we go to manage varient.
    ABAP Programme"ZBWR_ZMYYNNINOH_CSV_CHANGE"

  • PROCESS CHAIN ENDED RED

    process chain Ending with error showing
    Lock NOT set for: Deleting Data Completely from an InfoProvider
    please help how to correct and what it means
    regards

    Hi,
    In your process chain, you must be having a process for dropping cube contents. What happens is that, before you go to carry out any kind of updates(here updates means, adding records, changing records, deleting records) on a table, a lock would be set on the table so that no other user/ program can carry out any changes on this table.
    This lock is set by using function module starting with ENQUEUE. Till this lock is active, no other program can carry out changes on this table. Then to release the lock on this table another function module DEQUEUE is used. Only after this function is finished, the table is released for changes by any other user/ program.
    As you have got this error, it means that some other program was performing some tasks on this DSO/ infocube (loading data to/ from this DSO/ infocube) when your process chain reached the step to drop cube contents. Check if any other activity was being carried out for this cube/ DSO at that time. In order to avoid this from happening in future, change the timing of one of these processes.

  • Delete Indexes  Variant ended with errors in Process chain

    Hi experts,
    I have a process chain which executes dialy to load data Info Cube we create the index and finally  we delete the index after that we have few variants..
    Remaining all variants are executed with out errors except delete index variant I checked the error message it shows that <b>" The system has not finished loading request APO_R46PWZHRIA7JS9NOM8X879QEZJ into data target ZUP_CARF1"</b>
    It  is so happened weekly twice or trice not every day.  one day it was running with out any errors and one day this process chan was ended with errors.
    I need to know the  reason why this variant was executed with errors.?
    I need your valule sugestions regarding this issue.
    Regards
    sailekha

    hi sailekha,
    therevare some functional constraint of processes.
    while deleting indexes
    it is not possible to:
                                  loading
                                  indexes are being built
                                  stastics are being built
                                  during rollup
                                  while compressing
                                  while updating.
    my be u can check which is the other process chain that does all above oprations in concerned infoprovider.
    bye

  • The report l runs very night and gets ended with error

    Dear all,
    I am facing a problem in solution manger. There is an report (Program/Command  RDSMOPSOL_MONIREFRESH ) will runs very night and get ended with error and there is Run-time error "MESSAGE_TYPE_X".
    Please suggest how to solve the problem.
    Is this report is necessary   for the system because it is not mention in the sap stand jobs.
    SM37 log
    Job started
    Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
    Opening and closing session started. Session SM2000000000065
    Opening and closing the session was successful. Session: SM2000000000065
    Opening and closing session started. Session SM2000000000005
    ABAP/4 processor: MESSAGE_TYPE_X
    Job cancelled
    SM:CSA SESSION REFRESH
    No. Program/Command       Prog. type Spool list Parameter      User  Lang.
    1  RDSMOPSOL_MONIREFRESH ABAP                  &0000000000876 BASIS EN
    Sm21 log
    00:00:50 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
    00:30:57 BTC 08 200 BASIS             R68 Perform rollback
    00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
    00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
    00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
    00:30:57 BTC 08 200 BASIS             R68 Perform rollback
    00:30:57 BTC 08 200 BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
    Details
    Recording at local and central time........................ 12.11.2008 00:30:57
    Task................ 05312 . 08 B8 BTC background processor No. 08
    User................ BASIS
    Client.............. 200
    Terminal............
    Session............. 1
    Transaction code....
    Program name........
    Problem class....... T    Transaction Problem
    Development class... SABP
    Further details for this message type
    Module name......... abdynpro
    Line................ 1133
    Error text.......... ab_jmess
    Documentation for system log message AB 0 :
    The specified runtime error has occurred in the system.
    Parameter
      a.. MESSAGE_TYPE_X
    Technical details
    File................ 000048
    Position............ 0000253620
    Entry type.......... l      ( Error (Module, Row)            )
    Message ID.......... AB 0
    Variable parts...... ab_jmess                                            abdynpro1133
    Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
    00:30:57 BTC 08 200 BASIS             AB1 > Short dump "081112 003057 sapsm BASIS " generated
    etails
    ecording at local and central time........................ 12.11.2008 00:30:57
    ask................ 05312 . 08 B8 BTC background processor No. 08
    ser................ BASIS
    lient.............. 200
    erminal............
    ession............. 1
    ransaction code....
    rogram name........
    roblem class....... K    SAP Web AS Problem
    evelopment class... SABP
    BAP Mini dump
    ate................ 20081112
    ime................ 003057
    ost................ sapsm
    ser................ BASIS
    ocumentation for system log message AB 1 :
    A short dump was generated for the specified program termination.
    You can analyze this short dump in the system log evaluation by
    selecting this line or evaluating Table SNAP (Transaction ST22).
    echnical details
    ile................ 000048
    osition............ 0000253800
    ntry type.......... s      ( ABAP Runtime Error             )
    essage ID.......... AB 1
    ariable parts...... 081112003057sapsm   BASIS
    Time     Ty. Nr Cl. User         Tcod MNo Text                                                                    Date : 12.11.08
    00:30:57 BTC 08 200 BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081112003057sapsm BASIS 2001 )
    Details
    Recording at local and central time........................ 12.11.2008 00:30:57
    Task................ 05312 . 08 B8 BTC background processor No. 08
    User................ BASIS
    Client.............. 200
    Terminal............
    Session............. 1
    Transaction code....
    Program name........
    Problem class....... K    SAP Web AS Problem
    Development class... SDYN
    Module name.........
    Location............
    T100................ 00                  671
    Parameters..........
    Documentation for system log message D0 1 :
    The transaction has been terminated.  This may be caused by a
    termination message from the application (MESSAGE Axxx) or by an
    error detected by the SAP System due to which it makes no sense to
    proceed with the transaction.  The actual reason for the termination
    is indicated by the T100 message and the parameters.
    Additional documentation for message 00                  671
    ABAP/4 processor: &
    No documentation exists for message 00671
    Parameter
      a.. MESSAGE_TYPE_X
    00:30:57 BTC 08 200 BASIS             R68 Perform rollback
    Details
    Recording at local and central time........................ 12.11.2008 00:30:57
    Task................ 05312 . 08 B8 BTC background processor No. 08
    User................ BASIS
    Client.............. 200
    Terminal............
    Session............. 1
    Transaction code....
    Program name........
    Problem class....... W    Warning
    Development class... STSK
    Further details for this message type
    Module name......... thxxhead
    Line................ 1240
    Error text..........
    Caller.............. ThIRoll
    Reason/called....... roll ba
    Documentation for system log message R6 8 :
    An error has causes an SAP rollback.  All database updates are reset.
    Technical details
    File................ 000048
    Position............ 0000254520
    Entry type.......... m      ( Error (Function,Module,Row)    )
    Message ID.......... R6 8
    Variable parts......                                       ThIRollroll bathxxhead1240
    Regards,
    Shiva

    Hi karteek,
    I have check there is Switch of operation mode but when I have checked the t-code sm63 there is no new mode are in normal mode.
    There is  one thing I want to ask dose this report (Program/Command RDSMOPSOL_MONIREFRESH )  run   in your system or any one server because I have think there is some problem in job shued
    and is also not mention in the sap stand jobs.
    there is an error in sm21 in job.
    BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:
    BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was specified
    Is this SM37 log
    Job started
    Step 001 started (program RDSMOPSOL_MONIREFRESH, variant &0000000000875, user ID BASIS)
    Opening and closing session started. Session SM2000000000065
    Opening and closing the session was successful. Session: SM2000000000065
    Opening and closing session started. Session SM2000000000005
    ABAP/4 processor: MESSAGE_TYPE_X
    Job cancelled
    Sm21 log
    SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
    BASIS             R68 Perform rollback
    BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
    BASIS             AB1 > Short dump "081111 003056 sapsm BASIS " generated
    BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111003056sapsm BASIS 2001 )
    BASIS             R68 Perform rollback
    BASIS             R49 Communication error, CPIC return code 017, SAP return code 223
    BASIS             R64 > CPI-C function: CMINIT(SAP)
    *BASIS        SM36 EFK BP_CHECK_REPORT_VALUES: Invalid program values found. Reason:*
    *BASIS        SM36 EFC > Program RDSMOPSOL_MONIREFRESH has no variants, but a variant was*
    specified
    BASIS             R68 Perform rollback
    BASIS             AB0 Run-time error "MESSAGE_TYPE_X" occurred
    BASIS             AB1 > Short dump "081111 220948 sapsm BASIS " generated
    BASIS             D01 Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20081111220948sapsm BASIS 2001 )
    Details Page 2 Line 6 System Log: Local Analysis of sapsm                     1
    Time     Ty. Nr Cl. User         Tcod MNo Text
    00:00:51 DIA 00 000 SAPSYS            EEA OPERATION MODES: Switch to operation mode Normal triggered
    Details
    Recording at local and central time........................ 13.11.2008 00:00:51
    Task................ 04100 . 00 D0 Dialog work process No. 00
    User................ SAPSYS
    Client.............. 000
    Terminal............
    Session............. 1
    Transaction code....
    Program name........
    Problem class....... S    Operation Trace
    Development class... SBTC
    Sm63
      Start/end time   Name of the active operation mode
       00.00 - 01.00    Normal
       01.00 - 02.00    Normal
       02.00 - 03.00    Normal
       03.00 - 04.00    Normal
       04.00 - 05.00    Normal
       05.00 - 06.00    Normal
       06.00 - 07.00    Normal
       07.00 - 08.00    Normal
       08.00 - 09.00    Normal
       09.00 - 10.00    Normal
       10.00 - 11.00    Normal
       11.00 - 12.00    Normal
       12.00 - 13.00    Normal
       13.00 - 14.00    Normal
       14.00 - 15.00    Normal
       15.00 - 16.00    Normal
       16.00 - 17.00    Normal
       17.00 - 18.00    Normal
       18.00 - 19.00    Normal
       19.00 - 20.00    Normal
       20.00 - 21.00    Normal
       21.00 - 22.00    Normal
       22.00 - 23.00    Normal
       23.00 - 00.00    Normal
    Regards,

  • Program ended with error or warning, return code: F

    Friends, During client export i am facing below mention error, Pl suggest asap
    Client export from 06.04.2011 18:00:44
    System ID............................ PPT
    R/3 Release.......................... 700
       Basis Support Package...............SAPKB70018
    Host................................. pptest
    Start in background............. .....X
    User................................. SUPER
    Parameter
    Source client........................ 500
    Source client user masters............500
    Copier profile:.......................SAP_ALL
    Table selection
    Command file......................... PPTKT00008
    Customizing data .....................X
    With application data................ X
    Initialize and recreate......... X
    Change documents are not copied
    Transport control program tp ended with error code 0012
    Error exporting request PPTKT00008 23:40:31
    Program ended with error or warning, return code: F
    Runtime (seconds)         :         20,390
    End of processing: 23:40:33

    There could be three things possibly causing this error:
    1. There is some database issues, that is the connection to the database maybe is lost that's why TP ends.
    2. The TP return Code can also arise due to issues at the OS level, where SAP is installed.
    3. Due to permission issues also this can creep in. By permission issues I mean there are not enough permissions, please use trace ST01 and run the process again.
    Also please paste the Imort Log, as it can help in further analysis and with that please give your database and OS informations.

  • 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 0249

    Hello guys,
          I am facing an when importing transport.  After I click import to the transport in STMS, before it runs, a message window is displayed immediately. This was working find until last week, any kind of transport is followed by the same error.
    Transport control program tp ended with error code 0249
    Message no. XT200
    Diagnosis
    An error occurred when executing a tp command.
      Command: IMPORT BWDK903312 BIW client200 U0 pf=
    sapbiw1a\s
      Return code: 0249
      Error text: connect failed due to DbSL load lib failure
    Has anyone faced this error while trying to import a transport? I have not found the same error in sdn (0249)
    help will be appreciated.
    thanks
    DGF

    Your are right, but which is the Basis forum?
    Business Process Expert 
    Database & OS Platforms  ABAP Development 
    Enterprise SOA  Portal 
    Emerging Technologies 
    SAP Solutions 
    Business Intelligence 
    Scripting Languages 
    SAP Business One  Industries 
    Community Discussions 
    SAP NetWeaver  Application Server  Integration and Certification Center (ICC) 

  • Transport control program tp ended with error code 0016

    Hello colleagues,
    We are getting the following error when exporting system HRP to HRI:
    Transport program TP started successfully for HRPKX00005 21:25:45                                                                
    |   Transport control program tp ended with error code 0016                                                                           
    |   Error exporting request HRPKT00005 00:59:50                                                                               
    |   Program ended with error or warning, return code: F                                                                            
    |   Runtime (seconds)         :         13.876                                                                               
    |   End of processing: 00:59:50               
    Please could you kindly help us to solve the issue?
    Thanks in advance.
    Best regards
    Edited by: Víctor Barahona Cimas on Nov 12, 2009 3:33 PM

    ok thanks

  • 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.

  • Transport control program tp ended with error code 0212 | URGENT

    Hi All,
             We are trying to import requests in our PRD system. As soon as we select the request and try to import it , we get the error "Transport control program tp ended with error code 0212".
    This is tp version 305.12.42 (release 46D) for ANY database            
    /usr/sap/trans/cofiles/K915883.<SID> for transport: <SID>K915883: Permissio
    HALT 20070222114323                                                    
    ERROR: /usr/sap/trans/cofiles/K915883.<SID> : cant open                  
    : Permission denied                                                    
    ERROR: EXIT(16) -> process ID is: 6878                                 
    tp returncode summary:                                                 
    TOOLS: Highest return code of single steps was: 16                     
    ERRORS: Highest tp internal error was: 0212                            
    Output from tools called by tp:                                        
    This is R3trans version 6.05 (release 46D - 18.10.01 - 11:30:00).      
    R3trans finished (0000).                                                                               
    When i checked the transport tool and rfc destinations, everything was successful.
    When i tried to do tp connect -
    23> tp connect <SID> pf=/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL
    This is tp version 305.12.42 (release 46D) for ANY database
    E-/usr/sap/tran/bin/TP_DOMAIN_<SID>.PFL could not be opened.
    EXIT
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 0
    ERRORS: Highest tp internal error was: 0212
    tp finished with return code: 212
    meaning:
      could not access file as supposed (see SLOG for more details)
    We are having SAP 4.6C with DB -Oracle and OS HP-UX.
    Please let me know whow to rectifiy the issue. The situation here is getting worse.
    Regards,
    NK

    Hi Ruchit, Sorry for the delay. Here is the file you wanted -
    steic25q:root>ls
    DOMAIN.CFG          TPPARAM.bak         TP_DOMAIN_ID1.PFL   TP_DOMAIN_IQ1.PFL
    TMS_TEST.IS1        TPPRAMA0918         TP_DOMAIN_ID1.orig  nik.dev_evt
    TPPARAM             TP_DOMAIN_ID1.BAK   TP_DOMAIN_IP1.BAK
    steic25q:root>more TP_DOMAIN_ID1.PFL
    #TMS:0078:DOMAIN_ID1
    Caution !
    This file was generated by the Transport Management System.
    Do not change this file using a text editor.
    For more information, refer to the online documentation of the
    Transaction STMS.
    If this file was destroyed, it can be regenerated in the TMS.
    To do this, log on to the domain controller (system ID1) and call
    transaction STMS. In the System Overview, you can distribute the TMS
    configuration. This regenerates the file.
    STMS -> Overview -> Systems -> Extras -> Distribute TMS configugration
    TRANSDIR            = /usr/sap/trans
    DU1/CTC             = 1
    DU1/DUMMY           = 1
    DU1/NBUFFORM        = 1
    DU1/TP_VERSION      = 266
    DU2/CTC             = 1
    DU2/DUMMY           = 1
    DU2/NBUFFORM        = 1
    DU2/TP_VERSION      = 266
    ID1/CTC             = 0
    ID1/DBHOST          = steic24q
    ID1/DBLIBPATH       = /usr/sap/ID1/SYS/exe/run
    ID1/DBNAME          = ID1
    ID1/DBSWPATH        = /oracle/ID1/817_64
    ID1/DBTYPE          = ora
    ID1/NBUFFORM        = 1
    ID1/TP_VERSION      = 266
    IP1/CTC             = 0
    IP1/DBHOST          = steic25q
    IP1/DBLIBPATH       = /usr/sap/IP1/SYS/exe/run
    IP1/DBNAME          = IP1
    IP1/DBSWPATH        = /oracle/IP1/817_64
    IP1/DBTYPE          = ora
    IP1/NBUFFORM        = 1
    IP1/TP_VERSION      = 266
    IQ1/CTC             = 1
    IQ1/DBHOST          = cbnysap2
    IQ1/DBLIBPATH       = /usr/sap/IQ1/SYS/exe/run
    IQ1/DBNAME          = IQ1
    IQ1/DBSWPATH        = /oracle/IP1/817_64
    IQ1/DBTYPE          = ora
    IQ1/NBUFFORM        = 1
    IQ1/TP_VERSION      = 266
    TRN/CTC             = 1
    TRN/DUMMY           = 1
    TRN/NBUFFORM        = 1
    TRN/TP_VERSION      = 266
    steic25q:root>

  • Re: Transport control program tp ended with error code 0212

    Hi ,
              When transport request is added to import queue, getting following error :
    "Transport control program tp ended with error code 0212 "
    Please find the slog file description as follows:
       HALT 20110530001050
    ERROR: /usr/sap/trans/cofiles/K904416.<SID>: cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 2273
    HALT 20110530004629
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14341
    HALT 20110530004703
    ERROR: /usr/sap/trans/cofiles/K904416.<SID> : cant open
    : Permission denied
    ERROR: EXIT(16) -> process ID is: 14514
    How to correct this ?
    Thanks
    Srikanth

    Hi,
    It may happen happen due to permission issue when you are having SAN and sharing common trans directory now to check the permission of the file you have to login at os level and check the permission of the TR.
    cd /usr/sap/trans/cofiles/
    ls -l K904416<SID> - now here it will show the permission of the file please paste the output
    Thanks,
    Saleem

  • 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

  • Automatic imports throwing "tp ended with error code 0204"

    Hello frnds !
    In one of my non prod system, where automatic transport is enabled for 4 clients, we are getting tp error with 0204 error code in job jog of TMS_000000000*TMS_TP_IMPORT with report TMS_BCI_START_SERVICE.
    Can you plz suggest someting ..
    Release :
    SAP_BASIS : 700 : SAPKB70013 : SAP Basis Component
    Job log:
    Job log overview for job:    TMS_0000000005TMS_TP_IMPORT / 18003700
    Job started
    Step 001 started (program TMS_BCI_START_SERVICE, variant , user ID **)
    Transport control program tp ended with error code 0204
    Transport control program tp ended with error code 0204
    Job finished
    STMS errors :
    System   E40              Command  Start TMS_TP_IMPORT
    Client   000              Service  Transport Service
    User     HP               Start    Hintergrund
    Date     24.06.2009       Function TMS_TP_IMPORT
    Time     18:00:58         Message  TP_REPORTED_ERROR
    Transport control program tp ended with error c
    Errors: parameter is missing
    System   E40              Command  Start TMS_TP_IMPORT
    Client   000              Service  Transport Service
    User     HP               Start    Hintergrund
    Date     24.06.2009       Function TMS_TP_IMPORT
    Time     18:00:58         Message  TP_REPORTED_ERROR
    ************************************************************************************************************************Transport control program tp ended with error c
    Errors: parameter is missing
    This is tp version 372.04.40 (release 700)
    Warning: Parameter DBLIBPATH is no longer used.
    Warning: Parameter DBSWPATH is no longer used.
    /usr/sap/trans_P40/tmp/SLOG0926.E40.LOC is already in use (1), I'm waiting 2 sec (20090624180056). My name: pid 18030 on er3asu72
    (e40adm)
    HALT 20090624180058
    ERROR: Empty client(s) found in buffer E40. These entries cannot be filled implicitely.
    Either use one of the options 'CLIENT' or 'DEFAULTCLIENT' or#use the command 'FILLCLIENT' to fill these entries with a valid client.
    ERROR: EXIT(16) -> process ID is: 18030
    tp returncode summary:
    TOOLS: Highest return code of single steps was: 16
    ERRORS: Highest tp internal error was: 0204
    standard output from tp and from tools called by tp:
    ************************************************************************************************************************Thanks
    Ashish

    Hi Vikas,
    Could you please check the SLOG file and see what you observe
    /usr/sap/trans_P40/tmp/SLOG0926.E40.LOC is already in use (1), I'm waiting 2 sec (20090624180056).
    Please check the following Note 12746 - WARN <file> is already in use (), I'm waiting 5 sec.
    Mostly you have to perform the following step mentioned in Note
    "If there is only one tp process that writes the SLOG messages, stop this process and copy the generated file in tmp to the existing file in log on UNIX, for example, using cat /usr/sap/put/tmp/P<date>.<SID> >> /usr/sap/put/log/P<date>.<SID>Afterwards, you can delete the file in tmp and repeat the phase."
    Before trying above you can also stop all tp process and then start the transport job again.
    Thank You,
    Praveen

Maybe you are looking for