Symantec Management Platform (Notification Server)

Morning,

I am seeing a constant feed of Warnings detaling the following:

The handler 'GetClientTaskServers' is failed to process request. Called by unknown endpoint '54ade2fc-e25e-4206-ab6b-d920aabfbb6f'.

I found the resource associated to the GUID which was an unmanaged XP system which no longer exists on our domain and deleted it from the filter "All computers with no SM agent", but it continues.

We are running SMP 7.5 SP1 with the latest Hotfix on Server 2008 R2 SP1.

Any ideas would be welcome.

Thanking you in advnace.

 

Open Resource Manager for any systems and cut and paste the GUID into the address bar and see if it still seems to exist. Or in Altiris Log Viewer click on any blue underlined GUID to bring up the Item browser and paste the GUID at the bottom of that. this will tell you if the resource really is deleted.

Hi!

1. Do you have any agent manual assignments for Task Server?
2. "Legacy Agent Communication" option is enabled or disabled? If off, then 7.1 agents will be able to communicate with NS/TS

Thanks,

IP.

Hi Gents,

Thanks for the replies.

@Andykn101: I opened Resource Manager as indicated in your post and it dit populate a resouce with blank details, i used the right-click options to delete the resource, will monitor and see if there is any change.

@Igor: I do not have manual assigned agents and Legacy comms are enabled.

Kind Regards,

Eugene

Such trace indicates there must be some alive computer with SMA that trying to access NS web-interface with attempt to obtain the list of the Task Servers. Please try SQL select from Symantec_CMDB:

SELECT * from Inv_AeX_AC_TCPIP where _ResourceGuid = '54ade2fc-e25e-4206-ab6b-d920aabfbb6f'

It should return MAC and IP of such computer.

Note: it also could be some computer loaded with DS pre-boot environment as it also contains SMA.

Thank you,

Alex.

Thanks Alex,

The query provided the not return any result, i assume because of the below.

After deleting the resource via the method Andykn101 suggested, it seems the issue has gone away.

I will review for the day and revert before marking as solution.

Eugene

 

Eugene, no prob - glad it was solved :)

Thanks for the all the repsonses guys :)