NS7 trouble BaseXmlHttpCallbackExceptions
Hey folks,
I'm running NS7 and recently I started getting a bunch of BaseXmlHttpCallback Exceptions in my Altiris logs (no connection could be made because the target machine actively refused it 127.0.0.1:50121). I am also getting BaseXmlHttpCallbackExceptions on "thread was being aborted". I repaired NS to no avail. Also getting warnings on NotificationServerWebConnection::CheckCredentials(): Credential check for "my service account" failed: System.Net.WebException: The remote server returned an error: (401) Unauthorized. I've got maintenance windows and all that so there's no reason for the task server to be refusing traffic on 50121. In case this pertained to a recent .NET framework patch I cleared out .NET frameworks, reinstalled and reenabled web extensions etc. but I'm having this same problem anyway. My service account is also fine (not locked out, works as login etc) and nothing has changed on my SQL side. Any ideas?
Comments
Hi Blained,
About the "BaseXmlHttpCallback Exceptions" is known issue described at AKB 50577 (https://kb.altiris.com/article.asp?article=50577&p=1), this AKB have a detailed troubleshooting steps for this points:
1. Check for port blocking.
2. Check a 3rd party app using the ports.
3. Verify you are using default ports.
4. Check the taskmanagement.log file to see if the Task Service can communicate with the NS.
5. Ensure that the Management Agent is running on the Notification Server
6. Contact Support.
7. Verify the installation of Task Server.
8. Verify that Notification Server Task Server components are Installed
9. Verify the the Altiris Object Host Service is using the correct instance.
Regards,
If the suggestion has helped to solve your problem, please mark the post as a solution.
Fábio Sanches
Altiris Consultant
Hi Luke,
I reinstalled the Task Server and it was still not listening on 50121. However i saw that it was failing out on auth and i think it couldn't hit my NS at the FQDN I had provided in the agent, as I had a separate DNS record set up (for disaster recovery purposes). Changing this in the registry (HKLM\Software\Altiris\Altiris Agent\Servers) to my server's "real" FQDN fixed the issue. I'll credit you the solution because you definitely set me on the right path. Thanks!
Blaine Baker
Information Security Administrator
feedback
Thanks Blaine for your feedback!
Regards,
If the suggestion has helped to solve your problem, please mark the post as a solution.
Fábio Sanches
Altiris Consultant
Would you like to reply?
Login or Register to post your comment.