Error when deploy webapp to weblogic

Hi,
i am trying to deploy war file from jdeveloper to weblogic and i get this error:
conn_ucm = the name of the connection that i add to my project.
11:26:22 AM] Weblogic Server Exception: weblogic.application.ModuleException: [HTTP:101216]Servlet: "wcmInitServlet" failed to preload on startup in Web application: "webapp1.war".
oracle.stellent.wcm.common.LocalizedRuntimeException: java.lang.reflect.InvocationTargetException
at oracle.stellent.wcm.javaee.shared.ServletApplicationFactory.createInstance(ServletApplicationFactory.java:49)
at oracle.stellent.wcm.javaee.utils.ServletHelper.initializeApplication(ServletHelper.java:172)
at oracle.stellent.wcm.javaee.servlet.filter.WCMInitializeServlet.init(WCMInitializeServlet.java:41)
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:120)
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:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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: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.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.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:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at oracle.stellent.wcm.javaee.shared.ServletApplicationFactory.createInstance(ServletApplicationFactory.java:46)
... 45 more
Caused by: oracle.stellent.wcm.server.ServerException: !CORE_SERVERAPP_PROJECT_ERROR_INITIALIZING_APPLICATION! : Not Found.
at oracle.stellent.wcm.server.ServerContext.initialize(ServerContext.java:338)
at oracle.stellent.wcm.server.ServerContext.<init>(ServerContext.java:139)
at oracle.stellent.wcm.client.ClientApplication$1.<init>(ClientApplication.java:287)
at oracle.stellent.wcm.client.ClientApplication.createServerContext(ClientApplication.java:287)
at oracle.stellent.wcm.client.ClientApplication.initialize(ClientApplication.java:272)
at oracle.stellent.wcm.javaee.servlet.WCMServletApplication.<init>(WCMServletApplication.java:49)
... 50 more
Caused by: java.lang.RuntimeException: oracle.stellent.wcm.common.LocalizedRuntimeException: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.stellent.wcm.core.idc.IdcClientFactory.<init>(IdcClientFactory.java:62)
at oracle.stellent.wcm.server.ServerContext.initialize(ServerContext.java:277)
... 55 more
Caused by: oracle.stellent.wcm.common.LocalizedRuntimeException: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.stellent.wcm.core.idc.IdcClientFactory.populateConfigFromADF(IdcClientFactory.java:258)
at oracle.stellent.wcm.core.idc.IdcClientFactory.initialize(IdcClientFactory.java:158)
at oracle.stellent.wcm.core.idc.IdcClientFactory.<init>(IdcClientFactory.java:57)
... 56 more
Caused by: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.adf.share.jndi.ContextImpl.findObject(ContextImpl.java:662)
at oracle.adf.share.jndi.ContextImpl.lookup(ContextImpl.java:152)
at oracle.adf.share.jndi.ContextImpl.lookup(ContextImpl.java:157)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.stellent.wcm.core.idc.IdcClientFactory.populateConfigFromADF(IdcClientFactory.java:224)
... 58 more
[11:26:22 AM] Caused by: java.lang.Throwable: Substituted for the exception java.lang.reflect.InvocationTargetException which lacks a String contructor, original message -
[11:26:22 AM] See server logs or server console for more details.
[11:26:22 AM] weblogic.application.ModuleException: [HTTP:101216]Servlet: "wcmInitServlet" failed to preload on startup in Web application: "webapp1.war".
oracle.stellent.wcm.common.LocalizedRuntimeException: java.lang.reflect.InvocationTargetException
at oracle.stellent.wcm.javaee.shared.ServletApplicationFactory.createInstance(ServletApplicationFactory.java:49)
at oracle.stellent.wcm.javaee.utils.ServletHelper.initializeApplication(ServletHelper.java:172)
at oracle.stellent.wcm.javaee.servlet.filter.WCMInitializeServlet.init(WCMInitializeServlet.java:41)
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:120)
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:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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: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.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.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:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at oracle.stellent.wcm.javaee.shared.ServletApplicationFactory.createInstance(ServletApplicationFactory.java:46)
... 45 more
Caused by: oracle.stellent.wcm.server.ServerException: !CORE_SERVERAPP_PROJECT_ERROR_INITIALIZING_APPLICATION! : Not Found.
at oracle.stellent.wcm.server.ServerContext.initialize(ServerContext.java:338)
at oracle.stellent.wcm.server.ServerContext.<init>(ServerContext.java:139)
at oracle.stellent.wcm.client.ClientApplication$1.<init>(ClientApplication.java:287)
at oracle.stellent.wcm.client.ClientApplication.createServerContext(ClientApplication.java:287)
at oracle.stellent.wcm.client.ClientApplication.initialize(ClientApplication.java:272)
at oracle.stellent.wcm.javaee.servlet.WCMServletApplication.<init>(WCMServletApplication.java:49)
... 50 more
Caused by: java.lang.RuntimeException: oracle.stellent.wcm.common.LocalizedRuntimeException: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.stellent.wcm.core.idc.IdcClientFactory.<init>(IdcClientFactory.java:62)
at oracle.stellent.wcm.server.ServerContext.initialize(ServerContext.java:277)
... 55 more
Caused by: oracle.stellent.wcm.common.LocalizedRuntimeException: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.stellent.wcm.core.idc.IdcClientFactory.populateConfigFromADF(IdcClientFactory.java:258)
at oracle.stellent.wcm.core.idc.IdcClientFactory.initialize(IdcClientFactory.java:158)
at oracle.stellent.wcm.core.idc.IdcClientFactory.<init>(IdcClientFactory.java:57)
... 56 more
Caused by: javax.naming.NameNotFoundException; remaining name 'conn_ucm'
at oracle.adf.share.jndi.ContextImpl.findObject(ContextImpl.java:662)
at oracle.adf.share.jndi.ContextImpl.lookup(ContextImpl.java:152)
at oracle.adf.share.jndi.ContextImpl.lookup(ContextImpl.java:157)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.stellent.wcm.core.idc.IdcClientFactory.populateConfigFromADF(IdcClientFactory.java:224)
... 58 more
please, any idea to solve this error?
eranz

Hi,
Looking at your Stack Trace it feels that your application is dependent on Some JNDI name (Usually some application components are dependent on some JNDI objects like DataSource/JMS Queues/Connection Factories) So while deploying the applications if those names are not binded in the JNDI tree of a the server where you are trying to deploy your applications.
The easiest way is to check the JNDI tree of your Server where you are trying to deploy your applications (Just to check whether any Object is binded there with JNDI Name "conn_ucm'" Which your application is asking for .
Thanks
Ravish Mody

Similar Messages

  • Error when deploying application in weblogic 10.0

    weblogic.application.ModuleException: [HTTP:101216]Servlet: "cds-service" failed to preload on startup in Web application: "/cds-wsclient".
              org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2PersistenceManager' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Cannot resolve reference to bean 'hdr2SessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
              Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
              Caused by: org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
                   at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:339)
                   at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176)
                   at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:805)
                   at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745)
                   at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:134)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1202)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:428)
                   at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
                   at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
                   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
                   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
                   at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:261)
                   at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:109)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1100)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:862)
                   at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:424)
                   at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
                   at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
                   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
                   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
                   at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
                   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
                   at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:330)
                   at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:266)
                   at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:236)
                   at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
                   at javax.servlet.GenericServlet.init(GenericServlet.java:241)
                   at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
                   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:63)
                   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:504)
                   at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
                   at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
                   at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
                   at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
                   at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
                   at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
                   at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
                   at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
                   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:26)
                   at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
                   at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
                   at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
                   at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
                   at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
                   at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
                   at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
                   at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
                   at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
                   at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
                   at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
                   at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
                   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)
                   at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
                   at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:950)
                   at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
                   at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
                   at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
                   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:26)
                   at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
                   at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
                   at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
                   at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
                   at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
                   at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
                   at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
                   at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
                   at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
                   at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
                   at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
                   at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
                   at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
                   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)
                   at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

    I was trying to deploy a Hibernate based application on WL 10.0 . I was getting this exception.
              your help would be greatly appreciated.

  • Error when deploy application on weblogic's console(weblogic 10 on AIX)

    ?:|
    After successfully start weblogic,I access console and select "Deployment".While I click "Finish" after choose the application named "ls_app", an error appears as follow.
    - Messages
    The deployment has not been installed.
    java.lang.NullPointerException
    The log information from weblogic is as follow::-(
    Failures were detected while initiating distribute task for application 'ls_app'. Error is: ''
    WARN [PageFlowRequestProcessor] Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass".
    Page Flow actions in this module may not be handled correctly.
    Please help on this issue.Thanks!!:-)

    I have in log:
    2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
    l setLifecycleContextBuilder
    WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
    nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
    2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
    lize
    INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
    2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
    sourceProvider <init>
    INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
    2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
    trap add
    INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
    2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
    tchCredential
    WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
    mains\base_domain\config\oracle.
    2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
    Exception
    WARNING: Incomplete connection information
    Edited by: Debuger on Mar 26, 2009 11:18 AM

  • Invalid change to class error when deploying EJB

    We have EJBs that were built by Webgain Visual Cafe and successfully deploy
    to WLS 5.1. We then use the WLE EJB Deployer Tool to build WLE container
    classes and deploy the same EJBs in WLE 5.1.
    One EJB does not deploy in WLE. The ULOG error message is:
    133929.EA-LAWSTUC!JavaServer.517: main: IJENGINE_CAT:150: ERROR: Invalid
    change to class service.Request
    133929.EA-LAWSTUC!JavaServer.517: main: EJB_CAT:29: ERROR: While deploying
    jar ServiceEJB : com.beasys.weblogic.classloader.RedeploymentException:
    ERROR: Invalid change to class service.Request
    133929.EA-LAWSTUC!JavaServer.517: Finalizer: IJENGINE_CAT:152: INFO: Closing
    jar C:\aj\ServiceEJB_WLE.jar
    Does anyone know what can cause an "invalid change to class" error when
    deploying to WLE 5.1? Especially since the EJB deploys successfully in
    WLS.
    Carl Lawstuen

    Reason: database keeps a reference of the class in JAVA$CLASS$MD5$TABLE table. This table keeps a refrence to all java classes loaded in database, and is present in each schema you deploy classes. That's the reason why if you change the application module name, you can load this classes. It instead keeps a reference if you use DROP JAVA CLASS command to drop a java class from de database. Use DROP JAVA command to clear the reference of the dropped classes when dropping it.
    You can see this table as a class dictionary of the database, and you don't have to handle this records manually.

  • Error while deploying composite to weblogic

    Getting following error while deploying composite to weblogic; As I got some reason from google that, its because of jdk8. If it is a known issue, does oracle released any patch for this?
    8:16:43 AM] Server is most likely down. Please check the server status and make sure it is up.
    [08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
    [08:16:43 AM] HTTP error code returned [-1]
    [08:16:43 AM] Error message from server:
    Server is most likely down. Please check the server status and make sure it is up.
    [08:16:43 AM] Check server log for more details.
    [08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
    [08:16:43 AM] Deployment cancelled.
    [08:16:43 AM] ----  Deployment incomplete  ----.
    [08:16:43 AM] Error deploying archive file:/C:/JDeveloper/mywork/e2e-1201-composites/ValidatePayment/deploy/sca_ValidatePayment_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

    Hi Priya,
    Can you check the server status.It clearly says that the server is down.Check the status of the server and also the disk space .
    [08:16:43 AM] Error message from server:
    Server is most likely down. Please check the server status and make sure it is up.

  • Error when deploying a map

    hello i have the following error when deploying a map in a local database, the mapping is a simple transfert of data between two table,
    ORA-06550: line 0, column 0:
    ORA-04052: erreurs lors de la consultation de l'objet distant [email protected]@KCDBDEV
    ORA-00604: une erreur s'est produite au niveau SQL récursif 1
    ORA-01882: région de fuseau horaire introuvable
    ORA-02063: pré
    any help please
    thanks,
    tarek

    Hello thank u for helping, i have exactly the same problème in Error executing a query using a DB-Link
    but i am not inderstanding the solution, i found the same probleme in metalink, and the solution posted is:
    1. Create an errorstack of the ORA-1882 to see the ALTER SESSION SET TIME_ZONE statement that is causing the ORA-1882 during deployment. To create this errorstack, follow step 1 to 4 below:
    1. Just before you reproduce the error, open a SQL*Plus session with user SYSTEM.
    SQL> alter system set events '1882 trace name ERRORSTACK level 3'
    2. Deploy the mapping to reproduce the ORA-1882
    3. Disable the system event
    SQL> alter system set events '1882 trace name errorstack off';
    4. Take a look at the errorstack (located in the udump directory). Suppose the following statement is in there:
    ALTER SESSION SET TIME_ZONE = 'GMT+02:00'
    2. Modify the run_service.sh(.bat) file as follow:
    * For UNIX:
    Modify owb_server_home/owb/bin/unix/run_service.sh as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started (last line of run_service.sh)
    $JAVAPATH/bin/java -Xmx768M -Djava.awt.headless=true -DORACLE_HOME.....
    e.g:
    $JAVAPATH/bin/java -Xmx768M -Duser.timezone="+02:00" -Djava.awt.headless=true -DORACLE_HOME
    * For Windows:`
    Modify owb_server_home\owb\bin\win32\run_service.bat as follows:
    Add the parameter -Duser.timezone="+02:00" to the line where java is started
    %JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS%
    e.g.:
    %JAVAPATH%\jre\bin\javaw.exe -Duser.timezone="+02:00" %JVM_OPTIONS%
    3. Save the file and re-start the Runtime Service using stop_service.sql/start_service.sql.
    but in creating the errorstack of the ORA-1882 i not found the ALTER SESSION SET TIME_ZONE
    and i Modify the run_service i fixed -Duser.timezone="+01:00" cause the time zone here is Europe/Paris but there is no changes.
    the db link is from Oracle 10.2.0.2.0 to 9.2.0.1.0. and owb 10g R2
    other solution?
    thanks,
    tarek

  • Error when deploying ear file

    Hello
    What could be the problem that I get this error when deploying my ear file with a web service within.
    [#|2008-03-29T17:43:02.640+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=12;_ThreadName=Thread-26;_RequestID=0a164c90-57bc-4d4a-8b3f-270fc4584891;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-apps\agency_app\agency_jar\META-INF\wsdl\AgencyModuleWebServiceService.wsdl (The system cannot find the file specified)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
         at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
         at java.net.URL.openStream(URL.java:1007)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:699)
         at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:643)
         at com.sun.enterprise.deployment.backend.WebServiceDeployer.doWebServiceDeployment(WebServiceDeployer.java:165)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:855)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:339)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:222)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:359)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:214)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    |#]when I deployed this application on a custom domain setup, it does not fail. But it fails on default domain.
    Regards
    Michael

    How did you create your datasource, can you post the content, without passwords of course.
    Greetings.

  • BUG: Entering a "version" when deploying to a WebLogic server doesn't work

    By default when deploying to a weblogic server the "Version" is set to v2.0. If you change that to something like v2.1 when the application is deployed, the deployment logs still show the Version=2.0. What needs to be done to get the Version in deployment to accept the changes on the deployment form?

    Sorry, I wasn't clear. This is a Portal application deployed using MDS. So it doesn't have the file referenced in that blog post. The Version field I'm referring to is on the form that pops up to set the MDS repository. For reasons unknown it will always come up v2.0 even during the first deployment. Regardless of what I change it to the Version always equals 2.0 in the deployment logs.

  • Getting Error when deploying the WD application

    hi all,
    Anybody have idea about , what is the reason for the following error. Till now it is working properly. suddenly it is giving the following error when deploying the application.
    2.4.2007 13:17:36 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [004]Deployment aborted
    Settings
    SDM host : eimkopdvs4
    SDM port : 50118
    URL to deploy : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
    Result
    => deployment aborted : file:/C:/WINDOWS/TEMP/temp2898TestWebDynproProj.ear
    Aborted: development component 'TestWebDynproProj'/'local'/'LOKAL'/'0.2007.04.02.13.17.28'/'0':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [EIMKOPDVS4] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
         at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:167)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
         at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
         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.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
         at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
         at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
         at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
         at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
         at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
         at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
         at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
         at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
         at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
         at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
         ... 37 more
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.4.71.36,port=50104,localport=3057]
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
         ... 1 more
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi,
    Check if the server is running. If so, try restarting it and then retry.

  • Using ADWrapper but has error when deploy to IIS

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??

    Dear all,
    I am using below link to develop the program.
    Active Directory in VB.Net
    But has error when deploy to IIS as attached screen. Do you  know how to solve??
    Hi,
    I am moving this thread to Using Forums >Where is the Forum For…?
    forum, the owner of the forum will direct you to a proper forum.
    I would recommend you check this thread
    http://social.msdn.microsoft.com/Forums/en-US/13bb6961-720d-4604-8eff-22251604cd94/active-directory?forum=whatforum
     which shared a place where you could get help, and since this thread has lasted for a long time, you could create a new thread of that forum to get supports.
    Hello,
    Thank you for the post.  I would suggest posting your question in one of the below mentioned Web sites. Hope this helps you.
    http://social.technet.microsoft.com/Forums/en/winserverDS/threads
    http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.active_directory&cat=en_us_5bd43452-4bab-4720-8df9-d5f37d3153b9&lang=en&cr=us
    Have a great day!
    Tier 2 Application Support  Server and Tools Online Operations Team
    Thanks for your understanding.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Gettind error when deploying XI module

    Hi,
    I am getting the following error when deploying XI module in J2EE Engine. can anyone help me to proceed. Thanks.
    08/02/22 16:16:59 -  Start updating EAR file...
    08/02/22 16:16:59 -  start-up mode is lazy
    08/02/22 16:17:12 -  EAR file updated successfully for 13047ms.
    08/02/22 16:17:12 -  Start deploying ...
    08/02/22 16:18:27 -  EAR file uploaded to server for 2656ms.
    08/02/22 16:18:29 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/SignEncrypt..
                         Reason: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.; nested exception is:
                              com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/SignEncrypt in container EJBContainer.
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                              ... 10 more
                         Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey;
                              at java.lang.Class.getDeclaredFields0(Native Method)
                              at java.lang.Class.privateGetDeclaredFields(Class.java:1522)
                              at java.lang.Class.getDeclaredFields(Class.java:1098)
                              at com.sap.engine.services.ejb.deploy.verifier.BeanClassCheck.check(BeanClassCheck.java:78)
                              at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:51)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
                              at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)

    Hi Indira.
    As I can see in your log, you're getting the exception
    Caused by: java.lang.NoClassDefFoundError: Lcom/sap/aii/af/service/auditlog/AuditMessageKey
    May be you need to include aii_af_svc.jar (AuditLog classes are located into this JAR library) in your EAR archive.
    Regards,
    Gari.

  • Error when deploying JDeveloper 11.1.1.3.0 to WebLogic 10.3

    Hi All,
    Trying to migrate an existing web application which was running on the old Oracle App Server to WebLogic 10.3. In the process upgraded Hibernate, Spring etc. other libraries. Left the existing Strut 1.1 alone. Getting the following error during deployment -
    <Aug 19, 2011 12:05:18 PM EDT> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Documents and Settings\tariq.ahsan\Application Data\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\AppServerConversion\MaintenanceWebWebApp.war. Please make sure that the annotations are valid. The error is org.apache.struts.action.ActionServlet>
    <Aug 19, 2011 12:05:18 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1313769914734' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'CFMSWeb''
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
    Caused By: java.lang.ClassNotFoundException: org.apache.struts.action.ActionServlet
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
    I checked if C:\Documents and Settings\tariq.ahsan\Application Data\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\AppServerConversion\MaintenanceWebWebApp.war\WEB-INF\lib contains the 'Struts.jar'. It doesn't. Could this be the problem?
    Thanks

    You need to add a library which contains all the classes used by struts. I have build a library containing these jars
    <jdev_install>\jdeveloper\jakarta-struts\lib\antlr.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-beanutils.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-collections.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-digester.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-fileupload.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-lang-2.1.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-logging.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\commons-validator.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\jakarta-oro.jar
    <jdev_install>\jdeveloper\jakarta-struts\lib\struts.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\adfm.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\adfmweb.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\adftransactionsdt.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\bc4jhtml.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\datatags.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\db-ca.jar
    <jdev_install>\oracle_common\modules\oracle.adf.model_11.1.1\jdev-cm.jar
    <jdev_install>\jdeveloper\modules\jakarta.jstl_1.1\lib\jstl.jar
    <jdev_install>\jdeveloper\modules\jakarta.jstl_1.1\lib\standard.jarYou need to change jdev_install with the path where you have installed jdev.
    Next you need to remove the content of the weblogic-application.xml. Here jdev has made some entries which later prevent the struts servlet to wort. My weblogic-application.xml looks like
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
    </weblogic-application>Then you need to check the web.xml file as jdev tends to make addition here too.
    Timo

  • Ejb-ref errore when deploying a previously working ear on weblogic 8.1

    when deploying an ear module on weblogic 8.1 i get the following error:
    The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
    or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
    not be resolved. The target EJB for the ejb ref could not be found.
    The ear is composed of two sub-modules:
    CustomMessaginBrick.jar
    cmbrick.war.
    The same ear was deployed on weblogic 6.1.
    Every reference in the ear seems in the right place so i am really clueless.
    Hereafter i include the relevant portions of the deployment descriptors.
    Thanks in advance!
    Greets,
    Luca
    the web.xml for cmbrick.war contains the following data:
    <ejb-local-ref>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
    <local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
    <ejb-link>CustomMessagingBrick</ejb-link>
    </ejb-local-ref>
    its weblogic.xml file is the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <jndi-name>Service2</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-web-app>
    while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
    <weblogic-enterprise-bean>
    <ejb-name>CustomMessagingBrick</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>Service2</jndi-name>
    </weblogic-enterprise-bean>....

    The issue is that WLS 6.1 didn't really support ejb-links properly. An
    ejb-link should allow you to link a webapp or an ejb to another EJB
    without requiring additional information or a global JNDI name on the
    target EJB.
    WLS 8.1 is following your ejb-link and telling you there's not enough
    information.
    You have 2 options:
    1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
    using just an ejb-reference at that point, but you've already included
    the necessary information in the weblogic.xml that we can locate the EJB
    via its global jndi-name
    or
    2) Change the ejb-link to be
    <ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
    If you wanted to, you could then remove the reference info from the
    weblogic.xml
    -- Rob
    luca wrote:
    when deploying an ear module on weblogic 8.1 i get the following error:
    The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
    or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
    not be resolved. The target EJB for the ejb ref could not be found.
    The ear is composed of two sub-modules:
    CustomMessaginBrick.jar
    cmbrick.war.
    The same ear was deployed on weblogic 6.1.
    Every reference in the ear seems in the right place so i am really clueless.
    Hereafter i include the relevant portions of the deployment descriptors.
    Thanks in advance!
    Greets,
    Luca
    the web.xml for cmbrick.war contains the following data:
    <ejb-local-ref>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
    <local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
    <ejb-link>CustomMessagingBrick</ejb-link>
    </ejb-local-ref>
    its weblogic.xml file is the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <jndi-name>Service2</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-web-app>
    while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
    <weblogic-enterprise-bean>
    <ejb-name>CustomMessagingBrick</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>Service2</jndi-name>
    </weblogic-enterprise-bean>....

  • Error when deploying application in wiblogic WebLogic Server Version: 10.3.

    hi when doing deployment in my WebLogic Server Version: 10.3.6.0 am geitng this error
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false], [Extension-Name: oracle.jsp.next, exact-match: false], [Extension-Name: oracle.webcenter.framework, Specification-Version: 11.1.1, exact-match: false], [Extension-Name: oracle.webcenter.skin, Specification-Version: 11.1.1, exact-match: false].
    how can i install this libraires in weblogic i have install this in jdeveloper by help->check updatesEdited by: adf009 on 2013/01/29 11:47 AM

    Solution:
    open the weblogic server console, in home page--> click the Deployments-->Select the adf.oracle.domain-->select target tab-->Click Lock & Edit-->
    select the servers (admin and managed Server) and save.--> click Activate All changes.
    Redeploy the application.

  • Ejb-ref error when deploying a previously working ear on weblogic 8.1

    when deploying an ear module on weblogic 8.1 i get the following error:
    The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
    or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
    not be resolved. The target EJB for the ejb ref could not be found.
    The ear is composed of two sub-modules:
    CustomMessaginBrick.jar
    cmbrick.war.
    The same ear was deployed on weblogic 6.1.
    Every reference in the ear seems in the right place so i am really clueless.
    Hereafter i include the relevant portions of the deployment descriptors.
    the web.xml for cmbrick.war contains the following data:
    <ejb-local-ref>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
    <local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
    <ejb-link>CustomMessagingBrick</ejb-link>
    </ejb-local-ref>
    its weblogic.xml file is the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <jndi-name>Service2</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-web-app>
    while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
    <weblogic-enterprise-bean>
    <ejb-name>CustomMessagingBrick</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>Service2</jndi-name>
    </weblogic-enterprise-bean>....

    when deploying an ear module on weblogic 8.1 i get the following error:
    The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
    or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
    not be resolved. The target EJB for the ejb ref could not be found.
    The ear is composed of two sub-modules:
    CustomMessaginBrick.jar
    cmbrick.war.
    The same ear was deployed on weblogic 6.1.
    Every reference in the ear seems in the right place so i am really clueless.
    Hereafter i include the relevant portions of the deployment descriptors.
    the web.xml for cmbrick.war contains the following data:
    <ejb-local-ref>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
    <local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
    <ejb-link>CustomMessagingBrick</ejb-link>
    </ejb-local-ref>
    its weblogic.xml file is the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/Service2</ejb-ref-name>
    <jndi-name>Service2</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-web-app>
    while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
    <weblogic-enterprise-bean>
    <ejb-name>CustomMessagingBrick</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>Service2</jndi-name>
    </weblogic-enterprise-bean>....

Maybe you are looking for

  • How to get data passed back to server from Web Start client ?

    dear experts, my web application allows users to launch a web start window from the jsp page, after users enters some data in the web start page and press "OK", the data entered should be passed back server for process. i just have not much clue how

  • Browser background uploaded to my mac host but not my real website :( help!

    Hello, Thanks in advance for your help. Go easy on me, I'm not too technically savvy. So, a picture is worth a thousand words. I can't for the life of me understand why the browser background doesn't show up on my regular website. the other things th

  • SQL Developer v 1.1 - Debug

    SQL Developer on Windows XP desktop Connected to Unix server Oracle9i Enterprise Edition Release 9.2.0.6.0 Problem: I cannot get debug working in the new download of SQL Developer ver 1.1 I compile for debug That works But then none of the items in t

  • V$sql and v$sqlarea

    Go no replies under DB General, trying over here. I am trying to understand parsing_user_id and child_number in v$sql and how the numbers roll up into v$sqlarea. Here are some examples: SQL> select hash_value, parsing_user_id, child_number, execution

  • ORA-25150: ALTERING of extent parameters not permitted

    hello all, I am getting this error with my rman catalog db. ORA-01653: unable to extend table RMAN.ROUT by 128 in tablespace USERS USERS is locally managed , now how can i extend to unlimited as I can't with command alter table rman.rout storage(maxe