Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Unable to compare configuration files most likely caused by broken regular expressions

Unable to compare configuration files most likely caused by broken regular expressions

Updated August 23, 2017

Overview

This article describes issues related to the following error:
Unable to compare configuration files, most likely caused by broken regular expressions. Inspect your logs for details.

 

Environment

  • NCM 7.6

 

Cause 

 

The configuration differences engine doesn’t accept some regular expression characters or tokens.

Resolution

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click NCM Settings. 
  3. Under Configs, click Comparison Criteria.
  4. Replace all ‘\s’ occurrences to ‘[ \t\r\n\v\f]’ in the RegEx column.
    Example: ‘\s*crypto.*certificate’ -> ‘[ \t\r\n\v\f]*crypto.*certificate’
  5. Replace all ‘error’ occurrences to ‘er[r]or’ in the RegEx column.
    Example: ‘errors*’ -> ‘er[r]ors*’
 

 

Last modified

Tags

Classifications

Public