Deployment fails after ESS import

I want to modify an ESS application using NWDI.
I have setup NW2004s SP11 with NWDI and imported ESS SP8, PCUI_GP SP8.
In NWDS, when I try to deploy an ESS application, it shows dependency to PCUI_GP/xssutils which in turn shows dependency to PCUI_GP/xsscfg. I tried syncing and deploying PCUI_GP/cfg but it gives this error:
=> deployment aborted : file:/C:/DOCUME1/i042523/LOCALS1/Temp/temp48089sap.compcui_gpxsscfg.sda
Aborted: development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP05VAL_C'/'1183085'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_xsscfg.ear. Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Could you please help here.
Thanks and regards,
Sangeeta

Hi,
Did you ever figure this out? We are having the same issue.
Thanks,
Bert

Similar Messages

  • MDT 2013 Server 2012 R2 Core Deployment Fails After Disabling ChecksumOffloads on NICs

    When changes are made to the Checksum offloads, the NICs reset themselves and I'm losing connectivity to the deployment share during the deployment process (LiteTouch).  It happens during a custom PowerShell script I'm running in the Task Sequence
    after "Tattoo".
    PowerShell Script:
    Disable-NetAdapterChecksumOffload -Name * -IpIPv4
    Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
    Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
    Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
    Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
    Disable-NetAdapterLso -Name * -IPv4
    Disable-NetAdapterLso -Name * -IPv6
    Disable-NetAdapterRss -Name *
    Here are the errors from the BDD.log (sorry couldn't get the _SMSTaskSequence.log)
    ZTIPowerShell processing completed successfully. ZTIPowerShell 8/25/2014 2:27:28 PM 0 (0x0000)
    Command completed, return code = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
    Property RetVal is now = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
    Unable to copy log to the network as no SLShare value was specified. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
    What I was thinking about trying was adding a few lines to the end of my script:
    1. PING 1.1.1.1 -n 1 -w 30000 >NUL
        This would give the server 30 seconds to right itself after resetting the NICs
    2. net use command to remap the share.
    Two questions regarding re-mapping the share.
       1. I'm assuming this will run as Administrator token.  Will this be an issue for continued deployment?
       2. At the beginning of the deployment process the Tech has to enter his/her credentials to access the deployment share to begin the deployment process.  Are those the credentials I need to continue using, or does MDT use some other credentials
    to access the deployment share that far into the deployment process (during state restore phase)?
    Thank you for taking time to read my post.
    -Cheers!

    Apologies for the delay in responding to this thread.
    It turns out that Broadcom NICs are the culprit!
    For some reason Broadcom doesn't grant you access to all the feature sets on their NICs when it comes to PowerShell.
    Same script runs against Intel NICs with no issues.
    I placed a 15 second pause in the script to allow NICs to reset, I then remap MDT network drive to continue the deployment process.  Big thanks to Keith for assisting with reconnecting the network drive!
    Here is the script I settled on:
    # All settings will not take, if target is using Broadcom NICs.
    # You will still need to manually set TCP IPv4 and IPv6 to disabled.
    # Commands to disable Checksum Offloads.
    Disable-NetAdapterChecksumOffload -Name * -IpIPv4
    Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
    Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
    Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
    Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
    Disable-NetAdapterLso -Name * -IPv4
    Disable-NetAdapterLso -Name * -IPv6
    Disable-NetAdapterRss -Name *
    # Pause script for 15 seconds to allow ample time for NICs to reset.
    Start-Sleep -s 15
    net use %DeployRoot% /u:"%UserDomain%\%UserID%" "%USerPassword%"
    # Pause script end for 5 seconds to allow completion of share recreation.
    Start-Sleep -s 5

  • Deployment failing after filer migration in weblogic

    Hi, We have used weblogic on Netapps Filer, recently we migrated from Netapps to Sun filer and after this deployment issue came up. The deployment fails for 2-3 times with the following error "java.lang.NoClassDefFoundError: flex/messaging/license/AsnDecoder" and after that it deploys successfully.
    We have used Netapps for more than 3 years without any deployment issues.
    Can someone please let us know if you faced such problem...and what was the resolution.

    "java.lang.NoClassDefFoundError: flex/messaging/license/AsnDecoder"
    This indicates that the 'deployment' is missing the class that it uses for something.
    What you need to do is find the .jar file that includes the class. After some Googling it is found that flex-messaging-req.jar contains the class ( Download flex-messaging-data-req.jar : flex « f « Jar File Down…) - hope it is the right version.

  • Deploy fails after move of ABAP&JAVA stack to other server

    Hello,
    We moved our system (ABAP&JAVA) to a new server with exactly the same OS level and configuration by means of online backup and restore.
    Installation details are:
    SOLARIS 9
    SAP ECC5 SP12
    Java stack SP16
    After the move the ABAP and the Portal is ok.The server,dispatcher and SDM are also starting fine and no errors shown in the trace files.
    Problem is when trying to run&deploy any example application of the J2EE engine it fails with the following error:
    Application error occurred during request processing.
      Details:   java.rmi.RemoteException: Cannot commit handler in
    operation deploy with application sap.com/Calculator..
    Reason: Error occurred during DB access:
    apps/sap.com/Calculator/servlet_jsp, ; nested exception is:
    com.sap.engine.frame.core.configuration.ConfigurationException:
    Error occurred during DB access: apps/sap.com/Calculator/servlet_jsp,
    Exception id: [0003BAC828490049000000240000582F000419144C86546C]
    Did you encountered such an issue?
    Is there anything special to do for the SDM when moving to a different server? We simply restored from tape the filesystem containing the SDM and the J2EE folders.
    Thanks a lot for your help,
    Kind Regards,
    Florin

    Hello All,
    Please ignore the question; issue is fixed in the mean time.
    Reason was that after the restore the temporary tablespace had no file so this caused the deploy to fail
    Regards,
    Florin

  • FTP adapter deployment failed after restart of the server

    Hi,
    I have a single node 11g server. I had created some outbound connection pools for the ftp adapter. When I created them they were working fine.
    But after the restart of the server the FTP Adapter state in the summary of deployment page is showing failed. The error I am getting is below
    <Unable to set the activation state to true for the application 'FtpAdapter'.
    java.lang.NoClassDefFoundError: oracle/tip/adapter/file/FileLogger
         at oracle.tip.adapter.ftp.FTPManagedConnectionFactory.createConnectionFactory(FTPManagedConnectionFactory.java:154)
         at weblogic.connector.security.layer.AdapterLayer.createConnectionFactory(AdapterLayer.java:787)
         at weblogic.connector.outbound.ConnectionPool.getConnectionFactory(ConnectionPool.java:2013)
         at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1076)
         at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:183)
         at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:437)
         at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:303)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    ####<Apr 6, 2011 4:02:24 PM IST> <Error> <Deployer> <inhysu01> <osb_server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000IweNRSu8TsO8mjGNtn1Db43e000001> <1302085944811> <BEA-149250> <Unable to unprepare application 'FtpAdapter'.
    weblogic.application.ModuleException: Error occurred while trying to rollback the module: weblogic.connector.exception.RAException:
    There are 1 nested errors:
    There are 1 nested errors:
    ObjectLifeCycleException: weblogic.common.resourcepool.ObjectLifeCycleException: Attempted to shutdown the pool eis/Ftp/FtpAdapter when it is currently not in SUSPENDED state (Running)
         at weblogic.common.resourcepool.ResourcePoolImpl.shutdown(ResourcePoolImpl.java:299)
         at weblogic.connector.outbound.ConnectionPool.shutdown(ConnectionPool.java:355)
         at weblogic.connector.outbound.RAOutboundManager.internalShutdownPool(RAOutboundManager.java:346)
         at weblogic.connector.outbound.RAOutboundManager.rollback(RAOutboundManager.java:305)
         at weblogic.connector.common.RAInstanceManager.rollbackRAOutboundMgr(RAInstanceManager.java:623)
         at weblogic.connector.common.RAInstanceManager.rollback(RAInstanceManager.java:566)
         at weblogic.connector.deploy.ConnectorModule.unprepare(ConnectorModule.java:268)
         at weblogic.application.internal.flow.ModuleListenerInvoker.unprepare(ModuleListenerInvoker.java:285)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.previous(DeploymentCallbackFlow.java:523)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:211)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.unprepare(DeploymentCallbackFlow.java:202)
         at weblogic.application.internal.BaseDeployment$1.previous(BaseDeployment.java:619)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.BaseDeployment.unprepare(BaseDeployment.java:248)
         at weblogic.application.internal.SingleModuleDeployment.unprepare(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.unprepare(DeploymentStateChecker.java:205)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.unprepare(AppContainerInvoker.java:117)
         at weblogic.deploy.internal.targetserver.BasicDeployment.unprepare(BasicDeployment.java:287)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:363)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Can anyone please help me with this.
    Thanks in advance

    The solution is either change the order of deployment or copy the FileAdapter.rar file in $ORACLE_HOME/lib location and restart the server as mentioned here.
    http://soa-bpel-esb.blogspot.com/2011/04/javalangnoclassdeffounderror.html

  • AIA Deployment Failed After Patching

    Hi Oracle Community,
    We have a AIA purchase order interface. The interface itself has about 8 composites. We have been successfully using the following process to deploy the interface for the past 12 months:
    ant -f $AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=$AIA_HOME/deploy/purchaseorder/PurchaseOrderInterfaceDP.xml -DPropertiesFile=$AIA_HOME/aia_instances/<instance_name>/config/AIAInstallProperties.xml
    However, we have recently applied patch 'AIA 11.1.1.6 Rollup Patch 5 – Patch 17423167' to our Weblogic 11.1.1.6 environment. Since then we get the error below when attempting to deploy this AIA interface.
    BUILD FAILED
    /oracle/product/Middleware/AIA/Infrastructure/Install/AID/AIAExecuteDriver.xml:118: The following error occurred while executing this line:
    /oracle/product/Middleware/AIA/Infrastructure/Install/AID/AIAExecuteDriver.xml:65: The following error occurred while executing this line:
    /oracle/product/Middleware/AIA/aia_instances/AIA_TEST/tmp/AIDExecuteDP_temp_1308451709.xml:4: Unknown attribute [partition]
    Note that we are unable to deploy any of our AIA interfaces using this method since patching.
    Has anyone come across this problem?
    Hoang

    After further investigations, we removed the partition reference from the deployment script thereby deploying to the default partition and deployment was successful.
    I passed this knowledge onto sysadmins and a partition configuration step was missed. After configuration, deployment worked successfully as per prepatching.
    Hoang

  • Broken DC's after ess import

    Hi
    What are broken DC's? We have configured JDI for ESS web dynpro customizations in EP7 and we see about 210 Broken DCs.
    Do you think i should proceed with web dynpro customization with brokec dc?
    or do i have to reimport the ess .sca files?
    Please advice
    regards
    -madhu

    Hi Madhu,
    You can find more information about Broken DCs with following link. Please read this document carefully.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Mostly its problem with your Track. There are 3 SCs which almost every webdynpro DC uses. these are :
    SAP_JEE
    SAP_BUILDT
    SAP_JTECHS
    Please try to import / reimport these SCs into your track.
    Its better that you fix the Broken DC problem. frist and them go ahead with your development.
    Regards,
    Shrikant

  • MDT image deployment fails after adding applications

    I've been trying to use MDT (ie deployment workbench 6.2.5019.0) to build and deploy images for quite some time now, and I am having a lot of difficulty deploying images to target computers.  I've successfully built a reference image in a VM with all
    the Win7 updates.  I can deploy that image to HP z820 workstations while injecting drivers.  Then I've tried two ways of adding applications, capturing that image and then re-deploying it to other target machines.
    First, I run a standard client task sequence that will deploy and capture an image to a target machine.  I put in a suspend command in the task sequence.  I can then add applications and then restart the task sequence.  If I don't add applications,
    and I just let the task sequence do it's magic, inject drivers, add any remaining Windows updates, and then just resume, MDT will capture the image.  I can then add it to my deployment share and then deploy it back to my target machine that it came from
    or any other similar target.  On the other hand, if I add all my applications during the suspend, MDT will capture the image, but subsequent deployments of the image will always fail on the target machine during Windows setup.
    Second, I can deploy the reference image to a target, let the sequence finish, add the apps, then run a sysprep and capture task sequence.  I finally got that to work.  I have an image with apps that I can deploy.  However, I go to a target
    machine that image was deployed to, I added for example Office and Winzip.  Then I run the same sysprep and capture sequence, capture the image, and when I deploy that image back, it hangs while setup is installing devices.
    Why am I having so much trouble just adding applications to an image that deployed perfectly fine before, but once I add apps, I can no longer use the same task sequences to capture and deploy?  These same task sequences will capture and deploy the
    image without the apps, but not with the apps.  I don't get it.
    So, what's so special about adding applications, and also can anyone give me a good reference for troubleshooting deployment issues where sysprep and setup fail for whatever reason?

    Hmmm... Applications should not cause hangs when installing drivers. In fact NOTHING should cause a hang like that... except for a bad driver. Go back and go through you driver manifest with a fine tooth comb and find the bad driver. That may include removing
    all of your 3rd party drivers.
    Keith Garner - keithga.wordpress.com

  • Iview cannot be previewed after ESS BP deployment

    Dear Experts,
    Kindly need your help.
    Our iview (namely personal data iview in ESS) show blank (I mean really blank) iview in preview mode(portal content directory and as content administrator). We previously deployed a downloaded ESS Business Package, to get this iview.
    This occurs the same for all new iviews (deployed iviews according to ESS BP), but the "Overview" iview.
    When I preview the Overview iview, it shows error:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:467)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
        ... 74 more
    We have maintained the jco connection properly though.
    But when we logged in as user, the iview works fine.
    Any idea how to manage this?
    Thank you.

    Hi,
    So the JCO connection is green? Yes, all JCOs connection are all green
    The user used for usermapping is the same as for the other JCO metadata connection? Yes
    The mapped user is a SAP service user? we are using SAPJSF userID with profile SAP_ALL and SAP_NEW.
    Actually, all JCOs connection even SAP_R3_SelfGeneric_metada have been tested and pinged successfully.
    Thank you.

  • NWDI, ESS import fails

    Hi,
    I am trying to import .sca file in CMS, after 22 hours i was able to import into CMS. In between I got couple of times communication error.
    After that, I got problem in CBS. I tried import again and it started to import into CBS.
    But after couple of times, it started  import into CMS, I believe whatever I imported into CMS is gone.
    Right now I am back to pavilion, I am trying to import it again, I am getting communication error.
    Any help appreciated.
    Our envrionment: NWDI is installed on Unix.
    Regards,
    Balu

    Hi,
    Right now I am able to finish importing into CMS, now import is failed at CBS import, Please see the following error. Now the state is Import running. But in the details tab it shows import failed in CBS-make.
    Thanks,
    Balu
    Info:Starting Step CBS-make at 2006-09-13 15:45:18.0628 -7:00
    Info:wait until CBS queue of buildspace DI1_XSSSP6_D is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:buildspace = DI1_XSSSP6_D   build request id = 48
    Info:wait until CBS queue of buildspace DI1_XSSSP6_D is completely processed, before asking for build results
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Info:build process already running: waiting for another period of 30000 ms
    Error:CBS error on retrieving open build requests
    caused by:Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out)
    com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out)
         at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:530)
         at com.sap.cms.tcs.client.CBSCommunicator.getOpenBuildRequests(CBSCommunicator.java:1166)
         at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1546)
         at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:883)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by:
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1800)
         at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
         at $Proxy120.getOpenRequests(Unknown Source)
         at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:527)
         at com.sap.cms.tcs.client.CBSCommunicator.getOpenBuildRequests(CBSCommunicator.java:1166)
         at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1546)
         at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:883)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.net.SocketTimeoutException: Read timed out
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:134)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:805)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:340)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:249)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:358)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:472)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1372)
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1793)
         ... 53 more
    Error:more details on this error:
    caused by:Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out
    java.rmi.RemoteException: Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1800)
         at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
         at $Proxy120.getOpenRequests(Unknown Source)
         at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:527)
         at com.sap.cms.tcs.client.CBSCommunicator.getOpenBuildRequests(CBSCommunicator.java:1166)
         at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1546)
         at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:883)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.net.SocketTimeoutException: Read timed out
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:134)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:805)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:340)
         at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:249)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:358)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:472)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1372)
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1793)
         ... 53 more
    Fatal:communication error: CBS exception received: Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out)
    Error:CBS error on setting mode (to open):
    caused by:User not authorized. (Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.)
    com.sap.tc.cbs.client.error.CommunicationException: User not authorized. (Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.)
         at com.sap.tc.cbs.client.impl.BuildSpace.setInputMode(BuildSpace.java:383)
         at com.sap.cms.tcs.client.CBSCommunicator.setInputMode(CBSCommunicator.java:277)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:201)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by:
    java.rmi.RemoteException: Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.setInputMode(CBSHttpSOAPBindingStub.java:2725)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
         at $Proxy120.setInputMode(Unknown Source)
         at com.sap.tc.cbs.client.impl.BuildSpace.setInputMode(BuildSpace.java:381)
         at com.sap.cms.tcs.client.CBSCommunicator.setInputMode(CBSCommunicator.java:277)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:201)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:903)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1374)
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.setInputMode(CBSHttpSOAPBindingStub.java:2718)
         ... 52 more
    Error:more details on this error:
    caused by:Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
    java.rmi.RemoteException: Service call exception; nested exception is:
         com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.setInputMode(CBSHttpSOAPBindingStub.java:2725)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
         at $Proxy120.setInputMode(Unknown Source)
         at com.sap.tc.cbs.client.impl.BuildSpace.setInputMode(BuildSpace.java:381)
         at com.sap.cms.tcs.client.CBSCommunicator.setInputMode(CBSCommunicator.java:277)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:201)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:903)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1374)
         at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.setInputMode(CBSHttpSOAPBindingStub.java:2718)
         ... 52 more
    Error:CBS error: Resetting to old mode (open) failed [Contact CBS administrator]
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-09-13 17:09:04.0360 -7:00

  • ESS import failed

    Hi,
    ESS import failed with the below error
    "CBS throws exception during activation
    caused by Exception:com.sap.tc.cbs.client.error.ComminicationException : Read timed out (Service call excpetion;nested exception is:java.net.SocketTimeoutException:Read time out)"
    please guide the solution
    Thanks a ton

    H Daniel,
    Please check with the Log files and  Notes 872892, Note 1027830
    Read the link as,
    http://help.sap.com/saphelp_nw04/helpdata/en/a6/a4214174abef23e10000000a155106/frameset.htm

  • Ess deployment failed with an error localization failed

    Hi,
    I'm trying to deploy the ess business packages but got the following error during the deployment:
    Starting validation -
    Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending
    Info: Update strategy: UpdateLowerOrChangedVersions
    Info: Starting deployment prerequisites:
    Info: Loading selected archives...
    Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\BPERP5ESS15_0-10003288.SCA'
    Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPPCUIGP15P_1-20001215.SCA'
    Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPESS15_0-20000512.SCA'
    Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPMSS15_0-20000503.SCA'
    Info: Loading archive 'D:\usr\sap\NWP\JC00\SDM\program\temp\SAPPSS15_0-20001217.SCA'
    Info: Selected archives successfully loaded.
    Info: Actions per selected component:
    Info: Software type of SDA: J2EE
    Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Info: Begin of log messages of the target system:
    Start updating EAR file...
    start-up mode is lazy
    EAR file updated successfully for 1094ms.
    Start deploying ...
    EAR file uploaded to server for 1485ms.
    ERROR: Not deployed. Deploy Service returned ERROR: java.rmi.RemoteException: Cannot deploy application sap.com/ess~bp_ess..
    Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle',                     ID='Exception during deploy: Failed to deploy archive
    D:\usr\sap\NWP\JC00\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1245916977968\sap.comessbp_ess.epa
    and I tried to find the reader1245916977968 but it was not created in the path above.
    Thanks,
    Niranjan.

    Hi,
    Kindly paste error from sdm logs and dev_jrfc, dev_dispatcher. for more details.
    Shailesh

  • Client side NWDS Hardware Req after ESS Track import.

    Hi,
    I have imported the ESS Web Dynpros into my NWDS using the ESSTracks mentioned in the cookbook.
    But after this import of ESS Web dynpro, my PC has become very slow (when i open NWDS). Even expanding the project tree in NDWS takes lot of time...
    I am having 512 RAM.
    Please let me know what are the minimum hardware req. for Working withthe SAP Standard DCs in NWDS? How much mem is required?
    Is there any note available or SAP document for this?
    Regards
    Gaurav Gandhi

    Hi Venkat & Siddharth,
    Thanx for the reply.
    I do restarted the my PC everytime but again after sometime after opeaning NWDS, my PC becomes slow.
    My PC satisfies all the requirements as mentioned by Venkat, but still it becomes very slow.
    Venkat: Do you have some note or some doc which says this all...
    Right now since i am the only person in my team who has copied the DCs in NWDS but this is the condition of my PC, then what will happen if all the other developers also configure there NWDS for JDI & DTR?
    None of our work will be finished on time with such a speed..:-(
    Regards
    Gaurav Gandhi

  • Bpel deployment fails for all processes that have revision other than 1.0.

    Using: Release *10.1.3.3.1*
    Hello All,
    Bpel deployment fails for all processes that have revision other than *1.0*.
    We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
    D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
         at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.apache.tools.ant.Main.runBuild(Main.java:668)
         at org.apache.tools.ant.Main.startAnt(Main.java:187)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
    The structure of our automated deployment script is as follows:
    First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
    Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
    -     “.” – point to directory where script is running from because all the BPEL processes are located here
    -     “oc4jadmin”
    -     “*********” (whatever the password for out environment is)
    We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
    DO ant
    -Dprocess.name=%%b
    -Drev= !Rev!
    -Dpath=%BPEL_DIR%
    -Ddomain=default
    -Dadmin.user=%ADMIN_USER%
    -Dadmin.password=%ADMIN_PWD%
    -Dhttp.hostname=%HOST%
    -Dhttp.port=%PORT%
    -Dverbose=true
    (What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
    The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
    Example:
    Sample BPEL process:
    bpel_ThisIsProcess1_1.0.jar
    bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
    After tokenizing:
    %%a     %%b     %%c
    bpel     ThisIsProcess1     1.0.jar
    bpel     ThisIsProcess2     SOAv2.19.0.001B.jar
    *!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
    set RevN=%%c
    set RevN=!RevN:~0,-4!
    Hence, the usage of !Rev!.
    Below is a screenshot post of the ANT build.xml that goes with our script:
    <!--<?xml version="1.0"?>-->
    <!--BUILD.XML-->
    <project name="bpel.deploy" default="deployProcess" basedir=".">
         <!--
         This ant build file was generated by JDev to deploy the BPEL process.
         DONOT EDIT THIS JDEV GENERATED FILE. Any customization should be done
         in default target in user created pre-build.xml or post-build.xml
         -->
         <property name="process.dir" value="${basedir}" />
              <!-- Set BPEL process name -->
              <!--
              <xmlproperty file="${process.dir}/bpel/bpel.xml"/>
              <property name="process.name" value="${BPELSuitcase.BPELProcess(id)}"/>
              <property name="rev" value="${BPELSuitcase(rev)}"/>
              -->
         <property environment="env"/>
         <!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
              <condition property="bpel.home" value="${env.BPEL_HOME}">
                   <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
              </condition>
         <!-- show that both bpel and oracle.home are located (TESTING purposes ONLY) -->
         <!-- <echo>HERE:${env.BPEL_HOME} ${env.ORACLE_HOME}</echo> -->
         <!-- END TESTING -->
         <!--If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
         <property name="oracle.home" value="${env.ORACLE_HOME}" />
         <property name="bpel.home" value="${oracle.home}/bpel" />
         <!--First override from build.properties in process.dir, if available-->
         <property file="${process.dir}/build.properties"/>
         <!--import custom ant tasks for the BPEL PM-->
         <import file="${bpel.home}/utilities/ant-orabpel.xml" />
         <!--Use deployment related default properties-->
         <property file="${bpel.home}/utilities/ant-orabpel.properties" />
         <!-- *************************************************************************************** -->
         <target name="deployProcess">
              <tstamp>
                   <format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
              </tstamp>
              <!-- WRITE TO LOG FILE #tjas -->
              <record name="build_verbose.log" loglevel="verbose" append="true" />
              <record name="build_debug.log" loglevel="debug" append="true" />
              <echo></echo>
              <echo>####################################################################</echo>
              <echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
              <echo>--------------------------------------------------------------------</echo>
              <echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
              <echo>--------------------------------------------------------------------</echo>
              <deployProcess
                   user="${admin.user}"
                   password="${admin.password}"
                   domain="${domain}"
                   process="${process.name}"
                   rev="${rev}"
                   dir="${process.dir}/${path}"
                   hostname="${http.hostname}"
                   httpport="${http.port}"
                   verbose="${verbose}" />
              <sleep seconds="30" />
              <!--<echo message="${process.name} deployment logged to ${build_verbose.log}"/>
              <echo message="${process.name} deployment logged to ${build.log}"/> -->
         </target>
         <!-- *************************************************************************************** -->
    </project>
    SUMMARY OF ISSUE AT HAND:
    ~ Every bpel process w/ 1.0 revision deploys with no problems
    ~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
    QUESTIONS:
    1.     IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
    2.     WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
    3.     DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
    Edited by: 793292 on Jul 28, 2011 12:38 PM

    Only thing i can think of is instead of using a MAC ACL , u cud jus use the default class
    Policy Map Test
    class class-default
    police 56000 8000 exceed-action drop
    Class Map match-any class-default (id 0)
    Match any
    You would be saving a MAC-ACL ;-).

  • NW BI-JAVA 7.01 SP6 deployment failed with error main_rules.ept

    Dear all,
    I've installed a new Web AS JAVA instance 7.01 SR1 with usage type BI-JAVA
    I then patched this instance with SP6
    At the end of the deployment process, I got a message from JSPM stating that the deployment failed but all the components had the status deployed.
    I pushed further the investigation and found out in the file main_rules.ept.log the following problem
    PCD auto-import file main_rules.ept in no-overwrite-mode ...FAILED
    Import failed.
    Object ID: pcd:portal_content/administrator/super_admin/main_rules
    Transport File: D:\usr\sap\JD2\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent\no_overwrite\main_rules.ept
         at com.sapportals.portal.pcd.gl.transport.PcdGlTransportManager.handleXmlException(PcdGlTransportManager.java:984)
    < a lot of error messages here ... taken out for the sake of clarity>
    Original exception:
    java.lang.NullPointerException
    Though, the portal application is up and running! What can be the consequences of such an error? How to correct it?

    Hi everyone
    I had the same problem as you. After the deployment of SP6 JSPM told me that there was an error during portal deployment although all components had the status "Deployed" (newly installed system).
    PCD auto-import file main_rules.ept in no-overwrite-mode ...FAILED
    Import failed.
    Object ID: pcd:portal_content/administrator/super_admin/main_rules
    I opened a customer message @SAP:
    The solution is to rename the file "main_rules.ept.err" into "main_rules.ept" and restart the J2EE engine. If the file main_rules.ept was renamed to main_rules.ept.bak after the restart everything is OK acc. to SAP (-> note 1130469 ).
    Best regards
    Nik

Maybe you are looking for

  • Error when refresh a workbook

    Hy Experts I need your very import help!!! We have excel files with queries, and workbooks too. When I refresh them, the system canceled with the message: "System Error program  CL_RSR_GRID and FORM FILL_STRUCTURE_MEMBERS-1-" I see the SapNote 101545

  • Applescript compiles .app as directory why

    OS 10.6.8 with the latest patches AppleScript Editor 2.3 AppleScript 2.1.2 On 12/1/2012 compiled AppleScripts as app (application) and output was a single file with the extension .app.  Today the same compiled script yields a directory of files none

  • Macbook Pro heas issue

    I have a Macbook pro thats started developing some serious heat issues lately. The surface of the laptop gets quite hot even when its completely idle. This started happening around the same time that I did the recent battery update. It would seem tha

  • How do I uninstall safari 7 and reinstall safari 6 (snow leopard)?

    How do I uninstall safari 7 and reinstall snow leopard? I was on pinterest and it said I needed up to update my browser, so I did and now safari won't open for me since I have 10.6.8. How can I get safari back on my computer? I didn't know that my co

  • CO60 - Not working fine

    Hi T-Co60 does not show data  for some period March month data does not show but april data is showing. I have checked COCH table ist show CR has been creted Kindly let me know what condition i  need to be checked for displying the data