After upgrade to SMP 7.6 clients won't register with Task Server.

Products

• IT Management Suite

Issue/Introduction

We have updated everything to 7.6 and are still having problems being able to run jobs from the server to remote machines. Regular policy communication appears to work, but Task is not working.

"4/15/2015 4:38:30 PM","Failed to handle request to a service: RegisterClient

Value cannot be null.

Parameter name: s

   [System.ArgumentNullException @ mscorlib]

   at System.Convert.FromBase64String(String s)

   at Altiris.TaskManagement.Common.ClientTask.Communication.NotificationServerConnection.GetCurrentResourceEncryptionKey(INotificationServerConnection me)

   at Altiris.ClientTask.Server.ClientTaskServer.get_EncryptionKey()

   at Altiris.ClientTask.Server.ClientTaskServer.RegisterClient(AltirisResourceGuid resourceGuid, Boolean bLastResort, Boolean bBeingActive, String configurationXml, String crc, Hashtable& output)

   at Altiris.ClientTask.Server.ClientTaskServer.ProcessRemoteRegisterClient(Hashtable input, Hashtable& output)

   at Altiris.DotNetLib.RemotingRequestService.Altiris.DotNetLib.IRemotingRequestService.HandleRequest(String service, Hashtable parameters)

 

Exception logged from: 

   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)

   at Altiris.TaskManagement.Logging.AltirisServerLog.ReportException(String moduleName, String source, Exception handledException, String message, Object[] arguments)

   at Altiris.DotNetLib.Logging.AtrsLog.ReportExceptionWithSource(String source, Exception handledException, String message, Object[] arguments)

   at Altiris.DotNetLib.RemotingRequestService.Altiris.DotNetLib.IRemotingRequestService.HandleRequest(String service, Hashtable parameters)

   at SyncInvokeHandleRequest(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

   at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)

   at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)

   at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)

   at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)

   at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

   at System.ServiceModel.Channels.TransportDuplexSessionChannel.TryReceiveAsyncResult.OnReceive(IAsyncResult result)

   at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)

   at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

   at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.OnReceiveComplete(Object state)

   at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)

   at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)

   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)

   at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32 readBytes, Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.NegotiateStream.ReadCallback(AsyncProtocolRequest asyncRequest)

   at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32 bytes)

   at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)

   at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)

   at System.ServiceModel.Channels.ConnectionStream.IOAsyncResult.OnAsyncIOComplete(Object state)

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)

   at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

 

**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.6.1383.0&language=en&module=IFrNby/8zZUzkf8jfR5gSyjv5K0QP3oR6lVaOtvMVTB8fh0/qBT4otTHTYjXL22r+B3UtZcLX3QlkkwlldkgzQ==&error=1648444906&build=**CEDUrlEnd**

","ClientTaskServer","AtrsHost.exe","48","Errors"

Environment

ITMS 7.x, 8.x

Cause

Unsure at this time. Something about the upgrade replaced the "NSResourceGuid" key in CoreSettings.config with a different GUID than what we see in the Symantec Management Agent UI on the Notification Server.

Resolution

1. Please compare these two GUIDs: Symantec Management Agent (SMA) GUID displayed in the SMA UI on the Agent Setting page, and CoreSettings.config "NSResourceGuid" key. This is located (by default) at: C:\ProgramData\Symantec\SMP\Settings. You will need to find string "NSResourceGuid" inside the .config file and compare it with the GUID we see in the SMA UI settings page.
2. If the GUIDs are different then you will need to replace the "NSResourceGuid" key in CoreSettings.config with the SMA GUID.
3. After this is replaced, restart the Altiris Service, Symantec Management Agent service, Altiris Object Host Service and Altiris Client Task Data Loader Service. Once you do this you should see Client Task Agents connecting for Task.