Error in NS7: 'BaseXmlHttpCallback Exception: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:50121'

Article:TECH46695  |  Created: 2009-11-10  |  Updated: 2010-08-30  |  Article URL http://www.symantec.com/docs/TECH46695
Article Type
Technical Solution


Issue



Though the Altiris Agent is connecting to the Notification Server (Basic Inventory, Configuration Updates, Policies, etc) the following error appear in the Agent Logs.

"Description: BaseXmlHttpCallback Exception: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:50121"

*Note: The specific port (50121) listed may vary.  The most commonly appearing ports are 50121, 50122, 50123, and 50124.


Environment



Notification Server 7.0


Cause



A possible cause of these issues is the Altiris Object Host Service failing to bind to any of the ports listed in Site Server Setting under Site Management >> Settings >> Task Service >> Settings >> Task Service Settings.

 

The Altiris Object Host Service is one of the two main services used by the Client Task Server.  Why the ports are failing to bind is still unknown and is being researched.


Solution



For specifics regarding issues with port bindings for Task Server, see TECH47615.




Legacy ID



50058


Article URL http://www.symantec.com/docs/TECH46695


Terms of use for this information are found in Legal Notices