1 Reply Latest reply on Sep 11, 2014 7:20 AM by Lawrence Garvin

    Patch Manager - Package publishing 'Failure'

    Christopher Faithfull-Lisle

      Hi

      We are running Patch Manager 2.0.2207 in our enterprise.

      We are trying to publish a 'pre-defined' package for Google Chrome 37.0.2062.103 Business Enterprise MSI (Upgrade).

      The package content has downloaded fine, but when the 'Patch Manager Publishing Wizard' is run, it returns a Failure message, as follows:

       

      The Summary of the results of publishing the packages:

       

      Package: Google Chrome 37.0.2062.103 Business Enterprise MSI (Upgrade)

      Status: Failure

      Message: The process cannot access the file: C:\Program Files\Solarwinds\PatchManager\Server\data\auto\{really long GUID}\{Another really long GUID}\content.....because it is being used by another process. An unexpected internal failure occurred in the FileSystem component, or one of its descendants. Type: Xceed.FileSystem.DiskFile FullName: {then repeats the path and file from above}

      Screenshot is attached.

       

      We have restarted the various 'services' on the PAS and also restarted the server several times, but still the same error.

      We have tried this with various User accounts too, including the 'Solarwinds Enterprise Admin' user, but still the same error.

       

      After some digging, we found that the downloaded package is in a totally different folder path: C:\Program Files\SolarWinds\Patch Manager\Server\packages\publisher\55de0bc2-d1f1-4c3b-b6de-8634ef9a98f5

      Can anyone please give us some help on what we've done wrong, or what we need to do to get this package published.

      We have created and published packages fine in the past.

       

      Many thanks in advance for any help or suggestions. :-)

        • Re: Patch Manager - Package publishing 'Failure'
          Lawrence Garvin
          After some digging, we found that the downloaded package is in a totally different folder path: C:\Program Files\SolarWinds\Patch Manager\Server\packages\publisher\55de0bc2-d1f1-4c3b-b6de-8634ef9a98f5

           

          Correct, this is the source path for the package on the Application Role server..

           

          Message: The process cannot access the file: C:\Program Files\Solarwinds\PatchManager\Server\data\auto\{really long GUID}\{Another really long GUID}\content......because it is being used by another process


          But this is a working copy of the file being used by the Automation Role server attempting to access the file to transfer it to the WSUS server.

          Apparently, something has locked the file. Are there any tasks currently running on the server, including any tasks that may have hung.

          Most notably we'd be looking for another publishing task for this update.


          A very common culprit in cases like this is AntiVirus/AntiMalware software doing a scan-on-create which fails to finish before the Patch Manager server attempts to use the file again.

          You should exclude the ~\data folder tree from on-demand AV scans.


          If none of that resolves the issue, then I recommend the following:

          1. Enable logging, as described in SolarWinds KB32616, rerun the publishing task until the error is re-generated, then disable logging.
          2. Open a Support Ticket via customerportal.solarwinds.com.