An exception occurred while attempting to register the client
Article ID: 174733
Updated On:
Products
Issue/Introduction
The following entries are listed in the logs:
Problem 1
Error - Server Side
Process: w3wp.exe (5924)
Thread ID: 2612
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.*
Description: An exception occurred while attempting to register the client. Error: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at Altiris.Core.Sockets.SecureRemoting.SecureRemotingClient.EstablishConnection()
at Altiris.Core.Sockets.SecureRemoting.SecureRemotingClient.AttempSendRequest(String service, Hashtable input)
at Altiris.Core.Sockets.SecureRemoting.SecureRemotingClient.SendRequestI(String service, Hashtable input)
at Altiris.Core.Sockets.SecureRemoting.SecureRemotingClient.SendRequest(String service, Hashtable input)
at Altiris.ClientTask.Server.Web.WebClientApiManager.ProcessRegister(NameValueCollection queryValues, Stream requestStream, Int32 contentLength)
Information - Client Side
Process: AeXNSAgent.exe (6044)
Thread ID: 5420
Module: Client Task Agent.dll
Source: Client Task Agent
Description: CClientTaskServerConn::AttemptRegister(): Attempting to register with url:
http://xxx.xxx.xxx.xxx/Altiris/ClientTask/Server/Register.aspx?ResourceGuid=Guid_of_NS
Problem 2
Trace - Client Side
Process: AeXNSAgent.exe (1900)
Thread ID: 4432
Module: Client Task Agent.dll
Source: Client Task Agent
Description: CTaskServerConnection::Register(): CAtrsException exception, error = "Unable to find response node", OS error = 2147549183, at line 772 re-throw at CClientTaskServerConn::CheckResponseDocument re-throw at
CClientTaskServerConn::ParseServerListDocument re-throw at CClientTaskServerConn::UpdateCoordinationServerList re-throw at
CClientTaskServerConn::Register
Cause
Problem 1
The "Altiris Object Host Service" on the Task Server is stopped. This has been seen to happen after doing a repair of the TaskManagementSetup.msi file under ..\Setup Files\Task Server.
Problem 2
The Client Task Agent did not handle locked down security policies on the client.
Resolution
Problem 1
Start the "Altiris Object Host Service" on the Task Server.
Problem 2
Is fixed in Task Manager SP2 which was released first quarter 2009.
Applies To
Problem 1
Notification Server 6.0 SP3
Task Server 6.0.1356
Problem 2
Notification Server 6.0 SP3
Task Server 6.0.1356
Security Policies defined:
Local policies (security options) are configured on the Notification Server and clients as:
Microsoft network client: Digitally sign communications (always)—Disabled
Microsoft network client: Digitally sign communications (if server agrees)—Enabled
Network access: Allow anonymous SID/Name translation—Disabled
Network access: Do not allow anonymous enumeration of SAM accounts—Enabled
Network access: Do not allow anonymous enumeration of SAM accounts and shares—Enabled
Network access: Let Everyone permissions apply to anonymous users—Disabled
Network access: Named Pipes that can be accessed anonymously—COMNAP,COMNODE,SQL/QUERY,SPOOLSS,LLSRPC,EPMAPPER,LOCATOR,TrkWks,TrkSvr
Network access: Restrict anonymous access to Named Pipes and Shares—Enabled
Network access: Shares that can be accessed anonymously—COMCFG,DFS$
Network access: Sharing and security model for local accounts—Classic—local users authenticate as themselves
Network Security: LAN Manager authentication level—Send NTLMv2 response only / refuse LM & NTLM
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients—Require NTLMv2 session security, Require 128-bit encryption
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers—Require NTLMv2 session security, Require 128-bit encryption
Feedback
