Replication Queue reader stopped due to Comm failure

Hello,
I have replication (subscription with updateable subscribers) (pull) running on sql 2008 subscriber with 5 sql 2000 publishers. all seem well except the Queue agent stops at loss of network connectivity. It dosen't appear to restart
until I manually restart it.   It will run for hours until it stops or a shorter period.   Usually, early in the morning before any server activity.
It is not all the Queue readers stopping at the same time, seems random.
I have looked for competing jobs or heavy server activity,   I do not see any.
Per the error logs it is a network loss. (the network is a VPN and is know to have short down times.) (mostly seconds. not hours) (this is the reason I am doing queued transactions)
Is there a way to have the queue agent restart itself if down or to keep trying to start until the problem clears.   if so what affect will it have on the publishers overhead.
Is there something else I am missing as I am fairly new to replication.
The other agents seem to just jug along doing their jobs and the trans actions are followed through.
Thanks for any help
Barry

Hi Barryb,
we have 2 options in job step properties for your scenario
1.one is retry attempts :Sets the number of times that SQL Server Agent attempts to retry a failed job step .
2.On failure action: Sets
the action for SQL Server Agent to perform if the job step fails.
Pls marked as answer if this is use full to you
Thanks and Regards,
Chandar

Similar Messages

Replication Log Reader stopped unexpectedly

This morning our websites stopped serving pages. Whilst investigating I notice that the Replication Sql LogReader had stopped running and was reporting the error:
"SubSystem Message - Job 'XXX582060-XXXXX-1' (0x6D6877EFE4F8EA4D930F8C967FE49BE5), step
2 - A time out occurred while waiting for memory resources to execute the query. Rerun the query."
I have restarted the LogReader and it seems to be working fine but I'd really like to get to the bottom of why it stopped in the first place so I can prevent happening in the future.
Any help would be great.
Thanks
Mike

Check this blog -
http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
Also make sure that you have configured your memory settings properly.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Server stopped due to start up failure

hi!
i have downloaded and installed j2ee sdk without any problems.
however when i start the server it closes itself.
at the end of the log file it says:
" [#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]"
the whole log file is below. can anybody help?
ps: i am a beginner.
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-07-13T09:52:32.438+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2005-07-13T09:52:36.413+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-07-13T09:52:37.104+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-07-13T09:52:46.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-07-13T09:52:46.187+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-07-13T09:52:46.237+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-07-13T09:52:54.299+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-07-13T09:52:59.106+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-07-13T09:53:02.210+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-07-13T09:53:05.565+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-07-13T09:53:05.856+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.956+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.986+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.007+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.017+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.117+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.127+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-07-13T09:53:07.298+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-07-13T09:53:08.900+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2005-07-13T09:53:10.683+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2005-07-13T09:53:10.693+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-07-13T09:53:10.743+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-07-13T09:53:11.363+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2005-07-13T09:53:25.003+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2005-07-13T09:53:32.724+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:32.864+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:33.916+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:33.946+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:34.006+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:53:34.026+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
     at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
     at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
     at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
     at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
     ... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
     ... 25 more
|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2005-07-13T09:54:36.336+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2005-07-13T09:54:36.506+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2005-07-13T09:54:36.536+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2005-07-13T09:54:37.027+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-07-13T09:54:37.057+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-07-13T09:54:37.057+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

Hi,
Did you resolve this issue? I have the same problem. I appreciate if you could please let me know what the problem was.
Thanks

Event ID: 5014, 5004 The DFS Replication Service is stopping communication with partner / Error 1726 (The remote procedure call failed.)

I'm replicating between two servers in two sites (Server A - Server 2012 R2 STD, Server B - Server 2008 R2) over a VPN (Sonicwall Firewall). Though the initial replication seems to be
happening it is very slow (the folder in question is less than 3GB). I'm seeing these in the event viewer every few minutes:
The DFS Replication service is stopping communication with partner PPIFTC for replication group FTC due to an error. The service will retry the connection periodically.
Additional Information:
Error: 1726 (The remote procedure call failed.)
and then....
The DFS Replication service successfully established an inbound connection with partner PPIFTC for replication group FTC.
Here are all my troubleshooting steps (keep in mind that our VPN is going through a SonicWall <--I increased the TCP timeout to 24 hours):
-Increased TCP Timeout to 24 hours
-Added the following values on both sending and receiving members and rebooted server
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Value =DisableTaskOffload
Type = DWORD
Data = 1
Value =EnableTCPChimney
Type = DWORD
Data = 0
Value =EnableTCPA
Type = DWORD
Data = 0
Value =EnableRSS
Type = DWORD
Data = 0
---------------------------------more troubleshooting--------------------------
-Disabled AntiVirus on both members
-Made sure DFSR TCP ports 135 & 5722 are open
-Installed all hotfixes for 2008 R2 (http://support.microsoft.com/kb/968429) and rebooted
-Ran NETSTAT –ANOBP TCP and the DFS executable results are listed below:
Sending Member:
[DFSRs.exe]
TCP    10.x.x.x:53            0.0.0.0:0
LISTENING       1692
[DFSRs.exe]
TCP    10.x.x.x:54669
10.x.x.x:5722          TIME_WAIT       0
TCP    10.x.x.x:54673
10.x.x.x:5722          ESTABLISHED     1656
[DFSRs.exe]
TCP    10.x.x.x:64773
10.x.x.x:389           ESTABLISHED     1692
[DFSRs.exe]
TCP    10.x.x.x:64787
10.x.x.x:389           ESTABLISHED     1656
[DFSRs.exe]
TCP    10.x.x.x:64795
10.x.x.x:389           ESTABLISHED     2104
Receiving Member:
[DFSRs.exe]
TCP    10.x.x.x:56683
10.x.x.x:389           ESTABLISHED     7472
[DFSRs.exe]
TCP    10.x.x.x:57625
10.x.x.x:54886         ESTABLISHED     2808
[DFSRs.exe]
TCP    10.x.x.x:61759
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61760
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61763
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61764
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61770
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61771
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61774
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61775
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61776
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61777
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61778
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61779
10.x.x.x:57625         TIME_WAIT       0
TCP    10.x.x.x:61784
10.x.x.x:52757         ESTABLISHED     7472
[DFSRs.exe]
TCP    10.x.x.x:63661
10.x.x.x:63781         ESTABLISHED     4880
------------------------------more troubleshooting--------------------------
-Increased Staging to 32GB
-Opened the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:
a. The computer object of the DFS server
b. The DFSR-LocalSettings object under the DFS server computer object
-Ran
ping <var>10.x.x.x</var> -f -l 1472 and got replies back from both servers
-AD replication is successful on all partners
-Nslookup is working so DNS is working
-Updated NIC drivers on both servers
- I ran the following to set the Primary Member:
dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<primary member> /IsPrimary:True
Then Dfsrdiag Pollad /Member:<member name>
I'm seeing these errors in the dfsr logs:
20141014 19:28:17.746 9116 SRTR   957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{45C8C309-4EDD-459A-A0BB-4C5FACD97D44} csId:{7AC7917F-F96F-411B-A4D8-6BB303B3C813}
Error:
+ [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 9116 C The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 9116 C The content set is not ready]
+ [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 9116 C The content set is not ready]
---------------------------------------more troubleshooting-----------------------------
I've done a lot of research on the Internet and most of it is pointing to the same stuff I've tried. Does anyone have any other suggestions? Maybe I need to look somewhere
else on the server side or firewall side?
I tried replicating from a 2012 R2 server to another 2012 server and am getting the same events in the event log so maybe it's not a server issue.
Some other things I'm wondering:
-Could it be the speed of the NICs? Server A is a 2012 Server that has Hyper-V installed. NIC teaming was initially setup and since Hyper-V is installed the NIC is a "vEthernet
(Microsoft Network Adapter Multiplexor Driver Virtual Switch) running at a speed of 10.0Gbps whereas Server B is running a single NIC at 1.0Gbps
-Could occasional ping timeout's cause the issue? From time to time I get a timeout but it's not as often as the events I'm seeing. I'm getting 53ms pings. The folder
is only 3 GB so it shouldn't take that long to replicate but it's been days. The schedule I have set for replication is mostly all day except for our backup times which start at 11pm-5am. Throughout the rest of the time I have it set anywhere from
4Mbps to 64 Kbps. Server A is on a 5mb circuit and Server B is on a 10mb circuit.

I'm seeing the same errors, all servers are running 2008 R2 x64. Across multiple sites, VPN is steady and reliably.
185 events from 12:28:21 to 12:49:25
Events are for all five servers (one per office, five total offices, no two in the same city, across three states).
Events are not limited to one replication group. I have quite a few replication groups, so I don't know for sure but I'm running under the reasonable assumption that none are spared.
Reminder from original post (and also, yes, same for me), the error is: Error: 1726 (The remote procedure call failed.)
Some way to figure out what code triggers an Event ID 5014, and what code therein specifies an Error 1726, would extremely helpful. Trying random command line/registry changes on live servers is exceptionally unappealing.
Side note, 1726 is referenced here:
https://support.microsoft.com/kb/976442?wa=wsignin1.0
But it says, "This RPC connection problem may be caused by an unstable WAN connection." I don't believe this is the case for my system.
It also says...
For most RPC connection problems, the DFS Replication service will try to obtain the files again without logging a warning or an error in the DFS Replication log. You can capture the network trace to determine whether the cause of the problem is at the network
layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the following command in a
Command Prompt window:
NETSTAT –ANOBP TCP
This returns all open TCP connections. The connections in question are "DFSRs.exe", which the command won't let you filter for.
Instead, I used the NETSTAT command as advertised, dumping output to info.txt:
NETSTAT -ANOBP TCP >> X:\info.txt
Then I opened Excel and manually opened the .TXT for the open wizard. I chose fixed-width fields based on the first row for each result, and then added a column:
=IF(A3="Can not", "Can not obtain ownership information", IF(LEFT(A3,1) = "[", A3&B3&C3, ""))
Dragging this down through the entire file let me see that row (Row F) as the file name. Some anomalies were present but none impacted DFSrs.exe results.
Finally, you can sort/filter (I sorted because I like being able to see everything, should I choose to) to get just the results you need, with the partial rows removed from the result set, or bumped to the end.
My server had 125 connections open.
That is a staggering number of connections to review, and I feel like I'm looking for a needle in a haystack.
I'll see if I can find anything useful out, but a better solution would be most wonderful.

Hub startup failed due to licensing failure

Hi all.
I have just installed weblogic 6.0 sp1 on solaris 2.8. the web server starts
up and everything is hunky dory.
furthermore i downloaded collaborate 1.0.1 and installed it. the
installation went fine.
here is my problem. when i execute the startWeblogic.sh script in the hub,
Weblogic reports the following error:
<24-Apr-01 13:49:03 GMT+01:00> <Error> <WLC> <<Hub> ERROR: Hub startup
failed due to licensing failure.>
I get this problem using jdk122 and jdk130.
I cannot seem to find the problem.
Any feedback would be appreciated.
PS. My license.bea file looks as follows:
<?xml version="1.0"?>
<bea-licenses>
<license-group format="1.0" product="WebLogic Collaborate"
release="1.0">
<license
component="Core Server"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MC0CFCoH/XUHiZuu+yhzpuzv6UFl
kJ44AhUA2/U26g1keq5nNoO00NC2u9ezWeA="
/>
</license-group>
<license-group format="1.0" product="wlpi" release="1.2">
<license
component="WebLogic Process Integrator"
expiration="2001-05-24"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
users="5"
signature="2tDDH3g1qXubdlfsahWRNrR6+tc=0MCwCFEh5H427STpTMX1y25DSmc65
b/MVAhQMNJo1ujoB6DudzF59hL/Tx2vbGQ=="
/>
</license-group>
<license
component="WebLogic"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OFcm7oSc4jOT5vonluVZpsAHX2g=0MCwCFEmkcBweXEoxtJxzCIarx8i+
XBguAhQvCxM9E/T4HGfbIUfb4+OiNUYsPw=="
/>
<license
component="SSL/Export"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="OgS8PvglCrGr5xglLHeut8tE5vc=0MC0CFQDcxuNftALK3tZYuJw6hI15
GaqrBgIUcTi0vNzwoG1alTX1WXnvcX9EOiM="
/>
<license
component="2PC"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="CcdspC/3P0iELwWsETBWI/hEalw=0MC0CFQCtTlW7enw3kFZ7IU09jaa/
BVle5wIUSSfMk23C19hznredmfr+soEYiX0="
/>
<license
component="In-memory Replication - Servlet"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="c+mtrQ1ZuRiKeiELua/hSxvHqew=0MC4CFQC4qvLRsblTBvC5+IEVrDI1
Tek1YwIVAJ1NYWZE6xPHYyyVdlaXRJbhayCj"
/>
<license
component="In-memory Replication - EJB"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="ZenJ1bPXGf2N/Bq8XugDnDIP8sQ=0MC0CFQC+ayYQFxhpIMug7ZHtZIfS
vg4tlwIUHIYgx30GoxIdmR19cGddWM/mp3E="
/>
<license
component="EJB 1.1"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="XwwhoY5ysJ8h1pjzx23ujxZI9nY=0MC4CFQC2ATLeRv6cStQE1B/gyMUT
R6SRvQIVAMsQmtFC0/J4sF26n+B1zEyDOmv/"
/>
<license
component="EJB 2.0"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
units="5"
signature="ksI9jkE6gL9u8GdVEpZNQtOvjm8=0MCwCFBUir1rQV/FLNdc+4lfdIV1x
+xk5AhQpQwwWMfUd6TbL3UvB0u9DbZponQ=="
/>
<license
component="JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Z4Q4VngOAJSqSsr1UXC37DTOyVg=0MC0CFQCZtOwzb02hOSR3z9Hp6k86
nl1uFQIUfhy+ODL+Y7B9DkGDS7yT4zQPPpE="
/>
<license
component="Cluster"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Tkg9CGjEik3MbkFmi6rPsSiO0J0=0MC0CFEAV5hPKLVSgV8YoeCEVu5m7
5ktkAhUA2lBI0PwiMigvK1E/pVS0vqmsy3w="
/>
<license
component="Clustered JMS"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="nEpfLZwWyM4Bo7UZZHE4hQgntMc=0MCwCFBKYtPvqZE18JdGBvU6cZomM
xW1cAhR3moJKg7FHMxvsZphQz5jVCahrfA=="
/>
<license
component="jDriver/MSSQLServer4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="Dgw2DzDWyBNob6pJunUY1Xoz7c8=0MC0CFQC4PKj8UFoC3J0XuC7pmzRL
TtgP8QIUAhJF5DuvZ10zvf/6mxe0Ti/rG4c="
/>
<license
component="jDriver/Informix4"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="6O/i8fVnKIeVwzz+e0zUMQL5uRU=0MC0CFH+NK7nnRm+Qp+qRXZdeV2yF
6YxdAhUA3vch2xTdmM5Ao+00+IOR5f3jGH0="
/>
<license
component="jDriver/Oracle"
expiration="2001-05-23"
ip="any"
licensee="BEA Evaluation Customer"
type="EVAL"
units="5"
signature="NtSVpPAloTJqBstOWKVnuh3q0H4=0MC0CFA+2ny24Zdyrb0lsL3duwfEB
9zKMAhUAqDtTbLMN3QfJWUVhJr+NBQU/x/k="
/>
</license-group>
</bea-licenses>

Gotta add listeners.ContextListener to your CLASSPATH
in Eclipse.
I don't think that package name is right. You've got
another problem besides your context XML.
%The context XML may not be the problem at all. Such tomcat errors are standard when it was unable to load required classes on startup.
The listeners all being interfaces, it's impossible to say whether it is the standard listeners or custom listener classes (regd in your web.xml) that's not being found on startup.
cheers,
ram.

Microsoft Exchange Replication Service keep stopping

Not sure what is going on here. The replication service keep stopping on one of my servers within the DAG. I cant think of anything different about this server compared to others (anything known at least). This server sits at our DR facility and is the host
of the 3rd copy to a few of our databases, which primary and secondary ones live at our HQ. The application log reports this every 5-10 seconds
Watson report about to be sent for process id: 31860, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, msexchangerepl, M.Exchange.Common, M.E.C.H.DatabaseFailureItem.Parse, System.ArgumentOutOfRangeException, fe19, 15.00.0995.012.
ErrorReportingEnabled: False
The system log reports this every 5-10 seconds also:
The Microsoft Exchange Replication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
I have ran windows update, and it seems that every time I reboot the machine, the shutdown tracker comes up. I think it has something to do with hardware, but no idea where to look next.

Hi,
This issue occurred because Microsoft Exchange Replication Services Was Unable to Write In "Microsoft-Exchange-MailboxDatabaseFailureItems/Operational"
The fix for the issue will be available in next cumulative update. Meanwhile, please follow the steps below for a workaround to resolve the issue. This workaround is to clear the entries log storing mailbox database failure items.
On problem server, open command prompt in administrator privileges.
Run following command to clear the even entries from the log
Wevtutil.exe cl "Microsoft-Exchange-MailboxDatabaseFailureItems/Operational"
Best Regards.

DFSR replication server is stopping communication

Ok I am not fully failure with DFSR but here Is the error I am getting from my health report from my server:
DFSR
Event ID: 2147488662
The DFS Replication service is stopping communication with partner HOLYROODDC-2012 for
replication group Domain System Volume due to an error. The service will retry the connection
periodically.
Additional Information:
Error: 9036 (Paused for backup or restore)
Connection ID: 3E9A9A37-E124-490C-A3B7-CFCE3302B6CF
Replication Group ID: 00ACE2F9-D6D2-4EF2-98F0-7536A35EFD6D
Last occurrence: Monday, July 14, 2014 9:00:18 PM
Total occurrences: 1
this is a rather simple network with 2 windows 2012R2 server as DC's both onsite (no offsite servers) I am just not to familure with this error.

Hi,
Did this warning occur when we backed up our files? If yes, we don’t pay attention to this warning, for Backup tools may need to terminate the replication temporarily to avoid
the conflict and complete the backup task. The replication will be resumed automatically without intervention after the backup.
Best regards,
Frank Shen

DFSR Event 5014 - DFS Replication service is stopping communication

Hi,
I seem to be having issues with the DFSR warnings in the event log. I receive the below warning every 5 minutes:
"The DFS Replication service is stopping communication with partner 'Servername' for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 1726 (the remote procedure call failed.)"
The errors are immediately followed by an information entry (5004) stating that a connection was successfully established but then the warning repeats after 5 minutes again. Replication does actually seem to be working fine and the SYSVOL shares on both
domain controllers are identical.
I have run diagnostic reports from the DFS Management snapin and the only error reported is that
"The DFS Replication service is restarting frequently".
I have disabled TCP Offloading on the server as per other suggestions which doesn;t seem to have made a difference.
For reference, the domain controllers are in separate sites connected via site-to-site VPN. The AD sites are configured with the correct subnets and the WAN/VPN connection seems stable as I am getting consistent 87ms ping responses.
Any assistance would be greatly appreciated.
Thanks,
Charlie.

Although I haven't specifically run into this, doing a Bing search I have seen a common theme that if there is a firewall between the two it drops the connection after a set period of inactivity. You might want to investigate that possibility.
http://faultbucket.ca/2011/02/dfsr-event-5014-the-remote-procedure-call-failed/
http://social.technet.microsoft.com/Forums/windowsserver/en-US/68c4f402-6c77-4388-9701-51a4fc112964/error-1726-the-remote-procedure-call-failed-every-7-minutes-dfsr-backlogs?forum=winserverDS
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
Twitter @pbbergs
http://blogs.dirteam.com/blogs/paulbergson
Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

Portal failed to access remote resource due to network failures

Hi,
We have a portlet that allows users to upload files to a SQL Server database and make it available for other users to access. The portlet code is on our remote servers. Everything works fine in dev environment, but certain files fail in pre-prod and prod within the portal, but work fine when the code is executed outside the portal.
I keep getting this error:
Error - Portal failed to access remote resource due to network failures. Try again later or contact your portal administrator.
What could the problem be?
Thank you for your help.
Rad

If the Studio service looks good on the remote server where Studio is installed (check that
the service is started and look in the Studio logs for any warnings or errors), you should
also verify the configuration settings in the Studio remote server object. Is it properly
configured and pointing to the correct remote server?
If so, check the portal servers access to the Studio server via the port specified in the remote
server (default is 11935). You can test this by doing a telnet test on the portal server. In a cmd
prompt (Windows) or on the CLI (Unix), type 'telnet [studioserver] 11935', where "<servername> is
the name of your Studio remote server. The screen should just go blank, meaning that there is
something accepting connections on that port on the given server. (We would hope it's the Studio
app and not another service occupying that port.) If you get "Could not open connection to the host"
or some such similar result, check that the network between the portal and the Studio remote server
is open (ie, make sure there isn't any port blocking or a firewall in place that would hinder the
communication between the two servers).

Time Machine stops due to computer going into Sleep/Hibernation Mode

Time Machine stops due to computer going into Sleep/Hibernation Mode then restarts to try to start the Back up process again and again vicious cycle. I have made sure all settings are turned off. I have done one or two backups since the initial first backup. My HDD is almost full and I want it backed up before I try to clone/mirror the drive to upgrade it to a 1TB HDD. Thank you in advance.

Set the Energy Saver (in System Preferences) to Never. Then reset the NVRAM, as follows:
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the third time.
Release the keys.

During an update of the applications on the BlackBerry smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatis

I have reset both my torch and playbook back to original only thing that I kept was my contact. And still problems I am a few min away from leave my loved blackberry and going android !! Or heaven help us Phone
Issues 1) playbook wont connect to desktop manager anymore
2) Play book has 2 calendar icons with two different settings on them ??? I have one that is currently working with my yahoo email and calendar account.
3) my Phone when connected to desk top software shows the calendar as read only
4) Unable to update my phone says During an update of the applications on the BlackBerry® smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatisfactory dependencies."
I just want my email and Calendars to work I am tried of spending nights trying to get these deices working !!!
someone please help me. !!
I know you are going to ask I have updated everything last time and it is all as update as it can get.
As for now as I wait I am going to wipe my phone again and just set everything up again !! If I have to even my contacts AHHHH Help I am starting to think crazy thoughts

Did you try to eboot the your PC or laptop where your device is connected ?
I experienced this with my windows laptop, after a failed to do an update, I restart the laptop and my Torch, then retried, and it's worked

CORBA COMM FAILURE AND ORB

We are currently experiencing numerious and periodic CORBA COMM FAILUREs in prd. We are utilizing JDK 1.3 / CORBA and trying to submit to a C++ server object. When the web server starts up, it initializes the ORB using the ior and orb.init(). When the actual calls are made, we are narrowing to the server object and making the call. Problem is that periodically we get the CORBA COMM FAILURE when we make the call. During our investigation, we determined that the actual servers look to be running just fine and they are registared with the naming service. When this error occurs, we present the user with a communication failure message.
Our theory is that the ORB is caching the server objects and their connection paths. If the connection is broken for whatever reason, it throws a CORBA COMM FAILURE instead of trying to reconnect to the server object. Can anyone verify our theory? A detailed understanding of how the java ORB works would be very helpful.
Secondly, what is the best way to handle this exception. Should we shutdown the ORB and restart it? I am very apprehensive about this since users running on the other threads will be affected. Anyone familiar with orb.disconnect(Object ob) or orb.connect(Object ob)? Should I do these steps in my exception handling block to get the ORB to set up or cache a real server object?
In reading another discussion thread, I ran across someone using the objRef._non_existent() to get it to go. Anyone familiar with this method and understand the implications of its use?

If your server objects get recycled, which it sounds like might be happening, in general you are not guaranteed of getting the same IOR. If you have clients out there that have already narrowed on the server, and then the server gets recycled, you will need to go through the steps of narrowing on those objects again.
The nonexistent() does exactly what you expect it to do. If the referenced object does not exist, nonexistent() will return true, else false.
Hope this helps.

VMware SQL 2008R2 bcp error - SQLState = 08001, NativeError = 0 Error = [Microsoft][SQL Server Client 10.0] Client unable to establish connection due to prelogin failure

Can someone help me resolve this error? Thanks
Windows Server 2008 R2 Standard SP1 64-bit - SQL Server 2008R2 Standard 64-bit
VMware vCenter Server Version 5.1.0
SQLState = 08001, NativeError = 0
Error = [Microsoft][SQL Server Native Client 10.0]Client unable to establish connection due to prelogin failure
bcp program:
bcp SYM.dbo.ACCOUNT in "D:\Data\SQLExtract\EXTRACT.ACCOUNT" -f"D:\Data\SQLCommands\FMT.ACCOUNT" -S DEV-DATA\TEST\ -T -oSYMLOAD.LOG Type SYMLOAD.LOG >> SYMLOAD.LOG.CUMULATIVE
The bcp program executes successfully on a local instance of SQL Server.

The error has nothing to do with BCP as such, but it is a connection problem. That is, for some reason you cannot connect to your instance from the VM. I would exect that you face a similar problem if you tried SSMS.
It could be a firewall issue, but prelogin suggests that you reach the instance. But possibly you don't come far enough for the login failure to be recorded. Possibly the instance is not configured to audit login failures.
The message you would see would be similar to
2010-08-18 14:11:30.91 Logon Error: 17809, Severity: 20, State: 3
Possibly followed by a a line that details the message. The error number may be different.
Erland Sommarskog, SQL Server MVP, [email protected]

An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation ...

Hi All,
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
Error:
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
Regards,
Joseph

Ran into this error, and the password was correct. What the System Event Log said:
Code SnippetEvent Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7041
Date: 10/8/2008
Time: 9:33:09 AM
User: N/A
Computer: ComputerName
Description:
The SQLSERVERAGENT service was unable to log on as DomainName\SQLAgent with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: SQLSERVERAGENT
Domain and account: DomainName\SQLAgent
This service account does not have the necessary user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
...sure enough it had been removed from the "Logon as a service" list. Hope this helps.

How to automate checking status of Replication agent and Replication queue in CQ5

As part of monitoring the status of replication agents and replication queue, is it possible to automate the checking process?
We can check them from GUI, but from a monitoring perspective we are loking for a mechanism where the status can be checked continuously and we are alerted whenever there is some issue.
1. Check status of replication agent (enabled/disabled)
2. Check status of replication queue (if the queue is blocked)
Thanks in advance
nkrao

you can pull the queue from the page the same way the UI gets the list
in the table:
curl -u admin:admin
"http://localhost:4502/etc/replication/agents.author/publish/jcr:content.queue.json?agent=p ublish"
and then use a shell library like ticktick.sh to parse the json
response. A sample of how to get the bundles loaded and installed from
CQ using the ticktick library can be found here
https://github.com/kristopolous/TickTick
http://ruben42.wordpress.com/2012/04/24/using-ticktick-sh-to-parse-json-responses-from-ado be-cq5-5/

Replication Queue reader stopped due to Comm failure

Similar Messages

Maybe you are looking for