Message interface does not exist in any software components installed on th

Message interface does not exist in any software components installed on this business system.
hello,
When I check the interfaces on the business systems of 1 technical system, none of them have sender or receiver interfaces, hance I can't use them. The interfaces should ofcourse be on the Directory.
I have deleted the business systems and the technical system and created them again, but no result.
The product and software componets are in the technical sytem and business systems.
Any help would be usefull.
thanks,
Job

Hello!
If someone will search in the future for this error, here is the solution:
The error occurs if the GUID of the software component at the SLD is different to the one at the repository. Please compare the GUID at the SLD -> Administration -> Content Maintenance -> Dropdown "Component Version" -> Dropdown "Software Component Version". At the Integration Repository you select the Software Component Version at at the tab "Keys" you find the related GUID.
The error occured because the Software component has been created manually at the system. The repository content came from another system via import with own SLD (and because of that with another GUID for the software component).
Kind regards,
Klaus

Similar Messages

  • Message interface does not exist in any software components installed

    "Message interface does not exist in any software components installed on this business system"
    Essa é a mensagem de erro que estou tendo ao tentar configurar o XPath Receiver Determination do cenário SRVSC_WebAS_Outbound_ServiceStatusCheck.
    Já notei que a mensagem dá porque o meu BS da NFe não está com o SWCV SAP SLL-NFE 1.0. Mas isso só no ID porque no SLD ele aparece. Não sei mais o que fazer pra ele aparecer no ID. Já eliminei o BS, executei um refresh do cache do SLD, depois executei um refresh full e nada! Quando eu crio o BS novamente, ele vem sem o SWCV SAP SLL-NFE 1.0.
    Tive que configurar o XPath na mão para todas as SEFAZes!!!
    Já li vários threads a respeito desse erro e executei vários procedimentos sugeridos, mas nada.
    Alguém já possou por isso?!?

    para ser mais preciso, verifique no payload de envio e recebimento da mensagem de verificacao de status do servico se estao correspondentes ao que estao abaixo, essa mensagem é de verificacao do SEFAZ de SP (35) para o ambiente de homologacao
    (SENDER)
    <?xml version="1.0" encoding="utf-8"?><n0:nfeStatusServicoNF xmlns:n0="http://sap.com/xi/NFE/005a" xmlns:prx="urn:sap.com:proxy:PID:/1SAI/TASE95D30ADB76F1544C2D5:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe"><n0:cUF>35</n0:cUF><n0:tpEmis>1</n0:tpEmis><n0:tpAmb>2</n0:tpAmb><n0:nfeCabecMsg><n1:cabecMsg versao="1.02"><n1:versaoDados>1.07</n1:versaoDados></n1:cabecMsg></n0:nfeCabecMsg><n0:nfeDadosMsg><n1:consStatServ versao="1.07"><n1:tpAmb>2</n1:tpAmb><n1:cUF>35</n1:cUF><n1:xServ>STATUS</n1:xServ></n1:consStatServ></n0:nfeDadosMsg></n0:nfeStatusServicoNF>
    (RECEIVER)
    <?xml version="1.0" encoding="UTF-8"?>
    <nfeStatusServicoNFResponse xmlns="http://sap.com/xi/NFE/005a"><nfeStatusServicoNFResult><retConsStatServ xmlns="http://www.portalfiscal.inf.br/nfe" versao="1.07"><tpAmb>2</tpAmb><verAplic>SP_NFE_PL_005e</verAplic><cStat>107</cStat><xMotivo>Serviço em Operação</xMotivo><cUF>35</cUF><dhRecbto>2010-05-26T09:37:22</dhRecbto><tMed>1</tMed></retConsStatServ></nfeStatusServicoNFResult></nfeStatusServicoNFResponse>

  • Message interface does not exist in any software components

    Hi masters,
    I'm having problems with this message in my repository when I try to create an Interface determination with two interfaces mapping: "Message interface does not exist in any software components installed on this business system".
    note: I have read all the posts about this problem but nothing has solved it.
    I will describe more or less how is my SLD.
    First all, my Technical System is an Web AS ABAP (non a third party).
    I have created two receivers determination, with out problems, then, created the interface determination, with two Inbound interface, BUT, when I create a condition, the message appears, and the XPath doesn't shows the nodes for do the condition..
    I have checked the GUID, and that's good.
    NOTE: I have a second SWC but this is a third party... and when I test to do the same in this system, I have NO problems... so.. what is wrong with the Web As ABAP?
    Regards and thanks

    did you mean:
    SLD -> Technical System->Technical System Type: WebAsAbap-> Installed Products->Add New Product and add my Software Component???
    if is this, I have already done this, and still doesn't works.
    Thanks

  • Error - "Message Interface does not exist in any software components"

    HI
    This is an Idoc sender - SOAP receiver scenario.
    When I try to create the receiver determination, I get a warning message -
    " Message interface does not exist in any software components installed on this business system"
    I checked all the usual things & also reimported the IDoc metadata.
    Any suggestions are appreciated!
    Thanks
    Rachana

    Hi Rachana !!
    You should also check  if the given idoc type in mapping is the same that in the WE20.
    Also try to reactivate your integration directory objects by making any dummy changes.
    Check your receiver business system (I mean XI), that the logical systems are ok.
    Check this document (page 31):
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
    Regards,
    Matias.
    Message was edited by:
            Matias Denker
    Message was edited by:
            Matias Denker

  • Message interface not exist in any software components on business system

    Hi Experts,
    In development-environment we have an interface (SAP->XI->3rd party system) with a conditional receiver determination (based upon a fieldvalue in RFC that comes from SAP,  "CONTROL_RECEIPE_DOWNLOAD"). This functions properly in development.
    After transport to production environment this structure is not known when I try to use it in the Integration Directory when creating a conditional receiver determination. Double-click on the interface does result in the startup of the integration builder, but the interface itself can not be found. The following error-message appears:
    "Error message  Message interface does not exist in any software components installed on this business system"
    All design-objects have been put into production and in Integration Builder the structure is available. In IR it is not...
    In development In the business system of the sending SAP system, I can see the interface. In production, I don't see any interfaces at the business system....so this might be the problem but how can I add an interface manually to a business system?
    Can anybody please help?
    Thanks in advance
    William

    Hi William,
    One more thing. In Production, check the technical system of source. SWCV in which you have developed your interface, should be installed on the source system. If this SWCV is not in list of your installed products & SWCV then add it. Update the business sytem in ID again & it will work. I guess you have done a typo by saying that objects are not available in IR but in Integration builder its avaliable.
    Regards
    Sushil

  • Message Interface does not exist in IR u0096 but it does!

    Hi, well again i have a problem. I am still trying to get the XI-demo Checkflight…. to run but there are some obstacles on my way.
    I just wanted to check a MI given in the ID to check the attributes and picked it in the ID to get linked to the IR but a pop-up appears saying
    “Message Interface does not exists in Integration Repository”
    What’s the reason for this because obviously it is there, still existing.
    I tried to refresh the cache of all XI-components, did a server restart but nothing seems to be working.
    On the other hand I have some other questions:
    -     Why is it not possible to delete an object (business system) from the ID? I know because of the dependencies of the different channels but it should be possible because of re-generation of the communication-channels (this was also my approach for solving the problem mentioned above!)
    -     When do I have to refresh the cache in general? Is it indefinite whenever I want to or it seems to be the right time because something is not running the way it should and it seems a little odd

    Hi Carsten Heinrich,
    This will help you,
    1)     Cache Connectivity Test
    In RWB component monitoring, we now have the option of checking whether the cache-connectivity is functioning correctly. This is useful when we are experiencing problems when updating the runtime cache. The system displays a separate window in which we perform the test. If no previous tests have been performed, the system displays a corresponding message. Otherwise, the system shows when and by whom the last test run was started, together with the result of this test.
      To start a new test run, choose Start Test.
    The system displays the first results of the test run. Since the whole test takes some time, we can update the displayed results if necessary.
    To Update the displayed results, choose Refresh Display.
    The overall result for each component is displayed as a green, yellow, red, or gray symbol. A green symbol is only displayed if both update steps for the runtime cache were successful, that is, they both have a green symbol.
    2)     Cache notification status
    a)     Start the Integration Repository.
    b)     Select Environment ® Cache notification.
    c)   Have a look at the entries for the relevant user and date.
    d)   Have a look at the entries for the relevant cache instance, user and date.
                   3)    Cache update and resend the message
    a)Start transaction SXI_CACHE.
    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    c)     Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.        
             4)     Deleting the SLD Cache
      Many actions require  to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment  ®  Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

  • ESRfor PI 7.1) source message idoc does not exist in software componet

    Hi ,
    When using the sap predelivered integration content in the repository the above error (ESR ( for PI 7.1)  error : source message idoc does not exist in software component version id) is coming while opening the message mapping interface. Is it due to some content missing or a sp level mismatch ?
    Thanks
    Sri

    Hi,
    I'd say you need to import some other SWCV which has all the IDOC typos you use in your scenario
    probably this is a prerequisite for importing your SWCV
    I don't think this is related to sp level or anything like that
    it's just that SWCV is missing
    Regards,
    Michal Krawczyk

  • Error Message : Object does not exist (status management)

    Hi Gurus,
    I am working on tcode IW52(Change Notifications). and using badi's for validations at different points.
    1. Order level,
    2. Notification,
    3. Task level validations.
    In the task level validations, I have an requirement that if certain condition is met, than user should not be able to delete the task. I have no problem doing that, I am able to restrict it.
    Now the issue is :
    Say you have 6 tasks, and condition is met for the 5th task and I try to delete it. then the error message "can not delete task" is getting triggered from the badi.
    and after this error message if you try to do any functionality on the 6th task, I am experiencing error message "Object does not exist (status management)".
    Is anyone aware of this error message, any suggestions are highly appreciated.
    Thanks in advance.
    Shrikant
    Edited by: Alvaro Tejada Galindo on Mar 17, 2008 1:56 PM

    Hi ,
    You have posted this question long back that is one and half year back nearly.
    You got an error message in IW52 stating Object does not exist ( status management ).
    Now iam also facing the same problem in iw22 transaction. Can you say me how you solved if you remember.

  • OSA error 'SOCAT does not exist in any attached database'

    I'm connect Oracle Sales Analyzer(OSA11i) and then get the following error message which prevents us from opening the database in OSA.
    "Error opening in database, the following error occurred in Express. SOCAT does not exist in any attached database"
    Could you please help me to solve my problem?
    Thanks& Regards.

    SOCAT (or Source catalog) controls the behavior of application and is a two-dimensional variable in the SERVER database. Find the name and location of your "SERVER" database and then try to find out why it is not being attached by your osa session.
    An example of OSA database naming convention is:
    SATURN.db - Catalog Database
    MSATURN.db - Master or Public database
    DSATURN.db - Server Database
    PSATURN.db - Personal Database

  • The contained field name "ADTAGR" does not exist in any of the database tab

    hı all
    how can l  solved thıs problem
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
    not caught in
    procedure "PUT_QMFECAT" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    An Open SQL clause was specified dynamically. The contained field name
    "ADTAGR" does not exist in any of the database tables from the FROM clause.
    Information on where terminated
        Termination occurred in the ABAP program "SAPDBZQNQ" - in "PUT_QMFECAT".
        The main program was "ZQMR_BILDIRIM ".
        In the source code you have the termination point in line 732
        of the (Include) program "SAPDBZQNQ".
    Error occurred during batch input processing
        The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
         occurred in
        procedure "PUT_QMFECAT" "(FORM)", but it was neither handled locally nor
         declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPDBZQNQ "; its source code begins in line
        715 of the (Include program "SAPDBZQNQ ".
    FORM put_qmfecat.
      DATA: l_tab_fields  TYPE  rsfs_tab_fields.
      DATA: l_ds_clauses  TYPE  rsds_where.
    Dynamische Feldselektion
      MOVE 'QMFECAT_C' TO l_tab_fields-tablename.
      READ TABLE select_fields WITH KEY l_tab_fields-tablename
                                    INTO l_tab_fields.
      IF sy-subrc <> c_rc00.
        CLEAR l_tab_fields.
      ENDIF.
    Dynamische Selektionskriterien
      MOVE 'QMFECAT' TO l_ds_clauses-tablename.
      READ TABLE dyn_sel-clauses WITH KEY l_ds_clauses-tablename
                                 INTO l_ds_clauses.
    DB-Zugriff
      >>>>> SELECT (l_tab_fields-fields) FROM qmfe
      INTO CORRESPONDING FIELDS OF TABLE qmfecat_tab
       WHERE qmnum  =  rqmqmel-qmnum
       AND kzloesch =  space
       AND (l_ds_clauses-where_tab)
       ORDER BY PRIMARY KEY.
    regard sinan
    Edited by: eyup_sinan on Jan 6, 2012 3:21 PM
    Edited by: eyup_sinan on Jan 6, 2012 3:30 PM

    You seem to have made a copy of the standard program. You'll have to make sure that you are handling this field correctly in your code.
    Rob

  • Sales Order Error Message 'Product does not exist in system'

    Hi Gurus,
    we recently upgraded from CRM 4 to 7.0. There is a ECC attached (which was also upgraded from 4.7 to 6.0 before).
    Scenario: materials are replicatd from ECC to CRM. All mandatory customizing objects were initially loaded succesfully.
    Because of the upgrade we already have "old" products in CRM. We requested a single product from ECC, the bdoc went through with green. The product can be found via commpr01 and also on database in comm_product. But when try to add the product to an sales order e.g. quotation, it gives the error message "product does not exist in the system.
    We then tried to delete that product using the report com_product_delete_single. When entered the selection criteria for that report, we used the f4-valuehelp to enter the product. We found the product and then executed the report. But gives the message 'product not found'.
    We also created a product for testing purposes directly in crm, but it shows the same behaviour in sales orders and for the deletion report.
    Please help me with that issue. Your help will be highly appreciated!!!
    Kind regards
    Hannes

    Solved with the help of SAP.
    Keywords: COM_PRODUCT
    COM_PRODUCT_GUID_GET_INTERNAL
    CONVERSION_EXIT_PRID1_INPUT
    CRM_ORDERADM_I 501
    Relevant notes:
    Note 1449146 - Dump While Creation IP via WebUI
    Note 1445079 - Unable to add products to contract
    The notes do not exactly described our issue but the code corrections were still relevent for us.

  • Error message "resource does not exist"

    C6; have unistalled and reinstalled ovi store three times; now I get into the store, but when attempting to download app, get error message "resource does not exist". what is that???

    hey guys just updating you all.. i wrote previously how my ovi store wasn't working, it gave me an error message 'resource does not exist'. i did soft/hard reset, also uninstalled ovi store and reinstalled STILL it wasn't working. It lasted a day. And today it's working fine. i think it was a problem with their server. It sorted it self out
    But guys i did contact the team, and i got a reply that said i should do the following if it still doesn't work:
    1. GO TO MENU
    2. GO TO INTERNET
    3. CLICK ON WEB
    4.GO TO OPTIONS
    5. GO TO CLEAR PRIVACY DATA
    6. DELETE CATCHE AND COOKIES
    That should apperantly work.
    If not guys, then i wouldn't worry. Just like mines, yours should sort it self out

  • Unable to login: SAP System Message: Dynpro does not exist

    Hello All,
    I'm created a test system to practice our upgrade post steps on.  I created a pared down copy of one of our other systems.  When I try to login, I get a popup message saying: Dynpro does not exist.
    To create the pared down version, we used empty files for:
    COEP  
    GLPCA 
    BALDAT
    MSEG  
    BSIS  
    LIPS  
    LTAP  
    CE1LPOC
    ZHYPFIT
    BALHDR
    VBFA  
    COSP  
    COSB  
    CDCLS 
    ZHYPF2A
    /IRM0760
    CDHDR     
    COSS      
    CMFP      
    CHVW      
    RESB      
    ZHYPFIO   
    AUSP      
    VBOX      
    JCDS      
    VBAP      
    We don't think these being empty is the problem, but I wanted to mention it just incase it is. 
    Below is the dev_w0 log.  I've been searching Google / SDN / OSS for some of the errors but haven't come up with anything yet.
    Any insight you might have into this would be appreciated.  Thank you.
    ~TJ
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      79
    M sid        Q60
    M systemid   324 (IBM iSeries with OS400)
    M relno      7000
    M patchlevel 0
    M patchno    172
    M intno      20050900
    M make:      single threaded, Unicode, 64 bit, optimized
    M pid        6396
    M
    M 
    M Thu Jan 22 15:12:50 2009
    M  kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
    M  length of sys_adm_ext is 576 bytes
    M  ***LOG Q01=> ThInit, WPStart (Workproc 0 1 6396) [thxxhead.c   1290]
    M  ThInit: running on host USALSAPU
    M  calling db_connect ...
    C  DB4 SQL Reparse Activated
    C 
    C Thu Jan 22 15:12:51 2009
    C  R3INLPGM: RmtExeLib from /usr/sap/Q60/SYS/exe/run/DBSLDB4RMT
    C  R3INLPGM: RmtExeLib is KRNQ60700
    C  DBSLENCWT: rc=0, msg=CPF9897 CONCURRENT WRITE IS ENABLED.                                   
    C  DbSl/DB codepage check: table or row not found (db_rc=24) - OK.
    C  === Central DB connect successfull! ===
    C  === Connection settings ===
    C  connected               = TRUE
    C  con_hdl                 = 0
    C  db_handle               = 1
    C  dbhost                  = USALSAPU
    C  rdbname                 =                  
    C  dblib                   = R3Q60DATA
    C  r3sysle_changed         = TRUE
    C  query_compl_reval       = O
    C  dbconnecttype           = L
    C  user                    = Q6079    
    C  qaqqinilib              = Default (QUSRSYS)
    C  dbjobname               = WP00     
    C  dbjobuser               = Q6079    
    C  dbjobno                 = 197762
    C  rmtexelib               = KRNQ60700
    C  parallel_alter_tables   = *OFF
    C  ===========================
    C  Found only default query options in QUSRSYS/QAQQINI.
    C  -
    C  -
    DbSl EGO Structure
    C  -
    C     SAPSYSTEMNAME               = Q60
    C     Character encoding          = UNICODE
    C     process class               = dialog process
    C     workprocess id              = 0
    C     local host                  = USALSAPU
    C     dbhost                      = USALSAPU
    C     rdbname                     =                  
    C     dbname                      = Q60USALSAPU
    C     dblib                       = R3Q60DATA
    C     application server          = DVEBMGS79
    C     Connect type                = LOCAL
    C     pid                         = 6396
    C     wpjobname                   = WP00
    C     wpjobuser                   = Q6079
    C     wpjobno                     = 197762
    C     DB2/400 vers. appl. server  = PASE 1
    C     DB2/400 vers. DB server     = V6R1
    C     da_cache_size               = 100
    C     reopen                      = ON
    C     timeout_retry               = 3
    C     ODP threshold               = 800
    C     ODP commit thresh.          = 810
    C     ODP open thresh.            = 850
    C     QAQQINI library             = Default (QUSRSYS)
    C     Alternate QAQQINI library   = Not specified
    C     use_lobs_for_long           = ON
    C     use_lobs_for_short          = OFF
    C     single_execution_threshold  = 2000
    C     single_execution_reuse      = OFF
    C     keep_tmp_SQLpkgs            = OFF
    C     dbsl_trace                  = OFF
    C     allow_cancel                = Try (Unspecified)
    C     nqe_optimize_method         = O - All I/O (compatibility mode)
    C     nte_list_size               = 10
    C     dbsl_alternate_package      = OFF
    C  -
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20090122 151250 USALSAPU       
    M  db_connect o.k.
    M  ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 0x7000002d0000000, size: 120000000)
    M  SHM_ROLL_AREA          (addr: 0x7000002e0000000, size: 268435456)
    M  SHM_PAGING_AREA          (addr: 0x7000002f0000000, size: 335544320)
    M  SHM_ROLL_ADM               (addr: 0x700000310000000, size: 2672386)
    M  SHM_PAGING_ADM          (addr: 0x700000320000000, size: 820256)
    M  ThCreateNoBuffer          allocated 544152 bytes for 1000 entries at 0x700000330000000
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 12176 bytes (50 server) at 0x700000340000000
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation std
    X  <ES> Info: use normal pages (no huge table support available)
    X  ES initialized.
    B  dbntab: NTAB buffers created
    B  dbntab: Buffer FTAB(hash header)  (addr: 0x700000360000088, size: 584)
    B  dbntab: Buffer FTAB(anchor array) (addr: 0x7000003600002d0, size: 1280008)
    B  dbntab: Buffer FTAB(item array)   (addr: 0x700000360138ad8, size: 5120000)
    B  dbntab: Buffer FTAB(data area)    (addr: 0x70000036061aad8, size: 122880000)
    B  dbntab: Buffer IREC(hash header)  (addr: 0x700000370000088, size: 584)
    B  dbntab: Buffer IREC(anchor array) (addr: 0x7000003700002d0, size: 1280008)
    B  dbntab: Buffer IREC(item array)   (addr: 0x700000370138ad8, size: 1280000)
    B  dbntab: Buffer IREC(data area)    (addr: 0x7000003702712d8, size: 15360000)
    B  dbntab: Buffer STAB(hash header)  (addr: 0x700000380000088, size: 584)
    B  dbntab: Buffer STAB(anchor array) (addr: 0x7000003800002d0, size: 1280008)
    B  dbntab: Buffer STAB(item array)   (addr: 0x700000380138ad8, size: 1280000)
    B  dbntab: Buffer STAB(data area)    (addr: 0x7000003802712d8, size: 3072000)
    B  dbntab: Buffer TTAB(hash header)  (addr: 0x700000390000088, size: 2976)
    B  dbntab: Buffer TTAB(anchor array) (addr: 0x700000390000c28, size: 1280008)
    B  dbntab: Buffer TTAB(item array)   (addr: 0x700000390139430, size: 3200000)
    B  dbntab: Buffer TTAB(data area)    (addr: 0x700000390446830, size: 23360000)
    B 
    B Thu Jan 22 15:12:52 2009
    B  dbstat: table statistics switched on for 84171 tables
    B  dbstat: TABSTAT buffer created (addr: 0x7000003a0000000, size: 41152488)
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 23, CON_ID = -1
    B  dbtbxbuf: Buffer TABL  (addr: 0x7000003b0000100, size: 350000000, end: 0x7000003c4dc9480)
    B  dbtbxbuf: Profile: max_objects = 40000, displace = 1, reorg = 1
    B  dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5
    B  dbtbxbuf: protect_shm = 0, force_checks = 0
    B  dbtbxbuf: tsize_retry = 104857600
    B  ***LOG BB0=> buffer TABL       started with length 350000000  bytes [dbtbxbuf#3 @ 16202] [dbtbxbuf1620 2]
    B  dbtbxbuf: Buffer TABLP (addr: 0x7000003d0000100, size: 35840000, end: 0x7000003d222e100)
    B  dbtbxbuf: Profile: max_objects = 2000, displace = 1, reorg = 1
    B  dbtbxbuf: request_unit = 2000, sync_reload = 5, inval_reload = 5
    B  dbtbxbuf: protect_shm = 0, force_checks = 0
    B  dbtbxbuf: tsize_retry = 17590656
    B  ***LOG BB0=> buffer TABLP      started with length 35840000   bytes [dbtbxbuf#3 @ 16202] [dbtbxbuf1620 2]
    B  dbtbxbuf: Reading TBX statistics:
    B  dbtbxbuf: 29 object entries precreated
    B  Layout of EIBUF buffer shared memory:
    B  0: 1 * 4 = 4
    B  1: 1 * 416 = 416
    B  2: 23 * 40 = 920
    B  3: 80021 * 48 = 3841008
    B  4: 40000 * 256 = 10240000
    B  5: 80021 * 8 = 640168
    B  6: 1 * 200 = 200
    B  7: 513 * 8 = 4104
    B  8: 262473 * 256 = 67193088
    B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
    B  dbexpbuf: Buffer EIBUF (addr: 0x7000003f0000108, size: 81920000, end: 0x7000003f4e20108)
    B  ***LOG BB0=> buffer EIBUF      started with length 80000k     bytes [dbexpbuf#2 @ 2342] [dbexpbuf2342 ]
    B  Layout of ESM   buffer shared memory:
    B  0: 1 * 4 = 4
    B  1: 1 * 416 = 416
    B  2: 23 * 40 = 920
    B  3: 4001 * 48 = 192048
    B  4: 2000 * 256 = 512000
    B  5: 4001 * 8 = 32008
    B  6: 1 * 200 = 200
    B  7: 65 * 8 = 520
    B  8: 13500 * 256 = 3456000
    B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
    B  dbexpbuf: Buffer ESM   (addr: 0x700000400000108, size: 4194304, end: 0x700000400400108)
    B  ***LOG BB0=> buffer ESM        started with length 4096k      bytes [dbexpbuf#2 @ 2342] [dbexpbuf2342 ]
    B  Layout of CUA   buffer shared memory:
    B  0: 1 * 4 = 4
    B  1: 1 * 416 = 416
    B  2: 23 * 40 = 920
    B  3: 40009 * 48 = 1920432
    B  4: 20000 * 256 = 5120000
    B  5: 40009 * 8 = 320072
    B  6: 1 * 200 = 200
    B  7: 193 * 8 = 1544
    B  8: 65617 * 512 = 33595904
    B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
    B  dbexpbuf: Buffer CUA   (addr: 0x700000410000108, size: 40960000, end: 0x700000412710108)
    B  ***LOG BB0=> buffer CUA        started with length 40000k     bytes [dbexpbuf#2 @ 2342] [dbexpbuf2342 ]
    B  Layout of OTR   buffer shared memory:
    B  0: 1 * 4 = 4
    B  1: 1 * 416 = 416
    B  2: 23 * 40 = 920
    B  3: 4001 * 48 = 192048
    B  4: 2000 * 256 = 512000
    B  5: 4001 * 8 = 32008
    B  6: 1 * 200 = 200
    B  7: 81 * 8 = 648
    B  8: 13500 * 256 = 3456000
    B  Tracing = 0, Shm Protection = 0, Force checks = 0, Recovery delay = 500000
    B  dbexpbuf: Buffer OTR   (addr: 0x700000420000108, size: 4194304, end: 0x700000420400108)
    B  ***LOG BB0=> buffer OTR        started with length 4096k      bytes [dbexpbuf#2 @ 2342] [dbexpbuf2342 ]
    B  ***LOG BB0=> buffer CALE       started with length 500000     bytes [dbcalbuf#10 @ 2305] [dbcalbuf2305 ]
    B  dbtran INFO (init_connection '<DEFAULT>' [DB400:700.08]):
    B   max_blocking_factor =  20,  max_in_blocking_factor      =  40,
    B   min_blocking_factor =  10,  min_in_blocking_factor      =  10,
    B   prefer_union_all    =   0,  prefer_join                 =   0,
    B   prefer_fix_blocking =   1,  prefer_in_itab_opt          =   1,
    B   convert AVG         =   1,  alias table FUPD            =   1,
    B   escape_as_literal   =   0,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x00,  character encoding          = STD / <none>:-,
    B   use_hints           = abap->1, dbif->0x3, upto->2147483647, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0
    M 
    M Thu Jan 22 15:12:53 2009
    M  SecAudit(RsauInit): Start init of Security Audit Log for first wp.
    M  SecAudit(RsauCreateShm): New block for Security Audit Log allocated in SCSA
    M  SecAudit(RsauCreateShm): SCSA memory usage: SecAudit = 1152, total = 3048
    M  SecAudit(RsauShmInit): SCSA size................ = 4096
    M  SecAudit(RsauShmInit): addr of SCSA............. = 0x700000040000000
    M  SecAudit(RsauShmInit): addr of RSAUSHM.......... = 0x700000040000768
    M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO..... = 0x7000000400007a0
    M  SecAudit(RsauShmInit): addr of RSAUSLOTS........ = 0x7000000400007ac
    M  SecAudit(RsauShmInit): SHM version.............. = 5
    M  SecAudit(RsauShmInit): SHM Slot version......... = 2
    M  SecAudit(RsauShmInit): RSAU active.............. = 0
    M  SecAudit(RsauShmInit): number of slots possible. = 10
    M  SecAudit(RsauShmInit): number of slots requested = 2
    M  SecAudit(RsauShmInit): number of slots used..... = 2
    M  SecAudit(RsauShmInit): user selection........... = 0
    M  SecAudit(RsauShmInit): max size of one file..... = 0 KB
    M  SecAudit(RsauShmInit): max size of all files.... = 102400 KB
    M  SecAudit(RsauGetCurrentProfile): Init of shared memory completed
    M  SecAudit(RsauGetCurrentProfile): Security Audit Log not active
    M  SsfSapSecin: automatic application server initialization for SAPSECULIB
    N  SsfSapSecin: Looking for PSE in database
    N  SsfPseLoad: started...(path=/usr/sap/Q60/DVEBMGS79/sec, AS=USALSAPU, instanceid=79)
    N  SsfPseLoad: Downloading file /usr/sap/Q60/DVEBMGS79/sec/SAPSYS.pse (client:    , key: SYSPSE, len: 1872)
    N  SsfPseLoad: ended (1 of 1 sucessfully loaded, 1 checked...
    N  MskiCreateLogonTicketCache: Logon Ticket cache created in shared memory.
    N  MskiCreateLogonTicketCache: Logon Ticket cache pointer registered in shared memory.
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  CCMS: AlMsUpload called by wp 0.
    M  CCMS: AlMsUpload successful for /usr/sap/Q60/DVEBMGS79/log/ALMTTREE (0 MTEs).
    M  CCMS: start to initalize 3.X shared alert area (first segment).
    S 
    S Thu Jan 22 15:12:54 2009
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 0x18499b440
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  2 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 400
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 0x700000460000070
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 0x700000460000740
    S    using messages for server info
    S  size of spec char cache entry: 297032 bytes (timeout 100 sec)
    S  size of open spool request entry: 2272 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A 
    A  -PXA--
    A  PXA INITIALIZATION
    A 
    A Thu Jan 22 15:12:55 2009
    A  PXA: Locked PXA-Semaphore.
    A  System page size: 4kb, total admin_size: 139532kb, dir_size: 34808kb.
    A  Attached to PXA (address 0x700000470000000, size 1998848K, 4 fragments of 464832K )
    A  abap/pxa = shared unprotect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A 
    A  ABAP ShmAdm attached (addr=0x7000000b0577000 leng=20955136 end=0x7000000b1973000)
    A  >> Shm MMADM area (addr=0x7000000b0a50fa8 leng=244096 end=0x7000000b0a8c928)
    A  >> Shm MMDAT area (addr=0x7000000b0a8d000 leng=15622144 end=0x7000000b1973000)
    A  RFC Destination> destination USALSAPU_Q60_79 host USALSAPU system Q60 systnr 79 (USALSAPU_Q60_79)
    A  RFC Options> H=USALSAPU,S=79,d=2,
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 2
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects          allocated 47822 bytes at 0x7000004f0000000
    N 
    N Thu Jan 22 15:12:56 2009
    N  SsfSapSecin: PSE /usr/sap/Q60/DVEBMGS79/sec/SAPSYS.pse found!
    N 
    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is /usr/sap/Q60/SYS/exe/run/libsapsecu.o .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...completed with return code 5.
    N  =================================================
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    M  JrfcVmcRegisterNativesDriver o.k.
    W  =================================================
    W  === ipl_Init() called
    W    ITS Plugin: Path dw_gui
    W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
    W    ITS Plugin: sizeof(SAP_UC) 2
    W    ITS Plugin: Release: 700, [7000.0.172.20050900]
    W    ITS Plugin: Int.version, [33]
    W    ITS Plugin: Feature set: [17]
    W    ===... Calling itsp_Init in external dll ===>
    W  === ipl_Init() returns 0, ITSPE_OK: OK
    W  =================================================
    N  VSI: WP init in ABAP VM completed with rc=0
    E 
    E Thu Jan 22 15:12:58 2009
    E  Replication is disabled
    E  EnqCcInitialize: local lock table initialization o.k.
    E  EnqId_SuppressIpc: local EnqId initialization o.k.
    E  EnqCcInitialize: local enqueue client init o.k.
    M 
    M Thu Jan 22 15:13:03 2009
    M  SosICreateNewAnchorArray: sos_search_anchor_semantics = 1
    A 
    A Thu Jan 22 15:13:07 2009
    A  *** ERROR => RFC ======> cannot open SAPGUI
    [abrfcio.c    8185]
    A  RFC 1729  CONVID 62379446
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 exec_sapgui cannot open SAPGUI
    A  RFC> ABAP Programm: SAPLSLDAG (Transaction: )
    A  RFC> User: DDIC (Client: 000)
    A  RFC> Destination: SERVER_EXEC (handle: 2, , )
    A  RFC SERVER> RFC Server Session (handle: 1, 62377117, {4978D392-D34E-190F-E100-80020A001114})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code:  (Caller Program: SLDAPPL_SERV)
    A  RFC SERVER> Called function module: SLDAG_GET_COMPILED_BITS
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1738
    FUNCTION: 'exec_sapgui'
    cannot open SAPGUI
    PROG =rfcexec USALSAPU sapgw79 62379446 IDX=2
    [abrfcio.c    8185]
    A  *** ERROR => RFC ======> FUNCTION: 'exec_sapgui'
    cannot open SAPGUI
    [abrfcio.c    8185]
    A  RFC 1729  CONVID 62382527
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 exec_sapgui FUNCTION: 'exec_sapgui'
    A  cannot open SAPGUI
    A  RFC> ABAP Programm: SAPLSLDAG (Transaction: )
    A  RFC> User: DDIC (Client: 000)
    A  RFC> Destination: SERVER_EXEC (handle: 2, , )
    A  RFC SERVER> RFC Server Session (handle: 1, 62381506, {4978D397-D34E-190F-E100-80020A001114})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code:  (Caller Program: SLDAPPL_SERV)
    A  RFC SERVER> Called function module: SLDAG_GET_COMPILED_BITS
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1738
    FUNCTION: 'exec_sapgui'
    FUNCTION: 'exec_sapgui'
    cannot open SAPGUI
    PROG =rfcexec USALSAPU sapgw79 62382527 IDX=3
    [abrfcio.c    8185]
    A 
    A Thu Jan 22 15:13:14 2009
    A  *** ERROR => RFC ======> FUNCTION: 'exec_sapgui'
    FUNCTION: 'exec_sapgui'
    cannot open SAPGUI
    [abrfcio.c    8185]
    A  RFC 1729  CONVID 62392457
    A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 exec_sapgui FUNCTION: 'exec_sapgui'
    A  FUNCTION: 'exec_sapgui'
    A  cannot open SAPGUI
    A  RFC> ABAP Programm: SAPLSLDAG (Transaction: )
    A  RFC> User: DDIC (Client: 000)
    A  RFC> Destination: SERVER_EXEC (handle: 3, , )
    A  RFC SERVER> RFC Server Session (handle: 1, 62381506, {4978D397-D34E-190F-E100-80020A001114})
    A  RFC SERVER> Caller host:
    A  RFC SERVER> Caller transaction code:  (Caller Program: SLDAPPL_SERV)
    A  RFC SERVER> Called function module: SLDAG_GET_COMPILED_BITS
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1738
    FUNCTION: 'exec_sapgui'
    FUNCTION: 'exec_sapgui'
    FUNCTION: 'exec_sapgui'
    cannot open SAPGUI
    PROG =rfcexec USALSAPU sapgw79 62392457 IDX=6
    [abrfcio.c    8185]
    B 
    B Thu Jan 22 15:13:16 2009
    B  table logging switched on for client '010'
    M 
    M Thu Jan 22 15:13:22 2009
    M  AS400_API connected to 'USALSAPU'. DBJob: (197789/QUSER     /QXDARECVR )M  *** ERROR => AS400_API (APICODE 23) failed with SY-SUBRC = 9 [abas4api.c   1548]
    M  *** ERROR => Cannot open file '/usr/sap/transD60/config/infoapar.610' [             0]
    A  A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Thu Jan 22 15:13:22 2009
    A 
    A  ABAP Program SAPMSYST                                .
    A  Source SAPMSYST                                 Line 1770.
    A  Error Code DYNPRO_NOT_FOUND.
    A  Module  $Id: //bas/700_REL/src/krn/dynp/dybas.c#6 $ SAP.
    A  Function dyrdyp.c Line 545.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_GOTO_RABAX
    A  Dynpro does not exist.
    A 
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
    A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
    A  ** RABAX: level LEV_RX_ROLLBACK entered.
    A  ** RABAX: level LEV_RX_ROLLBACK completed.
    A  ** RABAX: level LEV_RX_DB_ALIVE entered.
    A  ** RABAX: level LEV_RX_DB_ALIVE completed.
    A  ** RABAX: level LEV_RX_HOOKS entered.
    A  ** RABAX: level LEV_RX_HOOKS completed.
    A  ** RABAX: level LEV_RX_STANDARD entered.
    A  ** RABAX: level LEV_RX_STANDARD completed.
    A  ** RABAX: level LEV_RX_STOR_VALUES entered.
    A  ** RABAX: level LEV_RX_STOR_VALUES completed.
    A  ** RABAX: level LEV_RX_C_STACK entered.
    A 
    A Thu Jan 22 15:13:23 2009
    A  ** RABAX: level LEV_RX_C_STACK completed.
    A  ** RABAX: level LEV_RX_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
    A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
    A  ** RABAX: level LEV_RX_INTERFACES entered.
    A  ** RABAX: level LEV_RX_INTERFACES completed.
    A  ** RABAX: level LEV_RX_GET_MESS entered.
    A  ** RABAX: level LEV_RX_GET_MESS completed.
    A  ** RABAX: level LEV_RX_INIT_SNAP entered.
    A  ** RABAX: level LEV_RX_INIT_SNAP completed.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
    A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
    A  ** RABAX: level LEV_RX_WRITE_SNAP entered.
    A  ** RABAX: level LEV_SN_END completed.
    A  ** RABAX: level LEV_RX_SET_ALERT entered.
    A  ** RABAX: level LEV_RX_SET_ALERT completed.
    A  ** RABAX: level LEV_RX_COMMIT entered.
    A  ** RABAX: level LEV_RX_COMMIT completed.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
    A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
    A  ** RABAX: level LEV_RX_RESET_PROGS entered.
    A  ** RABAX: level LEV_RX_RESET_PROGS completed.
    A  ** RABAX: level LEV_RX_STDERR entered.
    A  Thu Jan 22 15:13:23 2009
    A 
    A  ABAP Program SAPMS380                                .
    A  Source                                          Line 0.
    A  Error Code DYNPRO_NOT_FOUND.
    A  Module  $Id: //bas/700_REL/src/krn/dynp/dybas.c#6 $ SAP.
    A  Function dyrdyp.c Line 545.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_GOTO_SAPDEXT
    A  Dynpro does not exist.
    A 
    M  ThIUsrDel: th_rollback_usrdelentry = 1
    M  ***LOG R47=> ThResFree, delete (001024) [thxxmode.c   1384]
    S 
    S Thu Jan 22 15:14:20 2009
    S  found spool memory service RSPO-ACTIONS at 0x70000046000a478

    Hi TJ,
    you are having definetely other issues, than the ones that might be caused by clrpfm of the tables above ...
    But, based on that data, I do not know which ones ;-(
    There are dynpro tables like dynpload or d3456t or so not proper ...
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

  • Error message: "KNA1 does not exist, KNVI does" at Customer creation

    Hi all,
    I have created a new Account group (copy of an existing) and assigned an external number range.
    I have no problems entering the General data or Company code data but when going to Sales area data I get the following error message:
    Check: Table KNA1 does not exist, table KNVI does
    Message no. F2 061
    Please let me know if you have any idea around the error.
    Thanks,
    //anders

    Have you archived the previous customer?
    If so the records in the table KNA1 was archieved and KNVI was not archieved.
    In other words, There is inconsistencies in the database tables KNA1 and KNVI, that is table KNA1 that is main table for customer says that the customer does not exists but table KNVI for tax classification gives tax details for the customer.

  • Se14 message : View Does not exist in database

    Hi All ,
    I have created view and transported to test system , In the test system i am not able to activate it , the message is that " view does not exists in database ", Is it some thing for the basis to do .
    Thanks in advance
    Vinay

    hi,
    Have you tried to re register your database within OEM, CG

Maybe you are looking for