Deployment of MAM30 Patch 1 failed in SDM

Hello,
When I try to deploy the sda file XMAM30_3.000301.sda for MAM30 Patch 1 I get this error:
Starting Deployment of XAP-MBA-MAM-LPT
Aborted: development component 'XAP-MBA-MAM-LPT'/'sap.com'/'SAP AG'/'150.20070202191543.0000'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XAP-MBA-MAM-LPT.. Reason: Error while getting container files from EAR E:\usr\sap\CB3\DVEBMGS13\j2ee\cluster\server0\.\temp\deploy\work\deploying\XAP-MBA-MAM-LPT.ear in operation update with application sap.com/XAP-MBA-MAM-LPT.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Error while getting container files from EAR E:\usr\sap\CB3\DVEBMGS13\j2ee\cluster\server0\.\temp\deploy\work\deploying\XAP-MBA-MAM-LPT.ear in operation update with application sap.com/XAP-MBA-MAM-LPT.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of XAP-MBA-MAM-LPT finished with Error (Duration 3859 ms)
What does this error mean? When I make the sda file myself ( based on the zip file included ) with the mobile archive convertor in NetWeaver Mobile Administrator and then deploy I get no error.
Kind regards,
jeroen

Hello,
What do you mean by:
Finally, you shuold not upload the patch, but the complete version since merepmeta and listdef.xml have change. Otherwise, some fix won't be fixed.
Note 1024148 - How to deploy a patch for xApp Mobile Asset Management 3.0 or 1018248 - SAP xApp Mobile Asset Management SR3 PL01 does not describe things like this. It also says:
You will find that it contains 4 additional zip files. Extract each of these zip files. Each of them in turn contain the following:
[patch name].zip: actual patch file to be deployed to mobile clients with Mobile Infrastructure versions 2.5 SP17 or below.
[patch name].sda: actual patch file to be deployed to mobile clients with Mobile Infrastructure versions 2.5 SP18 and above, or 7.0 SP09 and above.
[patch name]_src.zip: source code with changes from PL0.
SyncBO.zip: syncBO definitions with changes from PL0(to be applied to the middleware)
And :
Uploading to the Mobile Administrator (Administrator) - For MI 7
You must upload MAM*.sda if you are using Mobile Asset Management.
      8. Connect to the SDM server via the Software Deployment Manager GUI.
      9. Choose the .sda files that you want to upload onto the server.
      10. Click on the "Deploy" button.
I don't understand why SAP ships an .sda file if it can't be used... I didn't change anything for the standard XMAM30 SR3 installation so I supposed I could apply this path with the same ease...

Similar Messages

  • Deployment of JAVA-Patches with SUM failed, MOPZ has downloaded malicious code

    some time ago, we did an upgrade of our doublestack PI-System from NW-PI-700-SPS18 to NW-PI-731-SPS05.
    Now, i wanted to upgrade this PI-system from NW-PI-731-SPS05 to NW-PI-731-SPS07.
    with SUM 1.0 SP10 PL4 we are now failing in the Execution-phase (Downtime):
    Error in phase 5.6. execution (downtime) of the JAVA-Part
    F  ********************************************************************************
    F  *** ERROR => Node 'deployment' failed with exit code 67.
    F  ***
    F  *** Please see section 'Failures in the 'deploying offline components' phase'
    F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
    F  ********************************************************************************
    and the instance could not start up anymore !?
    in sap-note 1316652 there is mentioned a separate sap-note 1550641 for this error
    http://service.sap.com/sap/support/notes/1316652
    in sap-note 1550641 - Update fails-Node 'deployment' failed with exit code 67.           
    http://service.sap.com/sap/support/notes/1550641
    Solution:
    A fix cannot be deployed as a patch, because the deployer itself is broken.
    The solution is to reset a back up state of the system, to download the new version of the stack from SAP Marketplace, and to rerun the update/upgrade procedure.
    i downloaded the patch-stack (with Solman MOPZ) some days ago,
    so MOPZ did download the malicious code of deployment components..... ?!
    so what to do?

    Hi,
    sorry for my late reply,
    but the whole story needs a lot of time (nearly 2 month) and finally ends successfully.
    first: (summary) the main-title of this thread is wrong,
    it was not MOPZ or Solman download, what caused this issue.
    the problem was caused by a remaining (old) sapxmltoolkit.jar in the java-bootstrap folder
    details are coming ...
    (all dates in yyyy-mm-dd)
    =========================================
    2014-05-16 at 13:04 CET: 
    SUM upgrade hangs with java-server did not start (in phase 5.2. Execution = downtime)
    i opend OSS-ticket with several details + logs attached and opened the connection to our system.
    SAP-Ticket, prio_Medium (because it is "only" a sandbox issue),
    2014-05-30 at 20:21 CET:
    1."sign-of-live" from sap-support,
    Asking for additional logfiles from the work-directory of the sap-system
    2014-06-02 at 11:14 CET:
    my Answer to the questions and adding the demanded logfiles.
    2014-06-02 at 21:57 CET:
    2.answer from SAP-support, asking to repeat the last SUM-step, to see, if the issue is still there
    2014-06-03 at 10:22 CET:
    my answer after repeating SUM-step and attaching new logfiles.
    2014-06-03 at 21:18 CET:
    3.answer from SAP-support, i should check if system is up and running, if hostname, port-no is correct.
    2014-06-03 at 10:22 CET:
    my answer: hostname + portnr are o.k. - but system still did not startup (java-server)
    2014-06-04 at 19:30 CET:
    4.answer from SAP-support, delivering an upload-URL, could not read attached splitted .zip-files of log-files
    2014-06-05 at 07:28 CET:
    i did collect all logfiles again and uploaded them to the 1.upload-URL
    2014-06-05 at 16:48 CET:
    5.answer from SAP-support, give hint to sap-note: 1550641 - Update fails-Node 'deployment' failed with exit code 67
    2014-06-06 at 10:17 CET:
    i answered that (in my opinion) the mentioned sap-note did not match the issue (only to NW-7.00) ,
    because i did not have to change anything, only i should do a restore from tape and start SUM from the beginning,
    i insisted in more and deeper investigations by SAP-support.
    2014-06-06 at 19:00 CET:
    6.answer of SAP-support: moving the ticket to the next support-level (developm.support)
    2014-06-09 at 10:11 CET:
    7.answer from SAP-support: asking for new submittion of logfiles of work-dir.
    2014-06-10 at 08:39 CET:
    asking for a new upload-URL because of large logfiles
    2014-06-10 at 17:31 CET:
    8.answer from SAP-support: providing an new upload-URL
    2014-06-10 at 17:53 CET:
    i did collect all logfiles again and uploaded them to the 2.upload-URL
    2014-06-12 at 09:07 CET:
    9.answer from SAP-support: asking for more details, listings of directory-content of ..../j2ee/cluster/...
    2014-06-12 at 10:23 CET:
    i did collect all dir-infos and attached a doc to the ticket
    2014-06-19 at 10:11 CET:
    10.answer from SAP-support: asking for WTS-connection to start investigate and debung on our systems
    2014-06-23 at 10:44 CET:
    i answered, and provided WTS-connection info
    2014-06-26 at 13:12 CET:
    11.answer from SAP-support: could not see a running SID-engine, no SAP-MC, no directory, no folder, where is the engine?
    2014-06-27 at 08:01 CET:
    i answered, and provided detailed server-info and WTS-connection info,
    remembering that SID is in SUM-downtime and java-server is not running, because could not be startet,
    2014-06-30 at 14:01 CET:
    12.answer from SAP-support: asking for an installed java6-sdk(jdk), the java6-jre is not enough to debug.
    2014-07-02 at 11:40 CET:
    my answer after installing java6-sdk on the WTS-server,
    2014-07-07 at 15:11 CET:
    13.answer from SAP-support: after debugging found an very old sapxmltoolkit.jar in the java-bootstrap folder
    moving the ticket to SUM-support - java-developm-support.
    2014-07-09 at 08:36 CET:
    14.answer from SAP-support: (SUM-support - java-developm-support) asking for attaching the SUM stack-xml file to the ticket.
    2014-07-09 at 14:32 CET:
    16.answer from SAP-support: asking to remove the sapxmltoolkit.jar from the java-bootstrap folder and restart SUM (repeat last step)
    2014-07-09 at 15:00 CET:
    i am happy to get the solution to this issue, 
    after removing the .jar file from java-bootstrap folder, SUM restart last step,
    the SUM-phase execution continues to run, java-server could start, ....
    .... finally SUM ended successfully.
    ==================================
    remarks:
    formerly, we did a copy of that mentioned sapxmltoolkit.jar to the java-bootstrap folder (in March 2013) because of investigation PI-processes
    after upgrading from NW-7.00 to NW-7.31, to get PI-system running after upgrade to NW-7.31
    but maybe that formerly issues were caused by other things, cache or so ...
    and since then (March 2013) we could start/stop that PI-system several times without any problem, only SUM-upgrade could not ......
    i really understand that investigating problems in SAP-software (e.g. SUM-process, java-startup ...) is not easy and could have many causes.
    but in summary this SUM-downtime was really large (55 days of downtime) , because of sandbox-system we want to investigate this time,
    to get the solution to this issue.
    if some SAP people want to look for speed-up options in the whole support-process, the OSS_ticket-no is:  ( 459757 / 2014 )
    Thanks to SAP-support (for the helpful solution)
    Christoph

  • Deployment failed in SDM ( SP8 to SP16)

    hi
    i am updating solman 4.0 SP8 to SP16, i have updated kernel and JSPM version to letest level.
    i have copied all .SCA files and XML file to eps/in folder...i have started java update from JSPM..
    java update failed in JSPM, so i have switched to safemode=NO and restarted java engine..
    I tried this with SIDADM and Administrator also, but same error
    after that from SDM i selected the all .SCA files...loading archives done with below error.
    Summary:
    ========
      There were 27 archives selected.
      18 archives successfully loaded.
       Loading of 9 archives failed.
    Details:
    ========
    1) Error loading archive
        D:\usr\sap\trans\EPS\in\ADSSAP15_0-10003001.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\ADSSAP15_0-10003001.SCA)
        There is already a component of the same type with identical name 'ADSSAP' and vendor 'sap.com' selected.
    2) Error loading archive
        D:\usr\sap\trans\EPS\in\CAF15_0-10003464.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\CAF15_0-10003464.SCA)
        There is already a component of the same type with identical name 'CAF' and vendor 'sap.com' selected.
    3) Error loading archive
        D:\usr\sap\trans\EPS\in\CAFUM15_0-10003472.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\CAFUM15_0-10003472.SCA)
        There is already a component of the same type with identical name 'CAF-UM' and vendor 'sap.com' selected.
    4) Error loading archive
        D:\usr\sap\trans\EPS\in\LMSERVICE15_0-20001429.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\LMSERVICE15_0-20001429.SCA)
        There is already a component of the same type with identical name 'LM-SERVICE' and vendor 'sap.com' selected.
    5) Error loading archive
        D:\usr\sap\trans\EPS\in\SAPBUILDT15_0-10003479.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\SAPBUILDT15_0-10003479.SCA)
        There is already a component of the same type with identical name 'SAP_BUILDT' and vendor 'sap.com' selected.
    6) Error loading archive
        D:\usr\sap\trans\EPS\in\SAPJEE15_0-10003469.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\SAPJEE15_0-10003469.SCA)
        There is already a component of the same type with identical name 'SAP-JEE' and vendor 'sap.com' selected.
    7) Error loading archive
        D:\usr\sap\trans\EPS\in\SAPJEECOR15_0-10003466.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\SAPJEECOR15_0-10003466.SCA)
        There is already a component of the same type with identical name 'SAP-JEECOR' and vendor 'sap.com' selected.
    8) Error loading archive
        D:\usr\sap\trans\EPS\in\SAPJTECHF15_0-10003468.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\SAPJTECHF15_0-10003468.SCA)
        There is already a component of the same type with identical name 'SAP_JTECHF' and vendor 'sap.com' selected.
    9) Error loading archive
        D:\usr\sap\trans\EPS\in\SAPJTECHS15_0-10003467.SCA
        (server side name is: D:\usr\sap\trans\EPS\in\SAPJTECHS15_0-10003467.SCA)
        There is already a component of the same type with identical name 'SAP_JTECHS' and vendor 'sap.com' selected.
    After that i have started deployment from SDM, but failed with below error.
    =======================================================================
    Log from SDM:
    ===========================================================================
    Deployment started Tue Jan 08 15:29:23 GMT+05:30 2008
    ===========================================================================
    Starting Deployment of tc/smd/cptdict
    Finished successfully: development component 'tc/smd/cptdict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/smd/cptdict finished successfully (Duration 8437 ms)
    Starting Deployment of SAP_BUILDT
    Finished successfully: software component 'SAP_BUILDT'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071117141300''/'0'
    Deployment of SAP_BUILDT finished successfully (Duration 5454 ms)
    Starting Deployment of tc/smd/datamgmt/dict
    Finished successfully: development component 'tc/smd/datamgmt/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/smd/datamgmt/dict finished successfully (Duration 5891 ms)
    Starting Deployment of tc/smd/server/service
    The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
    It could take some time, so please be patient.
    Finished successfully: development component 'tc/smd/server/service'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
    Deployment of tc/smd/server/service finished successfully (Duration 20954 ms)
    Starting Deployment of tc/webadministrator/ccrep/dict
    Finished successfully: development component 'tc/webadministrator/ccrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/ccrep/dict finished successfully (Duration 13625 ms)
    Starting Deployment of tc/webadministrator/ewa/dict
    Finished successfully: development component 'tc/webadministrator/ewa/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/ewa/dict finished successfully (Duration 6703 ms)
    Starting Deployment of tc/webadministrator/fvrep/dict
    Finished successfully: development component 'tc/webadministrator/fvrep/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
    Deployment of tc/webadministrator/fvrep/dict finished successfully (Duration 6812 ms)
    Starting Deployment of tc/webadministrator/httpanalysis/dict
    Finished successfully: development component 'tc/webadministrator/httpanalysis/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/httpanalysis/dict finished successfully (Duration 5734 ms)
    Starting Deployment of tc/webadministrator/lib/dict
    Finished successfully: development component 'tc/webadministrator/lib/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/lib/dict finished successfully (Duration 5875 ms)
    Starting Deployment of tc/webadministrator/lib/dbc
    Finished successfully: development component 'tc/webadministrator/lib/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/lib/dbc finished successfully (Duration 5563 ms)
    Starting Deployment of tc/webadministrator/logviewer/dict
    Finished with warnings: development component 'tc/webadministrator/logviewer/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by :
    No further description found.
    Deployment of tc/webadministrator/logviewer/dict finished with Warning (Duration 6078 ms)
    Starting Deployment of tc/webadministrator/navigation/dict
    Finished successfully: development component 'tc/webadministrator/navigation/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/navigation/dict finished successfully (Duration 7375 ms)
    Starting Deployment of tc/webadministrator/navigation/dbc
    Finished successfully: development component 'tc/webadministrator/navigation/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/navigation/dbc finished successfully (Duration 7671 ms)
    Starting Deployment of tc/webadministrator/scheduler/dict
    Finished successfully: development component 'tc/webadministrator/scheduler/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
    Deployment of tc/webadministrator/scheduler/dict finished successfully (Duration 6047 ms)
    Starting Deployment of tc/webadministrator/screp/dict
    Finished successfully: development component 'tc/webadministrator/screp/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/screp/dict finished successfully (Duration 6485 ms)
    Starting Deployment of tc/webadministrator/screp/dbc
    Finished successfully: development component 'tc/webadministrator/screp/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
    Deployment of tc/webadministrator/screp/dbc finished successfully (Duration 5562 ms)
    Starting Deployment of tc/webadministrator/selfcheck/dict
    Finished successfully: development component 'tc/webadministrator/selfcheck/dict'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by
    Deployment of tc/webadministrator/selfcheck/dict finished successfully (Duration 5968 ms)
    Starting Deployment of tc/webadministrator/selfcheck/dbc
    Finished successfully: development component 'tc/webadministrator/selfcheck/dbc'/'sap.com'/'SAP AG'/'7.0014.20080122064620.0000'/'0', grouped by software component 'LM-SERVICE'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20080122073158''/'0'
    Deployment of tc/webadministrator/selfcheck/dbc finished successfully (Duration 5500 ms)
    Starting Deployment of DocumentServicesLicenseManager
    The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
    It could take some time, so please be patient.
    Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'2', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of DocumentServicesLicenseManager finished with Error (Duration 323422 ms)
    Starting Deployment of AdobeDocumentServices
    Deployment of AdobeDocumentServices was skipped (Duration 5329 ms)
    Starting Deployment of tc/ads/grmg
    Aborted: development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'2', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of tc/ads/grmg finished with Error (Duration 6047 ms)
    Starting Deployment of ADSSAP
    Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071118055147''/'0':
    Failed deployment of SDAs:
    development component 'AdobeDocumentServices'/'com.adobe'/'Adobe Systems'/'800.20070708051308.406522'/'2' : skipped
    development component 'tc/ads/grmg'/'sap.com'/'SAP AG'/'7.0010.20061002104728.0000'/'2' : aborted
    development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'800.20070306123954.374077'/'2' : aborted
    Please, look at error logs above for more information!
    Deployment of ADSSAP finished with Error (Duration 5782 ms)
    Starting Deployment of bi/mmr/browser_ea
    Aborted: development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of bi/mmr/browser_ea finished with Error (Duration 6266 ms)
    Starting Deployment of bi/mmr/cwm_1.0_source
    Aborted: development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of bi/mmr/cwm_1.0_source finished with Error (Duration 7750 ms)
    Starting Deployment of bi/mmr/miniMetaModel
    Aborted: development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of bi/mmr/miniMetaModel finished with Error (Duration 5860 ms)
    Starting Deployment of bi/mmr/mini_md350
    Aborted: development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1', grouped by software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of bi/mmr/mini_md350 finished with Error (Duration 5750 ms)
    Starting Deployment of BI_MMR
    Aborted: software component 'BI_MMR'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072334''/'1':
    Failed deployment of SDAs:
    development component 'bi/mmr/mini_md350'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
    development component 'bi/mmr/miniMetaModel'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
    development component 'bi/mmr/browser_ea'/'sap.com'/'SAP AG'/'7.0011.20070124085018.0000'/'1' : aborted
    development component 'bi/mmr/cwm_1.0_source'/'sap.com'/'SAP AG'/'7.0015.20080131095802.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Deployment of BI_MMR finished with Error (Duration 5672 ms)
    Starting Deployment of caf/um/metadata/actions
    Aborted: development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'1', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/metadata/actions finished with Error (Duration 6172 ms)
    Starting Deployment of caf/um/metadata/content
    Aborted: development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/metadata/content finished with Error (Duration 5828 ms)
    Starting Deployment of caf/um/metadata/example
    Aborted: development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'1', grouped by software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/metadata/example finished with Error (Duration 5844 ms)
    Starting Deployment of caf/um/metadata/testwd
    Aborted: development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/metadata/testwd finished with Error (Duration 6078 ms)
    Starting Deployment of caf/um/relgroups/admin
    Aborted: development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/relgroups/admin finished with Error (Duration 5797 ms)
    Starting Deployment of caf/um/relgroups/test
    Aborted: development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of caf/um/relgroups/test finished with Error (Duration 5891 ms)
    Starting Deployment of CAF-UM
    Aborted: software component 'CAF-UM'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071117062847''/'0':
    Failed deployment of SDAs:
    development component 'caf/um/metadata/example'/'sap.com'/'MAIN_APL70VAL_C'/'963657'/'1' : aborted
    development component 'caf/um/metadata/content'/'sap.com'/'MAIN_APL70VAL_C'/'1497172'/'1' : aborted
    development component 'caf/um/metadata/testwd'/'sap.com'/'MAIN_APL70VAL_C'/'963659'/'1' : aborted
    development component 'caf/um/metadata/actions'/'sap.com'/'MAIN_APL70VAL_C'/'1077265'/'1' : aborted
    development component 'caf/um/relgroups/test'/'sap.com'/'MAIN_APL70VAL_C'/'963945'/'1' : aborted
    development component 'caf/um/relgroups/admin'/'sap.com'/'MAIN_APL70VAL_C'/'963666'/'1' : aborted
    Please, look at error logs above for more information!
    Deployment of CAF-UM finished with Error (Duration 5718 ms)
    Starting Deployment of tc/km_tc/kw
    Aborted: development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of tc/km_tc/kw finished with Error (Duration 6172 ms)
    Starting Deployment of tc/km_tc/sapiks
    Aborted: development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of tc/km_tc/sapiks finished with Error (Duration 5859 ms)
    Starting Deployment of tc/km_tc/sapirexthelp
    Aborted: development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of tc/km_tc/sapirexthelp finished with Error (Duration 6110 ms)
    Starting Deployment of tc/kw_tc
    Aborted: development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'0', grouped by software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of tc/kw_tc finished with Error (Duration 6766 ms)
    Starting Deployment of KM-KW_JIKS
    Aborted: software component 'KM-KW_JIKS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216072941''/'0':
    Failed deployment of SDAs:
    development component 'tc/km_tc/kw'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
    development component 'tc/km_tc/sapiks'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
    development component 'tc/km_tc/sapirexthelp'/'sap.com'/'SAP AG'/'7.0012.20070328121935.0000'/'0' : aborted
    development component 'tc/kw_tc'/'sap.com'/'SAP AG'/'7.0015.20080123135455.0000'/'0' : aborted
    Please, look at error logs above for more information!
    Deployment of KM-KW_JIKS finished with Error (Duration 5719 ms)
    Starting Deployment of SQLTrace
    Aborted: development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of SQLTrace finished with Error (Duration 6141 ms)
    Starting Deployment of com.sap.aii.util.rb
    Aborted: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'7.0012.20070328121059.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\1\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.aii.util.rb\SAP AG\1\7.0012.20070328121059.0000\aii_util_rb.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.aii.util.rb finished with Error (Duration 5922 ms)
    Starting Deployment of com.sap.aii.util.misc
    Deployment of com.sap.aii.util.misc was skipped (Duration 5359 ms)
    Starting Deployment of com.sap.aii.util.xml
    Deployment of com.sap.aii.util.xml was skipped (Duration 5547 ms)
    Starting Deployment of com.sap.aii.ibtranslationclient
    Deployment of com.sap.aii.ibtranslationclient was skipped (Duration 5218 ms)
    Starting Deployment of com.sap.aii.ibtransportclient
    Deployment of com.sap.aii.ibtransportclient was skipped (Duration 5266 ms)
    Starting Deployment of com.sap.aii.proxy.framework
    Deployment of com.sap.aii.proxy.framework was skipped (Duration 5266 ms)
    Starting Deployment of com.sap.engine.class.download
    Aborted: development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.engine.class.download finished with Error (Duration 6078 ms)
    Starting Deployment of com.sap.engine.customizing.ccms
    Aborted: development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.engine.customizing.ccms finished with Error (Duration 6016 ms)
    Starting Deployment of com.sap.engine.docs.examples
    Aborted: development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'7.0014.20071029094615.0000'/'0', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.engine.docs.examples finished with Error (Duration 9703 ms)
    Starting Deployment of com.sap.engine.heartbeat
    Aborted: development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'7.0012.20070328121153.0000'/'0', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.engine.heartbeat to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.util.monitor.grmg;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.engine.heartbeat finished with Error (Duration 6250 ms)
    Starting Deployment of com.sap.jdo
    Aborted: development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'7.0013.20070703111940.0000'/'0', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.jdo finished with Error (Duration 6219 ms)
    Starting Deployment of com.sap.lcr.namealloc
    Aborted: development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'1', grouped by :
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\1\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.lcr.namealloc\SAP AG\1\7.0013.20070703113613.0000\namealloc.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.lcr.namealloc finished with Error (Duration 5703 ms)
    Starting Deployment of com.sap.lcr.saprfc
    Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'7.0013.20070703113613.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcr.saprfc to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.lcr.saprfc finished with Error (Duration 6187 ms)
    Starting Deployment of com.sap.lcrabapapi
    Aborted: development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'7.0013.20070328121631.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot remove references from sap.com/com.sap.lcrabapapi to library:sap.com/com.sap.mw.jco, library:sap.com/com.sap.lcr.api.cimclient;  java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.lcrabapapi finished with Error (Duration 5906 ms)
    Starting Deployment of com.sap.mobile.clientinfo
    Aborted: development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'7.0013.20060719095239.0000'/'1', grouped by :
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.mobile.clientinfo.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.mobile.clientinfo finished with Error (Duration 5860 ms)
    Starting Deployment of com.sap.pmi.adm
    Aborted: development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'7.0014.20071029095144.0000'/'0', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.pmi.adm finished with Error (Duration 5765 ms)
    Starting Deployment of com.sap.rprof.dbprofiles
    Aborted: development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'7.0014.20070328121706.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\0\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\com.sap.rprof.dbprofiles\SAP AG\0\7.0014.20070328121706.0000\dbprofiles.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.rprof.dbprofiles finished with Error (Duration 5734 ms)
    Starting Deployment of com.sap.lcr
    Deployment of com.sap.lcr was skipped (Duration 5297 ms)
    Starting Deployment of com.sap.rprof.remoteProfile
    Deployment of com.sap.rprof.remoteProfile was skipped (Duration 5266 ms)
    Starting Deployment of com.sap.security.core.admin
    Aborted: development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'7.0014.20071029094847.0000'/'0', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.security.core.admin finished with Error (Duration 7688 ms)
    Starting Deployment of com.sap.util.monitor.jarm.ccms
    Aborted: development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'1', grouped by :
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.ccms.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.util.monitor.jarm.ccms finished with Error (Duration 5719 ms)
    Starting Deployment of com.sap.util.monitor.jarm.j2ee
    Aborted: development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'7.0013.20051128142456.0000'/'1', grouped by :
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\program\.\temp\temp_dm\com.sap.util.monitor.jarm.j2ee.jar. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineLib620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.util.monitor.jarm.j2ee finished with Error (Duration 5953 ms)
    Starting Deployment of com.sapmarkets.mesyncjco
    Deployment of com.sapmarkets.mesyncjco was skipped (Duration 5547 ms)
    Starting Deployment of com.sapportals.htmlb
    Deployment of com.sapportals.htmlb was skipped (Duration 5281 ms)
    Starting Deployment of com.sap.engine.services.webservices.tool
    Deployment of com.sap.engine.services.webservices.tool was skipped (Duration 5469 ms)
    Starting Deployment of com.sapportals.htmlb.ear
    Deployment of com.sapportals.htmlb.ear was skipped (Duration 5234 ms)
    Starting Deployment of sl.ut.content.nw
    Aborted: development component 'sl.ut.content.nw'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of sl.ut.content.nw finished with Error (Duration 5704 ms)
    Starting Deployment of sl.ut.infoprovider
    Aborted: development component 'sl.ut.infoprovider'/'sap.com'/'SAP AG'/'7.0014.20071123054250.0000'/'1', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\1\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is: ; nested exception is:      com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\sl.ut.infoprovider\SAP AG\1\7.0014.20071123054250.0000\sap.com~sl.ut.infoprovider.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Exception is:
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of sl.ut.infoprovider finished with Error (Duration 5828 ms)
    Starting Deployment of sl/ut/info
    Deployment of sl/ut/info was skipped (Duration 5297 ms)
    Starting Deployment of tc/SL/CMS/Util
    Aborted: development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'7.0014.20071002095021.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071123073950''/'0':
    Caught exception during library deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot perform action deploy on component library D:\usr\sap\ABA\DVEBMGS01\SDM\root\origin\sap.com\tc\SL\CMS\Util\SAP AG\0\7.0014.20071002095021.0000\CMSutil.sda. Reason: java.rmi.RemoteException: Only Administrators have the right to perform this operation.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deployLibrary(DeployServiceImpl.java:1463)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:336)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         

    Hi,
    I think there are two sda files with adsap so just check in the eps/in directory.
    Also just try to deploy the BI component individually using SDM.
    Regards,
    Vamshi.

  • Patching Always Fails on One WS Type

    Since I've implemented Patch Management in my organization I've cycled through several different workstation types, but recently I'm having trouble with this past year's computer model in that patching always fails.
    What is happening is that I have narrowed the patching down to doing the individual machines (HP dc7900). I'll select the patches I want to push go through the wizard using default settings and force the restart. The deployment process will go successfully but the install/launches will fail.
    In the reporting I'll get a remediate.exe failure with a Windows error: Unknown error (0xffffffff) on the bundle package. On the workstation I'll get notification messages for every patch in the bundle. Overall ZCM status reporting says that the package was successfully deployed but in actuality absolutely zero updates are applied.
    This happens the same for every dc7900 in our building which were set up using the same process as dc5700 and two generations of dc5800 workstations that all patch successfully. Has anyone run into a similar situation? Thanks!

    We make a new "source image" for each computer model that we have so different base images for the 5700, 5800 and 7900. All of our images are made with the same XP SP3 volume license and network deployed apps installed. The 57/5800 systems had Windows Updates enabled as "download and let me choose when to install" but with the 7900 we thought that we would be able to use Patch Management to deploy updates so on the image the updates were turned off, but we have since manually turned them back on to automatic to make sure they keep updating.
    I did recently find out that this behavior also follows application bundles on these systems now. I usually deploy bundles as dynamic administrator but have read in another thread that deploying as system may cause less hassles but I haven't had a chance to test this yet.

  • Error while deploying ear-file to J2EE via NWDS/SDM

    Hi everybody,
    i have a problem deploying an ear-file. I was looking for similar cases in forums, but didn't find anything. My application is developed by jsp/servlets. The deployment aborts with following error-massage:
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.warcom.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
    I don't know what the reason could be. The application is running on tomcat. And I can deploy other applications to j2ee with nwds/sdm.
    Maybe somebody had or has the same problem. Or somebody knows the answer for the problem. Please help, points will be regarded. Thanks in advance.
    best regards
    Lu

    Hi,
    I checked the log-files, but there are no helpful informations, but:
    07/04/23 12:08:04 -  Start updating EAR file...
    07/04/23 12:08:04 -  start-up mode is lazy
    07/04/23 12:08:20 -  com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
                         com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
                          java.io.IOException: Stream closed
    and
    Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy API:
    com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
    com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
    java.io.IOException: Stream closed
    thanks,
    Lu

  • Every PATCH installation fails after installing Windows Updates

    Hello,
    I want to report an issue which I think is a Windows bug introduced by one of the Windows updates (unfortunately I wasn't able to find out which one of them).
    Here is the test case:
    1. install a fresh copy of Windows on a test machine
    2. install all available Windows Updates (so the system is up to date)
    3. create a sample MSI installer which only installs some dummy files (let's say Product Version 1.0.0) and host it on a web server
    4. install the MSI from the online location using a command line like this:
    msiexec /i http://server/share/package.msi
    5. create a .MSP patch (e.g. v1.0.1) which only adds a new file to v1.0.0
    6. install the v1.0.1 patch
    RESULT: the patch installation fails with the following error message: "The filename , directory name , or volume label syntax is incorrect"
    NOTES:
    1. the issue was replicated on Windows 7 and 8 machines UP TO DATE
    2. the issue is not replicated on a fresh installation of Windows without Updates applied
    Is there anyone aware of what could cause this error? Once again the patch installation fails only on Windows machines with the latest Updates installed.
    Thx,
    Daniel

    Hello,
    I want to report an issue which I think is a Windows bug introduced by one of the Windows updates (unfortunately I wasn't able to find out which one of them).
    Here is the test case:
    1. install a fresh copy of Windows on a test machine
    2. install all available Windows Updates (so the system is up to date)
    3. create a sample MSI installer which only installs some dummy files (let's say Product Version 1.0.0) and host it on a web server
    4. install the MSI from the online location using a command line like this:
    msiexec /i http://server/share/package.msi
    5. create a .MSP patch (e.g. v1.0.1) which only adds a new file to v1.0.0
    6. install the v1.0.1 patch
    RESULT: the patch installation fails with the following error message: "The filename , directory name , or volume label syntax is incorrect"
    NOTES:
    1. the issue was replicated on Windows 7 and 8 machines UP TO DATE
    2. the issue is not replicated on a fresh installation of Windows without Updates applied
    Is there anyone aware of what could cause this error? Once again the patch installation fails only on Windows machines with the latest Updates installed.
    Thx,
    Daniel

  • How TO DEPLOY JAR FILES INTO XI Server using SDM

    Hi XI Gurus,
       im working on adapter development. we have created jar file in NWDS.
       now going ahead to deploy into XI server through SDM.
       can we deploy jar files directly into xiserver through SDM. or it needs to convert to any other formate like EAR, SDA. then how would i convert to SDA.
      i any have clear idea on this... pls throw the ways how to convert........
               JAR File to EAR format
               JAR file to SDA format
               EAR file to SDA format         
       can any one explain the procedure step by step how to convert jar file into deployment archive file in order to succesfully into XI server.
              thanks  i advance. points will be rewarded.
      Regards
      Rajesh

    Hi Rajesh,
    JAR file in itself in not deployable.
    So v need to envelop this jar file into an EAR file and then v deploy this EAR file on SDM.
    Creating Jar
    Inside NWDS --> Windows --> Open perspective --> J2EE Development --> right click on ur proj --> Build EJB Archive
    Converting .EAR file to .SDA
    Converting .EAR file to .SDA
    Regards,
    Prateek

  • FMW patching gets failing

    Hi friends,
    As a part of BIAPPS-ODI configuration, @ the step of Applying FMW patches biappshiphome patches is getting failed like in the final patching report im getting error like
    ----------START OF PATCHING REPORT------------------
    * BIAPPSSHIPHOME Patching Report ..........
    Patch Failed: fsclite_rel7mlr2_16424872.zip
    Patch Failed: BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip
    Patch Failed: atglite_rel7mlr5A_database_16239380.zip
    Patch Failed: atglite_rel7mlr5_16480022.zip
    Patch Failed: fsmlitedb_rel7mlr2_16424869.zip
    Patch Failed: fsmlite_rel7mlr2_16424870.zip
    Patch Failed: BISERVER_11_1_1_7_0_WINDOWS_X64_130326_2045_4_16583998.zip
    Patch Failed: BIFNDN_11_1_1_7_0_WINDOWS_X64_130322_1000_5_16462147.zip
    Since only the above BIAPPSSHIPHOME patches is failing, but the remaining oracle common patching, ODI patching got succeeded. Im getting issue only with the above BIAPPSSHIPHOME patches.
    When i tried to view the log file im getting the error like
    Oracle Interim Patch Installer version 11.1.0.9.9
    Copyright (c) 2012, Oracle Corporation.  All rights reserved.
    Oracle Home       : C:\Middleware\Oracle_BI1
    Central Inventory : C:\Program Files\Oracle\Inventory
       from           : n/a
    OPatch version    : 11.1.0.9.9
    OUI version       : 11.1.0.9.0
    Log file location : C:\Middleware\Oracle_BI1\cfgtoollogs\opatch\opatch2013-10-06_10-40-30AM_1.log
    OPatch detects the Middleware Home as "C:\Middleware"
    Log file location: C:\Middleware\Oracle_BI1\cfgtoollogs\opatch\opatch2013-10-06_10-40-30AM_1.log\
    OPatch failed with error code = 73
    What could be the issue for the above problem and how it can be solved.
    Thanks
    Regards,
    Saro

    Hi guys,
    The issue is been resolved, once after renaming the file patch_locked which is located in the path
    C:\Middleware\Oracle_BI1\.patch_storage
    Finally I got those biappshiphome patches applied successfully
    ----------START OF PATCHING REPORT------------------
    * BIAPPSSHIPHOME Patching Report ..........
    Patch Succeded: fsclite_rel7mlr2_16424872.zip
    Patch Succeded: BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip
    Patch Succeded: atglite_rel7mlr5A_database_16239380.zip
    Patch Succeded: atglite_rel7mlr5_16480022.zip
    Patch Succeded: fsmlitedb_rel7mlr2_16424869.zip
    Patch Succeded: fsmlite_rel7mlr2_16424870.zip
    Patch Succeded: BISERVER_11_1_1_7_0_WINDOWS_X64_130326_2045_4_16583998.zip
    Patch Succeded: BIFNDN_11_1_1_7_0_WINDOWS_X64_130322_1000_5_16462147.zip
    * Oracle Common Patching Report ..........
    Patch skipped since its already applied: p16433147_111170_Generic.zip
    Patch skipped since its already applied: p16080773_111170_Generic.zip
    Patch skipped since its already applied: Webservices_Patch-3-PS6RC3_bug-1648778
    .zip
    Patch skipped since its already applied: p16433036_111170_Generic.zip
    Patch skipped since its already applied: JDEVADF_REL7MLR10-RT_16525527.zip
    Patch skipped since its already applied: WebCenter_BP1REL7RC3_16311963.zip
    Patch skipped since its already applied: fmw_diagnostics_14757820_2.zip
    Patch skipped since its already applied: SOACOMMON_REL7B8_16438735.zip
    * SOA Patching Report ..........
    Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified
    * ODI Patching Report ..........
    Patch skipped since its already applied: p16629917_111170_Generic.zip
    * Weblogic Patching Report ..........
    ----------END OF PATCHING REPORT------------------
    This final patching report log file is also located at: C:\patches\final_patchig_report.log
    Regards,
    Saro

  • Patch 6372396 - FAILED: file FNDLIBR on worker + 6372396

    Hi,
    i cloned the apps and db.while applying 63772396 patch in windows env, i am getting "Patch 6372396 - FAILED: file FNDLIBR on worker 1" this error.
    thanks in advance

    -ms128m -mx256m -Xrs oracle.aurora.server.tools.loadjava.LoadJavaMain -f -thin -user "APPS/*****@adam.muscat.org:1521:MMAPPS" D:\MMAPPS\mmappsappl\admin\MMAPPS\out\p001ldjva.jar
    Calling D:\MMAPPS\mmappscomn\util\java\1.4\j2sdk1.4.2_04\bin\java.exe ...
    Error:
    Program exited with status 1
    Cause: The program terminated, returning status code 1.
    Action: Check your installation manual for the meaning of this code on this operating system.java.lang.NoClassDefFoundError: oracle/aurora/util/tools/ToolException
         at oracle.aurora.server.tools.loadjava.LoadJavaMain.<init>(LoadJavaMain.java:51)
         at oracle.aurora.server.tools.loadjava.LoadJavaMain.main(LoadJavaMain.java:56)
    Exception in thread "main"
    AD Worker error:
    The above program failed. See the error messages listed
    above, if any, or see the log and output files for the program.
    Time when worker failed: Wed Jan 06 2010 13:06:08
    Manager says to quit.
    Time when worker quit: Wed Jan 06 2010 13:08:26
    AD Worker is complete.
    Errors and warnings are listed in the log file
    D:\MMAPPS\mmappsappl\admin\MMAPPS\log\adwork001.log
    and in other log files in the same directory.

  • How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM

    Hello everybody,
           We assemblied a sca file in NWDI when we finished development.
           But when we used RemoteGUI to deploy the SCA file in another NetWeaver2004s engine.The Deploy order is wrong.The SDM doesn't first deploy the Library,EAR.It deployed the SDA ordering by the letter order ,not the dependence order.
           For example,there are two SDA in the SCA file, one's name is <b>d_lib</b>,another name is <b>a_ear</b>.The a_ear depend on the d_lib.When SDM deploy the SCA,it first deploy the a_ear,not d_lib.
          How to Confirm the SDAs deploy order of SCA in RemoteGUI of SDM?

    Hi Marc,
    Thanks for your help!
    I found the Prodiver.xml,and the content is:
    <?xml version="1.0" encoding="utf-8" ?>
    - <provider-descriptor>
      <display-name>om/library</display-name>
      <component-name>om/library</component-name>
      <description />
      <major-version>7</major-version>
      <minor-version>00</minor-version>
      <micro-version>0</micro-version>
      <provider-name>pjs.com</provider-name>
    - <jars>
      <jar-name>pjs.comomwcalistwcalist_daoWcalistPackage.jar</jar-name>
      <jar-name>pjs.comomlogequipdao~daoPackaged.jar</jar-name>
      <jar-name>pjs.comomnotificationnotification_daoNotificationPackage.jar</jar-name>
      <jar-name>pjs.comombasedaodaoPackaged.jar</jar-name>
      <jar-name>pjs.comomlogareaareadaopackaged.jar</jar-name>
      <jar-name>pjs.comompostpost_daoPostPackage.jar</jar-name>
      <jar-name>pjs.comompostpost_daoSpecialtyPackage.jar</jar-name>
      <jar-name>pjs.comomtaskdaopackaged.jar</jar-name>
      <jar-name>pjs.comomgradeprojectgradedaopackagSDA.jar</jar-name>
      <jar-name>pjs.comomlogreconlredaopackaged.jar</jar-name>
      <jar-name>pjs.comomsafeexcepreportExcepReportPackage.jar</jar-name>
      <jar-name>pjs.comomsaferecorddaoapi.jar</jar-name>
      <jar-name>pjs.comomlogelogelogdaopackaged.jar</jar-name>
      <jar-name>pjs.comomsysdaopackaged.jar</jar-name>
      <jar-name>pjs.comombasevindbasedaopackaged.jar</jar-name>
      <jar-name>pjs.comomlogsearchpersondao~SearchPersonSDA.jar</jar-name>
      <jar-name>pjs.comomplacarddaoplacardPackaged.jar</jar-name>
      <jar-name>pjs.comompostpost_daoPersonPackage.jar</jar-name>
      <jar-name>pjs.comomsbillrecorddaosbillRecordPackaged.jar</jar-name>
      <jar-name>pjs.comomdutyperson_dao~DutyPersonSDA.jar</jar-name>
      <jar-name>pjs.comomrptdaoRptSDA.jar</jar-name>
      <jar-name>pjs.comompostpost_daoEquipmentPackage.jar</jar-name>
      <jar-name>pjs.comomlogtypelogdaopackaged.jar</jar-name>
      <jar-name>pjs.comomsafeproeval_daoProEvalPackage.jar</jar-name>
      <jar-name>pjs.comompersonpostdaopackaged.jar</jar-name>
      <jar-name>pjs.comomlogsearchlogdao~SearchSDA.jar</jar-name>
      <jar-name>pjs.comompublic~packaged.jar</jar-name>
      <jar-name>pjs.comomspellgroupdaodaoPackaged.jar</jar-name>
      <jar-name>pjs.comomlogpersonlogdao~packaged.jar</jar-name>
      <jar-name>pjs.comompostpost_daoRlogPackage.jar</jar-name>
      <jar-name>pjs.comomschedule_dao~ScheduleSDA.jar</jar-name>
      <jar-name>pjs.comomreportrptdaopackaged.jar</jar-name>
      <jar-name>pjs.comompostpost_daoRecordClassPackage.jar</jar-name>
      <jar-name>pjs.comompostpost_daoReqpPackage.jar</jar-name>
      <jar-name>pjs.comomlogshiftclassdao~ShiftClassSDA.jar</jar-name>
      <jar-name>pjs.comomverifyrecorddao~RecordPackage.jar</jar-name>
      <jar-name>pjs.comomunit_dao~UnitSDA.jar</jar-name>
      <jar-name>pjs.comomdatadefinedefdaopackaged.jar</jar-name>
      <jar-name>pjs.comomheader_dao~HeaderSDA.jar</jar-name>
      <jar-name>pjs.comomspellspedaopackaged.jar</jar-name>
      <jar-name>pjs.comomlogrecdlcddaopackaged.jar</jar-name>
      <jar-name>pjs.comomlogsearchequip_dao~SearchEquipSDA.jar</jar-name>
      <jar-name>pjs.comomcompanycomdaopackaged.jar</jar-name>
      <jar-name>pjs.comommaceasyformdao~daoJAR.jar</jar-name>
      <jar-name>pjs.comomdeclaredecdaopackaged.jar</jar-name>
      <jar-name>pjs.comompostpost_daoFunlcodePackage.jar</jar-name>
      <jar-name>pjs.comomlogeventlevdaopackaged.jar</jar-name>
      <jar-name>pjs.comomclient_dao~ClientSDA.jar</jar-name>
      <jar-name>pjs.comomlogdepldedaopackaged.jar</jar-name>
      <jar-name>pjs.comomlogceqplceqdaopackaged.jar</jar-name>
      <jar-name>pjs.comomrptinforptdaopackaged.jar</jar-name>
      </jars>
      </provider-descriptor>
    I checked it and didn't find any error! What can i do?

  • Error - on using deployment procedures to patch a RAC cluster - 10.2.0.5

    I am using EM grid control 10.2.0.5. Using the deployment procedures to patch to a target host ucmlab that is on server devorclrac001.yeoman.dev.
    Here is the output log from the error. Any ideas. It appears to look like configuration missing.
    Thank you
    Output Log
    Downloading the patches from My Oracle Support.
    Building the runtime data for the deployment procedure ...
    Processing Target "ucmlab.yeoman.dev" on Oracle Home "/opt/app/oracle/product/10.2.0/db_1", Host "devorclrac001.yeoman.dev":
    For Target "ucmlab.yeoman.dev" patch will be applied to Oracle Home "/opt/app/oracle/product/10.2.0/db_1" on Host "devorclrac001.yeoman.dev".
    Processing Target "ucmlab.yeoman.dev" on Oracle Home "/opt/app/oracle/product/10.2.0/db_1", Host "devorclrac002.yeoman.dev":
    For Target "ucmlab.yeoman.dev" patch will be applied to Oracle Home "/opt/app/oracle/product/10.2.0/db_1" on Host "devorclrac002.yeoman.dev".
    Target "ucmlab.yeoman.dev" has a non-shared Oracle Home.
    Targets present in the Target List (Target Name, Host, Oracle Home):
    ucmlab.yeoman.dev,devorclrac001.yeoman.dev,/opt/app/oracle/product/10.2.0/db_1
    ucmlab.yeoman.dev,devorclrac002.yeoman.dev,/opt/app/oracle/product/10.2.0/db_1
    Oracle Homes being patched (Host, Oracle Home):
    devorclrac001.yeoman.dev,/opt/app/oracle/product/10.2.0/db_1
    devorclrac002.yeoman.dev,/opt/app/oracle/product/10.2.0/db_1
    Following Error(s) Occured :
    Property "NodeName" is not found for target "devorclrac001.yeoman.dev" of type "host"
    Property "NodeName" is not found for target "devorclrac002.yeoman.dev" of type "host"
    CAUSE: Insufficient Configuration Properties for the target(s)
    ACTION: Recompute the properties for the Agent with the target being in 'UP' status.
    (i) Run the following commands on the Agent of the target:
    $ emctl stop agent
    $ emctl start agent
    (ii) Run the following command: $ emctl reload agent dynamicproperties

    I decided to uninstall the agent, remove the target from EM and reinstall. It appears to be a little better. I get a different error now with the "opatch upgrade" step.
    I checked and OPATch_update job has already ran successfully once and software components have been downloaded once.
    Command Arguments: expandPatch -oh /opt/app/oracle/product/10.2.0/db_1 -pa_stage_loc /opt/app/oracle/product/10.2.0/agent10g/EMStage -i 6880880 -f p6880880.zip, Current Dir: /home/oracle
    Running: /opt/app/oracle/product/10.2.0/agent10g/sysman/admin/scripts/osm/ecmPatchDatabase.pl
    Argument count: 9
    Perl version: 5.008003
    Hostname: devorclrac002.yeoman.dev
    Operating system: linux
    Time: Tue Jul 14 14:49:36 2009
    Unpacking patch file p6880880.zip in /opt/app/oracle/product/10.2.0/agent10g/EMStage/6880880...
    /opt/app/oracle/product/10.2.0/agent10g/bin/unzip -o p6880880.zip
    Archive: p6880880.zip
    End-of-central-directory signature not found. Either this file is not
    a zipfile, or it constitutes one disk of a multi-part archive. In the
    latter case the central directory and zipfile comment will be found on
    the last disk(s) of this archive.
    unzip: cannot find zipfile directory in one of p6880880.zip or
    p6880880.zip.zip, and cannot find p6880880.zip.ZIP, period.
    ---------- Error Message ----------
    Error: 009
    Could not unpack p6880880.zip
    ----------- End Message -----------
    expandPatch failed

  • I can't update my existing firefox 8.0.1 to 9.0.1 on my new MacBook Pro OS X Lion (patch apply failed)?

    I can't update my existing firefox 8.0.1 (when prompted by updater) to 9.0.1 on my new MacBook Pro OS X Lion. Update failed with 'patch apply failed' message.

    resolved

  • The Update could not be installed (patch apply failed) this keeps happening after it has told me to update Why ?

    while running Firefox it comes on the screen saying security update so after it ties to update this comes on the screen "The Update could not be installed (patch apply failed)" I am running Firefox 6.0 and don't seem to have any other issues with it but it asks me several times to do this update but still says it cant do it
    I am running windows vista

    If files already have been downloaded then remove the files in the updates and updates\0 folder.
    You can also delete the active-update.xml file.
    *http://kb.mozillazine.org/Updates_reported_when_running_newest_version
    Software Update not working properly:
    *http://kb.mozillazine.org/Software_Update
    * C:\Users\&lt;user&gt;\AppData\Local\Mozilla\Firefox\Mozilla Firefox\updates

  • Want to deploy a Oracle patch for SOA

    Hi All,
    I wanted to deploy a oracle patch "p12326395_111130_Generic", in the readme text of this patch, it asks me to use the OPATCH utility. Unfortunately I do not have that utility with me.
    Can someone please guide me whether I can install the patch only with OPATCH or do I have any other option to do it?
    If OPATCH is the only option, please let me know the URL to download this utility.
    Thanks,
    Shiv..

    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e16793/opatch.htm#CBHGHAFA
    Regards,
    Anuj

  • Critical patch update fails with error code 73

    RDBMS Version: 10.2.0.3
    Operating System and Version: solaris 5.9
    Error Number (if applicable): error code 73
    Product (i.e. SQL*Loader, Import, etc.): oracle server enterpirse edition
    Product Version: 10.2.0.3
    Critical patch update fails with errors(urgent)
    UD00_102030>pwd
    /mnt/base_install/downloads/10gR2/cpu/6394981
    UD00_102030> opatch apply
    Invoking OPatch 10.2.0.3.0
    Oracle interim Patch Installer version 10.2.0.3.0
    Copyright (c) 2005, Oracle Corporation. All rights reserved..
    Oracle Home : /u01/app/oracle/product/10.2.0
    Central Inventory : /u01/app/oracle/oraInventory
    from : /var/opt/oracle/oraInst.loc
    OPatch version : 10.2.0.3.0
    OUI version : 10.2.0.3.0
    OUI location : /u01/app/oracle/product/10.2.0/oui
    Log file location : /u01/app/oracle/product/10.2.0/cfgtoollogs/opatch/opatch2007-10-19_19-53-31PM.log
    Failed to load the patch object. Possible causes are:
    The specified path is not an interim Patch shiphome
    Meta-data files are missing from the patch area
    Patch location = /mnt/base_install/downloads/10gR2/cpu/6394981
    Details = PatchObject constructor: Input file "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/actions" or "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/inventory" does not exist.
    ApplySession failed: PatchObject constructor: Input file "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/actions" or "/mnt/base_install/downloads/10gR2/cpu/6394981/etc/config/inventory" does not exist.
    System intact, OPatch will not attempt to restore the system
    OPatch failed with error code 73
    This cpu oct 2007 patch for 10.2.0.3(for solaris)

    That's great :) ...
    Does anybody know which is the difference between
    opatch napply
    and
    opatch apply ?
    thanks,
    P.

Maybe you are looking for

  • Problem while assigning Servlet to Execute queue

    Hi, We implement a IMS S-CSCF on BEA container 2.2. A call for us may be several times reentrant. Meaning that for one call we have to handle at least three different dialogs but in major use cases, it will be 6 or 7 for our next deployment. We are c

  • How can I detect that a device is from Motorola !

    hi all ! I want to detect if my device is a Motorola one, to do so, I was checking the class com.motorola.extensions.ScalableImage, if it's present I know that the device is a Motorola. but, now, I have some devices (V8) that didn't support this clas

  • Problem , about JMS sender in Point-to-Point Domains

    Hi all, I study jms tutorial in chapter 4,and i have a question. In the Point-to-Point example,i send two message(1,2),and then i send two message again(3,4). Now,i start SimpleQueueReceiver to receiver the message, it will show 3,1,2,4 in this seque

  • Help with RSS

    Hi guys Basically, I would like to create a panel for Photoshop CS4 getting an RSS feed of my video tuts. I know how to put the video window but I would like the RSS links to show the video once clicked. Kind of like what Scott Kelby did HERE but ins

  • Ava.util.regex.pattern and * - + /

    hi... i'm korean... so I can't speak english.. sorry..^^ but i hava a problem.. import java.util.regex.*; public class Operator /     public static void main(String args[])           String operator="/"; //////////////////////////////////////////////