cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

I registered my new and old ePO servers successfully. When I go to run the Synchronize Shared Policy task on the old ePO server, it runs but each of the pushes fails with this error:


Failed to Push Policy *Insert Policy Name here* to server *Server name* Error: "The formal parameter "(at)ResourceID" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output."

Note: Where it says (at), the error uses the @ symbol. However, the formatting of this forum didn't allow me to use it.

I tried researching this error online to no avail. This happens on each of the non-default policies that I created and are being used in my environment. Any ideas? I tried finding out what the @ResourceID means but couldn't come up with anything.

1 Solution

Accepted Solutions
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

There are a lot of schema changes in 5.9.1 vs 5.3, possibly not all policies are compatible for sharing between the different servers.  Do you have the same versions of extensions installed?  Policy import from one server to another is always recommended to be same epo and extension versions.  That would also apply to policy sharing.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

4 Replies
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

There are a lot of schema changes in 5.9.1 vs 5.3, possibly not all policies are compatible for sharing between the different servers.  Do you have the same versions of extensions installed?  Policy import from one server to another is always recommended to be same epo and extension versions.  That would also apply to policy sharing.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

Sorry for not responding.

The servers are different versions of ePO (5.3.2 to 5.10). I was able to manually export/import and it seems to be running fine. Thanks for your input and sorry for the long delay in responding.

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 5

Re: Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

No problem on the delay in responding.  We actually changed the kb for that as it previously stated you had to have same version of epo, but that is not the case.  It is ok to have different versions of epo, just need to make sure extensions are same at very least, or higher on receiving side.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Synchronizing Shared Policy failed - ePO 5.3 to ePO 5.9.1

Jump to solution

Thank you very much for the updated information! I'll review the extensions and go from there. Have a great day!

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator