Symantec Management Platform (Notification Server)

 View Only
  • 1.  Errors with finding valid site servers

    Posted Jun 22, 2012 11:38 AM

    I am getting a lot of errors in my log files on my SMP 7.1 SP2 server that state:

    *****

    Log File Name: C:\ProgramData\Symantec\SMP\Logs\a.log
    Priority: 1
    Help and Support:
    Date: 6/22/2012 9:27:36 AM
    Tick Count: -1190977869
    Host Name: <SERVER NAME>
    Process: AtrsHost (1596)
    Thread ID: 508
    Module: AtrsHost.exe
    Source: Altiris.TaskManagement.ClientTask.BaseClientTask.TryUpdateSiteAssignmentsForUnmanagedDevices
    Description: BaseClientTask.TryUpdateSiteAssignmentsForUnmanagedDevices():  Unable to find a valid site server for computer <COMPUTER NAME>  (GUID)

    *****


    I found two KB articles for version 7.0 : TECH136483 & TECH174733. The first article states there is an unknown cause for the issue and has no solution while TECH174733 states the issue is due to an AD import of invalid user accounts with blank names in them. The solution for 174733 is to remove the users with blank names by inserting them into the itemstodelete table. I have 66 entries that are returned with blank names but I have only counted about 44 errors. With the count difference and the solution being for 7.0 I am a little hesistant to insert those entries into the itemstodelete table.

    Has anyone else had this issue? If so is KB174733 the only way to fix this issue or is there another method I can use? I am also unclear as to why this would be related to a user import from AD. I am not importing users, just tech support personel.

    Enviroment:

    SMP 7.1 SP2



  • 2.  RE: Errors with finding valid site servers

    Posted Jun 22, 2012 12:40 PM

    You can safely insert these into ItemsToDelete.  They're just invalid users with blank names.  I have done this in two environments, both 7.0.  In one case, it fixed it; in another, it did not.  In the "not fixed" environment, I'm afraid it's a cliffhanger: there were other serious issues that had to be resolved first, which led up to my paternity leave, and it wasn't a priority in my absence.  Probably still loading errors into the logs.