IT Management Suite

Hello all,

we just upgraded our notification server from 7.5 HF4 to 7.5 SP1, the upgrade was smooth but site servers are not registering to itself as a Task server and showing not registered.

Please help asap.

I have tried repairing NS but not working for me.

Should i install hotFix5?

Is there any bug?

on site server agent, task service is showing upgraded but not getting registered to itself and showing not registered.

Hello all,

Please help me with some solution.

We have upgraded the SMP server with other user logged in instead of application credential.

Can it be the reason for the same.

Can anyone share their comments for the same.

Hello all,

Below are the logs for the same.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

NotificationServerWebConnection.PostToNotificationServer()
The remote server returned an error: (401) Unauthorized.
   [System.Net.WebException @ System]
   at System.Net.HttpWebRequest.GetResponse()
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.PostToNotificationServer(String url, ICredentials nsCredentials, NSWebConnectionBuildRequestStreamDelegate requestStreamDelegate, Int32 nMaxAttempts, Int32 nTimeout)

Exception logged from: 
   at Altiris.DotNetLib.Logging.AtrsLog.ExceptionMessage(String message, Exception exception)
   at Altiris.ClientTask.Server.Logging.NSAgentLog.ReportMessage(Severity severity, String moduleName, String source, Exception exception, String message, Object[] arguments)
   at Altiris.DotNetLib.Logging.AtrsLog.ReportExceptionWithSource(String source, Exception handledException, String message, Object[] arguments)
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.PostToNotificationServer(String url, ICredentials nsCredentials, NSWebConnectionBuildRequestStreamDelegate requestStreamDelegate, Int32 nMaxAttempts, Int32 nTimeout)
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.CheckCredentials(NetworkCredential nsCredentials)
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.FigureOutCredentials()
   at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.Initialize()
   at Altiris.ClientTask.Server.ClientTaskServer.RegisterTaskServer()
   at Altiris.ClientTask.Server.ClientTaskServer.OnRegisterTimer(Object unused)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._TimerCallback.PerformTimerCallback(Object state)
-----------------------------------------------------------------------------------------------------
Date: 14-08-2015 17:40:07, Tick Count: 289734152, Host Name: GURCHALT02, Size: 2.07 KB
Process: AtrsHost.exe (2912), Thread ID: 5564, Module: AtrsHost.exe
Priority: 1, Source: Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.PostToNotificationServer

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

Hi Krunal,

Have checked this discussion?

• https://www-secure.symantec.com/connect/forums/task-server-fails-register

1. Under which "Log On As" is running your "Altiris Object Host Service"?
2. Did you try to re-install "Task Server" x64 plug-in on problematic server?

Thanks,

IP.

Hi Igor,

I have checked the discussion which you have suggested.

I have tried re-installing the agent on the machine. Also, tried with re-installation of IIS and .NET framework.

Still the issue persist.

Have checked this discussion?

1. nder which "Log On As" is running your "Altiris Object Host Service"? - Service is running on Local System account on Site server and on Notification server it is running on same account.
2. Did you try to re-install "Task Server" x64 plug-in on problematic server? - Yes, Both manually and from SMP. Cabinetmaker.exe was prompting but with the help of Symantec support, we cleared the registry but doesnt help.

Please help me out as all the site servers are having the same problem, is it due to IIS or something else.

As prior to upgrade, everything was running fine.

Hi Igor,

I also want to notify you that Altiris was upgraded using other account instead of application account.

Is this the problem?

https://support.symantec.com/en_US/article.TECH42271.html

Does this link above helps you?

Do you have same settings for "Default Web Site" as it is on my server?

Hi Igor,

I have checked the article. But I have not changed the Targetted agent setting, currently it is application identity only.

For ISS setting, please find the screenshots, Settings are same as below:

Also find the Edit site and connect as settings, do you want me to change the site settings to Default App pool and then connect as application user?

Igor, Please suggest me with some changes.

I see a difference between our settings for "Default Web Site" where:

1. You have enabled "Basic Authentication" and "Windows Authentication", although they are disabled on my side.
2. Your "DefaultAppPool" is set to "Classic", although my "DefaultAppPool" is set to "Integrated" mode.
3. You are using specific user "crisil\altirisadmin", although on my server it uses "Application User".

Is there history reasons of why you have such settings in IIS on NS server?

Try to change them as I have (you will be able to return them back as you have now).

Thanks,

IP.

Hi Igor,

I had done the changes which you have asked me to perform, Notification Task server agent got registered to itself but can you suggest me some changes on Task Server so that Task Server also register to itself. Also, Symantec showed me that under default website>Altiris>TaskManagement> there was not TaskServerTasks website present in my IIS. Please find screenshot for the same:

Please find the screenshot for Task Server:

Please help me with something else I have to reinstall everything.

I have a roll-back of my previous version 7.5 HF4(VM snapshot), but the problem is that there are 4000 agents which are already upgraded to current version 7.5 SP1.

Can we start the snapshot and then upgrade once again back to 7.5 SP1.

Why you need to revert back to 7.5 HF4 snapshot if after changing IIS settings, you can register CTA with TS?

Of course you can revert snapshot and perform upgrade from 7.5 HF4 to 7.5 SP1 on NS side, but I'll suggest to blockout communication for already upgraded clients while upgrade will be running, because they will cause errors, etc in NS log during upgrade, since at least, Client Task Agent with higher version will doesn't work with lower version of Task Server.

Here is how looks IIS TS Application on Windows 2008 R2 with ITMS 7.5 SP1

Here is information about how to set appropriate assignments for registrations

• https://www-secure.symantec.com/connect/forums/site-server-task-servicespackage-services-question

Thanks,

IP.

Hi Igor,

Thanks for the prompt suggestion.

I am not going to revert as of now. I was just checking with you if I can do that or not.

Also, for TaskServerTasks website which is not available in the my NS installation, how can I use the article which you have provided me.

I am not able to open few pages on my console, I am not able to open Task server settings page.\

Below is the error on one of my Task server 1:

Below is the error on one of my Task server 2:

These are the errors which are coming on all of my Task servers. I can see on the console that some machines are showing active on the Task service which are getting "401 unautorised error". below is the screenshot for the same.

Please help me with some inputs.

Well, seems like after repair of NS, now these pages don't open for you?

According to log output, I see that there is a network problems with fqdn/hostname resolving between NS and client? Make sure that NS and client are able to resolve each other by hostname and fqdn.

Hi Igor,

Issue got sorted by deleting the .NET temporary cache from the below location and restarted the IIS:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\

Thanks for the help Igor.