(SCOM) cannot connect to this port 5724 to use its services
Hi can anyone please help me regarding this issue Thanks in advance!!!! Date: 8/17/2012 1:07:39 PM Application: Operations Manager Application Version: 7.0.8560.0 Severity: Error Message: Failed to connect to server 'Xxxxxxx.com' Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. ---> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://wm-flor-apvm199.wdw.disney.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:03.0635942. TCP error code 10061: No connection could be made because the target machine actively refused it [::1]:5724. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [::1]:5724 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService) --- End of inner exception stack trace --- at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService) at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals) at Microsoft.EnterpriseManagement.ManagementGroup.Connect(ManagementGroupConnectionSettings connectionSettings) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server) at Microsoft.EnterpriseManagement.Monitoring.Console.Internal.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args) System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://xxxxxxxxxxxx.com:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:03.0635942. TCP error code 10061: No connection could be made because the target machine actively refused it [::1]:5724. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [::1]:5724 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService) at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService) System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it [::1]:5724 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
August 22nd, 2012 3:56pm

Hi It seems that this management server (?) is not able to communicate to the other server using TCP port 5724. Make sure this port is open on both Servers. I suppose both servers are SCOM management servers and These systems need TCP port 5723 and port 5724 open. There might be a Firewall in between or the Windows Firewall is blocking traffic. Check for the port requirements here http://technet.microsoft.com/en-us/library/hh205990.aspx#BKMK_NetworkConnectivity . Stefan Blog: http://blog.scomfaq.ch
Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2012 4:09pm

Hi Can you give us a bit more background as to when you get this error. Is it when you start the console? Is it from an agent install? Can you check that the System Center Data Access Service is running on the Management Server? Is windows firewall configured to pass traffic on port 5724 (I suspect this isn't the issue as the error is "refused" which suggests a connection does take place). Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
August 22nd, 2012 4:10pm

Hi It seems that this management server (?) is not able to communicate to the other server using TCP port 5724. Make sure this port is open on both Servers. I suppose both servers are SCOM management servers and These systems need TCP port 5723 and port 5724 open. There might be a Firewall in between or the Windows Firewall is blocking traffic. Check for the port requirements here http://technet.microsoft.com/en-us/library/hh205990.aspx#BKMK_NetworkConnectivity . Stefan Blog: http://blog.scomfaq.ch
Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2012 4:12pm

Hi Can you give us a bit more background as to when you get this error. Is it when you start the console? Is it from an agent install? Can you check that the System Center Data Access Service is running on the Management Server? Is windows firewall configured to pass traffic on port 5724 (I suspect this isn't the issue as the error is "refused" which suggests a connection does take place). Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
August 22nd, 2012 4:14pm

Hi Please give us some more Infos about your and when and how this error occurs. As Graham mentioned make sure the Data Access Service is running on the management Server. Are there any other Errors in the eventlog? Install Telnet Client on a System (Windows Feature) and check if you get a responses by typing: Telnet [IP/Name of Server which you want to connect] 5724 This might be helping you by troubleshooting this case. Cheers, StefanBlog: http://blog.scomfaq.ch
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2012 2:19am

Hi Please give us some more Infos about your and when and how this error occurs. As Graham mentioned make sure the Data Access Service is running on the management Server. Are there any other Errors in the eventlog? Install Telnet Client on a System (Windows Feature) and check if you get a responses by typing: Telnet [IP/Name of Server which you want to connect] 5724 This might be helping you by troubleshooting this case. Cheers, StefanBlog: http://blog.scomfaq.ch
August 24th, 2012 2:21am

I am also getting the same error, I upgrade my 2007 R2 MS server (in place upgrade). Upgrade was successful without erros. After which I tried to open the Console got the same error listed this thread. SDK service is running, I tired to check the port 5724 with telnet with its not connecting, where as port 5723 is working fine with telnet, I also checked the registry and noticed that port 5723 is mentioned at below location. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\ManagementServerPort HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups\xxxx\Parent Health Services\0\Port HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups\xxxx\port NOTE: xxxx is the management group name
Free Windows Admin Tool Kit Click here and download it now
October 9th, 2012 11:39am

Make sure you also try a netstat -a to verify that the port is open and listening on both machines. If 5724 IS open andlistening and you can telnet between machines on 5723 then yes, I would look to a firewall related issue reguarding port 5724. Regards, Ryan
October 10th, 2012 1:18pm

I tried that, port 5724 is not listening, windows firewall is off on all the servers, and there is no other firewall between servers. Have submitted a case with MS, lets see..
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2012 4:28am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics