Problems with JSPM upgrading NW2004S to SP11

Hi,
I am really frustrated with JSPM
I've installed the sneak preview NW2004S and ran JSPM to upgrade it to SP11.
After 3 days of trials, I was able to get it to the point where it installed part of the SP11 pack.
Now it is stuck at EBPC. It gives the error that portal container runtime is not running. The server is running in safe mode.
I tried to restart the server in normal mode and retry it - but JSPM puts the server back to safe mode.
Any suggestions

I did not finally resolve the SP11 problem since SP12 was released on 5/25.
I'm installing SP12 instead.
Lessons learnt:
1. For some apps like EPBC, its easier to deploy directly with the SDM rather than JSPM.
2. Sneakpreview has extra apps that conflict with applying SP12 patch
so
Undeploy sap.com/TestSuiteUUIE and sap.com/cafUIptn~common
otherwise
Message : Failed to deploy application 'sap.com/tc~wd~samples~testsuite~uuie' for deployment state listener 'com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook'.
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'E:usrsapJ2EJC01j2eeclusterserver0.tempwebdynpropublicsap.comtc~wd~samples~testsuite~uuiewebdynproApplicationscom.sap.tc.webdynpro.tests.uuie.TestSuiteUUIETestSuiteUUIE.xml' into the database. Reason: Development Object 'sap.com/TestSuiteUUIE' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)

Similar Messages

  • Problems with auto upgrade Anyconnect 3.1

    Hello,
    I'm having problem with auto upgrade of Anyconnect 2.5 to 3.1.
    Here is the situation :
    I have ASA5510 running ASA 8.4.5 and clients are running Anyconnect 2.5.3055 and 3.1.00495 with 2 different profiles.
    Clients with 2.5 can upgrade to 3.1 but then receive an "Invalid host entry" when they try to connect with new client. It works if they use FQDN instead of profiles. It's the same situation with Windows 7, Mac OS X and linux.
    If I configure client software back to 2.5 on ASA, it works again for every client.
    Do you have an idea ?
    Thanks for your reply.
    Yann

    I have seen the same behavior on Mac OS X. A couple of points for me:
    If I delete the profiles from /opt/cisco/anyconnect/profile then I can connect once (using the FQDN) but it then downloads the client profile and on next attempted connection it receives "invalid host entry." My profiles use the FQDN of my ASA and both forward and reverse DNS resolution are configured properly.
    My workaround is to remove the AnyConnect Client Profile entirely, but I can get away with that because I have a very simple setup, with all users in one default group. If I had to pass different profile information to different users that would not be a solution.
    Second, better workaround: I just exported the client profile, imported it under a different name, edited the new client profile to remove the server address, and assigned the new profile to the group policy. At their next login, users get all the profile settings and since the client remembers the FQDN they used to connect it doesn't adversely affect the user experience.

  • I want to upgrade from Tiger to Snow Leopard on my 2008 MacPro. How do I avoid problems with the upgrade process?

    I want to upgrade from Tiger to Snow Leopard on my 2008 MacPro. How do I avoid problems with the upgrade process?

    #1 Do a complete bootable backup of your drive before upgrading. That way should anything happen you can revert back to the start and try again.
    Make sure you meet Snow Leopard 10.6 Technical Requirements - http://support.apple.com/kb/SP575
    You might also want to make sure you don't have software issues with SL:
    A Mac OS X 10.6 Snow Leopard Application Compatibility List - http://snowleopard.wikidot.com/

  • Problems with Mavericks upgrade?

    Thinking about uprgrading to Mavericks, but have been coming across a lot of threads/reviews about people losing date and/or having real problems with the process. It's been a while since I've been here, and just wanted to ask for an opinion/advice.  I'm using Snow Leopard 10.6.8.  Should I stay away from it, or if I do, what advice/tips do you have for a smooth upgrade?
    OR -- is it possible to get Mountian Lion Somewhere?  I looked for it in the app store, but couldn't find it.  I heard some negative reviews about Lion, so I just kept Snow Leopard, rather than take any chances with a new OS.

    Mavericks is excellent on my MBP 8,2. Fast and flawless. Faster than Mountain Lion.
    New features I like: iBooks, iCloud keychain, enhanced dictation.
    A few things to consider:
    Any new OS has some bugs and incompatibilities with old software and hardware. If you are uncomfortable with basic Mac troubleshooting, then perhaps waiting would be a better strategy. I didn't have any problems, with installation or after.
    If you have any mission-critical software or peripherals, make sure they are compatible first. Check your apps for compatability here: RoaringApps - Application compatibility and feature support for OS X and iOS
    Mavericks does not play well with some old/bad software and hardware:
    Crapware: anything that purports to "clean", "monitor", "protect", or "accelerate"  your mac. Unnecessary on Macs and often harmful. Examples: CleanMyMac and MacKeeper (the King of Crapware).
    antivirus software. Unnecessary on Macs.
    WD hard drives.
    Before you install Mavericks:
    backup your old system, either with Time Machine, or better yet, a bootable backup.
    have enough RAM. The specs say 2GB, but 4 is probably a more realistic minimum.
    uninstall Crapware, antivirus software, and any other junk you don't need.
    repair your hard drive and permissions with Disk Utility
    boot into safe mode, and then run the installer Mac OS X: What is Safe Boot, Safe Mode?
    ML is available here: OS X Mountain Lion - Apple Store (U.S.)

  • Problems with Vista upgrade on Moduslink

    'COA invalid', 'Irrecoverable Error', 'Alert not Implemented'... these are kind of messages I get from Moduslink. I'm not expecting to reply my emails since they are in neck-deep.
    I love my A100 SAA9E, a very stable and powerful machine. I'm from London and have selected all the right options, but it would either come up with a random COA prob, or an error after my penultimate step.
    What can I do? Help.
    Shawn

    I was unable to complete the Vista upgrade via the Moduslink on Toshiba's website http://wwww.toshiba-europe.com/vista-upgrade, even though I got to paying for the upgrade with my credit card. When my payment was being processed I got an 'unrecoverable error', so I went back to repeat the process and this time the site didn't recognize my COA on the bottom of the laptop.
    I contacted Moduslink via the following Tel No. 00800 666 44 666 (UK) and spoke to one of their support staff (choose options 5 and then 8). There is a problem with their site excepting payments from credit or debit cards. The representative reset my COA, but it takes 48 hours for it to clear (so much from electronic data communications to servers). I have been told to retry the upgrade process again on Friday 16/02/2007, however, this time to pay either by wireless transfer from my bank or send a cheque.
    Hopefully, this will help others who were frustrated with the Vista upgrade debacle. It would be more appropriate however, if the company concerned, Modulink, resolved the issue in the 1st place. Firstly by informing their customers that there was an issue, secondly on a work around to the problem and finally fixing the problem. Will commonsense ever prevail?
    Ala (14/02/2007)
    Message was edited by: Ala_Jackson

  • I could not see how to continue after upgrade to firefox 4. This has never been a problem with ast upgrades. I am finding Firefox to be very user unfriendly for non-tech people.

    I am being told that my current version of firefox is no longer protected. When I tried to upgrade to firefox 4 some time ago, the menu bar(?) was gone--no bookmarks. I set my computer back to an earlier date to get my book marks back and have been afraid to attempt this upgrade again. Firefox also appears to have tried to do the upgrade automatically and says I have incompatible add-ons. I have never had problems with previous updates. I have read negative reviews of firefox 4 and am frankly afraid of it. I hate to leave firefox and am afraid of losing my book marks as well. I find the "Help" forums etc. here extremely difficult to navigate and they seem to be aimed at people who are more tech savy than many of us are.

    #Firefox 3.5.19 which you are using is no longer supported and is not being updated for any issues, including security problems.
    #The Menu Bar (File, Edit, View, History, Bookmarks, Tools, Help) was replaced in Firefox 4 by the "Firefox button" in the upper left corner
    #*You can turn the Menu Bar back on by doing one of the following in Firefox 4:
    #**click Firefox button, click Options, click Menu Bar to select it
    #**HOLD down the ALT key while pressing the keyboard letters VTM
    #**right-click on an empty space in the Navigation Toolbar, then click Menu Bar to select it.
    #Some information about Firefox 4 changes:
    #*https://www.mozilla.com/en-US/firefox/features/
    #*there is a link "watch the video" under '''''Improved Interface''''' on the above page
    #You can make Firefox 4 look more like prior versions: http://www.computertechtips.net/64/make-firefox-4-look-like-ff-3-6/
    Your bookmarks should be safe during the upgrade; they are in a separate place on your hard drive. You should keep them backed-up in case of any problems with your system. See:
    *https://support.mozilla.com/en-US/kb/Backing%20up%20your%20information#w_backing-up-your-profile
    *http://kb.mozillazine.org/Profile_backup
    *http://kb.mozillazine.org/Profile_folder_-_Firefox

  • Problem with PRD upgrade from 4.6C to ECC 6.0

    Hello,
    I'm experiencing a problem with our live Productive system, and hoping for some ideas on how to resolve.  First, we have successfully upgraded our DEV and QA environment, and are now upgrading PRD.  I was successful in getting through the uptime SAPup of our downtime minimized upgrade.  Note that I did not need to log into the Shadow instance at all, because all modifications will be transported from DEV during downtime.
    However, I did want to log into the Shadow instance to take a look at it.  I first had to start the instance in the SAP Management console, and then when I attempted to access via the SAPGUI, I recieved error "Internal TSKH error.  Session terminated".  Also, I noticed that as soon as I started up the Shadow instance, I am now getting "SYSTEM_CANT_CLEAR" short dumps every minute.  Error says:  Error when initializing the work area "SYST".
    Since I don't need to log into the Shadow instance to complete the upgrade, I'm not sure if this is going to be an issue for me or not while I complete the upgrade.
    Any assistance would be greatly appreciated.
    Thank you,
    Leeanna Travis

    Hello,
    I'm experiencing a problem with our live Productive system, and hoping for some ideas on how to resolve.  First, we have successfully upgraded our DEV and QA environment, and are now upgrading PRD.  I was successful in getting through the uptime SAPup of our downtime minimized upgrade.  Note that I did not need to log into the Shadow instance at all, because all modifications will be transported from DEV during downtime.
    However, I did want to log into the Shadow instance to take a look at it.  I first had to start the instance in the SAP Management console, and then when I attempted to access via the SAPGUI, I recieved error "Internal TSKH error.  Session terminated".  Also, I noticed that as soon as I started up the Shadow instance, I am now getting "SYSTEM_CANT_CLEAR" short dumps every minute.  Error says:  Error when initializing the work area "SYST".
    Since I don't need to log into the Shadow instance to complete the upgrade, I'm not sure if this is going to be an issue for me or not while I complete the upgrade.
    Any assistance would be greatly appreciated.
    Thank you,
    Leeanna Travis

  • TS1717 are there problems with iTunes upgrading from Vista to Windows 7?

    are ther problems upgrading iTunes from Vista to Windows 7?

    The best method is to use Windows Easy Transfer first to backup all your data, and do custom clean install. And install all your apps and drivers afterwards.
    Yes it should work. Make sure you are ready, and have all the latest drivers and applications ahead of time.
    There are some "gottchas" with the upgrade from Vista.

  • Problems with license upgrade on AIP-SSM

    Hi guys:
    I have a problem with my AIP-SSM, recently I download the latest license and I need to install in my AIP but when I try to do this I receive this error:
    "errSystemError-idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file"
    So I download the license again, because maybe was corrupted, but I receive the same error at the time I want to install it.
    Does anybody knows what this error means?
    Regards

    It sounds like you are attempting to install a .lic license-key file via the Update Sensor section (which is used for software upgrades/updates instead). If you are trying to install a .lic license-key file, you can do that from IDM or IME's Configuration > Sensor Management > Licensing section. Ensure the Update From: option is set to License File, then click the Browse Local… button and locate/select the .lic license-key file on your local client machine. Finally, click the Update License button to upload and install the license-key file onto the sensor.
    If you try to install a .lic license-key file via the Update Sensor section, then you will encounter the error message you noted.

  • Problems with RAM upgrade iMac G5 1.8GHz

    Stuck - Need Help!
    I've previously upgraded up iMac to 2 500Mb RAMs and felt recently that it needed that little bit extra, so I ordered two 1Gb chips from crucial.
    Followed instructions to T, but with the two new chips in, the machine won't load.
    Interestingly, it boots up with the following RAM combinations
    old 500MB + new 1GB (in any combination) - recognised as 1.5GB
    one new 1GB RAM (again either one) - recognised as 1GB
    I spoke to crucial who said that as the RAMs work individually, there isn't a problem with them, it could be a Firmware issue. I've upgraded all my software, and don't know what to do next?
    Anyone overcome a similar problem in the past?
    Thanks

    I'm experiencing something very similar to shaow. I'll share my experience in gory details - sorry for the long post but I've spent more hours trying to stabilize. I should have worked the hours at walmart and bought a new iMac with the money I could have earned
    Anyway, here goes:
    Two iMac G5 1.8Ghz 17" (both Fall 2005 model), will call one A and the other B.
    Prior to attempting ram upgrade: A, config working fine: both a config using 1GB slot 1, 256MB slot 2 and a single 1 PC3200 1GB stick. OS X 10.4-10.5.7. No problems. I did have the motherboard replaced under warranty after having sleep problems - capacitors were expanded. No problems since that motherboard swap.
    Prior to attempting ram upgrade: B, config working fine: 2 x 256MB sticks. OS X 10.3.9
    Ordered 3 PC3200 400Mhz 1GB sticks from Data Memory Systems.
    Upgraded A: Added 1GB stick = 2GB total
    Upgraded B: Removed both 256MB sticks from B and added two 1GB sticks = 2GB total
    Booted B, experienced gray screen of death with the multi-language crash message - somethign like: 'Please hold down the power button and restart'. Power cycled B, booted off a retail box DVD of OS X 10.5.6. Began upgrade to 10.5.6. Gray screen of death part way thru upgrade. Power cycled, gray screen of death again during early boot phase.
    Decided to run tests on B. I could not locate the Apple Hardware Test (neither on system dvd 1 nor on a separate DVD). I resorted to using TechnoTools Deluxe which was included with AppleCare box. No hardware problems found including on the 2GB memory.
    Removed both new 1GB sticks, pulled older working 1GB stick from A and installed into B. Completed upgrade with just 1GB memory on B to 10.5.6 and subsequently pulled down all updates for OS X 10.5.8. Powered down, added second 1GB stick to B, booted into 10.5.8 successfully. Repaired disk permissions, restarted. Began using applications, then after only about 5 minutes experienced gray screen of death. Powered down, removed new 1GB stick, replaced with one of the two remaining new 1GB sticks. Read about reseting PRAM/NVRAM. Followed steps to reset PRAM then decided to do the reset NVRAM within openfirmware. Started back up and logged into 10.5.8. Ran several applications - did not experience gray screen of death after about 20 minutes use. Have not had time for further tests on B yet.
    Back to my saga with A (my original iMac G5 that was working fine with 1GB stick on 10.5.7):
    Called Data Memory Systems and they sent me a replacement for the 'bad' 1GB stick.
    While I was waiting for the new 1GB stick from DMS, I was struggling to get machine fully updated. Software Updater was failing with the weird network error (network was fine) and after following steps to troubleshoot, I backed up the user accounts and decided to reinstall OS X fresh from the 10.5.6 retail box (family license). Finally, I had OS X 10.5.8 all fully updated on the 1GB iMac G5 (A).
    New memory arrived, installed 2nd 1GB stick. Booted up, immediately I got the gray screen of death. Restarted, booted up got about 5-15 minutes use then gray screen of death. Puzzled, I called DMS who said unlikely I got 2 bad sticks. They suggested I try memtest. So I did...
    So on A, I first ran memtest from single user mode on the 2GB config. It crashed immediately with some 'Unexpected' error. Did not look like a memory error. I powered down, removed 2nd 1GB stick, and ran memtest from single user on the 1GB stick. Ran all tests 3x over a couple hours - no problems found. Retested after swapping the 1GB stick for the other. Both tested fine. Installed both sticks again and ran memtest all tests, one pass (didn't want another 6 hours lost) on the 2GB config, and all tests passed. Booted up and got gray screen of death - I don't recall if it was on bootup or after running but I ran fsck with no disk problems found, then restarted, logged in, ran disk utility to repair all permissions. Some repairs were made. Restarted A, reset PRAM and NVRAM again, booted successfully.
    I haven't had much time to run extensively apps on A yet. It's sleeping as I type this on another mac. My next test will be to reset SMU.
    I'm starting to wonder if the original iMac G5 has firmware problems that would prevent it from being unstable with two 1GB sticks??? My experience on two identical models of iMac G5 plus reading this post with VERY similar behaviors and after all the normal tests. I've concluded the memory is A-OK and something more sinister is lurking...
    Any thoughts are appreciated.

  • Problems with new upgrade

    Is anyone having problems with the new IOS 6 upgrade. I couldn't log into my iTunes account and the maps app, which I use loads is now rubbish! Can it be uninstalled without losing everything I've put on the iPad since purchase.

    It is not possible to uninstall or downgrade iOS 6.

  • Problem with N73 upgrade v4 and connectivity to gp...

    N73 working fine especially with tomtom v6 and gps receiver, however silly me decided to upgrade firmware and on doing so, now gps receiver is found but not allowed to work. Has anyone elese had this issue with N73 upgrade and tomtom and or bluetooth. The person with a fix gets a reward in heaven!

    Did you try uninstalling and then reinstalling TomTom?

  • Problems with downloading upgraded iOS

    I downloaded the 4.2.1 software onto my 3G phone and even though I transferred purchased apps and music and backed up everything, my purchased items are not on my phone.  Worse I can't download any new apps; they appear on the screen like they are going to download, but then they vanish.  What's going on?

    But what happened to the apps I already had?  I didn't have a problem before I upgraded.

  • Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE

    Hello Expert,
    I have a problem when a try to execute the upgrade in the phase
    DEPLOY_ONLINE,
    <<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
    Trouble Ticket Report
    Upgrade to SAP NetWeaver'04s
    SID................: J2E
    Hostname...........: sapepd
    Install directory..: d:/usr/sap/J2E
    Upgrade directory..: D:\SAPEPD\saploc\jupgrade
    Database...........: Microsoft SQL Server
    Operating System...: NT
    JDK version........: 1.4.2_11 Sun Microsystems Inc.
    SAPJup version.....: 1.1.101
    Source release.....: 630
    Target release.....: 700
    Current usages.....: EP;AS;DI
    ABAP stack present.: false
    The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
    Error while executing SDM process phase with action DEPLOY_SLOT. See
    D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
    Cannot execute Java process for deployList with parameters
    D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.
    Return code condition success evaluated to false for process java.exe
    for action ACTION_DEPLOY_LIST.
    More information can be found in the log file
    D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
    Use the information provided to trouble-shoot the problem. There might
    be an OSS note providing a solution to this problem. Search for OSS
    notes with the following search terms:
    com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
    com.sap.sdt.ucp.phases.PhaseException
    Error while executing SDM process phase with action DEPLOY_SLOT. See
    D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
    DEPLOY_ONLINE
    UPGRADE
    NetWeaver Upgrade
    SAPJup
    Java Upgrade
    <<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
    THE FILE: DEPLOY_ONLINE_DON_01.LOG
    BEGIN DEPLOY_ONLINE_DON_01.LOG----
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
    <!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
    #1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
    #1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#action#DEPLOY_SLOT#
    #1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java###  Parameter =#2#connect#standard#
    #1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
    #1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
    #1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
    #1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
    #1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2#  #C:
    j2sdk
    jre
    bin
    java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
    usr
    sap
    J2E
    JC00
    SDM
    program
    bin
    SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.LOG#
    #1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2#  #D:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.OUT#
    #1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
    #1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
    #1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
    #1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
    #1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
    #1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
    SAPEPD
    saploc
    jupgrade
    log
    DEPLOY_SLOT_0__DON_01.LOG for details.##
    #1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
    #1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
    #1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
    #1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
    #1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    *************END  DEPLOY_ONLINE_DON_01.LOG*******************
    FILE ************** DEPLOY_SLOT_0__DON_01.LOG
    BEGIN  DEPLOY_SLOT_0__DON_01.LOG----
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:33 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:33 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:33 PM  Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:33 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
    Jul 18, 2007 3:18:33 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:33 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:36 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:33 -  ***********************************************************
    07/07/18 15:18:34 -  Start updating EAR file...
    07/07/18 15:18:34 -  start-up mode is lazy
    07/07/18 15:18:34 -  EAR file updated successfully for 172ms.
    07/07/18 15:18:34 -  Start deploying ...
    07/07/18 15:18:34 -  EAR file uploaded to server for 500ms.
    07/07/18 15:18:36 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
                         Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
                              com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                              at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    07/07/18 15:18:36 -  ***********************************************************
    Jul 18, 2007 3:18:36 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:36 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:36 PM  Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
    Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
         com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 18, 2007 3:18:36 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:36 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:36 PM  Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
    Jul 18, 2007 3:18:36 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
    Jul 18, 2007 3:18:36 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:36 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:39 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:36 -  ***********************************************************
    07/07/18 15:18:36 -  Start updating EAR file...
    07/07/18 15:18:36 -  start-up mode is lazy
    07/07/18 15:18:37 -  EAR file updated successfully for 375ms.
    07/07/18 15:18:37 -  Start updating...
    07/07/18 15:18:37 -  EAR file uploaded to server for 422ms.
    07/07/18 15:18:39 -  Successfully updated. Update took 1641ms.
    07/07/18 15:18:39 -  Deploy Service status:
    07/07/18 15:18:39 -    Application : sap.com/tcwdtools
    07/07/18 15:18:39 -   
    07/07/18 15:18:39 -    sap.com/tcwdtools  - WEBDYNPRO
    07/07/18 15:18:39 -    sap.com/tcwdtools monitoring configuration  - MONITORING CONFIGURATION
    07/07/18 15:18:39 -  ***********************************************************
    Jul 18, 2007 3:18:39 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:39 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:39 PM  Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:39 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:40 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:40 PM  Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
    Jul 18, 2007 3:18:40 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
    Jul 18, 2007 3:18:40 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:40 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:40 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:40 -  ***********************************************************
    07/07/18 15:18:40 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
    07/07/18 15:18:40 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
    Jul 18, 2007 3:18:40 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:40 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:40 PM  Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
    Jul 18, 2007 3:18:40 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:41 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:41 PM  Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:41 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
    Jul 18, 2007 3:18:41 PM  Info: Software type of SDA: J2EE
    Jul 18, 2007 3:18:41 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:49 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:41 -  ***********************************************************
    07/07/18 15:18:41 -  Start updating EAR file...
    07/07/18 15:18:41 -  start-up mode is lazy
    07/07/18 15:18:42 -  EAR file updated successfully for 1000ms.
    07/07/18 15:18:42 -  Start deploying ...
    07/07/18 15:18:43 -  EAR file uploaded to server for 891ms.
    07/07/18 15:18:48 -  Successfully deployed. Deployment took 5375ms.
    07/07/18 15:18:48 -    Application : sap.com/tc~workflowmodeler
    07/07/18 15:18:48 -   
    07/07/18 15:18:48 -    /Application/WorkflowModeler  - LOGGING CONFIGURATION
    07/07/18 15:18:48 -    com.sap.workflowmodeler.modeler  - LOGGING CONFIGURATION
    07/07/18 15:18:48 -    workflowBean  - EJB
    07/07/18 15:18:48 -    WorkflowConnection  - EJB
    07/07/18 15:18:48 -    Modeler  - WEB
    07/07/18 15:18:48 -    sap.com/tc~workflowmodeler monitoring configuration  - MONITORING CONFIGURATION
    07/07/18 15:18:48 -  ***********************************************************
    Jul 18, 2007 3:18:49 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:49 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 18, 2007 3:18:49 PM  Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    The application start is forbidden, because of the server mode and action.
    Jul 18, 2007 3:18:49 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:49 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:49 PM  Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
    Jul 18, 2007 3:18:49 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
    Jul 18, 2007 3:18:49 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:49 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:49 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:49 -  ***********************************************************
    07/07/18 15:18:49 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
    07/07/18 15:18:49 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
    Jul 18, 2007 3:18:49 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:49 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
    Jul 18, 2007 3:18:50 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:50 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:50 PM  Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
    Jul 18, 2007 3:18:50 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
    Jul 18, 2007 3:18:50 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:50 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:50 -  ***********************************************************
    07/07/18 15:18:50 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
    07/07/18 15:18:50 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
    Jul 18, 2007 3:18:50 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:50 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:50 PM  Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
    Jul 18, 2007 3:18:50 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:51 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:51 PM  Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
    Jul 18, 2007 3:18:51 PM  Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
    Jul 18, 2007 3:18:51 PM  Info: Software type of SDA: library
    Jul 18, 2007 3:18:51 PM  Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:52 PM  Info: Begin of log messages of the target system:
    07/07/18 15:18:51 -  ***********************************************************
    07/07/18 15:18:51 -  Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
    07/07/18 15:18:52 -  Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
    Jul 18, 2007 3:18:52 PM  Info: End of log messages of the target system.
    Jul 18, 2007 3:18:52 PM  Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jul 18, 2007 3:18:52 PM  Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
    Jul 18, 2007 3:18:52 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:52 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:52 PM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
    Jul 18, 2007 3:18:52 PM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
    Failed deployment of SDAs:
    development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
    Please, look at error logs above for more information!
    Jul 18, 2007 3:18:52 PM  Info: Starting to save the repository
    Jul 18, 2007 3:18:52 PM  Info: Finished saving the repository
    Jul 18, 2007 3:18:52 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 18, 2007 3:18:52 PM  Error: -
    At least one of the Deployments failed -
    Jul 18, 2007 3:18:53 PM  Info: Summarizing the deployment results:
    Jul 18, 2007 3:18:53 PM  Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
    Jul 18, 2007 3:18:53 PM  Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
    Jul 18, 2007 3:18:53 PM  Error: Processing error. Return code: 4
    END  DEPLOY_SLOT_0__DON_01.LOG----
    I SAW the SDN forum and talk about the question
    Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
    but this one doesnu00B4t work
    best regards
    Luis Moreno

    Hi
    I resolved the issue by undeploying the TestSuiteUUIE  component using SDM.
    Thanks
    Naresh P.

  • Duplex printing problem with Reader Upgrade

    I upgraded Acrobat Reader 10.1.8 to 11.0.4 and can no longer access fast or duplex printing for PDF's. I have a Canon MP970 printer for 3 years and have always been able to do both fast printing and duplex printing of PDF's.
    How do I resolve?

    I have an identical issue to neuegestaltung, but with an HP 5500. I can print single-sided to A3/tabloid successfully but when I try printing duplex the right quarter of the page is cut off on both sides - almost as if it thinks it's printing portrait.
    Applications affected include Adobe Acrobat 8 and 9, Adobe CS3 and CS4 applications including InDesign.
    Preview works fine, but of course the colour balance makes the output unusable.
    OS 10.6.2, print driver HP Color LaserJet 5500 v 3010.107.
    Using the Gutenprint driver I can't either do A3 or colour so there is no solution there.
    Worked fully and correctly with the same apps under 10.5.x.
    At the moment I am running Windows XP under VMWare to print from Acrobat, which is plainly silly.
    Any useful* observations, suggestions or workarounds welcome.
    *Needless to say, "It's Adobe's problem" or similar are not acceptable responses. It may well be an interaction between the Adobe's applications and Apple's printing system and/or driver of course; in that case the companies need to collaborate to solve the issue.

Maybe you are looking for

  • HP PhotoSmart C4599 problems with Wireless on Windows 7 x64

    Hello, I have a printer HP PhotoSmart C4599 running great on my Windows 7, but the problem is the Wireless of the printer. I've got a laptop (running on Windows Vista x86) that I use to print documents via Wireless and when i try to add the printer b

  • User-Defined Fields Window

    Hi All, I have one issue with the User-Defined Fields window of the ACTIVITY form. I had added some user defined fields (UDF) to the Activities so that the User-Defined Fields are displaying in a separate window just near to the Activity window with

  • Choice list in af:query turns into inputText when AM pooling is disabled

    Hi all, I have a choice list field in an af:query search area. This field is based on attribute FlagYN VARCHAR2(1) and is bound to a list of values. When AM pooling is disabled, executing the search makes that field loose its Display property and sea

  • Runtime.exec error in windows

    When i try to run an external program with Runtime.exec() in windows 2000, i get a windows pop-up with the following error msg: d:\winnt\system32\ntvdm.exe Error while setting up environment for the application. I have no idea how to fix this since i

  • StageVideo in Air 2.5?

    Hi, How do I get StageVideo in Air ?