severity='2' hostName='MachineName' source='Client Task Agent' module='Client Task Agent.dll' process='AeXNSAgent.exe' pid='5152' thread='4016' tickCount='170139812' > Description: CAtrsException exception, error = "Unable to register",OS error = 2147549183, at line 463 re-throw at CTaskAgentBase::CheckRegister.
This message was received when trying to manually register the client from the web browser (using http://servername/Altiris/ClientTask/Server/Register.aspx):
<response result="failure">![CDATA[Error registering client: System.Exception: We cannot service this request because the web application failed to initialize. ---> System.Exception: Unable to configure remoting during Application Start ---> System.IO.DirectoryNotFoundException: Could not find a part of the path "D:\". at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path) at System.IO.Directory.CreateDirectory(String path) at Altiris.ClientTask.RemoteApi.CSLogFile.Initialize(String LogConfigurationFilePath) at Altiris.ClientTask.Server.Web.WebClientApiManager.GetLogFile() at Altiris.ClientTask.Server.Web.WebClientApiManager.Initialize(String configFilePath) at Altiris.ClientTask.Server.Web.Global.Application_Start(Object sender, EventArgs e) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at Altiris.ClientTask.Server.Web.WebClientApiManager.ProcessRegister(NameValueCollection queryValues, Stream requestStream, Int32 contentLength)]]</response>
The Identity Account (in this case Network Service) used in the DefaultAppPool didn't have the proper access rights to the root drive where the Altiris Agent was located. This should have at least have Read permissions.
Note: In this case, the customer installed the Altiris Agent on the D drive and the remote Task Server installed its components under this drive when the Task Server SP1 upgrade started. In the past, the Task Server components were installed by default in the C drive even though the Altiris Agent was in a different drive. This has changed on this release of Task Server, now it will install in the same drive as the Altiris Agent no matter what drive it is on.
Since the message received on the client registration page http://servername/Altiris/ClientTask/Server/Register.aspx) was referring to one of the requests made to the Web application had failed because "Could not find a part of the path 'D:\,'" it was necessary to check the components of the Task Server on IIS that were related to the D:\ drive.
Check the Identity of the Default Application Pool. By default it is Network Service.
Check what drive the ClientTask virtual directory is pointing to. You can check what drive is been used by opening IIS Manager and browsing to the ClientTask virtual directory (Web Sites > Default Web Site > Altiris > ClientTask) and opening the Properties page of it. Under the Virtual Directory tab, you should be able to identify the Local Path for the files used in this virtual directory.
Make sure that the account used as Identity on the DefaultAppPool has READ rights at least to the root of the D drive (or what ever drive you have IIS pointing too). If that account is not part of the Security tab on the D drive (check if that account used as Identity for the DefaultAppPool is not part of another Group. In some cases the Network Service account could be a member of 'MachineName\Users'), give it Read/Execute rights for This Folder Only on the root of the D drive.
Open the Properties for the drive and check if the Identity account for the DefaultAppPool is listed. In this case it is Network Service.
If it is not listed, add it. Click the Add button on the Security tab on the Properties page. Then add the account name.
After it is added, select the account and click on Read & Execute permission (usually automatically will add List Folder Contents and Read permissions as well).
Then click on the Advanced button and select from the list the account and click on Edit.
Then under Apply onto drop-down list, select This folder only. You should also see that Traverse Folder/Execute File, List Folder/Read Data, Read Attributes, Read Extended Attributes, and Read Permissions are already selected on the Permissions list. Click OK.
After the Identity account has been added, restart the Altiris Agent service, and the Task Server client should register successfully.
Applies To Notification Server 6.0.6074 SP3 R7 Task Server 6.0 SP1 upgrade
Imported Document ID: TECH40187
Subscribing will provide email updates when this Article is updated. Login is required.