Server not starting - Failed to Connect to hostname/3201
Hi,
The Sneak Preview Version was working fine.. All of a sudden the server is not starting up.. It is throwing up the following error in the server0 log default.trc
##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to ganni/3201(Connection refused: connect)#
What is this server 3201.. How can i fix this issue..
Thanks,
Ganesh
Hi,
I assume you are talking about the ABAP Stack:
3201 is a port number, normally used on the ABAP Stack for dialog with SAP-Gui. 01 should be your system number. Did you change anything in the services File or any other configuration?
There should be an entry look like this:
File: C:\WINDOWS\system32\drivers\etc
sapdp01 3201/tcp
Possible reason: Port is allocated, Changed User credentials?
Regards,
Christian
Similar Messages
-
Weblogic server not starting due to connection pool error.
Hi all,
We have some issues with the network due to that, weblog server not able to create the connection pool or make physical connection with the database in the allocated time, we need to increase the timeout so that weblogic can wait and create a connection and then start the apps. How to achieve this?
Currently the server crashes and forcing to shutdown the error listed below
<Oct 10, 2012 5:08:47 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:09:48 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:49 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:50 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oltpDS' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:276)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1155)
Truncated. see log file for complete stacktrace
javax.naming.NameNotFoundException: Unable to resolve 'oltpDS'. Resolved ''; remaining name 'oltpDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.healthedge.j2ee.PooledConnectionHelper.addDataSource(PooledConnectionHelper.java:202)
at com.healthedge.j2ee.PooledConnectionHelper.getSTConnection(PooledConnectionHelper.java:281)
at com.healthedge.j2ee.PooledConnectionHelper.getConnectionIgnoreTxn(PooledConnectionHelper.java:268)
at com.healthedge.j2ee.PooledConnectionHelper.getConnection(PooledConnectionHelper.java:251)
at com.healthedge.query.execution.Query.prepareStatement(Query.java:504)
at com.healthedge.query.execution.Query.setValue(Query.java:716)
at com.healthedge.config.util.ReferenceResolutionHelper.setConstraintValues(ReferenceResolutionHelper.java:277)
at com.healthedge.config.util.ReferenceResolver.getTypeReference(ReferenceResolver.java:232)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:221)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:211)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:187)
at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:156)
at com.healthedge.config.eval.HicIdentifier.getReference(HicIdentifier.java:58)
at com.healthedge.startup.StartupService.startup(StartupService.java:56)
at com.healthedge.startup.wl.WLStartupService.main(WLStartupService.java:13)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
NESTED TRACES DONE
>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 10, 2012 5:11:18 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>Hi,
It looks like your DB is down for now and that is reason why the server cannot initialize your App while startup.
Check which Data source you are using and make initial capacity as zero and try to restart the server again.
Note: you need to do this changes from JMS module under %Domain_Home% / config / jdbc/
Regards,
Kal -
SOA server not starting: Due to change of hostname of SOA suite 11g
Hi friends,
My machine has been recently moved to a new location and hostname (ip address remains same) has changed. Hence, the soa server (admin server still running) on my machine is not starting up.
Some details are:
a.) Earlier hostname: CALTP8BB13
b.) New hostname: CALTP8BB16
From the soa server log files the details are as follows:
####<Jul 13, 2010 6:31:52 PM IST> <Info> <messaging.interception> <CALTP8BB16> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1279026112029> <BEA-400000> <Initializing message interception service>
####<Jul 13, 2010 6:31:54 PM IST> <Error> <Configuration Management> <CALTP8BB16> <soa_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1279026114342> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://CALTP8BB13:7001 during startup. Since bootstrap succeeded check that t3://CALTP8BB13:7001 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: CALTP8BB13]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:411)
at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:173)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any pointers regarding the same will be helpful.
Regards,
ShomitHi Shomit
As far as I know, the Domains Hostname is stored only in config.xml file. So IP Address is same just Host name is changed CALTP8BB13 to CALTP8BB16. Check for some basic things.
1. If on Windows OS, try adding this new Hostname and its IP address in hosts file located at C:\WINDOWS\system32\drivers\etc. If on Unix Env, I guess there should be a similar file to set the hostnames mapped with IP addresses.
2. Since the machine is moved to a brand new location and incase kind of different network, check the firewall settings to see if firewall is blocking this new hostname.
3. To make sure the domain is still good, I guess you already tested with old hostname after moving to new building. Try testing by giving the direct IP address also. This is just confirmation test to make sure domain is not messed up. If both of these works, it simply means issue is with Hostname and IP not getting mapped or new hostname getting blocked over the network. May be network folks can pitch in.
Hostname or IP addresses should not be in any startup or env scripts. Domainname, servername will be definetly there in lot of files but not the hostname or ip address as far as I know.
Thanks
Ravi Jegga -
Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)
Hello All,
There are some changes in out portal sever, but not related to SAP EP.
So it is needed to restart the server. After restarting the server,
we are not avail to start the server. There is nothing in the SAPMMC.
"There is no item to display" is showing in the SAPMMC.
So we tried couple of time to get the SAPMMC icons by restarting the server.
But it is not getting any display in SAPMMC.
I am sending some part of the latest log file of that server below:
Our server name is INMAA02AS03.
1.5#00145E3D3B630046000000000000175000041A3F6EB5EB39#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed#
#1.5#00145E3D3B630046000000010000175000041A3F6EB5EC0B#1154759649523#com.sap.engine.core.cluster.impl6.ms.MSEventListener##com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(protocol, port, serverCount)#######OrderedChannel for http service##0#0#Error##Plain###java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
#1.5#00145E3D3B630046000000020000175000041A3F6EB5F178#1154759649523#com.sap.engine.services.httpserver.dispatcher##com.sap.engine.services.httpserver.dispatcher#######OrderedChannel for http service##0#0#Error##Plain###Cannot update HTTP load balancing information in the Message service
com.sap.engine.frame.cluster.ClusterException: Socket closed
at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1377)
at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.putLogonInfo(MSConnectionImpl.java:605)
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.putLogonInfo(ClusterManagerImpl.java:3144)
at com.sap.engine.core.service630.context.cluster.session.CommunicationSessionContextImpl.putLogonInfo(CommunicationSessionContextImpl.java:143)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.putLogonInfo(HttpDispatcherFrame.java:854)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.closeSocket(HttpDispatcherFrame.java:800)
at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.stop(HttpDispatcherFrame.java:404)
at com.sap.engine.core.service630.container.ServiceStopper.run(ServiceStopper.java:31)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
Caused by: java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)
at com.sap.engine.core.cluster.impl6.ms.MSMessageHeader.write(MSMessageHeader.java:401)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:1017)
at com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendRawMessage(MSRawConnection.java:971)
at com.sap.engine.core.cluster.impl6.ms.MSEventListener.putLogonInfo(MSEventListener.java:1374)
... 10 more
#1.5#00145E3D3B6300400000000B0000175000041A3F6EC43762#1154759650461#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000D0000175000041A3F6EF146BF#1154759653414#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000000F0000175000041A3F6F1E56B0#1154759656367#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000110000175000041A3F6F4B6526#1154759659320#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000130000175000041A3F6F787519#1154759662273#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000150000175000041A3F6FA584C7#1154759665226#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000170000175000041A3F6FD29438#1154759668179#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000190000175000041A3F70014F86#1154759671242#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001B0000175000041A3F70300A99#1154759674304#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001D0000175000041A3F705D1A24#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000001F0000175000041A3F705D1B81#1154759677257#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 11 times#
#1.5#00145E3D3B630040000000210000175000041A3F708A296B#1154759680210#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000230000175000041A3F70B738CB#1154759683163#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000250000175000041A3F70E4487A#1154759686116#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000270000175000041A3F7111581F#1154759689069#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000290000175000041A3F713E67B3#1154759692022#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002B0000175000041A3F716B77A1#1154759694976#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002D0000175000041A3F719886C2#1154759697929#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000002F0000175000041A3F71C596D5#1154759700882#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000310000175000041A3F71F45176#1154759703944#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000330000175000041A3F72230C96#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000350000175000041A3F72230DF3#1154759707007#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 21 times#
#1.5#00145E3D3B630040000000370000175000041A3F72501BF9#1154759709960#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000390000175000041A3F727D2BC1#1154759712913#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003B0000175000041A3F72AA3BCA#1154759715866#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003D0000175000041A3F72D74B1A#1154759718819#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000003F0000175000041A3F73045A4C#1154759721772#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000410000175000041A3F73316A0D#1154759724725#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000430000175000041A3F735E799A#1154759727678#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000450000175000041A3F738D34D0#1154759730740#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000470000175000041A3F73BBEF81#1154759733803#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000490000175000041A3F73E8FF05#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004B0000175000041A3F73E90064#1154759736756#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 31 times#
#1.5#00145E3D3B6300400000004D0000175000041A3F74160E68#1154759739709#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000004F0000175000041A3F74431E16#1154759742662#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000510000175000041A3F74702DEA#1154759745615#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000530000175000041A3F749D421D#1154759748568#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000550000175000041A3F74CA4CD6#1154759751521#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000570000175000041A3F74F75CC8#1154759754474#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000590000175000041A3F75246C5C#1154759757427#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005B0000175000041A3F75517C0B#1154759760381#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005D0000175000041A3F7580368E#1154759763443#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B6300400000005F0000175000041A3F75AEF19A#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to INMAA02AS03/3201(Connection refused: connect)#
#1.5#00145E3D3B630040000000610000175000041A3F75AEF2F2#1154759766505#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######SAPEngine_System_Thread[impl:6]_5##0#0#Error#1#/System/Server#Plain###ReadThread: failed to connect to server 41 times#
Any idea what to do?
Please help me out.
**Points will be rewarded for a suitable answer.
Regards,
Uttam.Hi Uttam,
Were you able to solve the problem? I am also getting a similar error message. If you had solved your problem, please share, how?
Thanks & Regards,
Santhosh.C -
WebLogic admin server not starting.
Hi all,
I have a problem with my WebLogic Admin server not starting. Following a VM reboot last week our admin servers are no longer starting. On this particular server we have 3 admin servers serving 3 separate environments.
Theserver seems to be getting stuck right at the very start. I have tried removing tmp, cache and ldap directories. Searched for and removed all .lok files. I have manually turned on full debug to try and flush some extra information through standard out but no luck. It is very peculiar. When we have exported the domain to another box and started the admin server it has come up successfully.
This is the output from the logs - this is literally as far as it get before it hangs and does nothing. As far as I know the next thing WebLogic is doing is checking the version. Has anyone any ideas what the problem could be? It is server wide as all 3 admin servers on the same box are suffering the same problem.
This is Weblogic 10.3.2 on a Solaris vm
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Development
CLASSPATH=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/lib/tools.jar:/apps/Oracle/Middleware64/utils/config/10.3/config-launch.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.jar:/apps/Oracle/Middleware64/modules/features/weblogic.server.modules_10.3.2.0.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/webservices.jar:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/apps/Oracle/Middleware64/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/apps/Oracle/Middleware64/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/xqrl.jar
PATH=/apps/Oracle/Middleware64/wlserver_10.3/server/bin:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/jre/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin:/usr/bin:/usr/sfw/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
Starting WLS with line:
/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/apps/Oracle/Middleware64/wlserver_10.3 -Dwls.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
<09-Jan-2013 18:32:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.1-21-133393-1.6.0_20-20100512-2127-solaris-sparcv9 from Oracle Corporation>Just a wild guess (as you have restarted the physical servers), it could be related to the entropy of the machine.
What you can try to do is edit the java.security file in the $JAVA_HOME/jre/lib/security directory.
Find the entry securerandom.source and edit the value to file:/dev/./urandom (instead of file:/dev/urandom) -
System Landscape Directory server not started
Hi,
We are running Solution Manager 4.0 SP13.
When I log ito the NWA get the message : System Landscape Directory server not started
We are trying to configure CEN but only the Local System can be administered.
If I goto the Central SLD and login - Administration - Server Started.
If I look at the ABAP - Transaction SLDAPICUST - save configuration - all ok
I goto the Jco Connectors and ensure all Jco Connections are configured: SAPSLDAPI_SID
ABAP RFCs; All configured
ABAP - Transaction - sldcheck .. it returns with success.
I login to the ABAP stack - smgw - logged in clients and all Jco Connections are available
I go into the J2ee Admin - navigate to the SLD Data supplier - all tests return success.
The SLD CIM is version 1.5.20
The application com.sap.engine.class.download is started ( Note 1017526 )
However when I login to with the J2ee_admin tool the following is missing from the CIM Client:
sap.com/tclmwebadminmainframewd/webdynpro/public/lib/app.jar
sap.com/tclmwebadminsldwd/webdynpro/public/lib/app.jar
Please help.Hi Anand,
I verified the SLD Post Processing doc in case I missed something. The doc I used:
https://websmp106.sap-ag.de/~sapidb/011000358700003772372006E
I went through every point in the doc and verified that it was completed .
If I open Monitoring Setup Guide for SAP NetWeaver 7.0 SP Stack 12 ( Can't find 13 ) I go to page 68 :
6.5.2. Configuring the Connection Between CEN and the SLD ... I have followed all the steps without any error.:
I followed it Step-by-Step.... however the following CIM Client Genearations do not exist:
sap.com/tclmwebadminmainframewd/webdynpro/public/lib/app.jar
sap.com/tclmwebadminsldwd/webdynpro/public/lib/app.jar
What is available and Activated :
sap.com/tclmwebadminmainframewd/webdynpro/public/lib/sap.comtclmwebadminmainframe~wd.jar
sap.com/tclmwebadminsldwd/webdynpro/public/lib/sap.comtclmwebadminsld~wd.jar
I alos Decided for the purpose of Troubleshooting to Activate All:
sap.com/tclmwebadmin~mainframe.......
sap.com/tclmwebadmin~sld..........
When I go into NWA .. its still says SLD Not started.
If I go inot the J2ee Admin Tool - SLD Data Supplier - Trigger Data Transfer OK
I goto the SLD - Administration . SLD Started
I Can see all the Techinical systems - ABAP and Java.
All business Systems are there
SLDCHECK works fine .. no errors !
But I can't change the status of the NWA System Landscape Selectipon From Local to Central.
Warning / Error :
System Landscape Directory server not started
and
Only local system can be administered
I maybe missing something but I can't see what it is....
Further Help required ! -
Hi I have only files from catalog DATA form my SQL Server 2008. After I installed sql server and replates file in katalog DATA server not starting.
Where I have problem, what I need to do to work? thanks for any help
best regardsThis Is my Error log
2014-01-02 12:28:05.84 Server Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-01-02 12:28:05.84 Server (c) 2005 Microsoft Corporation.
2014-01-02 12:28:05.84 Server All rights reserved.
2014-01-02 12:28:05.84 Server Server process ID is 6840.
2014-01-02 12:28:05.84 Server System Manufacturer: 'Hewlett-Packard', System Model: 'HP ENVY Sleekbook 4 PC'.
2014-01-02 12:28:05.84 Server Authentication mode is WINDOWS-ONLY.
2014-01-02 12:28:05.84 Server Logging SQL Server messages in file 'F:\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2014-01-02 12:28:05.84 Server This instance of SQL Server last reported using a process ID of 6948 at 2014-01-02 12:22:16 (local) 2014-01-02 11:22:16 (UTC). This is an informational message only; no user action is required.
2014-01-02 12:28:05.84 Server Registry startup parameters:
-d F:\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e F:\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l F:\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2014-01-02 12:28:05.92 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-01-02 12:28:05.92 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-01-02 12:28:05.97 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-01-02 12:28:11.12 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-01-02 12:28:11.17 spid7s Starting up database 'master'.
2014-01-02 12:28:11.36 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2014-01-02 12:28:11.37 spid7s SQL Trace ID 1 was started by login "sa".
2014-01-02 12:28:11.37 spid7s Starting up database 'mssqlsystemresource'.
2014-01-02 12:28:11.39 spid7s The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2014-01-02 12:28:11.50 spid7s Error: 15466, Severity: 16, State: 1.
2014-01-02 12:28:11.50 spid7s An error occurred during decryption.
2014-01-02 12:28:11.53 spid10s Starting up database 'model'.
2014-01-02 12:28:11.55 spid7s Server name is 'MACIEK\SQLEXPRESS'. This is an informational message only. No user action is required.
2014-01-02 12:28:11.55 spid7s Informational: No full-text supported languages found.
2014-01-02 12:28:11.55 spid7s Starting up database 'msdb'.
2014-01-02 12:28:11.56 spid10s Error: 17204, Severity: 16, State: 1.
2014-01-02 12:28:11.56 spid10s FCB::Open failed: Could not open file E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\model.mdf for file number 1. OS error: 3(System nie może odnaleźć określonej ścieżki.).
2014-01-02 12:28:11.56 spid10s Error: 5120, Severity: 16, State: 101.
2014-01-02 12:28:11.56 spid10s Unable to open the physical file "E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\model.mdf". Operating system error 3: "3(System nie może odnaleźć określonej ścieżki.)".
2014-01-02 12:28:11.56 spid7s Error: 17204, Severity: 16, State: 1.
2014-01-02 12:28:11.56 spid7s FCB::Open failed: Could not open file E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 3(System nie może odnaleźć określonej ścieżki.).
2014-01-02 12:28:11.56 spid7s Error: 5120, Severity: 16, State: 101.
2014-01-02 12:28:11.56 spid7s Unable to open the physical file "E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBData.mdf". Operating system error 3: "3(System nie może odnaleźć określonej ścieżki.)".
2014-01-02 12:28:11.58 spid10s Error: 17207, Severity: 16, State: 1.
2014-01-02 12:28:11.58 spid10s FileMgr::StartLogFiles: Operating system error 2(Nie można odnaleźć określonego pliku.) occurred while creating or opening file 'E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2014-01-02 12:28:11.58 spid10s File activation failure. The physical file name "E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\modellog.ldf" may be incorrect.
2014-01-02 12:28:11.58 spid10s Error: 945, Severity: 14, State: 2.
2014-01-02 12:28:11.58 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2014-01-02 12:28:11.58 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2014-01-02 12:28:11.58 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2014-01-02 12:28:11.58 spid7s Error: 17207, Severity: 16, State: 1.
2014-01-02 12:28:11.58 spid7s FileMgr::StartLogFiles: Operating system error 2(Nie można odnaleźć określonego pliku.) occurred while creating or opening file 'E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2014-01-02 12:28:11.58 spid7s File activation failure. The physical file name "E:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\MSDBLog.ldf" may be incorrect.
Any idea? -
Hello,
The J2EE Server not starting. (Not able to communicate with message server)
The following is the description I got from SAP.
" Most likely you did configurations on the instance properties, instead
of the global properties, which is the one where the the configurations
should be done. That is why now you did set local properties
which are now false, for example : ume.ldap.access.server_port=[]
This is the cause why the LDAP connection data cannot be retrieved.
This is why the UME service cannot be started.
This is why the J2ee engine is not comming up. "
Pls help.Hi Karan
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool.
2.No go to instance -
>server----->services--->com.sap.security.core.ume.services node.
3.Look for ume.ldap.access.server_port=[]
4.See if you have changed the value for the above parameter.If yes change the value to default and restart the engine.It will work
If at all you want to change any configurations you should do it following the below steps:
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool
2.Go to Global Server Configurations-->Services--
>
Please award points: -
I installed Crystal Reports server 2008, i'm geting server not started erro
Hi,
I'm getting error with server not started or not available error (FWM 01003). If i check in CCM, i don't see any entry for CMS server entry. How to start CMS server??? Please advise me. i installed trail version of crystal reports server 2008.
thanks in advance!!!
Ben.I am a consultant for Business Object products and experienced the same exact problem. We were installing Business Objects Edge, which is similar to Crystal Reports Server 2008, with MS SQL Server 2000 SP4 for the CMS System Database on a server that was named <Numbers>-<Letters>.
We discovered that some scripts that the installation and CMS run fail when the Server Name of the Business Objects Edge Server start with a number. When the CMS System Database is setup, a table called CMS_IdNumbers6 is created. It should have three columns, NameId, IdName and third column that is named after the server where you are installing Crystal Reports Server 2008, Business Objects Edge or Business Objects Enterprise. This column is called <ServerName>_iad_intensive_int_6400.
This column fails to get created when your server name starts with a number and subsequent scripts that insert records into this column fail. Renaming the server where we were installing Business Objects Edge to <Letters><Numbers> (no dashes either to be safe) solved the problem. We were successfully able to install Business Objects Edge. Please note: This is the server where you are installing Crystal Reports Server 2008 that needs to be renamed and NOT the MS SQL Server--just making a note because we had to go back and forth with our server team a couple of times on this point. -
Play video (http) works, stream video (rtmp) does not; edge server not starting
However, I think the problem is the edge server not starting.
I looked in the logs directory and found the core log, the master log.
I also found /var/log/messages.
Shouldn't there be an edge log?
I did this from the readme:
sudo ./fmsmgr server fms start
udo ./fmsmgr adminserver startrats, hit the wrong button
here is the rest of the report
I did this
sudo ./fmsmgr server fms start
sudo ./fmsmgr adminserver start
sudo ./server start
The master.log:
#Date: 2011-07-21
#Fields: date time x-pid x-status x-ctx x-comment
2011-07-21 16:34:35 26286 (i)2581173 FMS detected IPv6 protocol stack! -
2011-07-21 16:34:35 26286 (i)2581173 FMS config <NetworkingIPv6 enable=false> -
2011-07-21 16:34:35 26286 (i)2581173 FMS running in IPv4 protocol stack mode! -
2011-07-21 16:34:35 26286 (i)2581173 Host: bastet.cam.corp.google.com IPv4: 172.31.194.67 -
2011-07-21 16:34:35 26286 (i)2571011 Server starting... -
2011-07-21 16:34:35 26286 (i)2581224 Edge (26306) started, arguments : -edgeports ":1935,80" -coreports "localhost:19350" -conf "/opt/adobe/fms/conf/Server.xml" -adaptor "_defaultRoot_" -name "_defaultRoot__edge1". -
2011-07-21 16:34:35 26286 (i)2571111 Server started (/opt/adobe/fms/conf/Server.xml). -
2011-07-21 16:34:40 26286 (i)2581226 Edge (26306) is no longer active. -
#Date: 2011-07-21
#Fields: date time x-pid x-status x-ctx x-comment
2011-07-21 16:36:16 26713 (i)2581173 FMS detected IPv6 protocol stack! -
2011-07-21 16:36:16 26713 (i)2581173 FMS config <NetworkingIPv6 enable=false> -
2011-07-21 16:36:16 26713 (i)2581173 FMS running in IPv4 protocol stack mode! -
2011-07-21 16:36:16 26713 (i)2581173 Host: bastet.cam.corp.google.com IPv4: 172.31.194.67 -
2011-07-21 16:36:16 26713 (i)2571011 Server starting... -
2011-07-21 16:36:16 26713 (e)2571122 Server aborted. -
The /var/log/messages output shows "Server starting ..." messages.
When I do the ps:
ps auxww | grep adobe
nobody 19178 0.0 0.0 203444 11124 pts/2 Sl 16:03 0:00 /opt/adobe/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app registry -inst registry -tag -console -conf /opt/adobe/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:registry:registry:
I expected to see the fmsedge binary.
lsof doesn't show anybody listening on 1935 as I expected for an rtmp server. -
ITunes does not start anymore when connecting iphone
Hello,
since my latest upgrade of itunes (still under snow leopard) itunes does not start anymore when connecting my iPhone 4 to my Macbook Pro.
Meanwhile I upgraded to Lion and installed the latest itunes patch but same behavior,
Does anybody has an idea to solve this issue?
Thx,
HendrikHi,
See this Discussion:
https://discussions.apple.com/message/15693777#15693777
Cheers, -
Itunes does not start automaticly when connected although auto is thicked help?
Itunes does not start automaticly when connected although autostart is thicked can anyone help?
Hi,
See this Discussion:
https://discussions.apple.com/message/15693777#15693777
Cheers, -
Surfing the web I constantly get a dialog box popping up that says "The connection was rest" or " Server not found" or "The connection has timed out". The panel gives me three possible causes, none of which are correct and tells me to "Try again". Sometimes when I try again the site appears, sometimes it does after several tries and sometimes it never does. I called my IP, Cox and they told me it is a result of something Microsoft put out in their updates to IE (presumably to discourage people from using Firefox). Can you help me get rid of this problem?
Surfing the web I constantly get a dialog box popping up that says "The connection was rest" or " Server not found" or "The connection has timed out". The panel gives me three possible causes, none of which are correct and tells me to "Try again". Sometimes when I try again the site appears, sometimes it does after several tries and sometimes it never does. I called my IP, Cox and they told me it is a result of something Microsoft put out in their updates to IE (presumably to discourage people from using Firefox). Can you help me get rid of this problem?
-
Hi
When i started SAPMMC database getting up. but message server not starting. What will be the problem.
Regards
Basis ConsHi Ganesh,
First place to look is in the SAPMMC Console and see whats the status of the processes specially if they are yellow. Then you can go and check the work directory and check dev_ms for errors in the message server, dev_disp for errors in the dispatcher and dev_w* for errors in the workprocesses. the work directory is located at <drive>:\usr\sap\<sid>\<instance>\work.
If the message server is not starting i will look first at the dev_ms and look for the error.
Hope this help!
Juan
Please reward with points if helpful -
my ipad still will not start. When connected to wall charger it shows the connect to itunes. When connected to computer it is a black screen and slightly blinks
Frozen or unresponsive iPad
Resolve these most common issues:
• Display remains black or blank
• Touch screen not responding
• Application unexpectedly closes or freezes
http://www.apple.com/support/ipad/assistant/ipad/
iPad Frozen, not responding, how to fix
http://appletoolbox.com/2012/07/ipad-frozen-not-responding-how-to-fix/
iPad Frozen? How to Force Quit an App, Reset or Restart Your iPad
http://ipadacademy.com/2010/11/ipad-frozen-how-to-force-quit-an-app-reset-or-res tart-your-ipad
Black or Blank Screen on iPad or iPhone
http://appletoolbox.com/2012/10/black-or-blank-screen-on-ipad-or-iphone/
What to Do When Your iPad Won't Turn On
http://ipad.about.com/od/iPad_Troubleshooting/ss/What-To-Do-When-Your-Ipad-Wo-No t-Turn-On.htm
iOS: Not responding or does not turn on
http://support.apple.com/kb/TS3281
Home button not working or unresponsive, fix
http://appletoolbox.com/2013/04/home-button-not-working-or-unresponsive-fix/
iPad: Basic troubleshooting
http://support.apple.com/kb/TS3274
Using iPhone/iPad Recovery Mode
http://ipod.about.com/od/iphonetroubleshooting/a/Iphone-Recovery-Mode.htm
Cheers, Tom
Maybe you are looking for
-
Only recently has Firefox for my macbook pro been acting strange when starting up. I will hear a piano chord play only once when the tabs are loading. Over the past two-three weeks on daily usage, this has happened three times. I'm just concerned my
-
How to restore deleted notes, but iTunes won't let you?
I've tried hooking up my phone to my computer and clickin on the restore from backup, but when I click it, it starts and then says it can't continue because there isn't enough room on my phone. Is there any way to get the restore even though it says
-
Selection screen in Cc reporting showing two lines when changed Person Res.
Hi Guruz I have changed Person responsible in Cost centre hierarchy. Now I have two interval with different person responsible 1st one is from 01.01.07 to 31.12.2008 and 2nd one is from 01.01.2009 to 31.12.9999. When I go to cost centre report and lo
-
Problem calling rwcgi60.exe on WebLogic
I have this Exception on Weblogic when executing some types of Reports. I'm using the CGI rwcgi60.exe given with Oracle Reports Server java.lang.ClassCastException: weblogic.utils.Executable$Drainer at weblogic.servlet.internal.ResponseHeaders.setDat
-
Any tips on how to stop the zip > cpgz file looping? I have a zip file that I can't seem to open except that it gets converted to a cpgz file. Thoughts?