1 of 1 people found this helpful
It seems to indicate that the Policy Handler is not running on the Agent Handler; the first KB you refer to would seem appropriate.
What are the 3 DLLs you have in your directory? And you might like to check the agent handler log files to see if there is an error indicated there.
thanks for the response.
the 3 DLL's are...
I've checked the DCOM settings and can see the correct entry in there.
As far as i can see, the only other error I've found is "No Policy Store"
not quite sure how the agent handlers work.
Hmmm....have you tried restarting the agent handlers (or ePO if you have no specific agent handlers)?
The "No policy store" message is a red herring, so no worries there.
Restarting the Agent Handler would be a good exercise to try, since it will clear any cached processed policies.
Quick question: what version of the EEPC extensions do you have, and what client versions are in the mix? Are they all 6.2?
Just restarted about 20 minutes ago, and it hadn't made a difference.
Not 100% sure how to restart the agent handlers. If it's a service, there's no service for it on the server. I've not dealt with agent handlers specifically before.
EEPC extensions are at version 188.8.131.526
software is at 184.108.40.2066
fixed the issue. It was complaining about that unprocessed policy (My Default). So I've just deleted that policy and created a new one. That default policy didn't hold any real significance anyway.
Thank you for all the suggestions in this thread.