cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ENS Firewall catalog import failure

Using ePO 5.9.1 I've exported all the Rules from the Firewall Catalog. When I try to import the rules on another instance of ePO 5.9.1, the import fails (it can't parse). The orion log indicates

Import Failed:

com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$UnknownFieldException: No such field com.mcafee.endp.fw.catalog.model.Rule.policySettingsId

---- Debugging information ----

field : policySettingsId

How do I fix this? Is the issue different/incompatible extensions? If so, which extension(s)?

Labels (1)
2 Replies
ktankink
Employee
Employee
Report Inappropriate Content
Message 2 of 3

Re: ENS Firewall catalog import failure

I would suggest opening a Service Request with McAfee Support to have the XML file reviewed.  Please provide the FW Catalog XML file and the debug Orion.log (from that error) from your ePO server for review.

Re: ENS Firewall catalog import failure

I edited the xml file, removing all occurrences of policySettingsId, tried the import again. It failed again, this time flagging the field "remote" within the NamedNetwork class. I removed all occurrences of remote and this time it imported. What a pain!!! Why are you guys changing schemas and not building in smart schema versioning?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community