Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Error when publishing packages in the Patch Manager Publishing Wizard

Error when publishing packages in the Patch Manager Publishing Wizard

Updated March 6, 2018


When you publish your packages using the Patch Manager Publishing Wizard, the following error displays:

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 previously moved and you did not use the wsusutil movecontent command, see the Microsoft TechNet article entitled, Specifying Where to Store Updates (© 2017 Microsoft, available at, obtained on January 26th, 2017)

    If the content is in the store, run the wsusutil movecontent <existing path> <log file> -skipcopy command to make sure 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 the password is correct.
  4. When you publish your packages, select the Verify WSUS version compatibility and required signing certificate is distributed option.
    If the certificates are not in place, see Publishing packages error: Verification of Signature failed for file. This article contains steps for checking for the certificate and putting it in place.
  5. If the error reappears when you publish the package, rerun the Wizard and select Re-sign existing selected packages and Re-download packages that have already been downloaded in the Wizard.


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