Deploy KMC 7.0 Components to NW CE7.1

Hello,
is it possible to deploy the KMC components with the version 7.0 to NW CE7.1?
Thx, Vanessa

hi,
NW CE 7.1 is not having KM.
But you can use NW 7.0 KM in CE 7.1 by integrating CE 7.1 with NW 7.0 KM.
[SDN Help doc|http://help.sap.com/saphelp_nwce10/helpdata/en/1c/aa6eaf373c416cbfa416665887ab1c/frameset.htm]
Edited by: Sampath Gunda on Dec 2, 2008 12:23 PM
Edited by: Sampath Gunda on Dec 2, 2008 12:25 PM

Similar Messages

  • Jdev 9iRC: deployment of BC4J-UIX components to OC4J !2.0! does not work

    in different threads the problem of deployment of BC4J UIX components to OC4J 1.2.2.x is addressed (see http://forums.oracle.com/forums/message.jsp?id=679060 for example). contrary to the sayings of different members of the jdev-team i face the same problem with OC4J 2.0 (java lang nullpointer exception).
    i'm using jdev9iRC and 9iASWE v2 beta which comes with OC4J 2.0.
    i followed the recommendations of the thread mentioned above, no result. i followed the recommendations of steve muench in thread HELP! Loading Java Classes into Oracle ERROR result is the same error but now already when calling the main.uix. next try was also on recommendation of steve muench somewhere else: i installed the complete jdev 9iRC on my application server and tried to deploy to this "embedded" OC4J. result: uncomplete deployment because of denied access to the files server.xml and http-website-xml:
    Beginning to deploy to Oracle9i Application Server...
    Wrote WAR file to C:\Programme\oracle\jdeveloper\jdev\mywork\WF_Wettfamily\src\F1StammdatenUIX.war
    Wrote web EAR file to C:\Programme\oracle\jdeveloper\jdev\mywork\WF_Wettfamily\src\F1StammdatenUIX.ear
    Invoking Oracle9iAS admin tool...
    C:\Programme\oracle\jdeveloper\jdk1.3\jre\bin\javaw.exe -jar C:\Programme\oracle\jdeveloper\j2ee\home\admin.jar ormi://bajor.skypages.net admin **** -deploy -file C:\Programme\oracle\jdeveloper\jdev\mywork\WF_Wettfamily\src\F1StammdatenUIX.ear -deploymentName F1Administration-F1StammdatenUIX-app
    Auto-unpacking E:\ORACLE\jdev9iRC\j2ee\home\applications\_F1StammdatenUIX.ear... done.
    Auto-unpacking E:\ORACLE\jdev9iRC\j2ee\home\applications\_F1StammdatenUIX\F1StammdatenUIX.war... done.
    java.io.FileNotFoundException: E:\ORACLE\jdev9iRC\j2ee\home\config\server.xml (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at com.evermind.xml.XMLConfig.storeToURL(XMLConfig.java:433)
    at com.evermind.xml.XMLConfig.store(XMLConfig.java:420)
    at com.evermind.server.ServerComponent.store(ServerComponent.java:756)
    at com.evermind.server.ServerComponent.store(ServerComponent.java:728)
    at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplicationInstallation.java:466)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:79)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:62)
    Exit status of Oracle9iAS admin tool (-deploy): 0
    C:\Programme\oracle\jdeveloper\jdk1.3\jre\bin\javaw.exe -jar C:\Programme\oracle\jdeveloper\j2ee\home\admin.jar ormi://bajor.skypages.net admin **** -bindWebApp F1Administration-F1StammdatenUIX-app F1StammdatenUIX http-web-site /F1Administration-F1StammdatenUIX-context-root
    Communication error: E:\ORACLE\jdev9iRC\j2ee\home\config\http-web-site.xml (Access is denied)
    Exit status of Oracle9iAS admin tool (-bindWebApp): 1
    ---- Deployment finished. ---- 12.02.2002 12:53:02
    what am i supposed to do? is there a solution?
    please help
    TIA, trevi

    Yes, I can create a new as3 file, but I can't "fill it with
    sensible content". Neither my As3-codes are recognized nor simple
    components are displayed to me in a proper way when testing the
    movieclip.
    Now, I have just reinstalled my CS4 on another computer and
    there it works with AS3. Really strange. Does CS4 need to
    communicate with some internet services while executing a simple
    fla-file or something like that?

  • Deploying MDM Web Dynpro Components on NWCE 7.2 - /wdconfig not displayed

    Hi all -
    I'm trying to deploy the MDM Web Dynpro Components Framework  (the goal is to
    have NW CE connect to and 'see' the MDM repositories) and according to the URL
    http://help.sap.com/saphelpnwmdm71/helpdata/en/4a/8c20a0dc93203be10000000a42189b/frameset.htm,
    one of the steps is to run the MDM Web Dynpro Configuration Manager application
    (_http://<server>:<port>/mdm/wdconfig).  However, I get an error stating the page
    wasn't found (example: Error: Requested file /wdconfig does not exist).
    Looking further, I see that WD Framework needs to be configured as a pre-req.
    I'm in the JSPM and I see that MDM JAVA WD FRAMEWORK 7.1 7.11, MDM JAVA API Library
    and MDM Java Connector needs to be deployed (JAVA API and Connector are first).
    Under the 'Deployed Components' tab in JSPM, I see :
    >> sap.com/MDM_JAVA_API - 7.1
    sap.com/com.sap.mdm.tech.apireset
    sap.com/com.sap.mdm.tech.connector
    sap.com/com.sap.mdm.tech.mdm4j
    >> sap.com/MDM_JAVA_WD_FRAMEWORK - 710.711 (SP05)
    sap.com/tc/mdm/wdcomps/core/ear
    I deployed MDM_JAVA_API first and have restarted the NWCE system.
    I don't see any error in the logs and the URL for the /wdconfig still does not exist.
    Is there something that I have to deploy?  Can someone point me to a document other than
    the help.sap.com that talks about CE 7.2 and MDM 7.1 configurations?  I do have the master
    and install guide for both. 
    Please advise!
    Thanks!
    -s

    Update:
    Hi - thanks for the followup.
    I have the correct SCAs.  I have done the following:
    UNDEPLOY both components
    Restarted the services
    Deployed the JAVA_API first
    Restart services
    Deployed the Framework
    Restarted the services
    Yes, even though the docs said I can deploy them in order, I think there may have been
    a few hitches that the error logs didn't catch.
    Specifically, when I re-deployed the FRAMEWORK 7.1 7.11, there were now 19 components
    listed instead of one.
    I am able to go to ~mdm/wdconfig now.
    However, I get a new message:
    "You are not authorized to use MDM Web Dynpro Components Configuration Manager".
    Even though I'm the Administrator? 
    I did see in the docs that I need to create a Project first and that the userID that logs in
    should exist in UME and the MDM system.
    (_http://help.sap.com/saphelp_nwmdm71/helpdata/en/4a/41a40c343f2ab1e10000000a42189c/content.htm)
    I am looking into that now.  I think I will close this thread and start a new one
    specifically for that.
    Thanks!
    -s

  • New Deployment: SE: Installing Lync Components Error Installing OcsMcu.ms

    New SE Lab Deployment: 1 Windows 2008 DC, 1 x 2008 R2 Lync Server.
    I get the following error when going through the Installing Lync Components Process:
    Error returned while installing OcsMcu.msi(ASMCU), code 1603. Please consult log at C:\Users\Nav\AppData\Local\Temp\Add-OcsMcu.msi-ASMCU-[2012_11_20][20_13_58].log
    The events show the following:  
    Product: Microsoft Lync Server 2010, Conferencing Server -- Error 27761. Error 0x80070002 (The system cannot find the file specified) granting access to 'RTC Component Local Group' on MACHINE\SYSTEM\CurrentControlSet\Services\MediaPerf\Performance\Parameters
    performance counters.
    How do I get past this error?

    I have tried to run this package manually from the disk.
    It starts the installation then during the early stages of the install i get the error message asking me to insert the disk.
    When I try and install seperate components i get the following error message:
    Product: Microsoft Lync Server 2010, Conferencing Server -- Error 27761. Error 0x80070002 (The system cannot find the file specified) granting access to 'RTC Component Local Group' on MACHINE\SYSTEM\CurrentControlSet\Services\MediaPerf\Performance\Parameters
    performance counters.

  • Deployment utility drivers and components, some missing?

    I have Testand 3.5 and LabWindows/CVI 8.5 installed on my machine.  I would like to modify an existing TestStand deployment to include the LabWindows/CVI 8.5 Run-Time Engine, so that the installed program can run as an executable on the target system(s) without requiring a full install of LW/CVI.  When I click on "Installer Options" and then "Drivers and Components" I see that the LW/CVI 8.1 RTE is available, but not 8.5.  I've never had 8.1 on my machine.  I have 7.1 and 8.5 installed.  (See attached screenshot.)  I assumed that the 8.5 RTE would be installed along with LW/CVI 8.5, but is this not the case?
    -Joel
    Attachments:
    TS_deploy.PNG ‏31 KB

    Hi Joel,
    This is most definitely a bug with the NI Build Installer. The bug has been reported under ID 100489.
    Rest assured however that although the Drivers and Components list shows CVI 8.1 RTE, it will actually bundle the CVI 8.5 RTE with the deployed system. This is true since the Build Installer captures the CVI Run-time from: C:\Program Files\National Instruments\Shared\ProductCache, which contains the latest CVI RTE.
    Thanks for the info Joel.
    Nestor

  • J2EE Deployment of non-ejb components.

    A question. When installing into a J2EE app server - what is the prefered way to install just standard java classes your application uses? Should they be in the classpath, somehow in the jar or ear files?
    thanks in advance :)

    Answers to questions such as these can be easily found in the Java� 2 Platform Enterprise Edition Specification document. You can refer to this document at http://java.sun.com/j2ee/j2ee-1_3-fr-spec.pdf
    In fact, reading this document and other platform level specifications is very important for J2EE developers.

  • Error while deploying mobile components through SDM

    Hi,
    I have installed MI system in my landscape and i have deployed few MI related components through SDM
    Components are:
    NWMTR.sda
    NWMTS.sda
    NWMTTREPOSITORY.sda
    I got the following error when deployed through SDM
    Starting Deployment of MBA-MTR
    Aborted: development component 'MBA-MTR'/'sap.com'/'SAP AG'/'200600'/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/MBA-MTR.. Reason: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='mcd.xml is incorrect! Header information are missing.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key mcd.xml is incorrect! Header information are missing.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Please suggest me to go further.
    Regards,
    jagadish

    Hi Jagadish
    The main reason for the deployment to fail is the following error message "mcd.xml is incorrect! Header information are missing". Hence can i know if you have modified or removfed any attributes of the standard mcd xml file that is present in the application zip file.  If this you have not modified the xml file, then can you please check if you have downloaded the correct sda files from SAP service market place.  Note that the version of MTR, MTS etc are different for MI 7.0 and Mobile 7.1.  If you are using MI 7.0 server then kindly download application that is compatible with MI 7.0 only.  Please try and let me know.
    Best Regards
    Sivakumar

  • Errors while deploying LiveCycle Components in the Config Manager

    Hi All
    I've been having some problems with a LiveCycle deployment on Websphere. Here are some details about the environment:
    - Windows 2008, Enterprise
    - Oracle 11g
    - WAS ND 6.1.0.29
    - LiveCycle ES2.5
    Installation works perfectly and everything in the config manager works perfectly until I get the page where it deploys the LC components (the xxx-dsc,jar and xxx.lca files)
    At that page, when I click on deploy it fails on deploying any of the components.
    The error message thrown by the config manager is code "Error [ALC-LCM-030-200]" and description "Failed to deploy component"
    WAS log file is pretty long (considering that one exception is thrown for each component), so I won't repeat the whole thing here, but most of them look roughly like what I have below:
    [10/27/11 13:37:31:485 CAT] 00000036 ExceptionUtil E   CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "doRequired" on bean "BeanId(LiveCycleES2#adobe-dscf.jar#EjbTransactionCMTAdapter, null)". Exception data: com.adobe.idp.DocumentError: java.lang.Error: IP Helper Library GetIfTable function failed
        at com.adobe.idp.Document.getLocalHostId(Document.java:2896)
        at com.adobe.idp.Document.writeNullContent(Document.java:982)
        at com.adobe.idp.Document.writeObject(Document.java:947)
        at com.adobe.idp.Document.<init>(Document.java:715)
        at com.adobe.idp.DocumentStorage.persistInline(DocumentStorage.java:85)
        at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl._createInlineArchive(ArchiveStoreImpl. java:343)
        at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl.access$500(ArchiveStoreImpl.java:79)
        at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl$6.doInTransaction(ArchiveStoreImpl.jav a:233)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequired(Ej bTransactionCMTAdapterBean.java:274)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionCMTAdapter_ caf58c4f.doRequired(Unknown Source)
        at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:129)
        at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
        at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl.createInlineArchive(ArchiveStoreImpl.j ava:231)
        at com.adobe.idp.dsc.registry.component.impl.ComponentRegistryImpl$4.doInTransaction(Compone ntRegistryImpl.java:234)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew (EjbTransactionCMTAdapterBean.java:299)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionCMTAdapter_ caf58c4f.doRequiresNew(Unknown Source)
        at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
        at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
        at com.adobe.idp.dsc.registry.component.impl.ComponentRegistryImpl.install(ComponentRegistry Impl.java:230)
        at sun.reflect.GeneratedMethodAccessor189.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
        at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassi vationInterceptor.java:53)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTran sactionBMTAdapterBean.java:197)
        at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionBMTAdapter_ 3af08fdf.doBMT(Unknown Source)
        at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:95)
        at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:165)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
        at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
        at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:121)
        at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
        at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.invoke(AbstractMessageReceiv er.java:329)
        at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:139)
        at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
        at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
        at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
        at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
        at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
        at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
        at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
        at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java: 190)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
        at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:41)
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java: 190)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837)
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680)
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
        at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:525)
        at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.jav a:90)
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:751)
        at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:126)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink .java:458)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink .java:387)
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
        at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConn ectionInitialReadCallback.java:214)
        at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitia lReadCallback.java:113)
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionLi stener.java:165)
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
    Caused by: java.lang.Error: IP Helper Library GetIfTable function failed
        at java.net.NetworkInterface.getAll(Native Method)
        at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:216)
        at com.adobe.idp.Document.getLocalHostId(Document.java:2873)
        ... 93 more
    I have found a couple of forum posts that reference this issue, but none seem to provide a solution. Once suggestion that seemed reasonable was that the GDS folder was not writable, but that doesn't seem to be the issues.
    Any help is much appreciated
    Greg

    Greg:
    The exception is coming from the method getLocalHostId which makes me want to look at your server's TCP/IP configuration.
    Is this a multi-homed server?  IPv6, IPv4 or both?
    [10/27/11 13:37:31:485 CAT] 00000036 ExceptionUtil E   CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "doRequired" on bean "BeanId(LiveCycleES2#adobe-dscf.jar#EjbTransactionCMTAdapter, null)". Exception data: com.adobe.idp.DocumentError: java.lang.Error: IP Helper Library GetIfTable function failed
        at com.adobe.idp.Document.getLocalHostId(Document.java:2896)

  • How to deploy selected components on the production server with the same solution

    Hello,
    We've a production server where we had deployed the visual studio based solution which contains all the web parts and their business logic. Production server is up and running live and end-users have started using it as well.
    Now, some issues and change requests have been reported regarding some components (web parts). We've made all the relevant changes. However, I want to deploy only those selected components (web parts) instead of entire solution again.
    So, as per my understanding, if i include the selected components in the package/feature then at the time of deployment, wsp retracts the old solution and deploys the new one. When the new one won't have those web parts which didn't updated then portal/site
    will start giving error and site will be collapsed.
    Another option is to create another farm solution in Visual Studio 2010 and add the updated components in it. Then, we may be able to deploy it. Then, i'll be able to remove the old web parts from the selected pages and deploy the updated one.
    Is there any better option which anyone could let me know?
    Thanks!
    Sohaib Khan

    Hello,
    We've a production server where we had deployed the visual studio based solution which contains all the web parts and their business logic. Production server is up and running live and end-users have started using it as well.
    Now, some issues and change requests have been reported regarding some components (web parts). We've made all the relevant changes. However, I want to deploy only those selected components (web parts) instead of entire solution again.
    So, as per my understanding, if i include the selected components in the package/feature then at the time of deployment, wsp retracts the old solution and deploys the new one. When the new one won't have those web parts which didn't updated then portal/site
    will start giving error and site will be collapsed.
    Another option is to create another farm solution in Visual Studio 2010 and add the updated components in it. Then, we may be able to deploy it. Then, i'll be able to remove the old web parts from the selected pages and deploy the updated one.
    Is there any better option which anyone could let me know?
    Thanks!
    Sohaib Khan
    Hi Sohaib, your another option is a good idea, only make sure to retract and remove the original from your farm, the add and install the new updated solution.  And if you run into any error that says features already exist, you can use powershell, install-SPSolution
    and -force to get the new solution deployed.  http://tinyurl.com/q8erz72
    Or, you could use Upgrade-SPSolution with a package that has same features from original, with the new artifacts.  Although, if any of the original features are modified, I would recommend retract remove redeploy.
    Stacy www.sharepointpapa.com

  • Deploying FCM after the EPM components

    This is version 11.1.2.2. Planning, HFM and FDM are up and running. We are attempting to evaluate FCM
    http://www.oracle.com/webfolder/technetwork/tutorials/obe/hyp/FCM11.1.2.2-MultiNodeInstall/FCMMultiNodeInstall.htm#t2
    So far I have been following the tutorial from the url above, just that I skipped the EPM component installation and configuration as they are already there.
    Under the section "Configuring SOA Suite on Machine A", instead of creating a new weblogic domain "base_domain", I chose to extend from the existing domain "EPMSystem" cause I read from the other documents that the SOA applications and the EPMs need to be on the same domain.
    I click through and select the products as advised and set the JDBC and component schema for each of the product, I passed the testing. Just that on step 10, I have the "Extend" domain option to click instead of "Create", so I click "Extend"
    The system comes back with an error: "CFGFWK-60321: Duplicate Server listen ports exist in your domain configuration. Port 7001 on AdminServer"
    Which 7001 is the port for my WebLogic admin server when deploying the other EPM components. Reading other emails I can find it seems that all configured SOA before EPM.
    My questions are:
    1. Is it possible to install FCM on top of an existing EPM deployment?
    2. Is there anything I have done incorrectly from my description above. Shall I create a new weblogic domain in this case?
    Any idea would be much appreciated. Thank you.

    Thanks for the reply. I stopped the AdminServer and retried, same error message pops up.
    Just that in the second attempt I notice that on the "Select a Weblogic Domain Directory" screen, under the "user_projects" directory, there is an entry of "epmsystem1" (my EPM instance name) and a "EPMSystem" under the "user_projects\domains", which was what I have been choosing, is it correct? EPMSystem is the name I have chosen when configuring the deployment to WebLogic for my EPM components.
    Also in the next screen I was given two options 1) "Extend my domain automatically to support the following added products" and 2) "Extend my domain using an existing extension template"
    I chose #1, is that correct? The products I have chosen are "Oracle SOA Suite - 11.1.1.0[Oracle_SOA1]" and "Oracle WSM Policy Manager - 11.1.1.0[oracle_common]"
    I used to choose also the Oracle Enterprise Manager in my first attempt, but now it is default checked and dimmed for selection.
    Is anything above sound weird to you?

  • Deployment Error In Webcenter Content Components

    Hi All,
             After Installation of WebCenter Content I logged in to Web-logic Administration Console Where the deployment part shows the following errors:
    The Deployment of some particular components shows state as "Failed".Please tell me how to rectify it.

    Hi,
        Thanks for the reply,The files shows a bunch of statements where am not getting any clue.I copied the statements below,If u find anything pls let me know,
    <Feb 25, 2015 2:46:37 PM> <INFO> <NodeManager> <Server output log file is 'D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\logs\URM_server1.out'>
    'D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\bin\\Installer64' is not recognized as an internal or external command,
    operable program or batch file.
    'D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    Content Server provided no native path information in idcCommEnv.cmd.
    'D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    'D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\bin\\Installer' is not recognized as an internal or external command,
    operable program or batch file.
    FINDSTR: No search strings
    JAVA Memory arguments: -Xms256m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\lib\tools.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;D:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.6.0.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;D:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;D:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;D:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\jlib\idcloader.jar;D:\Oracle\MIDDLE~1\ORACLE~2\ucm\idc\components\NativeOsUtils\classes-NativeOsUtils.jar;;.;D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\lib\tools.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;D:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.6.0.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;D:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
    PATH=D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\native;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\native;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\jre\bin;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\bin;D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\native;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\native;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\jre\bin;D:\Oracle\MIDDLE~1\JROCKI~1.0-1\bin;C:\ProgramData\Oracle\Java\javapath;E:\OraHome_1\bin;E:\OraHome_1\jre\1.4.2\bin\client;E:\OraHome_1\jre\1.4.2\bin;D:\DevSuiteHome_2\jdk\jre\bin\classic;D:\DevSuiteHome_2\jdk\jre\bin;D:\DevSuiteHome_2\jdk\jre\bin\client;D:\DevSuiteHome_2\jlib;D:\DevSuiteHome_2\bin;D:\DevSuiteHome_2\jre\1.4.2\bin\client;D:\DevSuiteHome_2\jre\1.4.2\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
    *  To start WebLogic Server, use a username and   *
    *  password assigned to an admin-level user.  For *
    *  server administration, use the WebLogic Server *
    *  console at http:\\hostname:port\console        *
    starting weblogic with Java version:
    java version "1.6.0_29"
    Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
    Oracle JRockit(R) (build R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-ia32, compiled mode)
    Starting WLS with line:
    D:\Oracle\MIDDLE~1\JROCKI~1.0-1\bin\java -jrockit   -Xms256m -Xmx512m -Dweblogic.Name=URM_server1 -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none  -da -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server  -Dcommon.components.home=D:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1 -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\config\fmwconfig\servers\URM_server1 -Doracle.domain.config.dir=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\config\fmwconfig  -Digf.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\config\fmwconfig\carml  -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\config\fmwconfig\arisidprovider -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\Oracle\MIDDLE~1\user_projects\domains\base_domain1\servers\URM_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol  -Dweblogic.jdbc.remoteEnabled=false  -Dipm.oracle.home=D:\Oracle\Middleware\Oracle_ECM1 -Ducm.oracle.home=D:\Oracle\MIDDLE~1\ORACLE~2 -Dirm.oracle.home=D:\Oracle\Middleware\Oracle_ECM1 -Dem.oracle.home=D:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.55.41:8001  -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath  weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    <Feb 25, 2015 2:46:41 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Feb 25, 2015 2:46:42 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Feb 25, 2015 2:46:42 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-ia32 from Oracle Corporation>
    <Feb 25, 2015 2:46:45 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Feb 25, 2015 2:46:48 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Feb 25, 2015 2:46:48 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Feb 25, 2015 2:46:49 PM IST> <Notice> <LoggingService> <BEA-320400> <The log file D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\logs\URM_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Feb 25, 2015 2:46:49 PM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\logs\URM_server1.log00003. Log messages will continue to be logged in D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\logs\URM_server1.log.>
    <Feb 25, 2015 2:46:49 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\Oracle\Middleware\user_projects\domains\base_domain1\servers\URM_server1\logs\URM_server1.log is opened. All server side log events will be written to this file.>
    <Feb 25, 2015 2:47:26 PM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Feb 25, 2015 2:48:56 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Feb 25, 2015 2:48:57 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Feb 25, 2015 2:50:30 PM IST> <Warning> <JDBC> <BEA-001110> <No test table set up for pool "URMDS". Connections will not be tested.>
    <Feb 25, 2015 2:51:15 PM IST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in D:\Oracle\Middleware\oracle_common\atgpf\modules\oracle.applcore.model_11.1.1\oracle.applcore.model.stub.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Feb 25, 2015 2:51:28 PM IST> <Warning> <Security> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    <Feb 25, 2015 3:05:55 PM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.rules, referenced from: D:\Oracle\Middleware\Oracle_ECM1\soa\modules\oracle.soa.workflow_11.1.1\oracle.soa.workflow.wc.jar]. Make sure the referenced optional package has been deployed as a library.>
    INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
    <Feb 25, 2015 4:53:05 PM IST> <Warning> <oracle.adfinternal.view.faces.partition.FeatureUtils> <ADF_FACES-30130> <Ignoring feature-dependency on feature "AdfDvtCommon".  No such feature exists.>
    IDC Servlet initial class path is D:/Oracle/MIDDLE~1/ORACLE~2/ucm/idc/jlib/idcserver.jar
    Thanks,
    Guru.

  • 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-V 5.0: Adding Visio 2013 and Project 2013 to a previously deployed virtual Office 2013

    Good morning.
    I can successfully deploy Office 2013 via PowerShell and App-V v5.0 without difficulty.  I've read the document at
    http://support.microsoft.com/kb/2915745/en-us and followed all instructions successfully.
    My question is this:  If Office 2013 without Visio 2013 or Project 2013 is virtually deployed, how can those components be added later?
    For instance, we may have 100 users that acquire a virtualized Office 2013 without Project or Visio.  We then may have 25 users that require a virtualized Office and Visio without Project and, perhaps, another 15 that require Office and Project without
    Visio.
    Currently, when I attempt a second virtual deployment of one of these components, it removes Office 2013 making it inaccessible.
    How can Project and/or Visio be deployed to an already existing virtually deployed Office 2013?
    Thanks very much.
    John
    IAmStrings

    As a part of MDOP, you'll also have access to UE-V which will provide a mechanism of moving user preferences across the same applications from difference packages.
    It will require planning, configuration and deployment, but will ensure you don't face the same issue in the future.
    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
    answer your question). This can be beneficial to other community members reading the thread.
    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
    Twitter:
    @stealthpuppy | Blog:
    stealthpuppy.com |
    The Definitive Guide to Delivering Microsoft Office with App-V

  • Deployment Profile items are all greyed out

    I am using Jdev 10.1.3.3.0 with Jheadstart. I created an application and started looking at deploying it as a WAR file. I was able to create a connection to the target Application Server with a Successful test connection. The next step is to create a Deployment Profile for the JDeveloper Project. I am following the Jdeveloper Help step 3.
    Step 3   Create a Deployment Profile for the JDeveloper Project
    Deployment profiles are project components that govern the deployment of a project or application. A deployment profile specifies the format and contents of the archive file that will be created.
    To create a deployment profile:
    In the Applications Navigator, select the project for which you want to create a profile.
    Choose File > New to open the New Gallery.
    In the Categories tree, expand General and select Deployment Profiles.
    In the Items list, select a profile type. For ADF applications, you should select one of the following from the Items list: WAR File EAR File
    You can also select Business Components Archive, if you are using ADF Business Components.
    If the desired item is not found or enabled, make sure you selected the correct project, and select All Technologies in the Filter By dropdown list.
    Click OK.
    I problem is that all the items listed under Deployment Profiles are greyed out.
    Thanks for your help in advance.

    Maybe if I select the right object as the project I would fix my own problem.
    Thanks

  • Database Login Prompt in Deployment PC

    Hi,
    I had developed a WinForm App using VS C# 2008, CR Basic for VS 2008, and SQL Server 2005 Express.
    For the crystal report, I can view it through report viewer without problem in development server, but in deployment/client PC without development tools, the database logon kept prompting even I keyed in the correct logon information and I cannot view the report.
    For your information, I design the crystal report to use OLEDB (ADO) for SQL Server with integrated security. I had tried server authentication too which providing UserID and Passwd but with no luck. I had tried to set the logon info programmatically too but the problem still exists.
    My deployment/client PC is WinXP SP3 and I deployed the CR Basic components by using redistributable bundled with the VS 2008 (located in C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5).
    I wonder is there a problem with CR driver for OLEDB or any else.
    Does anyone encounter the similar problem?
    Thanks for any reply and suggestion.

    Hi;
    Have a look at the following artilce on database troubleshooting: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0225775-88c4-2c10-bd80-8298769293de&overridelayout=true
    One of the suggestions is to create a UDL file, that would be helpful to see if the OLE DB is setup correctly on that system.
    Best Regards,
    Jonathan
    Follow us on Twitter u2013 http://twitter.com/SAPCRNetSup

Maybe you are looking for