Application - not getting deployed only during certian TIME interval

Hi Guys,
Am not aware of the technical reason for the below issue, please help me with this,
--> i deploy a application during my night time. it gets deployed successfully.
--> when i deploy the application during my morning time, NO RESPONSE from the policy pulling that or NO ACTION.4
is there any maintanence window stopping my deployment ..
i want my deployment to work 24X7 ... please help me with the option in client settings or deployment options.

To add-on to Gerry, it's indeed probably a configured maintenance window or a user ignoring it during business hours. For a good read about business hours and maintenance windows, see:
http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
If you really want the deployment to always happen on the deadline you can use the options in the
User Experience tab of the deployment. There you can configure if the installation (and restart) can also be performed outside the maintenance windows.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

  • Application not getting deployed in NWDI

    Hi,
      I have activated application in NWDI.  The request  was activated but its not deployed. In the actvation requests view its showing the tick mark for only activation but not for the deployment. I am not getting any errors in fact.
    Sometimes its not even getting activated...
    Could anybody help me what should i check exactly to make my application get deployed?
    Regards
    Sireesha.

    Hi Anil,
      I have activated the activity in DC perspective only not in the NWDS. And after activating i am checking the activation results in the Activation Requests View.
    In the Activation Requests View for each request u have three coulmns with Request ID and a Icon which shows Activation results and other tick Icon which is for Request Activities.
    Whenever an actvity is activated  a request ID will be created and displayed in the relevant column say Request ID in the activation requests view. In the same way activation result is also displayed in the second columns with the green tick mark and if its deployed thrid column truns out to green tick. That means application is deployed and u can create a iview in the portal and test the application.
    In my case that thrid column is showing empty after activating the activity...
    My doubt is how to deploy that activity...?
    I hope u r clear with this....
    Regards
    Sireesha.

  • HT3275 For the past several days, I have been getting this message during backups: Time Machine could not complete the back up.  The backup disk image "Volumes/Data/iMac.sparsebundle" could not be accessed (error-1).

    For the past several days, I have been getting this message during backups:
    Time Machine could not complete the back up.  The backup disk image "Volumes/Data/bhoppy2's iMac.sparsebundle" could not be accessed (error-1).  When I click on the 'help' icon on the message, it reverts to a blank page, and I cannot find anything online regarding the term 'sparsebundle.'  In addition, I cannot access previous backups any longer. 
    Help?

    See C17 in Time Machine Troubleshooting by Time Machine guru Pondini:
    http://pondini.org/TM/Troubleshooting.html

  • Axis - Web service is not getting deployed on https

    I am using axis api for creating web service and Tomcat to deploy it. When I deploy the web service first time, it works perfectly, but If I upgrade my web
    application, the server-config.wsdd file gets deleted from WEB-INf directory of my web application.
    If I try to deploy the web service again, it does not get deployed on https, but on http it gets deployed. I am using following commands to deploy the web
    service:
    On HTTPS:
    java -Djavax.net.ssl.keystore=/root/.keystore -Djavax.net.ssl.keyStorePassword=password org.apache.axis.client.AdminClient -lhttps://localhost/serviceURL
    deploy.wsdd
    HTTP:
    java org.apache.axis.client.AdminClient -lhttp://localhost/serviceURL deploy.wsdd
    When I deploy the web service on http, the server-config.wsdd file gets created automatically and the web service gets deployed, but the problem is on https.
    Web service does not gets deployed on https and the server-config.wsdd file is not created. Even if I create the server-config.wsdd file manually, the web
    service does not get deployed on https. Once I deploy the web service on http, I am able to deploy it on https.
    Please help resolving the issue. Thanks.

    Hi Reema,
    Thanks for your reply.
    But here I am not doing replication, I am working on initial upload of vendor master.
    For all the standard fields its working fine.
    but we have some 'Z' fields so I enhanced the web service with 'Z' fields after that I am not able to save and activate the web service.
    Please find above screenshot for error.
    Please let me know if I am missing some setting or anything.
    Thanks,
    Sudhir

  • After restore from backup, iphone is not getting start, only apple logo is there on screen

    after restore from backup, iphone is not getting start, only apple logo is there on screen

    Hi there.
    Try some basic trouble shooting steps first, before looking into some advanced issues that might be causing this. The first thing I would try, is holding down the power button and home button at the same time until the screen turns off on you. See what steps you can take from there, if any.
    Kind Regards.
    - Mike.

  • Problem in the setup of oracle soa " could not get deployment manage"

    hi,
    i'm trying to install Oracle SOA with oracle database XE, but i'm having an error message in the oracle bpel process manager configuration assistant: 'could not get deployment manage'..
    can u help me please!!!

    Is the database up and running, can you connect to the orabpel user?
    cheers
    James

  • I have a new iPhone 6 and I am not getting iMessages, only txt messages.  How do I change this to receive iMessages, too?  My friends are sending me iMessages that I am not receiving.

    I have a new iPhone 6 and I am not getting iMessages, only txt messages.  How do I change this to receive iMessages, too?  My friends are sending me iMessages that I am not receiving.

    If you didn't have imessage on and now do, it sometimes takes a while to get synced up.

  • ERROR : Object could not be scheduled within the specified time interval

    I have the next error Object could not be scheduled within the specified time interval.
    When i schedule a report to be refreshed and the moment come when the report have to be refresh appear the error.
    i check the error in the following path in the CMC
    HOME> FOLDERS > USER FOLDERS > ... > "REPORT FOLDER"  Instance Properties
    Why i get this error?
    Anyone can give me a good solution to solve this error?
    Thanks!!!

    Hi Ed,
    The above error message is appearing due to the reason, when a large number of requests are scheduled to start at the same time, this may exceed the Maximum Number of Simultanius Requests that the deployment can support.
    To resolve this error message, increase the end time on the scheduled instance. To increase the end time, use the following steps:
    1. In the Infoview, browse to the desired report and click 'History'.
    2. Find the desired scheduled instance and click 'Reschedule'.
    3. Under the 'When' section, increase the end time for the scheduled instance.
    Upon completing these steps, the error message no longer appears.
    Hope it will help in resolving the error.
    Regards,
    Ritesh Nayyar

  • Error Message : Object could not be scheduled within the specified time interval

    Post Author: mohamed elkashef
    CA Forum: Publishing
    Dear All when i try to run event for daily reports it sometimes take generation status failed with this error  message : Object could not be scheduled within the specified time interval so  i need to know the reason of failure and how can i fix  this error  thanks a lot 

    Post Author: nvnaresh
    CA Forum: Publishing
    Dear jsanzone,
    I'm facing the same error even when the server time out is more than the query execution time of the report.By server time out I assume connection time out of WebI report server which I have set to 180 min.But the actual query takes maximum of 5 min.
    We are using BO XIR2+SP2.
    I scheduled a webI report to get saved in Excel format to an Unmanaged disk location upon a File Event.
    We have 3 such reports to be scheduled on the same event.
    Expected frequency of File Event getting fired in a day is twice.Scheduling frequency I have set it as every one hour with the file event.
    This usually should work fine.
    But frequently 1 or 2 of the above 3 instances are getting failed with the following error "Object could not be scheduled with in specified time interval " after being in Running state for few hours(8). Amazingly this is not happening every time. May be once or twice in a week.This works fine after I restart the BO services and the same thing repeats after 3 or 4 days.
    Do I need to increase any server parameters?
    Why is this happening randomly?  

  • Applications not being deployed during task sequence - MDT 2013 + SCCM 2012 R2

    Hi everyone,
    I have recently integrated MDT2013 with my SCCM 2012 R2 and I am trying to move away from OSD in SCCM and switch to MDT. I managed to get a blank image deployed and now I am trying to tweak CustomSettings.ini to install applications based on the default
    gateway and model. For some reason, the apps are getting pulled but not deployed. Here is what I have in the files:
    Settings Package - CustomSettings.ini
    [Settings]
    Priority=DefaultGateway, Model, Default
    Properties=MyCustomProperty
    [OptiPlex 9020]
    Applications001=Mozilla Firefox
    [DefaultGateway]
    192.168.XXX.254=Poland
    192.168.XXX.254=London
    [Poland]
    Applications001=ESET
    [Default]
    DoCapture=No
    OSInstall=Y
    SkipCapture=YES
    SkipAdminPassword=NO
    SkipProductKey=YES
    Administrators001=myDomain\adminGroup
    Applications001=Skype
    Applications002=Office Professional Plus 2010
    When the TS runs, I can see it's getting all the apps from the list, here is a snippet from ZTIGather.log
    Using from [Settings]: Rule Priority = DEFAULTGATEWAY, MODEL, DEFAULT
    ------ Processing the [DEFAULTGATEWAY] section ------
    Match found for default gateway 192.168.XXX.254, retrieving settings.
    ------ Processing the [Poland] section ------
    Property APPLICATIONS001 is now = ESET
    Added value from [Poland]: APPLICATIONS = ESET
    ------ Processing the [OptiPlex 9020] section ------
    Property APPLICATIONS001 is now = ESET
    Property APPLICATIONS002 is now = Mozilla Firefox
    Added value from [OptiPlex 9020]: APPLICATIONS = Mozilla Firefox
    ------ Processing the [DEFAULT] section ------
    Property OSINSTALL is now = Y
    Using from [DEFAULT]: OSINSTALL = Y
    Property DOCAPTURE is now = No
    Using from [DEFAULT]: DOCAPTURE = No
    Property SKIPCAPTURE is now = YES
    Using from [DEFAULT]: SKIPCAPTURE = YES
    <Message containing password has been suppressed>
    <Message containing password has been suppressed>
    Property SKIPPRODUCTKEY is now = YES
    Using from [DEFAULT]: SKIPPRODUCTKEY = YES
    Property APPLICATIONS001 is now = ESET
    Property APPLICATIONS002 is now = Mozilla Firefox
    Property APPLICATIONS003 is now = Skype
    Added value from [DEFAULT]: APPLICATIONS = Skype
    Property APPLICATIONS001 is now = ESET
    Property APPLICATIONS002 is now = Mozilla Firefox
    Property APPLICATIONS003 is now = Skype
    Property APPLICATIONS004 is now = Office Professional Plus 2010
    Added value from [DEFAULT]: APPLICATIONS = Office Professional Plus 2010
    Property ADMINISTRATORS001 is now = myDomain\adminGroup
    Added value from [DEFAULT]: ADMINISTRATORS = myDomain\adminGroup
    ------ Done processing CustomSettings.ini ------
    So the settings do get picked up and selected. ZTICoalesce.log also shows the apps picked up:
    Coalesce pattern to be used: Applications
    Coalesce base variable to use: CoalescedApps
    Added value ESET-KRKLON from APPLICATIONS001 to the list
    Added value Mozilla Firefox from APPLICATIONS002 to the list
    Added value Skype from APPLICATIONS003 to the list
    Added value Office Professional Plus 2010 from APPLICATIONS004 to the list
    Property CoalescedApps01 is now = ESET
    Property CoalescedApps02 is now = Mozilla Firefox
    Property CoalescedApps03 is now = Skype
    Property CoalescedApps04 is now = Office Professional Plus 2010
    ZTICoalesce processing completed successfully.
    Now when I go to the smsts.log file, I can see this:
    App policy for 'ESET' not received. Make sure the application is marked for dynamic app install
    Policy download failed, hr=0x80004005
    and later
    Failed to run the action: Install Application. 
    Unspecified error (Error: 80004005; Source: Windows)
    After that, no other apps are mentioned and seems like the failure on ESET drops the whole sequence and moves forward. I can see later the default admin being added correctly.
    Any ideas what I may be missing here? Especially on the failed policy download?
    Thanks
    Jakub

    HI,
    "App policy for 'ESET' not received. Make sure the application is marked for dynamic app install"
    Is the ESET application deployed? it sounds like it could be the check box on the application "Allow this application to be installed from install application task sequence action without beeing deployed" that is missing? If the application isn't
    deployed this checkbox must be ticked.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • J2EE application not getting started.

    Hi there,
    I have depoyed my J2EE application successfully but it is not getting started, below is the log trace that is being shown.
    My java path seems fine but cudn't get to know why the initializing is failing.
    Favour would be definitely appreciated.
    One Observation is, WAR file seems like not got deployed properly even though at the time of deployment every acknowledgement message shown was fine.
    **My version is Oracle Weblogic 11g (10.3.0) on IBM AIX 64-bit 6.1 power series system.**
    **JDK used is 1.6.0**
    BEA-149231:
    *Unable to set the activation state to true for the application 'SAMPLEAPP1'. weblogic.application.ModuleException: [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:222) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) 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:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) 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:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) ... 43 more at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) 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:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) 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:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.NumberFormatException: null at java.lang.Throwable.<init>(Throwable.java:67) at java.lang.Integer.parseInt(Integer.java:428) at java.lang.Integer.parseInt(Integer.java:511) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:88) at java.lang.J9VMInternals.initializeImpl(Native Method) at java.lang.J9VMInternals.initialize(J9VMInternals.java:200) at com.ofss.infra.controller.BranchController.init(BranchController.java:118) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) 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:196) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233) 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:173) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89) at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    Cheers.. PCZ

    with the same problem but with weblogic, i tried this solution but i still get this error
    Exception:
    [HTTP:101216]Servlet: "BranchController" failed to preload on startup in Web application: "FCJNeoWeb". java.lang.ExceptionInInitializerError at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3046) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:463) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:417) at java.lang.Integer.parseInt(Integer.java:499) at com.ofss.fcc.common.BranchConstants.<clinit>(BranchConstants.java:92) at com.ofss.infra.controller.BranchController.init(BranchController.java:122) at javax.servlet.GenericServlet.init(GenericServlet.java:241) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) ... 3 more
    and my deployment state is failed

  • EXW price is not getting picked up during preference determination

    HI .. all,
    We have transferred Sales order from ECC to GTS. But during prreferrence determination, EXW price of the Sales order is not getting picked up.
    Please suggest if any configuration is missing .
    Thnks in Advance .

    Hi Sapcongts,
    Of course you should not modify standard SAP code, and I will not help you to do that.
    I don't agree with your idea of proposed and actual EXW values.  The Sales Order is your way of recording the customer's Purchase Order, and the price should be fixed at that point.  The billing process should not change the agreed price of the goods - only perhaps re-calculate taxes and any other charges that could not be confirmed at the time of order.
    If your standard prices are offered as FOB, then I can understand your needing to subtract some components to reach the EXW price, but in that case you will have problems transferring the correct amount to GTS.  As I mentioned earlier, you can manipulate the data in the BAdI /SAPSLL/IFEX_SD0A_R3, but I had not looked closely enough at this specific requirement.  Unfortunately the pricing table KONV is not provided in the BAdI and that data will not yet be available in the database.  Provided the elements to be subtracted are to be read from Master Data, then you could make that same subtraction again in the BAdI.  But if there are complex dependencies, it might not be easy.
    Having looked in more detail at the code, I think you would be reasonably entitled to complain to SAP about missing functionality here.  In the ERP system, the SD pricing provides a specific sub-total (KOMP-PREVA: subtotal 8) for Preference Value, and you can easily configure that to be filled after your subtractions.  But that subtotal is not used in the GTS mapping, and I think that's a mistake.  You might want to create an OSS message about it, requesting that the GTS Preference value be taken from the sub-total that was clearly designed exactly for that purpose.
    In any case, good luck with the project.
    Regards,
    Dave

  • SOADEMO - deploying SOAOrderBooking build.xml "Could not get Deployment M..

    Hi All, I have seen a few issues with the SOA demo but still not able to resolve my issue so posting a thread.
    First off using SOA suite 10.1.3.1.0 and Jdev 10.1.3.1.0, so the same versions. Downloaded the demo from the same oracle page as downloaded suite from etc so should be compatible. Installed SOA Suite on an OE Linux 4 update 5 install. Using jdev on Vista laptop. I appreciate that these are not the most current versions but they should work as on the Oracle site and I am not able to install newer versions for the next few weeks.
    Going through the install guide for the demo and hitting a problem with deploying the build.xml for SOAOrderBooking as a few others have. The first error I am getting is:
    [deployDecisionServices] Failed at "Could not get DeploymentManager".
    I have checked the build.properties file which matches exactly that from the 'SelectManufacturer' which deployed fine.
    One of the main differences between these two is that the 'SelectManufacturer' does not have any decision services.
    One thread I saw suggested changing in the properties file
    platform=ias_10g
    #platform=oc4j_10g
    to
    # platform=ias_10g
    platform=oc4j_10g
    I did do this and the deployment when further but then fails at a later stage. I should not have to make this change anyway as I am using ias_10g so I have gone back to the original. Why would this change allow me to get further?? Appreciate any comments on this bit apart from my general problem.
    Any ideas why the deployment of the decision services would fail?
    I have spent a fair bit of time as you do trying to resolve it but no luck so any help greatly appreciated. Searched google, metalink, technet etc.
    FYI I have edited the properties file to use a different port for HTTP etc. Again these settings worked fine for 'SelectManufacturer' so do not think there is a problem with the URI being used.
    Also appreciate on debugging could anyone tell me under the IAS control panel which log component I should set to get some more debug info on this deployment error. I have tried a few without success and cannot find a clear explanation of the various component logs.
    Thanks for reading my post Cel

    Hi James, thanks again for your reply.
    I went on to the linux server and ran the below to validate the URI:
    /oracle/product/10.1.3.1/OracleAS_1/jdk/bin/java -jar /oracle/product/10.1.3.1/OracleAS_1/j2ee/home/admin_client.jar deployer:oc4j:opmn://del4100.cel:6003/appserver/oc4j_soa oc4jadmin <password> -validateURI
    This is the same command being executed by jdeveloper when I try to deploy the decision service.
    I get the same error as with jdev:
    Failed at "Could not get DeploymentManager".
    I had a further look at the command and omitted the name of the application server instance which in my case is 'appserver', the default when you install SOA Suite.
    so now ran:
    /oracle/product/10.1.3.1/OracleAS_1/jdk/bin/java -jar /oracle/product/10.1.3.1/OracleAS_1/j2ee/home/admin_client.jar deployer:oc4j:opmn://del4100.cel:6003/oc4j_soa oc4jadmin <password> -validateURI
    This validated the successfully. Went back to jdev and commented out the line from the build.properties:
    # asinstancename=appserver
    Re-ran the ant build and this time the deployment of the decision service succeeded.
    This has now failed on the next stage of the build on compiling the bpel process SOAOrderBooking which I shall look at now.
    Do you know why the above would not work with the appserver instance name. I have checked and it is the correct name and spelling?
    I have another error now on the next stage of the build and wonder if this is related to it.
    The error I am getting is that could not read the wsdl and:
    Error happened when reading wsdl at "http://localhost:7777/esb/wsil/Fulfillment/OrderFulfillment?wsdl", because "Failed to read wsdl file at: "http://localhost:7777/esb/wsil/Fulfillment/OrderFulfillment?wsdl", caused by: java.net.ConnectException. : Connection refused: connect".
    Thanks for your suggestions and welcome any other comments on this next error as I wonder if it is related to the first one that I have worked around.
    Thanks Cel

  • Flex application not getting past preloader

    Hi,
    I have this Flex 4.1 application which sometimes refuses to show as it won't get past the preloader screen (I have attached a screenshot). The only solution is to refresh the page 2,3,4 or sometimes more times in order to get it to work. I've also tried running it in debug mode and then I'm not getting any errors so I don't know what is wrong here.. anyone have an idea? This is quite annoying, sometimes it works from the first time but mostly it doesn't.

    Actually I found that there was an error when running in debug from Flash Builder. But I have the debug player installed so I'm not sure why the error was not thrown?

  • Software Updates and SCUP updates are not getting rolled out during system rebuild.

    Hi,
    I am trying to rebuild the machines for one of my client and i am getting below error during Software update stage as it throws below error, Could someone please let me know why the below updates are getting failed.
    =======================[ smsswd.exe ] ======================= PackageID = '' BaseVar   = '', ContinueOnError='' SwdAction = '0001' Set command line: Run command line Working dir 'not set' Executing command line: Run command line Process completed with
    exit code 0 Command line returned 0 
    dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526
    failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd
    failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109 Received job completion notification from Updates Deployment Agent  Reboot Required Setting
    TSEnv variable SMSTSRebootRequested=HD Setting TSEnv variable SMSTSRetryRequested=TRUE Installation is not yet complete, action needs to be re-run after reboot Setting TSEnv variable SMSTSInstallUpdateJobGUID=
    109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr
    = 0x800b0109 Received job completion notification from Updates Deployment Agent  GetIPriviledgedInstallInterface successful Refreshing Updates Successfully initiated RefreshUpdates operation  Waiting for RefreshUpdates complete notification from
    UpdatesDeployment Agent Notification received, RefreshUpdates have been completed Signaled RefreshComplete notification Received RefreshUpdates complete notification from Updates Deployment Agent RefreshTargetedUpdates() returned S_FALSE which indicates a
    non fatal error. Update installation will continue. RefreshUpdates operation has been completed, hr=0x00000001 GetIComponentControllerInterface successful Installation of updates completed successfully Setting TSEnv variable SMSTSInstallUpdateJobGUID= 
    I have checked TS logs of few machines and there are few updates which are matching.
    Machine1 :
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109
    Machine 2 :
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5c5e9a15-238b-4df4-b0df-b1b28f2ce658 failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 
    Machine 3 :
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5c5e9a15-238b-4df4-b0df-b1b28f2ce658 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109 
    Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 

    Hi,
    The error translates to "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."
    Have you imported the WSUS self signed certificate or the certificates issued by your CA in the Task Sequence so that they are trusted during the OS deployment?
    More information can be found here:
    http://ccmexec.com/2011/06/system-center-updates-publisher-and-osd/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

Maybe you are looking for