Scheduled tasks and other auxiliary SMP functions fail to run and indicate the reason was because the target machine actively refused it.

book

Article ID: 158572

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

Scheduled tasks and other SMP functions fail to run. The SMP logs are filled with errors similar to the following (excerpt)

Module: ScheduleProcessor.exe
Source: ScheduleProcessor.Processor.MainReal
Description: Unable to process schedule. Failed to connect to the Altiris Service. (Target: {bd6bf880-bfae-4dad-b746-e8be99f3b8a8}, Exception: No connection could be made because the target machine actively refused it 10.10.3.100:4010)
**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.1.8400.0&language=en&module=lV2IN6tn8RcsxXpOcAhnj+23y2a3scamF/Pe0lMGPis=&error=93700800&build=**CEDUrlEnd**

 

Module: w3wp.exe
Source: System.Threading.ExecutionContext.runTryCode
Description: Caught unknown exception when loading event for event {493acd3e-e0bc-48be-9364-4e56fd021290} in FlushReportedEventThreadProc. Error=System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.3.100:4010

Server stack trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)
   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
   at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
 

Cause

There was an entry in the Windows hosts file ( C:\Windows\System32\drivers\etc ) which specified that "localhost" was to be assigned and resolve to the server's statically assigned IP address and not the loopback address 127.0.0.1

 Explanation:   The IP address referenced in the error is the address through which the SMP service groups communicate with each other internally. This is done by calling the address assigned to "localhost" which is usually the loopback (127.0.0.1). The port specified in the error, 4010, is the port through which the internal communications are made, which can be done via the internal loopback address, but cannot be done via the server's assigned IP address unless special configurations are made in DNS and on the network.

The following excerpt is how the hosts file was configured.


#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#             127.0.0.1       localhost
#             ::1             localhost

                localhost             MyServer.MyCompany.Com
                10.10.3.100         localhost
 

Resolution

It was unclear why the entry to the hosts file had been added and was not needed for any tactical configurations. Therefore the simple solution was to comment out or remove the last two lines and then restarted IIS and the Altiris service.

 This allowed the SMP functions to use the loopback address which resolved the problem.  The scheduled tasks were able to run to completion.

#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#             127.0.0.1       localhost
#             ::1             localhost

#             localhost             MyServer.MyCompany.Com
#             10.10.3.100         localhost
 


Applies To

Symantec Management Platform 7.1 SP2 MP1.1