High CPU usage, w3wp.exe, caused by Task Management Server

Article:TECH22026  |  Created: 2006-10-03  |  Updated: 2007-07-16  |  Article URL http://www.symantec.com/docs/TECH22026
Article Type
Technical Solution


Issue



Experiencing high CPU usage: Notification Server is acting really slow. Checked NSEs and not getting excessive bad NSEs. All servers and clients have sufficient hard disk space (greater than 500 MB). The a.log Altiris NS Log Files are getting flooded with:

Unhandled exception. Type=System.ArgumentNullException Msg=ArgumentNull_String

and the occasional or frequent:

Unhandled exception. Type=System.ArgumentNullException Msg=ArgumentNull_String"

and

"Unable to execute remote SQL from server "<computername" <guid>. ( Unhandled exception. Type=System.Exception Msg=An unapproved task server is trying to connect to the database.  Please make sure all Task Server computers have been added to the Configuration\Server Settings\Notification Server Infrastructure\Task Server\Approved Task Servers collection Src=Altiris.ClientTask.Web

The Altiris Task Management Server is installed or was been installed at some point.


Environment



Notification Server 6.0
Task Management Server

Cause



This is caused by many Task Servers attempting to access the Notification Server. The default "Applies to Collections" setting for Configuration > Server Settings > Notification Server Infrastructure > Task Server > Task Server Rollout > Task Server Install should be set to Task Servers. If it is set to All Computers, or any other collection, it should be changed to Task Servers before being enabled.

To find out if Task Servers have already been pushed out, check the Configuration > Server Settings > Notification Server Infrastructure > Task Server > Task Server Uninstall > With Task Server Installed collection; this will list all computers that have Task Server installed whether they're in the approved Task Servers lists or not. (Approved Task Servers are contained in either the Configuration > Server Settings > Notification Server Infrastructure > Task Server > Task Server Rollout > Task Servers collection or the Configuration > Server Settings > Notification Server Infrastructure > Task Server > Approved Task Servers collection.)


Solution



If the Altiris Agent is still present on all affected computers, disable the Task Server Install policy (or change the Applies To Collection setting to the Task Servers Collection) and enable the Task Server Uninstall policy with the Applies To Collection setting set to the With Task Server Installed collection.

If the Altiris Agent was removed, either reinstall the agent on all computers (which may take some time if the server is being overloaded) or deploy a script via Deployment Server or Logon scripts (or other means) to uninstall the Task Server from these computers.

The command line to run to remove the Task Server is:

msiexec.exe /qn REBOOT=ReallySuppress /x {FA682242-B9E4-4B35-BED6-1E09B36A7EC6}

(To verify that the uninstall command hasn't changed, on one of the affected computers, open the registry to HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall, do a Find for "Task", find the Altiris Client Task Server, and take the command line, or GUID, from the Uninstall value.)


Legacy ID



28252


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


Terms of use for this information are found in Legal Notices