Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Error: "Could not decrypt file discovery whitelist after sync" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Error: "Could not decrypt file discovery whitelist after sync"
KB0727848

Error: "Could not decrypt file discovery whitelist after sync"


26186 Views Last updated : Dec 20, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Under the MID server record in the "MID server issues" tab you see the following error:

"Could not decrypt file discovery whitelist after sync".

Release

All

Cause

Cause 1:

  • This happens when the MID server tries to decrypt files that are trying to be synced from the instance before it had a chance to be validated. 

Cause 2:

  • The issue is caused by the fact that the instance will return nothing if the plugin "com.snc.discovery.file_based_discovery" doesn't have a license and the code on the mid server doesn't handle the error correctly so that the error message is misleading.
  • Please take a look at the sys_web_service script GetMIDInfo. When MID server starts, it will send a SOAP request to instance asking for updating file discovery allow-list. The request will be handled by the following function in GetMIDInfo: 
    function updateFileDiscoveryWhitelist() { 
    var havelicense = sn_lef.GlideEntitlement.hasBetaLicenseForApp('com.snc.discovery.file_based_discovery');
    if (!havelicense) {
    response.midInfo = null;
    return;
    }
    var agent = request.agent;
    var doc = MIDServerInfoAccessor.updateFileDiscoveryWhitelist(agent);
    response.midInfo = doc;
    }
    Since there is no license for this, it returns a response with an **empty** midInfo and the MID server will see that as a mid server issue, this can be ignored.

Resolution

Cause 1:

  • Make sure the MID server is validated
  • Manually resolve the Issue on the instance
  • Restart the MID Server, the issue should not come back anymore

Cause 2:

  • On the script comment out the license verifying code to work around it. (Please note the update to this file during platform upgrades might be skipped)

    OR

  • Add a business rule to ecc_agent_issue (MID server issues) table to automatically change the state of that particular error message to 'Resolved' so it does not appear on the MID issue list as a 'New' issue any longer. 

If the above performed and still have some issues, please follow the below 

  • Stop the mid server from the host machine, deleted the Keystore folder and started the MID- server service.
  • The Keystore folder will be created automatically
  • Now login to the ServiceNow instance and validate the mid server 
  • Wait for 2-5 minutes and the error will disappear from "MID SERVER ISSUE TAB"

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.