Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > The directory is not empty. DataPortal_Execute method failed DataPortal.Update failed

The directory is not empty. DataPortal_Execute method failed DataPortal.Update failed

Updated January 27, 2017


The following message is displayed in the Patch Manager Publishing Wizard:

The directory is not empty. DataPortal_Execute method failed DataPortal.Update failed


  • All Patch Manager versions
  • All WSUS versions


Various issues with the configuration of the WSUS server or Patch Manager server may cause this issue:

  • Incorrect permissions for the WSUS content folders.
  • Incorrect permissions or missing shares for the WSUS content folders.
  • The WSUS content store was moved without using the wsusutil command.
  • Issues with the account in the credential ring.
  • Missing certificates on the Primary Application Server (PAS) or WSUS server.
  • Issues during downloading and publishing the package.


  1. Check the permissions for WSUS folders and shares.
  2. If the WSUS content store was moved previously and the wsusutil movecontent command was not used, consult the Specifying Where to Store Updates technet article. (© 2017 Microsoft, available at, obtained on January 26th, 2017)
    Note:  If the content is in the store where it should be, you can run the wsusutil movecontent <existing path> <log file> -skipcopy command to make sure that the registry and other settings are updated without copying the content again.
  3. Verify that the account in the credential ring has sufficient permissions to the WSUS server and that the password is correct.
  4. When publishing, select the Verify WSUS version compatibility and required signing certificate is distributed option.
    1. If the certificates are not in place, the Publishing packages error: Verification of Signature failed for file contains steps for checking for the certificate and putting it in place.
  5. If you are still seeing the error when publishing the package, select the Re-sign existing selected packages and Re-download packages that have already been downloaded options.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified