When navigating through the SMP7 Console, may see "Server too busy".
NS logs report errors and warnings related to Task Server:
Priority: 1
Date: 8/20/2009 12:55:14 PM
Tick Count: 6579734
Host Name: ServerName
Process: w3wp (6820)
Thread ID: 44
Module: w3wp.exe
Source: Altiris.TaskManagement.ClientTask.*
Description: BaseXmlHttpCallback Exception: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:50121
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.EstablishConnection()
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.AttempSendRequest(String service, Hashtable input)
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequestI(String service, Hashtable input)
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequest(String service, Hashtable input)
at Altiris.ClientTask.Server.HttpHandlers.WebClientApiManager.ProcessRegister(XmlTextWriter wr, NameValueCollection queryValues, Stream requestStream, Int32 contentLength)
at Altiris.ClientTask.Server.HttpHandlers.Register.WriteResponse(XmlTextWriter wr)
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)
/////////////////////////
Priority: 1
Date: 8/20/2009 12:55:14 PM
Tick Count: 6569906
Host Name: ServerName
Process: w3wp (6820)
Thread ID: 202
Module: w3wp.exe
Source: Altiris.TaskManagement.ClientTask.*
Description: BaseXmlHttpCallback Exception: System.Threading.ThreadAbortException: Thread was being aborted.
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequestI(String service, Hashtable input)
at Altiris.DotNetLib.Sockets.SecureRemoting.SecureRemotingClient.SendRequest(String service, Hashtable input)
at Altiris.ClientTask.Server.HttpHandlers.WebClientApiManager.ProcessRegister(XmlTextWriter wr, NameValueCollection queryValues, Stream requestStream, Int32 contentLength)
at Altiris.ClientTask.Server.HttpHandlers.Register.WriteResponse(XmlTextWriter wr)
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)
//////////////////////////
Priority: 2
Date: 8/20/2009 12:55:14 PM
Tick Count: 6542390
Host Name: ServerName
Process: AtrsHost (3364)
Thread ID: 9
Module: AtrsHost.exe
Source: Altiris.TaskManagement.ClientTask.*
Description: System.Net.WebException: The remote name could not be resolved: 'ServerName.es'
at System.Net.HttpWebRequest.GetRequestStream()
at Altiris.ClientTask.Server.ClientTaskServer.RegisterTaskServer(TaskServerGroupGuid serverGuid, Guid serverSecret)
///////////////////////////
Priority: 2
Date: 8/20/2009 12:55:14 PM
Tick Count: 6540140
Host Name: ServerName
Process: AtrsHost (3364)
Thread ID: 9
Module: AtrsHost.exe
Source: Altiris.TaskManagement.ClientTask.*
Description: AltirisAgentSettings.FigureOutCredentials(): Credentials in Agent registry were invalid, or there was an error connecting to the server.
/////////////////////////////
Priority: 2
Date: 8/20/2009 12:55:14 PM
Tick Count: 6540140
Host Name: ServerName
Process: AtrsHost (3364)
Thread ID: 9
Module: AtrsHost.exe
Source: Altiris.TaskManagement.ClientTask.*
Description: Credential check for "Administrator" failed: System.Net.WebException: The remote name could not be resolved: 'ServerName.es'
at System.Net.HttpWebRequest.GetResponse()
at Altiris.ClientTask.Server.AltirisAgentSettings.CheckCredentials(NetworkCredential credentials, String authenticateWebBaseUrl)
These errors and warnings were logging frequently. Also, the client machines may be having a hard time registering the Client Task plugging due to some authertication failures.
Check the NS logs for issues with resolving the server name (The remote name could not be resolved: 'ServerName.es') as well authentication messages (Credential check for "Administrator" failed). Customer mentioned that 'ServerName.es' was not correct.
There are multiple possible resolutions:
1. Search the registry and replace 'ServerName.es' to 'ServerName'. Then recycle the defaultAppPool (http://support.microsoft.com/kb/332088).
2. If the domain or server name has changed recently, search the registry for the old server.domain and replace it with the new server.domain. Then recycle the defaultAppPool (http://support.microsoft.com/kb/332088).
Applies To
Symantec Management Platform 7.0 SP2 + Hotfix 1
Task Server 7.0