Exception occurred while attempting to register the client

Products

• IT Management Suite
• Task Server

Issue/Introduction

After a new installation of Altiris Task Server, client computers were unable to register with the Notification Server. Each time the Altiris Agent on one of the client computers was restarted, the following errors were logged exactly six times for each client computer in the Altiris Notification Server a.log files:

Priority: 1
Date: 7/10/2007 1:21:26 PM
Tick Count: -1925389781
Host Name: COMPUTERX
Process: w3wp.exe (5440)
Thread ID: 7056
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.*

Description: An exception occurred while attempting to register the client. Error: System.Exception: An exception occurred while executing the request ---> System.Exception: System.Exception: Unable to register the client 53bea68e-09ad-409c-9abd-e33932bd5537 ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_CTR_ClientTaskServerGuid_CTS_ClientTaskServerGuid". The conflict occurred in database "Altiris", table "dbo.ClientTaskServers", column 'ClientTaskServerGuid'.

The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Altiris.ClientTask.Data.AltirisClientTaskSqlConnection.ExecuteReaderTransaction(SqlCommandDefinition command)
at Altiris.ClientTask.Data.AltirisClientTaskSqlConnection.ExecuteReader(SqlCommandDefinition command, Boolean transaction)
at Altiris.ClientTask.Common.Data.BaseClientTaskDataManagement.UpdateTaskClient(Guid ResourceGuid, Guid ClientTaskServerGuid, Byte[]& state)
at Altiris.ClientTask.Server.ClientTaskServer.RegisterClient(Guid resourceGuid, String configurationXml)

--- End of inner exception stack trace ---
at Altiris.ClientTask.Server.ClientTaskServer.RegisterClient(Guid resourceGuid, String configurationXml)
at Altiris.ClientTask.Server.ClientTaskServer.ProcessRemoteRegisterClient(Hashtable input, Hashtable& output)
at Altiris.Core.Sockets.SecureRemoting.SecureRemotingServer.ProcessRequestObject(Object work)

--- End of inner exception stack trace ---
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)

On the Windows workstations, the following warning was logged in the agent.log files:

Priority: 2
Date: 7/10/2007 1:21:34 PM
Tick Count: 98301359
Host Name: COMPUTERX
Process: AeXNSAgent.exe (1916)
Thread ID: 548
Module: Client Task Agent.dll
Source: Client Task Agent

Description: CAtrsException exception, error = "Unable to register", OS error = 2147549183, at line 440 re-throw at CTaskAgentBase::CheckRegister

Cause

While the exact cause of this error is unknown, the error message indicates that there was a corruption in several of the server side files used by Task Server.

Resolution

In order to resolve this issue, you need to run a repair on the Task Server .msi files, followed by a reboot of the Notification Server.

To perform the repair:

1. On the Notification Server navigate to C:\Program Files\Altiris\Setup Files\Task Server\.
2. Double-click on "TaskManagementSetup.msi".
3. When prompted, choose Repair to launch a repair.
4. Repeat this process for "ClientTaskSetup.msi".
5. Reboot the Notification Server.

In extreme cases, it might be necessary to run a repair on the remaining .msi files found in this directory.

Applies To
Notification Server 6.0 SP3 R4
Task Server 6.0