Portal Server 6.2 does not start

Hi, i have installed Portal Server 6.2 with Identity 6.1 and Web Server 6.1 versions.
When attempt to start the Web Server or the Portal Server, to be generated errors of java in log of the web server.
It is possible that some ClassPath it�s missing in the configuration?
Somebody helps me?
Logs of the Web server is the following ones:
[29/Sep/2009:17:59:50] info (28363): CORE1116: Sun ONE Web Server 6.1 B09/11/2003 19:00
[29/Sep/2009:17:59:50] info (28364): CORE3016: daemon is running as super-user
[29/Sep/2009:17:59:50] info (28364): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.1_06] from [Sun Microsystems Inc.]
[29/Sep/2009:17:59:50] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [amserver]
[29/Sep/2009:17:59:52] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [amconsole]
[29/Sep/2009:17:59:52] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [ampassword]
[29/Sep/2009:17:59:52] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [amcommon]
[29/Sep/2009:17:59:52] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [portal]
[29/Sep/2009:17:59:52] warning (28364): WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[29/Sep/2009:17:59:52] info (28364): WEB0100: Loading web module in virtual server [https-ccsesp01.intranet.rts] at [search]
[29/Sep/2009:17:59:57] failure (28364): CORE4007: Internal error: Unexpected Java exception thrown (java.lang.NoClassDefFoundError: com/iplanet/am/console/base/ConsoleServletBase, com/iplanet/am/console/base/ConsoleServletBase), stack: java.lang.NoClassDefFoundError: com/iplanet/am/console/base/ConsoleServletBase
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1715)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:982)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1429)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1299)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:870)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3455)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3737)
at com.iplanet.ias.web.WebModule.start(WebModule.java:238)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
at com.iplanet.ias.web.WebContainer.start(WebContainer.java:411)
at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:506)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[29/Sep/2009:17:59:57] failure (28364): CORE3186: Failed to set configuration
Thanks

Did you install the portal with some user other than root? (ie, the user that runs portal)
Try changing the permissions of the portal fles to that user and see if that helps.

Similar Messages

If default domain name and server name is not accepted weblogic server 6.1 does not start as NT service

I want to change the domain name and the server name ( I do not want
mydomain, myserver) while installing
weblogic as an NT service. After installing and starting weblogic from NT
services program, weblogic does not start
But if I start it from the command script, it starts
Thanks
madhu

Hi,
I could start weblogic as an nt service by changing the name of the
default server and domain. I had to include password in the
installNTservice script.
Thanks
Madhu
Michael Young <[email protected]> wrote in message
news:[email protected]..
Hi.
Please open a case with BEA support.
Thanks,
Michael
m holur wrote:
I want to change the domain name and the server name ( I do not want
mydomain, myserver) while installing
weblogic as an NT service. After installing and starting weblogic from
NT
services program, weblogic does not start
But if I start it from the command script, it starts
Thanks
madhu--
Developer Relations Engineer
BEA Support

Quicktime Streaming Server - qtss - service does not start in Server Admin.

Hi,
We're currently trying to configure a video/audio streaming server, but we've fallen at the first hurdle and the QuickTime Streaming service will not start (I am trying to enable it via Server Admin). Can anyone think of any possible reasons for this?
Many thanks,
Dave

It's probably not hugely relevant but are you trying to start it remotely or locally on the server? I know Server Admin can get a bit laggy and not always do what it should when starting services. Also can you check in the logs for the service (Quicktime Streaming>Logs>Error Log) to see if there's anything in there which gives and indication. Paste the output here if you need anymore help with that.
N.

Absence request workflow does not start

Hello, I have created a workflow for absence request and I configured it in transaction PTARQ for my absence type.
I tried several times making an absence request from portal but the workflow does not start. I have also seen in transaction PTARQ that the request was really made and has status SENT but has no workflow associated.
Any help?
Thanks

Hi Mário,
Check using transaction SWIA to see if the workflow is actually started by the leave creation (if not could be a problem with the event trigger)? If it is started, you should see in SWIA where the workflow stops/breaks down, normally this is due to missing container elements or bindings.
Good luck!
Gareth

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                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)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Opmn does not start all processs when server ( windows 2003 is rebooted ).

There is a startup script which starts every process when run from cmd. But when the server is rebooted it does not start Portal, WebCache.
The startup Script :
@ECHO OFF
REM ---------------------------------------------
REM 10gAS Rel 2 Midtier startup script
REM ---------------------------------------------
date /t
time /t
REM ----------------------------------
REM Set Oracle Home
REm -----------------------------------
set ORACLE_HOME=d:\Oracle\Ora10gMid
set PATH=%ORACLE_HOME%\bin;%ORACLE_HOME%\dcm\bin;%ORACLE_HOME%\opmn\bin;%PATH%;
REM ----------------------------------
REM startup ProcessManager (OPMN)
REM ----------------------------------
REM call %ORACLE_HOME%\opmn\bin\opmnctl startall
call %ORACLE_HOME%\opmn\bin\opmnctl start
call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=WebCache
call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=OC4J
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=WebCacheAdmin
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=home
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=OC4J_BI_Forms
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=OC4J_Portal
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=HTTP_Server
REM call %ORACLE_HOME%\opmn\bin\opmnctl startproc ias-component=Discoverer
======================================================
I tried starting each process type individually and it does not start OC4J and WebCache components. This does not work only during reboot.
Thanks in advance for our valuable suggestions
v

no bat file is needed for opmn to startall on service restart or system reboot. Opmn remembers the state of the services on a clean shutdown of the service & will bring it back. So just do a opmn startall, then restart the Oracle<OraHome>ProcessManager service & check using opmn status. All services should be in the same state as before the Oracle<OraHome>ProcessManager was restarted.
where/why are you trying to use a bat file to stopall/startall? It can be done via a script, but the user that starts the bat file MUST be the same user that installed OAS/OID.

Portal does not start after RI installation

Hi,
we installed the EP 6 with the RI. The installation went through all steps without problems.
At the end, when the portal should come up, the server does not start. The only message I receive in the trace log is:
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_svrsapep6
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_svrsapep6
[Thr 2892] Mon Apr 25 13:41:29 2005
[Thr 2892] *** ERROR => Invalid property value [box.number/J2EJC00svrsapep6] [jstartxx.c   808]
[Thr 2892] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   808]
What may be the reason for this and how can we fix this in a way that the server will startup properly?
Thanks in advance

Hi,
the error message didn't mean anything. The only problem was that the JVM had a to high memory setting. We were running the portal in a VMWare with just 1.5 GB RAM. When we changed the amount of the heap memory size in the configtool, the portal came up.

Portal does not start up

hi,
I am are running sap enterprise portal. I used the Visual Admin to stop some applications (VA -> server -> services -> deploy -> Applications). I also stopped the application IRJ (which is the portal application), which was a big error from me because
unfortunately the j2ee enigne does not start up any more. Does anyone know a possibility to activate the irj application (in offline mode) again? The VA only works with a running j2ee engine.
Regards
Michael

Hi Michael,
Im not sure about what exactly you changed, but have you try to change it back using Configtool? (Offline editor)
Also check the error in the logs std_server0.out and std_dispatcher.out
Hope this help!
Juan
Please reward with points if helpful

MII UDS does not start automatically on server reset

Hi,
MII UDS does not start automatically on server reset, although it was set as automatically start.
What could be the reason of this problem?
Thanks.

Hi,
Is the runtime mode is set to service?
Have you referred this document?
[Programatically Starting and Stopping an SAP xMII UDS Executable Instance|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0f460c3-7f92-2910-02af-b608f92977c3]
Regards,
Musarrat
Edited by: Musarrat Husain on Jul 6, 2011 8:27 PM

Oracle service, Listener and http server does not start automatically

Hello,
I have Oracle 9i release 2 installed on Unix HP box if system restart in case of power failure the Oracle service, Listener and http server does not start automatically, is there any ready reference available to check what's wrong is happening(I don't have knowledge of Unix).
Thanks, Khawar.

Hi Rajesh,
Thanks for reply, I will check this link and will be back if facing problem.
Regards, Khawar.

Microsoft Forefront Server Protection for Exchange Registration Service does not start automatically

Hello,
I am having an issue when I start my TMG 2010 machine:
(*TMG 2010 + Forefront protection for Exchange + Exchange Edge server role, acting like a SMTP relay and Antispam filter)
The service "Microsoft Forefront Server Protection for Exchange Registration Service"
does not start, it is set to "Manual".
I tried to find some information about which services should be started and which should not, but I cannot find such information, not even in Technet (my fault probably).
Thanks in advance.
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Hi,
Have you received any errors in event logs when
you started the Microsoft Forefront Server Protection for Exchange Registration Service?
Based on my research,
Microsoft Forefront Server Protection Controller service is a dependency of the Microsoft Forefront Server Protection Registration service and the Microsoft Forefront
Server Protection Registration service is a dependency of the Microsoft Exchange Transport service.
The Microsoft Forefront Server Protection Registration service normally only runs for a brief time (less than a minute) when FPE initializes. It then shuts
down and does not need to be running for transport scanning to occur.
You can refer to the link below:
Services
Best regards,
Susie

J2EE 5 sneak preview:Server does not start

Hi,
I need some help since after installation of the sneak preview 5 I could not start the server.
The db and the central instance are running but not the server.
1)I get always time out error"StartWait
FAIL: process jstart.exe J2EE Server not running
The WAS is installed on a USB2 hard disk.
2)Furtheremore I cannot operate on the SAP management Console since I get Authorization error.
I installed the was with windows user IT/paceg
which is by Domain IT accessible even if I am not in the Domain.
Anyone can help me,please?
thanks
Bye,
Giamma
===================================================
============== Starting System JP1 ================
===================================================
=============== Starting database instance ...
Servizio richiesto già avviato.
Ulteriori informazioni sono disponibili digitando NET HELPMSG 2182.
The MaxDB Database Starter, Version 7.6.00.33
Copyright 2000-2006 by SAP AG
OK
============== Starting central services instance ...
09.10.2006 12:37:21
Start
OK
09.10.2006 12:37:21
StartWait
OK
============== Starting java instance ...
09.10.2006 12:37:21
Start
OK
09.10.2006 12:38:36
StartWait
FAIL: process jstart.exe J2EE Server not running
============== Start operation timed out !
Premere un tasto per continuare . . .

Just for update:
The error means that the message server is not able to translate the IP address into the hostname (reverse name lookup). If this fails the Startup Framework cannot connect to the message server and the server does not start. Please check the network setup on this host.
Replay:
thanks to all.
all is done:Just insert my loopback ip 10.10.0.10 in file host resolving on my host name romnb120.
Regards Galin

Connection Server does not start

Hello guys,
The Connection Server does not start anymore.
When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).
It's a BOE XI 3.1 SP2 with IK 3.1 SP2 installed on a Windows 2003 Server.
BO XI database is on a SQL Server and all tables are there and seems to be OK
The log file for the connectserver via trace is below :
2010/01/28 19:06:43.339|>>| | | 4524|4528| |||||||||||||||TraceLog::Admin: logdir ('C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/')
2010/01/28 19:06:43.339|>>| | | 4524|4528| |||||||||||||||TraceLog::Admin: update ()
2010/01/28 19:06:43.339|==| | | 4524|4528| |||||||||||||||TraceBridge::Initialize: pullable set to 1
2010/01/28 19:06:43.339|==| | | 4524|4528| |||||||||||||||TraceLog state:
// device_info
// process        (process#pid)   = ConnectionServer#4524
// device         (name#deviceid) = ConnectionServer#MainDevice
// pull/push      (pullable)      = Pull
// pull mode settings
//   configfile   (ini)           = C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\logConfig\BO_trace.ini
//   every ... s (period)        = 60
// config
active        = true;
severity      = 'W';
importance    = '<<';
keep          = true;
always_close = false;
log_dir       = "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/";
2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Unknown.:
2010/01/28 19:06:43.402|==| | | 4524|4544| |||||||||||||||SIServiceStopThread::run: SIServiceStopThread::run exited
2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||CsContainer::uninitialize
2010/01/28 19:06:43.402|==| | | 4524|4528| |||||||||||||||TransientObjectMonitor stopMonitor()...
.\siserver.cpp:974: TraceLog message 11
2010/01/28 19:06:43.402|>>|A| | 4524|4528| |||||||||||||||assert failure: (.\siserver.cpp:974). (false : SIServerController::run: Unknown exception caught in server's uninitialization function).
Any help please?!
thank you very much.
Cesar

Hello,
I have the same problem (Connection Server does not start).
I'am under BOXI R2 SP6 (unix) and i have this error in my log when i want to start ConnectionServer :
Timestamp       ProcessID       ThreadID        Message
[Fri May 7 07:37:09 2010]      31154   1103673168      Log: level=3 cat=1 msg=35100 p=ConnectionServer started
[Fri May 7 07:37:09 2010]      31154   1103673168      trace message: SIServerController::run: Before initialize
[Fri May 7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:416): trace message: SUNIXDaemon::init: starting
[Fri May 7 07:37:09 2010]      31154   1103673168      trace message: SUNIXDaemon::init: redirecting stdio to /dev/null
[Fri May 7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:209): trace message: installing fg terminiation handler
[Fri May 7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:220): trace message: installing abnormal sys handler
[Fri May 7 07:37:09 2010]      31154   1103673168      (sidaemon.cpp:506): trace message: SUNIXDaemon::init: finished
[Fri May 7 07:37:09 2010]      31154   1103673168      Log: level=0 cat=14 msg=35101 p=The root server reported an error Unknown.
[Fri May 7 07:37:09 2010]      31154   1103673168      trace message: SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Un
known.:
[Fri May 7 07:37:09 2010]      31154   1103673168      trace message: CsContainer::uninitialize
[Fri May 7 07:37:09 2010]      31154   1103673168      trace message: TransientObjectMonitor stopMonitor()...
[Fri May 7 07:37:09 2010]      31154   1103673168      Log: level=0 cat=14 msg=35101 p=The root server reported an error Internal Error. (Reason: Unknown exception caught in ser
ver).
[Fri May 7 07:37:09 2010]      31154   1103673168      assert failure: (siserver.cpp:953). (false : SIServerController::run: Unknown exception caught in server's uninitializatio
n function
[Fri May 7 07:37:09 2010]      31154   1103673168      Log: level=3 cat=1 msg=35100 p=ConnectionServer stopped
Any idea ?
Thanks.

Certificate authority does not start on migrated 2012R2 server

I have migrated the root CA from windows 2003 to 2012R2 according to TechNet instructions
http://technet.microsoft.com/en-us/library/ee126140(v=ws.10).aspx
The service does not start.
The error shown is:
The dependency service does not exist or has been marked for deletion. 0x433 (WIN32: 1075 ERROR_SERVICE_DEPENDENCY_DELETED)
In the event log:
The Certificate Services service depends on the following service ProtectedStorage. This service might not be installed.
Thanks,
James.
James.

Hi Mark,
Thanks for helping me out here.
The CA is enterprise, has the same name and there is no hardware module. It is not on a Domain Controller. Its history is that it was a Windows 2000 CA that was upgraded to 2003 using a similar method (many years ago). There has been no customisations
or any changes from the default values.
I think I found the mistake I made. When I had edited the registry settings backup file, I had only changed file locations. I needed to also go through all the settings and delete those from the file that are not listed on the document. There was one setting
about dependent services that should not have been brought over to the new service. After I did this, the service started ok.
I also found I made another mistake, that I had not backed up the certificate templates from the old server and so could not restore them to the new server. When I go to the CA manager and click on Certificate Templates, it shows an error "Template
information could not be loaded".
Do you know if this is important?
Do I need to get the old templates or can I create new ones? We have not customised anything. I did not connect the new CA to the network yet, so it can not access AD.
That step is in another document for "preparing to migrate". Of course I googled straight into the "Migrating.." document, so missed it from my work list.
Regards,
James.
James.

Calendar server does not start

We installed an OCS onebox 90411 on Win 2000 Server in january. Since last week calendar server does not start:
D:\ocs_onebox\mtier\ocal\bin\unistart
unistart: Oracle Calendar Server 9.0.4
unistart: Copyright (c) 1993, 2003, Oracle.
unistart: All rights reserved.
unistart:
unistart: Starting the Calendar Lock Manager
unistart [error]: Error starting the Calendar Lock Manager
unistart [error]: More details can be found in 'D:\ocs_onebox\mtier\ocal\log\unistart.log'
unistart [error]: and in 'D:\ocs_onebox\mtier\ocal\log\lck.log'.
Last entry in lck.log is from january.
Last entries in unistart.log:
DATE = Wed Apr 14 21:44:02.718 2004
PID = 5336; TID = 5332
ERROR CODE -> 0x50B05
FUNCTION NAME -> ADM_Service::Start()
SIS_ServerStart failed ((unilckd) SIS_ServerStart: StartService error :1069,Der Dienst konnte wegen einer fehlerhaften Anmeldung nicht gestartet werden. )
DATE = Wed Apr 14 21:44:02.734 2004
PID = 5336; TID = 5332
ERROR CODE -> 0x50B05
FUNCTION NAME -> Unistart::ProcessLocalStartServer()
Error starting the Calendar Lock Manager. (unilckd) SIS_ServerStart: StartService error :1069,Der Dienst konnte wegen einer fehlerhaften Anmeldung nicht gestartet werden.
Any idea ?

Hi,
Please log a TAR for this issue.
Thanks,
Lily

Portal Server 6.2 does not start

Similar Messages

Maybe you are looking for