MSS  1.0 sp13 Keyfigure Monitor

Hi ,
I have deployed the MSS 1.0 sp13 . when i execute the keyfigure monitor which is component developed in webdynpro for ABAP . When i am executing this application i am getting an error .
Error Details
The exception 'CX_FQDN' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
  'CX_FQDN=======================CP' has to be
terminated.
Any one has any clues on this exception .
the application name is : key_figure_monitor
Thanks & Regards
Praveen.K.T

Hi Thomas Jung  ,
Thnaks for the reply.
i noticed one thing that just i created a test iview for ABAPwebdynpro  by using one flight component in /bc/webdynpeo/sap /.
this also not working .
i have given Name sapce as : SAP
and the applicationname : as the component name .
basically this should work know .
Regarding the actual problem in MSS iview
when the abapwebdynpro iview is called its giving pagecannot be displayed ie the service it self is not called
i am getting the link like this
res://C:\WINDOWS\system32\shdoclc.dll/dnserror.htm#http://bbleccdev.bharatbijlee.com:3600/sap/bc/webdynpro/SAP/fpb_variance_monitor_overview/;sap-ext-sid=xASS1uCSonu*dp7kglIO4AgWrJBYscTK81P7OrZDeHSg
but from this link if i put
http://bbleccdev.bharatbijlee.com:3600/sap/bc/webdynpro/SAP/fpb_variance_monitor_overview in the browser directly its calling the application .
Do u have any idea why such things happening . since portal is also calling the URL only know ..
Thanks  for the support
Thanks & Regards
Praveen.K.T

Similar Messages

  • MSS 1.0 SP13 - Budget- Critical Variances

    Hi ,
    we are implementing MSS1.0 sp13 . for the scetion budget -critical variences,Critical posting
    there are basicall two iview varience monitor overview  for  critical variences
    and for critical posting - Postings Monitor Overview
    both of these iviews are ABAP Webdynpro iview . We have activated the services in SICF under webdynpro node .
    when we try giving testservice from there its getting executed .
    But when we try executing the iview in the portal its saying page cannot be displayed . I think the service itself is not called .
    whenther any configuration that need to be done from the portal side to display the AbapWebdynpro iview
    Can anyone hlep me in this issue .
    Thanks & Regards
    Praveen.K.T

    Hi Thomas Jung  ,
    Thnaks for the reply.
    i noticed one thing that just i created a test iview for ABAPwebdynpro  by using one flight component in /bc/webdynpeo/sap /.
    this also not working .
    i have given Name sapce as : SAP
    and the applicationname : as the component name .
    basically this should work know .
    Regarding the actual problem in MSS iview
    when the abapwebdynpro iview is called its giving pagecannot be displayed ie the service it self is not called
    i am getting the link like this
    res://C:\WINDOWS\system32\shdoclc.dll/dnserror.htm#http://bbleccdev.bharatbijlee.com:3600/sap/bc/webdynpro/SAP/fpb_variance_monitor_overview/;sap-ext-sid=xASS1uCSonu*dp7kglIO4AgWrJBYscTK81P7OrZDeHSg
    but from this link if i put
    http://bbleccdev.bharatbijlee.com:3600/sap/bc/webdynpro/SAP/fpb_variance_monitor_overview in the browser directly its calling the application .
    Do u have any idea why such things happening . since portal is also calling the URL only know ..
    Thanks  for the support
    Thanks & Regards
    Praveen.K.T

  • Position Holders iView in MSS 1.0 SP13

    Hi,
          The position holders iView and the Org. unit Search iview are displaying only the first person assigned to a position.
    I have assigned 2 managers for an org. unit but the Org unit search iview displays only the first manager. Can the Org. unit search iview display multiple managers or do we have to customize the iView to achieve this.
    The position holder iview provides a link "Multiple", but when i click on the link only one of the person assigned to the position is being displayed. Can the position holder iview display multiple holders or do we have to customize the iview to achieve this.
    Thanks,
    Anand

    Hi Anand,
    For org unit search ;
    Please make change in the column group.
    Presently you may be using column group MSS_TMV_ORG1 or custom copy..
    From this column group remove TMV_ORG_MANG to ORG_MANAGER.
    For position search;
    Apply the latest SP of SAP_ MSS 600. There is a bug in the code.
    Regards
    Pooja

  • HR administrator to process MSS- PCRs for employees

    Hello all,
           We are on SAP ECC 6.0 , EP 7.0 Sp15  and MSS version 600 SP13 .
    We are using MSS Personnel change requests like separation , termination etc.
    We want HR administrator to intiate PCR for all employees as managers do for employees in their respective org. units they
    are heading .
                          We know that in HCM P&F  , HR admin can initiate  Forms for employees .But since we are already using PCRs , we cant switch to HCM P& F .
                                              Is there any way we could meet this requirement with MSS PCRs .
    I feel the only way is if HR admin is at CEO position and is heading all org units , he can process PCRs for all employees .
    But this doesn't seems to be workable .
    I searched the forum and could find out that we can go for customized application .
    any pointers are greatly appreciated.
    Thanks,
    Sahiba

    You can assign manager, Hr admin role as well, and have a custom evaluation path which will populate the
    employees he intends to perform the services!

  • Key Figure Monitor   MSS

    Good Night.
    I am implementing MSS with BP 1.41 and ECC 604.
    In the moment of run the workset Work Overview  the system display the messsage of error of the following link
    [Key Figure Monitor |http://www.freeimagehosting.net/uploads/be4c81b139.jpg]
    Someone can help me with the cause of this error, please.
    Regards

    Good Morning  kaushal kishore 
    The issue was solved with your suggestions.
    But now the portal  display the following message :
    Key Figure Monitor
    No Administrator Key Figure variants found.
    The current key figure view does not containt any key figures.
    Regards

  • NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

    We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
    ECC5.0
    Abap Stack
    EP6 SP13
    Java Stack
    latest versions of MSS and ESS BPs
    The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
    With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
    Any help on this will be greatly appreciated.
    Thanks in advance.
    Regards, Neeta

    Hi,
    Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
    http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
    The error message I get is (rather long....):
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
        ... 53 more
    See full exception chain for details.
    Correction Hints
    Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
    Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version 
    DOM version 
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 95420.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Other
    Session Locale en_US
    Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
         ... 53 more
    Thanks, Neeta

  • Need MSS 1.0 or SP13 or 600

    can any one please provide me information from where can i get downloaded information for MSS  1.0 or SP13 or 600..
    Pls

    To Download the MSS business package 1.0 visit the content portfolio at
    https://www.sdn.sap.com/irj/sdn/contentportfolio
    Under managers you will find the MSS 1.0 and a download option on the left hand side.
    Also refer to these links.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/b0c571af-a46d-2910-8f8d-9e90ce7c398a
    http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm
    Hope this helps.
    Cheers,
    Sandeep Tudumu

  • Notes for SP13 for ESS/MSS

    Hi does anyone know do we have any NOTE which comprises of a list of Notes applicable for SP13.
    recently i saw a note for SRM whcih list all the number of notes listed for srm in it for SP13.
    Similarly of ESS/MSS SP13 do we have anything??

    Hi anyone any idea?

  • 'Task Type' property in Monitoring of Task iview in MSS

    Hi,
    There is a property called 'Task Type' in the iview 'Monitoring of Task'.
    This is supposed to restrict the display of task types to what is specified here in this property only.
    For eg, if i have 3 task types configured for It0019 in the back-end and want only 2 to get displayed in the portal, then i will mention those task types in this property.
    1 -- Monitoring Overtime
    2 -- Monitoring payments
    3 -- Monitoring absence.
    I have mentioned the task types separating them by ';'.
    However now no task is getting displayed.
    Can anyone help please?
    Thanks and Regards,
    Pinki

    can you please check your iview property
    FUNCTION HRMSS_RFC_RD_DATES_GETLIST
    FUNCTION HRWPC_RD_DATES_GETLIST_INTERNA
    LOOP AT lt_monitoringtask
                    INTO  ls_monitoringtask
                    WHERE ( p0019-termn BETWEEN begda AND endda ) OR
                          ( p0019-mndat BETWEEN begda AND endda ).
            check for allowed employment status
              IF NOT t_employmentstatus_mt[] IS INITIAL.
                LOOP AT lt_action
                        INTO  ls_action
                        WHERE pernr  = ls_monitoringtask-p0019-pernr AND
                              begda <= ls_monitoringtask-p0019-termn AND
                              endda >= ls_monitoringtask-p0019-termn.
                  EXIT.
    http://help.sap.com/saphelp_erp60/helpdata/EN/43/376d7ced1f1bcee10000000
    a1553f7/frameset.htm

  • Error Updating WAS SP13 -- SPS18, Phase Deploy Online: SAPJTECHS18_0.SCA

    hello,
    I can not update SAP WAS Java SP13 to SPS18. I get an error message during phase "deploy online" (18 of 24). see the error message and log below.
    Previous to running the update I successfully run the WAS SP18 Prerequisite Check based on "WAS-PREREQUISITE_CHECK_DATA_640.XML" downloaded at 2006-08-24 without any warnings or errors.
    I used sapcar 6.40 patchlevel 4, I extracted the following downloaded files in this order:
    sapcar -xvf SAPINST18_0-20000118.SAR -R NW04-WebASJava-18
    sapcar -xvf CTRLMSS18_0-20000118.SAR -R NW04-WebASJava-18
    sapcar -xvf J2EERT18_0-10001982.SAR -R NW04-WebASJava-18
    sapcar -xvf J2EERTOS18_0-20000118.SAR -R NW04-WebASJava-18
    for any help I would be very greatful.
    thanks, volker.
    WARNING 2006-08-25 01:42:13
    Execution of the command "C:\j2sdk1.4.2_12/bin/java.exe '-Xmx256M' '-jar' 'C:\usr\sap/J2E/JC00/SDM/program/bin/SDM.jar' 'deploy' 'list=C:\Program Files\sapinst_instdir\PATCH\MSS/SDAS_TO_BE_DEPLOYED.LST' 'onerror=stop' 'sdmhome=C:\usr\sap/J2E/JC00/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\PATCH\MSS/callSdmViaSapinst.log' 'logtoconsole=true'" finished with return code 4. Output: Info: Info: ============================================Info: =   Starting to execute command 'deploy'   =Info: ============================================Info: Starting SDM - Software Deployment Manager...Starting SDM - Software Deployment Manager...Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000Info: SDM operation mode successfully set to: StandaloneInitializing Network Manager (50017)Info: Initializing Network Manager (50017)Checking if another SDM is running on port 50018Info: Checking if another SDM is running on port 50018Info: -
    Starting deployment -
    Info: Error handling strategy: OnErrorStopInfo: Prerequisite error handling strategy: OnPrerequisiteErrorStopInfo: Update strategy: UpdateLowerVersionsInfo: Starting deployment prerequisites:Info: Loading selected archives...Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'Info: Selected archives successfully loaded.Info: Actions per selected component:Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6. ...
    ERROR 2006-08-25 01:42:13
    MUT-02041  SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
    ERROR 2006-08-25 01:42:13
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    this is the contents of callSdmViaSapinst.log:
    Aug 25, 2006 12:30:06... Info: Start logging to console
    Aug 25, 2006 12:30:06... Info:
    Aug 25, 2006 12:30:06... Info: ============================================
    Aug 25, 2006 12:30:06... Info: =   Starting to execute command 'deploy'   =
    Aug 25, 2006 12:30:06... Info: ============================================
    Aug 25, 2006 12:30:06... Info: Starting SDM - Software Deployment Manager...
    Aug 25, 2006 12:30:06... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Aug 25, 2006 12:30:08... Info: SDM operation mode successfully set to: Standalone
    Aug 25, 2006 12:30:08... Info: Initializing Network Manager (50017)
    Aug 25, 2006 12:30:08... Info: Checking if another SDM is running on port 50018
    Aug 25, 2006 12:30:08... Info: -
    Starting deployment -
    Aug 25, 2006 12:30:08... Info: Error handling strategy: OnErrorStop
    Aug 25, 2006 12:30:08... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Aug 25, 2006 12:30:08... Info: Update strategy: UpdateLowerVersions
    Aug 25, 2006 12:30:08... Info: Starting deployment prerequisites:
    Aug 25, 2006 12:30:11... Info: Loading selected archives...
    Aug 25, 2006 12:30:11... Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Aug 25, 2006 12:30:16... Info: Selected archives successfully loaded.
    Aug 25, 2006 12:30:18... Info: Actions per selected component:
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.13.0.20050720034335''/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'0' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163602.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719161053.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'0' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133205.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'0' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140206.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'0' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154449.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'0' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050624161235.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'0' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164103.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628142849.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'0' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140331.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:20... Info: Ending deployment prerequisites. All items are correct.
    Aug 25, 2006 12:30:20... Info: Saved current Engine state.
    Aug 25, 2006 12:30:20... Info: Starting: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:20... Info: Creating connections to database "J2E".
    Aug 25, 2006 12:30:20... Info: Creating vendor connection to database.
    Aug 25, 2006 12:30:20... Info: Vendor connection created successfully.
    Aug 25, 2006 12:30:20... Info: Creating openSQL connection to database.
    Aug 25, 2006 12:30:21... Info: OpenSQL connection created successfully.
    Aug 25, 2006 12:30:25... Info: <!LOGHEADER[START]/>
    Aug 25, 2006 12:30:25... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
    Aug 25, 2006 12:30:25... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    Aug 25, 2006 12:30:25... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003021.log]/>
    Aug 25, 2006 12:30:25... Info: <!PATTERN[jddilog20060825003021.log]/>
    Aug 25, 2006 12:30:25... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
    Aug 25, 2006 12:30:25... Info: <!ENCODING[Cp1252]/>
    Aug 25, 2006 12:30:25... Info: <!LOGHEADER[END]/>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTX >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTX >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSINST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSINST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSOC >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSOC >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CLASS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CLASS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESP >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESP >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUAL >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUAL >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ROLE >>>
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ROLE >>>
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
    Aug 25, 2006 12:30:25... Info: Finished successfully: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0'
    Aug 25, 2006 12:30:25... Info: Starting to save the repository
    Aug 25, 2006 12:30:26... Info: Finished saving the repository
    Aug 25, 2006 12:30:26... Info: Starting: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:27... Info: <!LOGHEADER[START]/>
    Aug 25, 2006 12:30:27... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
    Aug 25, 2006 12:30:27... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    Aug 25, 2006 12:30:27... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003026.log]/>
    Aug 25, 2006 12:30:27... Info: <!PATTERN[jddilog20060825003026.log]/>
    Aug 25, 2006 12:30:27... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
    Aug 25, 2006 12:30:27... Info: <!ENCODING[Cp1252]/>
    Aug 25, 2006 12:30:27... Info: <!LOGHEADER[END]/>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:

    It looks like you need to make sure server0 is running before trying to deploy the AutoID (AII) components; from your SDM log:
    ERROR: Cannot perform action deploy on component library C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\com.sap.aii.ibtransportclient\SAP AG\0\6.4018.00.0000.20060413102101.0000\aii_ibtransportclient.sda. Reason:
    com.sap.engine.services.rmi_p4.P4ConnectionException: <b>Possible problem: no available running server node. Check your running servers.</b>
    The SDM can't connect to the P4 service of the instance; make sure it's started and then try deploying the package again.
    Rich

  • App Integeator error in MSS

    Hi All,
    I have recently upgraded EP 7.0  to SP13. Also upgraded MSS to SP 11. In the key figure monitor I ma getting the following error :
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : EP_MSS1
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;&lt;ProducerInfo&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    Please Help
    Thanks
    Raktim

    Hi,
    I think the Key Figure Monitor does use the system alias SAP_ECC_Financial for the system lookup. Did you maintain all the relevant data for this system?
    Maybe this iVIew is currently pointing to the wrong system.
    Regards,
    Holger.

  • Monitoring servers in SCOM 2012 via different locals within the same management group

    Hi,
    I have 2 management servers in a same management group. The 1st one is having English (US) locale while other is installed on Swedish locale. Both are accessed by different users having same admin rights.
    Once a USER 1 try to register a server through authoring tab from 1st management server(installed on English locale), a profile/group wrt the server registered is created successfully but the USER on 2nd management server (installed on Swedish locale) can
    not see the same in Authoring tab. He can view it in Monitoring tab as as well as Administration tab.
    The Vice versa is also true.
    Does any one have idea that is it SCOM 2012's expected behaviour wrt 2 2 different users on 2 different locales within a same management group ?
    Thanks in advance.

    Hi,
    I am a little confused, what do you mean by "register a server through authoring tab"?
    Do you mean that when you discover a server on 1st MS with discovery wizard then you cannot see it on 2nd MS(and the vice versa)?
    As far as I know, all those information should be stored in the operation database which is shared to both MSs within the same management group.
    We may use SQL query to find the discovered server on the operation database. Please also check operation manager event logs to get more information to troubleshoot this issue.
    Regards,
    Yan Li
    Regards, Yan Li

  • PDFDocument Exception in MSS-PCR

    Hello ,
    We are on EP7.0 and configured ADS server successfullt with our DEV and QAT system but the PCR application was working successfully in these systems...but now all of a sudden when we try to create a new PCR in QAT it blows with the following exception:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/msspcr/PcrApplication/wd_key41_1194013279594/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=DefaultExternal1194012746990&sap-ext-sid=HG0eF8QM883ta%2B5igpTM2g%3D%3Dgn0nJ2IIuGlVKF5fdTKsJQ%3D%3D%2Fpcd%3Aportal_content%2Fcom.adc.root%2Fmgrtool%2Froles%2Fcom.adc.mgrtool.mgrtool_rl%2Fmss_ws%2FTest%2Fcom.sap.pct.erp.mss.pcrapplication_page%2Fsap.com%2Fmss%7Epcr%2FPcrApplication%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200702010738
        at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:379)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
        ... 41 more
    See full exception chain for details.
    Correction Hints
    PDF Document Render Exception.
    Please check the following:
    Template file is not corrupted.
    Data being passed is a vaild XML.
    You have configured the web service client proxy properly.
    Adobe Document Service (ADS) is configured properly (follow the configuration guide available at SAP service market place to check with all the supported configuration options).
    If the problem still persists, report it to us. We need the following information to investigate the problem further:
    Click here to download the error pdf that has been generated instead of the actual pdf. This is an important document to analyse the problem further.
    Follow the steps below to get the system information where web dynpro is running:
    Go to : http://host:port/sap/monitoring/SystemInfo
    Log on as Administrator user.
    Click on link all components... there. This will take you to the system information page that lists the version information of all the componenets installaed on your server.
    Save this entire page (containing the version information of all the componenets installed on your server)
    Follow SAP notes mentioned below to get the trace files for web dynpro and ADS. Then run your application again. Get the latest updated trace files from the server. If webdynpro and ADS are not running on the same server, then you need to turn on the tracer for the respective servers:
    #742674 to turn on the web dynpro trace on the server where web dynpro is running.
    #846610 to turn on the ADS trace on the server where ADS is running.
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:18:32[UTC], changelist=434634, host=pwdfm101), build date: Wed Apr 18 21:55:17 CDT 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en_US
    Time of Failure Fri Nov 02 09:21:19 CDT 2007 (Java Time: 1194013279625)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0011.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:49:49[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:48[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0011.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-01-31:19:50:27[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to  UPDATEDATAINPDF
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:392)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:779)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:714)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:69)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1259)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:324)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:830)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../sap.com/msspcr/PcrApplication/wd_key41_1194013279594/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=DefaultExternal1194012746990&sap-ext-sid=HG0eF8QM883ta%2B5igpTM2g%3D%3Dgn0nJ2IIuGlVKF5fdTKsJQ%3D%3D%2Fpcd%3Aportal_content%2Fcom.adc.root%2Fmgrtool%2Froles%2Fcom.adc.mgrtool.mgrtool_rl%2Fmss_ws%2FTest%2Fcom.sap.pct.erp.mss.pcrapplication_page%2Fsap.com%2Fmss%7Epcr%2FPcrApplication%2Fbase&sap-wd-norefresh=X&sap-ep-version=7.00.200702010738
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:379)
         ... 45 more
    Although it is still working in DEV system.....Please help.
    Any help would be highly appreciated.

    Dear Raja,
    I loggged into Visual Admin to change the value of sap.ADSCallingMode", from "http" to "soap. but that particular property is not maintained in the default property sheet  in the following path
    Server -> Services -> Configuration Adapter -> webdynpro -> sap.com -> tcwddispwda.
    but you can see in the error trace i have given above that it is a SOAP based request. I am on EP 6 SP 9; will I have to upgrade or is it any other problem?
    Regards,
    Shyam

  • Payload not visible in the XI monitor

    In my scenario an xml message was successfully reaching its destination. The XI system was upgraded from support pack 13 to support pack 16. After that the process is still working fine as the XML message is still successfully reaching its destination. The issue we have is that the ‘Payload’ is not visible in the last two steps of the monitor. We can see the Payload until ‘Technical Routing’ in the monitor. But ‘Call Adapter’ and ‘Response’ steps do not have payload.
    (TCode: SXMB_MONI)
    when we double click a message we get XML message details and on the left hand side it shows following hierarchy:
    XML Message:
    Receiver Grouping
       -     SOAP Header
       -     SOAP Body
       -     Payloads
    Request Message Mapping
       -     SOAP Header
       -     SOAP Body
       -     Payloads
    Technical Routing
       -     SOAP Header
       -     SOAP Body
       -     Payloads
    Call Adapter
       -     SOAP Header
       -     SOAP Body
    <b>(( No Payload displayed, but present above!! ))</b>
    Response
       -     SOAP Header
       -     SOAP Body
    <b>(( No Payload displayed, but present above!! ))</b> 
    Any suggestions would be highly appreciated!
    Thanks in advance.
    Faiq

    Hi faiq
    This seems to be the normal behaviour starting with SP13 or 14. There was a discussion about this a while ago and I believe it turned out to be works as designed.
    This is what was posted as final conclusion in Re: SXMB_MONI does not show payload after upgrade to SP15:
    <i>According to SAP (OSS) this is working as designed. Apparently it was an error in the past that the payload was stored in the DB on the ABAP (IE) side when the AE is involved, as it would then be stored twice at DB level. This explains why this is not a problem when e.g. the IDOC adapter is used.
    Anyway, the only way to let the system show the payload in SXI_MONITOR is to set the runtime trace level to 3 (full trace) and parameter logging to 1 (trace switched on).</i>
    regards,
    Peter

  • Missing MSS iViews in Federated Portal Network

    Hello, portal gurus, we have a FPN related issue that hope some of you can help.
    We have two portal systems that we set up as a Federated Portal
    Network. One producer portal, verision is 7.0, SP11, and one 
    consumer portal, version is 7.0 SP13. We installed the ESS and MSS business
    packages in the producer portal. Those business packages came with the SAP NetWeaver
    2005 installation, and they are working ok on the producer portal.
    In addition, we were able to do the remote role assignment in the
    consumer portal successfully. The problem is that some of the MSS
    links and iViews that are shown up ok in the producer portal are missing from the consumer portal.
    Have anyone experienced the same issue? Is it because the dismatch of the SP level causing the issue? Are there any fixes to this issu?
    Thanks a lot for any input!
    Jane

    Hi Jane,
    PCD content and KM content are two different things and they have different transport mechanism.
    If you want to transport PCD content to another portal go to System Administration/Transport/Transport Package/Export. In PCD tree in any place create transport package and add to it objects which you need (folders, roles, worksets, iviews and so on) and save transport package file localy on your computer or server. After that go to the system where you want to locate your content. Go to System Administration/Transport/Transport Package/Import If you save tranport file localy on your computer chose client and upload tranport file.
    KM transport very clear describe here How to Export KM Contents by ICE protocol using Offline Channel Beside this way you can transport KM content use program Portal Drive (very useful program especially when you need quickly transport some KM files from one portal to another).
    Regards
    Dmitriy

Maybe you are looking for