Can't Load Package from Publishing Server - Event ID 1008 RRS feed

  • Question

  • I'm stuck, using the production release of App-V 5.0, not the BETA version. Converted several packages from version 4.6 leveraging Powershell cmdlet.  Published the package and created a local policy to set the publishing server on the client. I've tried the troubleshooting steps here (http://support.microsoft.com/kb/2778168?wa=wsignin1.0) and elsewhere, but haven't turned up anything out of the ordinary, should volunteer that the packages are hosted on DFS and I've confirmed that the logged in account can access the share.

    This is what I get in event viewer:

    Event ID 1008

    Package {c851601d-e4c2-4c7a-aa23-857d9067fbf7} version {cb8cc299-87e4-45b9-9f09-032bff09a78b} failed configuration in folder 'C:\ProgramData\App-V\C851601D-E4C2-4C7A-AA23-857D9067FBF7\CB8CC299-87E4-45B9-9F09-032BFF09A78B' with error 0x86D00D06-0xB.


    This is what I get when I force a sync via Powershell

    PS H:\> import-module AppvClient
    PS H:\> Sync-AppvPublishingServer 1
    Sync-AppvPublishingServer : There were errors encountered when trying to publish packages from the server.
    Operation attempted: RefreshPublishingServer.
    AppV Error Code: 070000000B.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Sync-AppvPublishingServer 1
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Sync-AppvPublishingServer], ClientException
        + FullyQualifiedErrorId : RefreshPublishingServerError,Microsoft.AppV.AppvClientPowerShell.SyncAppvPublishingServer


    In case anyone's interested here's the script I'm using to recurse a folder and convert the package:

      $Source = "C:\PACKAGES"
      $Destination = "C:\PACKAGES.V5"
    # create destination folder (parent)
      New-Item -Path $Destination -type directory
    # create subfolders
      Get-ChildItem -Path $Source | ForEach-Object { New-Item -Path $Destination\$_ -type directory }
      $Packages = Get-ChildItem -Path $Source
      cd c:\packages
      foreach ($Item in $Packages){
         $Result = Test-AppvLegacyPackage $Item.FullName
         if ($Result.Errors.Count -eq 0) {
            Write-Host "Processing " $Item.FullName
            ConvertFrom-AppvLegacyPackage -SourcePath $Item -DestinationPath $Destination\$Item

    Saturday, November 17, 2012 11:46 PM

All replies

  • What steps did you take when publishing the packages via the Management server?

    What's the output from Get-AppvClientConfiguration on the client?

    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

    Sunday, November 18, 2012 10:34 AM
  • It feels like the same problem as in this thread: http://social.technet.microsoft.com/Forums/en-US/appvserverandmanagement/thread/743564ed-0013-4f88-858b-8f8814dc7098

    If you have published for example version to a client and it has started it once and then you publish a new version, this error appears on the client.

    More posts about this issue:



    My impression is that you can't publish a new version in App-V 5....

    Tuesday, November 27, 2012 7:50 PM
  • I don't think these are related, in your scenario, from what I understand, you have converted from 4.6 and cannot deliver an App-V 5 version at all? Is that correct?

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Friday, November 30, 2012 4:56 PM
  • Hello,

    What happens if you add the packages manually via powershell and avoid looking at the infrastructure part at the moment?

    Nicke Källén | The Knack| Twitter: @Znackattack

    Sunday, December 2, 2012 9:22 PM