Critical Services Not Starting Automatically & Access to Server occasionally dropping out
For the last few months we have been trying to resolve an issue where access to files on the server (SBS2011 - running domain services, exchange, etc) get so slow or just unresponsive. Logging onto the server is also not possible till it starts responding
again.
We also found that when the server starts, the Netlogon services does not start automatically event though it is set to auto start. There are a number of other services mainly exchange services that do not start as well but it seems this may be due to the
net service not starting.
We have re-installed the OS but this does not seem to have fixed the issue. The environment is a mix of the SBS2011 server, two Windows Server 2003 boxes - one running Terminal Services. The other was being used for SAP but no longer in use. The clients
are mainly XP with a few Windows 7 machines. We are in the process of planning the replacement of the XP machines.
You re-installed SBS2011? - that seems rather drastic. Did you maintain your domain or just set it all up again?
This sounds like a DNS issue but have a look at the event viewer and google/post the Event ID and Source. Given those two you can start to track down the cause and possible fixes at www.eventid.net. Just be aware that SBS2011 has a lot of
"normal" event errors, see http://support.microsoft.com/kb/2483007
You should also run the SBS best practice analyzer and maybe run the "Fix my network" wizard in the SBS console. Also make sure SBS is the DHCP server for the network.
-- Al
Similar Messages
-
SQL Server Reporting Services not starting automatically
Hi,
I have Reporting Services configured on my SharePoint 2010 Foundation server and the service is set to start automatically under a domain account. However, the service does not in fact start automatically and requires me to manually start it otherwise when
I try to use SharePoint to read some Reports, it doesn't work. Once I start the service, it works.
Is this normal behaviour? The service will remain started until the server is restarted (Windows Updates for example). I would like the service to start automatically when needed i.e. requesting to read a Report on SharePoint site.
Many thanksService should start automatic then, are you using some third party firewall that could block service?
And if you are using domain account for service, make sure it has log on as a service rights on local machine.
What is your event viewer saying?
In our domain environment we had similar problem with SQL and SSRS service, when I changed form of account for starting service from
domain\account to account@domain, problem was solved. I still don't really know how this helped. -
Listener service not start automatically after reboot in Win2K server Clust
Hi all,
I set up a two node Server Cluster with Microsoft Windows 2000 server cluster service. Hardware are two HP DL380 servers and HP MSA500 (the shared storage). The cluster's IP address is 10.1.241.65. When I shut down both servers and restart the primary server, the listener server service will not start automatically. The listener log is:
Started with pid=1108
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.241.65)(PORT=1521)))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
32-bit Windows Error: 49: Unknown error
The service is set up automatically start. I suspect the cluster virtual IP is not available immediately after reboot. So I tried setting the Recovery after first failure and second failure to 3 minitues each, and setting up Dependencies of the listener on the cluster service in the Win2K Service panel. Neither worked.
The service can be manually start.
Any suggestion?
Frank.The command to start automatically the listener is :
lsnrctl start
check the parameters in : <ORACLE_HOME>/network/admin/listener.ora
check the IP address or host name
Joel Pérez -
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 -
Invocation service not start automatically
hi, I have configured invocation service to start automatically as below, however, it did not work. And I need to code in application to get the service by CacheFactory.getService("MyInvocationService") to start it... why this is so? thanks.
Henry
<invocation-scheme>
<scheme-name>example-invocation</scheme-name>
<service-name>MyInvocationService</service-name>
<thread-count>10</thread-count>
<autostart system-property="tangosol.coherence.invocation.autostart">true</autostart>
</invocation-scheme>922963 wrote:
hi, I have configured invocation service to start automatically as below, however, it did not work. And I need to code in application to get the service by CacheFactory.getService("MyInvocationService") to start it... why this is so? thanks.
Henry
<invocation-scheme>
<scheme-name>example-invocation</scheme-name>
<service-name>MyInvocationService</service-name>
<thread-count>10</thread-count>
<autostart system-property="tangosol.coherence.invocation.autostart">true</autostart>
</invocation-scheme>Hi,
the autostart property provides information to the DefaultCacheServer.startServices() method and to methods it calls. That method will start the service if it is marked to be autostarted. The DefaultCacheServer class (the standalone cache server node script starts this application) is the only class which out-of-the-box calls that method (or possibly there are a few other ones like MBeanConnector).
But if you use your own main class then it is not automatically called, it is your responsibility to call that method (or DefaultCacheServer.start()) if you want the services to autostart. Read the javadoc of the DefaultCacheServer class for more info on methods in that class and variations between them (e.g. monitoring thread, which configurable cache factory is used, etc).
Best regards,
Robert -
Wily Enterprise Manager Service not Started in Windows 2008 Server
Hi All,
Our Solution Manager is in EHP1 SP21 and OS-Windows 2008 Server.
We installed Wily Enterprise Manager 8.0. and found 1 non-fatal error in the installation log. The service is not starting.
However it works fine for Windows 2003 Server.
Can anyone encountered with the same kind of problem?
This is the latest log file information:
Summary
Installation: Successfulwith errors.
387 Successes
0 Warnings
1 NonFatalErrors
0 FatalErrors
Action Notes:
Execute ANT Script: Script:
Status: ERROR
Additional Notes: ERROR - E:\usr\sap\ccms\wilyintroscope\install\em.installer.exec.ant15.xml:425: Timeout: killed the sub-process
Thank you in advance.
Regards
SanjaiNote 1273028 - Introscope 8 Release Notes resoved this issue.
Known problems in all Releases 8.x
2. Windows Server 2008 is not yet officially supported by CA Wily for the Enterprise Manager. If you want to install the Enterprise Manager anyway, set the "Windows 2003 compatibility mode" for the installer before launching it. To activate this mode, right click on the installer.exe file in the Windows Explorer, select tab "Compatibility", activate the check box for compatibility mode and select Windows 2003. If you do not set this, the installer will consider your OS as Unix and install shell scripts (no suffix) instead of batch files (.bat) and leave out some files for Windows Service registration.
If the windows service still fails to start please check if files ServiceWrapper.jar and ServiceWrapper.dll are present in folder lib. If not download them from attachment of this note.
The service should start although giving an error message regarding the ServiceWrapper.dll. You can ignore this error. -
MSExchangeSA and IS is not starting automatic at reboot after upgrading the server from SP1 to SP2
I am running a 2 node DAG with separate Hub & CAS servers
I have already upgraded the Hub CAS server and they are fine
Exchange running on Windows 2008 R2 SP1
All are in VM-Ware ESXi 5.0
After I upgrade the mailbox server to SP2 the SA and IS service not starting automatic after reboot
If I run "net time /set" command and then restart ADtopology server, the IS and SA starts fine
But again after reboot they do not start
Also I get the below event in the app log when the IS & SA fails to start
Log Name: Application
Source: MSExchangeIS
Date: 05/22/2012 5:15:03 AM
Event ID: 5003
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: server.domain.com
Description:
Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either on the client or on the server, and may require a restart of that computer. Verify that your domain is correctly
configured and is currently online.
If I check the Registry for time resource it is taking from the DC
I manually compared the time between DC and Exchange and it is fine
Since the Exchange mailbox is virtual, I checked the time sync on VM-Ware tools and it is "unchecked"
Checked for group policy and do not find any specific to time sync.
Confirmed that Windows Time service is running
Suspecting a Operating system issue, tried to upgrade the other DAG
Even that node is displaying the same symptom and Issues
Tried to install RU1 on both nodes and that too did not fix the issue.
Checked with VM-Ware engineer and he said that every thing from VM-Ware end is fine
Is Anyone have come across the issue before ?Exchange 2010: Unable to initialize the Information Store
Problem:
Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either in the client or the server, and may require a reboot of that computer. Verify that
your domain is properly configured and is currently online.
Solution:
Open a cmd prompt from the Exchange Server as administrator (right mouse click on the command prompt shortcut and select “Run as Administrator”)
Run this command
Net time \\ADServerName /Set
Restart the Microsoft Exchange Active Directory Topology Service
*Important!! You have to restart the Microsoft Exchange Active Directory Topology Service or this fix will not work.. I tried just starting the Information Store service after running the command it it still failed..
This worked for me and all is well on my exchange server.
- See more at: http://www.mountainvistatech.com/2012/06/04/exchange-2010-unable-to-initialize-the-information-store/#sthash.SwQpgQEM.dpuf -
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. -
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 -
Windows listener service will not start automatically
I just installed 11.2.0.3 Standard Edition One and when I reboot the server, the listener service is not started. The service is set to start Automatically. I have to login, open services and then push start.
The oraceServiceSId does start automatically,
The listerner service does not start automatically,
The dbconsole service does not start automatically,
The processManger1 service (from middleware) does not start automatically
This is Windows 7 64 bit.
Any ideas?
Edited by: brian.mcginity on Dec 10, 2011 11:25 AMI found where the services logs are recorded in the event viewer. Funny thing just happened, I was just about to do another reboot so I could check the logs when I noticed there were window updates in q.
So after running the updates, the os requested to reboot . For the first time, the services started automatically.
These are the updates which fixes the probem:
Security Update for Windows 7 for x64-based Systems (KB2639417)
Cumulative Security Update for Internet Explorer 9 for Windows 7 for x64-based Systems (KB2618444)
Security Update for Windows 7 for x64-based Systems (KB2620712)
Cumulative Security Update for ActiveX Killbits for Windows 7 for x64-based Systems (KB2618451)
Edited by: brian.mcginity on Dec 13, 2011 9:52 PM
Edited by: brian.mcginity on Dec 13, 2011 9:53 PM -
Windows listener +service does not start automatically eventhough Automatic
Hi
When I restart the database server, the listener is not starting automatically , so as the service.
Both are set to start automatically.
This was working before and all of a sudden, this problem appeared.
I dont remember changing any setting on the database side but on windows server side, not sure if anything is changed.
The error we received:
============
The OracleServiceGEOOAP service failed to start due to the following error: %%1053 Service error on GEPGPO01-V
The OracleOraDb11g_home1TNSListener service failed to start due to the following error: %%1053 Service error on GEPGPO01-V
alert log
=======
Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.7.0 - Production
Time: 11-MAR-2011 15:44:26
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
listener.log
========
Fri Mar 11 15:44:23 2011
11-MAR-2011 15:44:23 * service_update * geop * 0
11-MAR-2011 15:44:29 * service_died * geooap * 12547
TNS-12547: TNS:lost contact
11-MAR-2011 15:44:30 * service_died * geop * 12547
TNS-12547: TNS:lost contact
Fri Mar 11 15:44:37 2011
11-MAR-2011 15:44:37 * (CONNECT_DATA=(SID=GEOOAP)(CID=(PROGRAM=C:\Program Files\Quest Software\Toad for Oracle\toad.exe)(HOST=D00661)(USER=app_nathv))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.4.136.230)(PORT=65288)) * establish * GEOOAP * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
11-MAR-2011 15:44:41 * (CONNECT_DATA=(SID=GEOOAP)(CID=(PROGRAM=C:\Program Files\Quest Software\Toad for Oracle\toad.exe)(HOST=D00661)(USER=app_nathv))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.4.136.230)(PORT=65289)) * establish * GEOOAP * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
11-MAR-2011 15:44:43 * (CONNECT_DATA=(SID=GEOOAP)(CID=(PROGRAM=C:\Program Files\Quest Software\Toad for Oracle\toad.exe)(HOST=D00661)(USER=app_nathv))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.4.136.230)(PORT=65290)) * establish * GEOOAP * 12505
TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
Fri Mar 11 15:53:46 2011
So now we have to manually restart the listener and service , for the database to be opened. Is it possible to give direction what areas need to check, to solve this issue?
Thanks.Hi Krithi,
Can you confirm my understanding here:
* Since a short time the automatic startup of the listener and Oracle instance fail.
* You can manually startup the listener and database instance without any problem, and then all runs as expected
so far so good?
What's your procedure to start the listener and DB instances?
Are you performing the startups with your own user account, or SYSTEM, or a dedicated Oracle account?
Are the windows services running under SYSTEM, a dedicated Oracle user....??
Could it be that the system administrator installed something (like a new Oracle client) which would have changed some settings?
Can you compare the environment variables (ORACLE_HOME, ORACLE_SID, PATH) between the account YOU use for manual startup and those for the user account used to (auto)start the services?
Maybe you can try to plan a reboot after you have set the problematic services to run under your profile?
Well.... a few points to investigate if not yet considered.
HTH,
Thierry -
Hi,
I am trying to upgrade Exchange 2010 SP2 from SP1, but Transport service does not start automatically.
Tried manually start services, it started successfully but again goes down within few seconds automatically.
Reboot server. but no luck.
Any help.
MDHi,
I recommend you use event viewer to check if there are any relate event logs. This may help us to find the cause.
In addition, as Amit mentioned, Exchange 2010 SP2 isn't supported by Microsoft, I think upgrading to SP3 is a much more sensible approach.
Thanks.
Niko Cheng
TechNet Community Support -
After Upgrade, Windows Service will not start automaticly
I just upgraded from 10.2 to 10.4. When I did the Windows File Service, will not start automaticly. I can start it manually, after a reboot. Any idea on how to fix this?
I am having the same problem on a clean install of Server 10.4.10, AFP & Web starts automatically on restart, but not Windows Service. This is the first time I have run into this, it starts fine on all other servers I administer. Then entry in /etc/hostconfig for SMBSERVER is set to "-YES-", there is no errors or messages of any kind in the console or system log, it just won't start.
This complicated with the problem I am having on the same server where I cannot connect via ARD after reboot without someone there physically plugging a monitor into the video port first (another open post I have - http://discussions.apple.com/message.jspa?messageID=5850246#5850246 ). So, doing maintenance at off-hours is almost unworkable. -
SunONE CS 5.1.1 HTTP Service will Not Start Automatically
Hello,
I have just upgraded from iPlanet Calendar Server 5.1 to SunOne Calendar Server 5.1.1. (great improvement). However, the HTTP service will not start automatically on boot anymore. But after the boot sequence, I can start in manually. There are no errors posted to the Event Log so I am not sure what exactly is happening here. Maybe an ICS.CONF setting? I am doing this on Windows NT Server 4.0, SP6a. Any help would be great - thanks.This is due to the fact that the directory server was not ready when the calendar needed it. I assume the directory server is running on the same machine as the calendar server.
What you have todo is the following :
you must create a dependancy between the http NT service and the LDAP NT service
- run regedt32.exe
- goto HKEY_LOCAL_MACHINE
- goto \system\currentcontrolset\services\iplanetcalendarhttpservice5
- you will see that this entry has alread an attribute with the name DependOnService
- click on it, and it will open
- add below tcpip the name of the service of the ldap. This service name can be found in the same
\system\currentcontrolset\services\
tree and begins with slapd-<instance-name>
when you reboot now, the http will wait until the LDAP has succesfully started before starting HTTP. -
OracleOraHome92ManagementServer service is not starting automatically
Hi all,
OracleOraHome92ManagementServer service is not starting automatically, though we have set it to start automatically. We get the following error message when we tried to start manually.
"Could not start the OracleOraHome92ManagementServer service on Local computer.
The service did not return an error. This could be an internal winodws error or an internal service error."
If we restart the entire server , then OracleOraHome92ManagementServer service is getting started automatically.
Kindly assist me in resolving the issue.
On analysing we find the error messages below is the error message.
VXA-2028 :
Unable to connect to OMS repository.
at oracle.sysman.vxa.VxaAppServer.startServices(VxaAppServer.java:1596)
at oracle.sysman.vxa.VxaAppServer.main(VxaAppServer.java:3144)
Error starting Oracle Management Server.
VXA-2028 :
Unable to connect to OMS repository."Could not start management server. Initialization failure"
OEMCTL for Windows NT: Version 9.2.0.1.0 Production
Copyright (c) 1998, 2002, Oracle Corporation. All rights reserved.
Starting the Oracle Management Server... [main][2012-1-4:9:14:7:67] VdbSession.processError: errorCode >12505<
[main][2012-1-4:9:14:7:67] VdbSession.processError: errorMsg >ORA-12505: TNS:listener could not resolve SID given in connect descriptor
<
[main][2012-1-4:9:14:7:67] VdbSession.processError: invalid connect string
[main][2012-1-4:9:14:17:129] VdbSession.processError: errorCode >12505<
[main][2012-1-4:9:14:17:129] VdbSession.processError: errorMsg >ORA-12505: TNS:listener could not resolve SIDIf you check internet most times it is about adding the ip address and hostname (+ FQDN ) in C:\WINNT\System32\Drivers\Etc\Hosts file. Do you have that in your hosts file?
Eric
Maybe you are looking for
-
What to do when your phone will not back up so you can transfer to a new device?
-
Problem with email web service
I'm trying to implement the email web service tutorial. When I run the application I get the initial page but when I try to send mail I get the following error: Service call exception; nested exception is: java.net.UnknownHostException: proxy We don
-
Hey all. Not long bought myself an X-FI Xtreme gamer edition, I installed it and set up the drivers, plugged in the speakers and set them up and found there was something wrong. I can't get surround sound!? At first I thought it was my speakers, and
-
SUS POs update with Goods Receipts and Invoices Information
Hi SRM Experts, We have a SRM - SUS - R/3 landscape. 1. We create POs in SRM (extended classic scenario) and transfer them to R/3 (via RFC) and to SUS (via XI Interfaces PurchaseOrderRequest_Out and PurchaseOrderChangeRequest_Out). 2. We post Goods
-
Thumbs up song playing on Pandora from lock screen on iPad.
I know this is a user forum, but I would like the ability to tell pandora I like a song from the lock screen. I'm thinking if many people send Apple this suggestion, then they will include it in a future update of iOS.