when I try to update to the latest VSE Management Extension 22.214.171.1248 I got the same error message as described in McAfee KB86016 (McAfee KnowledgeBase - VirusScan Enterprise 126.96.36.1992 (Patch 6) management extension upgrade Fails).
Recommended Workaround: Identify and remove the corrupt policies, and then retry the upgrade.
So far so good but can someone explain how to identify the corrupt policy? I cannot remove all AP policies just to find the corrupt one??
BTW the last Extension Update to Version 188.8.131.520 from Hotfix 1087536 succeeded without any Problems.
Any help would be appreciated.
Solved! Go to Solution.
OK just received the fix for this. Issue is with the Verisign Certificates in the client browser.
Need to install :
Once I did this I was able to install P7 and the Extension does not fail install.
I hope this article will help you to identify corrupted policy.
Thanks for your reply, unfortunately the article does not help because according to the article all AP Policies in our environment should be fine. Means that categoryid and section names looks like in the default McAfee AP policy.
Unfortunately not, I have still an open SR.
First the support asked me to check if the AP Policies are corrupt:
"You can identify the corrupt policies by viewing the attributes (click to edit policy) and it will not show the contents. Also it will show as blank, in accessible."
As this is not the case the following are the suggested steps from McAfee (which I have not performed so far):
But be careful, after removing the Extension all your policies are gone and all clients would receive the default polices until you have sccessfully reimported the policies. To avoid that you have to disconnect the ePo Server from the Network.
As already mentioned, I haven't performed these steps so far because I noticed that ePo Hotfix 1124228 seems to resolve an issue with extensions:
This hotfix supersedes HF1117371. HF1117371 was packaged with an
updated version of a Java library that was found to be incompatible with
some ePO product extensions. With this updated hotfix, the incompatible
library has been replaced with the version originally packaged with ePO.
I think I will install the hotfix this week and hope that it will resolve the issue.
I just opened a SR as well.
What version ePO server are you running? I am on 5.1.1 HF1.
I have checked all of our AP and OAS policies to make sure they are not corrupt and all of them seem to populate. I do not like other option about disconnecting the ePO from the network and "bouncing" the extension, I think a lot could go wrong.
I haven't applied HF1117371 or H1124228 as I have not seen it pop up as needed for me as of yet.