none
Snyc-AppVPublishingServer error 070000000D on client 5.0 after removing a package on the server

    Question

  • Hi all,

    On a fresh brand new install of App-V 5.0 full infrastructure RTM version.

    I published an Office 2010, everything was fine both on server and client side, no error anywhere.

    Then I deleted the Office 2010 package and recreated it, with exactly the same name but using a different publishing URL (I changed from SMB to HTTP).

    Now the App-V client is still working OK but I have the following error when synchonizing with the publishing server:

    "Sync-AppvPublishingServer: there were errors encourntered when trying to un-publish packages that have been removed from the server"

    "AppV error code: 070000000D"

    I suspect I have an issue on the client side not on the server side. I tried to remove the client completely, rebott and reinstalled it but the error message is still there. What could I do ?

    THANKS and best regards,

    Lionel

    Thursday, November 29, 2012 10:06 AM

Answers

  • My issue occured again ( 070000000D ) , I found out in the event viewer Microsoft\Appv\Client\Admin, I had an event 19104 and 1008 with 0x8007002 which is " ERROR_FILE_NOT_FOUND"

    You can not actually unpublish a package that does not exist anymore on the content store. I just had to add back the package to the content and re do an publish - unblish to remove package on the client side

    Thursday, February 07, 2013 6:16 PM

All replies

  • have you followed this article: How to troubleshoot publishing server refresh failures in App-V v5


    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 my employer, Microsoft, its employees, or other MVPs.

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

    Thursday, November 29, 2012 10:39 AM
    Moderator
  • Hi,

    As I said, the server and the client are working fine. I can publish applications, they get downloaded and I can run them on the client. So, my config seems fine. I checked again the link you provided but it does not apply to my situation.

    The error message arrived after I deleted a package.

    Thanks for your help

    Lionel

    Thursday, November 29, 2012 10:42 AM
  • Hello,

    Did you publish this for a user or a machine?

    Its currently not supported to sequence Office 2010, so perhaps verifying the behavior with a different type of application would be a good idea

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


    • Edited by znack Thursday, November 29, 2012 8:40 PM
    Thursday, November 29, 2012 8:39 PM
  • Hi,

    I used no specific config file so I published to a group of AD users.

    I tried with Adobe Reader and I have the same error: whenever i publish an application and then delete/recreate it, I have this error.

    I have this error also on three different environments, so I guess something is weird and I opened a support request to MS.

    THANKS

    Lionel

    Tuesday, December 04, 2012 3:07 PM
  • Hi,

     I have the same error msg when I try to 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

    I can browse to the publishing server site & get the xml page with the package that I published. This is a fresh clean install of Appv 5.0 RTM.

    Any fixes?

    Thanks,

    Sh1va.

    Thursday, December 06, 2012 9:01 AM
  • So what does the log say?


    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 my employer, Microsoft, its employees, or other MVPs.

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

    Thursday, December 06, 2012 9:21 AM
    Moderator
  • Just checked the event log under c:\ProgramData\Microsoft\Application Virtualization Client\sftlog.txt

    It doesn’t show any logs for yesterday & today. i.e. 12/06/12 & 12/07/12. Is this where I check for the log files or is there any other place I can check?


    [12/05/2012 11:53:29:450 SRVC WRN] {tid=12B8}
    --------------------------------------------------------
    Initialized client log (C:\ProgramData\Microsoft\Application Virtualization Client\sftlog.txt)


    [12/05/2012 11:53:29:497 ???? INF] {tid=12B8}
    App-V filter loaded.


    [12/05/2012 11:53:29:513 VSCM INF] {tid=12B8}
    Starting Virtual Service Control Manager.


    [12/05/2012 11:53:30:183 JGSW INF] {tid=12B8}
    The Application Virtualization file system was initialized successfully.


    [12/05/2012 11:53:30:324 INTF WRN] {tid=12B8}
    The Application Virtualization Client Core initialized correctly.
    Installed Product:
    Microsoft Application Virtualization Desktop Client
    Version: 4.6.1.20870
    Install Path: C:\Program Files (x86)\Microsoft Application Virtualization Client
    Global Data Directory: C:\ProgramData\Microsoft\Application Virtualization Client\
    Machine Name:
    BEF-4136-D16
    Operating System: Windows 7 64-bit Service Pack 1.0 Build 7601
    OSD Command:


    [12/05/2012 11:53:30:339 SRVC INF] {tid=12B8}
    ---- The Application Virtualization Client Service version 4.6.1.20870 has started ----


    [12/05/2012 11:53:31:260 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 1)


    [12/05/2012 11:53:31:322 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 2)


    [12/05/2012 11:53:31:416 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 3)


    [12/05/2012 11:53:31:650 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 4)


    [12/05/2012 11:53:31:681 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 5)


    [12/05/2012 11:53:31:697 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 6)


    [12/05/2012 11:53:31:821 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 7)


    [12/05/2012 11:53:31:993 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 8)


    [12/05/2012 11:53:32:055 AMGR INF] {tid=131C:usr=lnai006}
    Delete application (hApp was 9)


    [12/05/2012 11:53:32:274 SRVC INF] {tid=10F8}
    The Application Virtualization Client Service received a stop request from the Service Control Manager and will now attempt to shut down.


    [12/05/2012 11:53:32:461 JGSW INF] {tid=1234}
    The Application Virtualization file system was shut down cleanly.


    [12/05/2012 11:53:32:477 THRD WRN] {tid=1234}
    The Client detected 0 hanged threads remaining on shutdown that need to be terminated.

    Thursday, December 06, 2012 8:51 PM
  • Hello,

    This an App-V 4.x log?

    12/05/2012 11:53:30:324 INTF WRN] {tid=12B8}
    The Application Virtualization Client Core initialized correctly. 
    Installed Product:
    Microsoft Application Virtualization Desktop Client
    Version: 4.6.1.20870
    Install Path: C:\Program Files (x86)\Microsoft Application Virtualization Client
    Global Data Directory: C:\ProgramData\Microsoft\Application Virtualization Client\
    Machine Name:
    BEF-4136-D16
    Operating System: Windows 7 64-bit Service Pack 1.0 Build 7601
    OSD Command: 


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

    Thursday, December 06, 2012 8:59 PM
  • The logs for Appv 5.0 are not being recorded.

    Thursday, December 06, 2012 11:41 PM
  • The App-V client logs are recorded and enabled by default in the Event Logs under - Applications and Services / Microsoft / AppV 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 my employer, Microsoft, its employees, or other MVPs.

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

    Friday, December 07, 2012 8:48 AM
    Moderator
  • I've gone through all steps in      "How to troubleshoot publishing server refresh failures in App-V v5"

    Step 1: Verify the Publishing Server URL configured on the client                                 Get-AppvPublishingServer       http://comappv5.com.auckland.ac.nz:333

    Step 2: Add Windows Firewall exception on the Publishing Server                                Windows Firewall on the Publishing Server is turned OFF.

    Step 3: Verify the Publishing Server site is started on the Publishing Server                 Started (http)    :333 (http)  

    Step 4: Verify the Publishing Server application pool is started on the Publishing Server   Started   .NET Framework Version  v4.0  Management Pipeline Mode    Integrated       Identity   ApplicationPoolIdentity   Applications   1

    Step 5: Verify the Publishing Server URL is accessible using a web browser      http://comappv5.com.auckland.ac.nz:333

    -<Publishing Protocol="1.0">

     -<Packages>

       <Package PackageId="1af9995d-c02d-4645-9776-404b47afcd9b" VersionId="865b1252-c1e7-4cd3-abab-8b217f71247a"

           PackageUrl="\\comappv5\content\SPSS21 x64\SPSS21 x64.appv" />

       </Packages>

     - <NoGroup>

          <Package PackageId="1af9995d-c02d-4645-9776-404b47afcd9b" />

        </NoGroup>

      </Publishing>

    SPSS21 x64 is the only package currently published on the Publishing Server.

    Step 6: Perform a publishing server refresh          Sync-AppvPublishingServer

    Sync-AppvPublishingServer : There were errors encountered when trying to publish packages fromt he server.

    Operation attempted: RefreshPublishingServer.

    AppV Error Code : 070000000B.

    Please consult AppV Client Event Log for more details.

    At line:1 char:1

    * Sync-AppvPublishingServer

      *CategoryInfo                 : InvalidResult: (:) [Sync-AppvPublishingServer],  ClientException

      *FullyQualifiedErrorId      : RefreshPublishingServerError,Microsoft.AppV.AppvClientPowerShell.SyncAppvPublishingServer

    In the App-V client console, click Update   NOT greyed out. But on clicking Update it just oscillates. Doesn't update.

    • App-VEvent Logs

    Log Name:                Microsoft-AppV-Client/Admin
    Source:                    Client
    Event ID:                 19104
    Task Category:         Publishing Refresh
    Level:                      Error
    User :                      UOA\lnai006

    OpCode:                  Info

    Package {1af9995d-c02d-4645-9776-404b47afcd9b} version {865b1252-c1e7-4cd3-abab-8b217f71247a} failed configuration in folder" with error 0x74F01B0C-0x7.

    Monday, December 10, 2012 11:03 PM
  • Hello,

    Try the latest hotfix once its available - see this announcement;

    http://social.technet.microsoft.com/Forums/en-US/appvclients/thread/8ca1ff54-35ea-40f5-b241-de186c206eb8


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

    Monday, January 28, 2013 8:09 AM
  • Hi,

    I had the same issue, APPV 5 hotfix 1 did not solved it nether the Server or Client reboot

    I solve my issue by republishing all my previous app and after a sync-publishing server I unpublished them again.

    Tuesday, February 05, 2013 6:46 PM
  • Hello,

    I suggest you report the issue to Microsoft then, as your issue may be different.


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

    Tuesday, February 05, 2013 7:22 PM
  • My issue occured again ( 070000000D ) , I found out in the event viewer Microsoft\Appv\Client\Admin, I had an event 19104 and 1008 with 0x8007002 which is " ERROR_FILE_NOT_FOUND"

    You can not actually unpublish a package that does not exist anymore on the content store. I just had to add back the package to the content and re do an publish - unblish to remove package on the client side

    Thursday, February 07, 2013 6:16 PM
  • I'm trying to understand the meaning of this error, because I have it as well in my environment

    When there's an old version of a package or an old package that is not in used - I don't unpublish it, I delete it.

    My common sense tells me that if these packages are still exist on the clients, they'll be unpublished on the next logon\refresh , as they won't find themselves published on the server.

    and I'm trying to combine it according what you wrote.

    does it make any sense that I will need to keep all my legacy packages unpublished just so my client will be able to refresh the packages from the server without any errors?

    not mentioning VDI environments.... where all the packages works on local cache and harder to manage and follow... :/ 


    Tamir Levy

    Tuesday, February 11, 2014 2:11 PM
  • It means that you first should make sure the package is unpublished from all clients and after that you remove it from the server after a grace-period.

    (btw. this was recommended for App-V 4/Softgrid too: first unpublish on the server, wait a few days-weeks, then remove entirely)

    While I see the benefit of an 'the package isn't on the server any longer so I unpublish it' approach, it has some downsides, too. What happens if your client can connect to the server but the server hangs for a second and does return an 'empty' app list? Just unpublish anything on the client ... just in case? Or if you have configured multiple servers, and one isn't working propperly. Or if you added a few packages manually...


    Falko

    Twitter @kirk_tn   |   Blog kirxblog   |   Web kirx.org   |   Fireside appvbook.com

    Wednesday, February 12, 2014 2:34 PM
    Moderator
  • Thanks for your answer Kirk,

    I have a problem that every login takes forever and when I check the taskmgr I see that the Appvclient.exe takes 80-90% of CPU.

    I wonder if it's related

    Can you guide me where to find the documentation about the publish - un-publish  best practice? (4.x or 5.x)

    Thanks


    Tamir Levy

    Thursday, February 13, 2014 7:49 AM
  • Running this command on the client fixed it for me:

    Sync-AppvPublishingServer -Force -serverid <id>"

    Tuesday, February 18, 2014 4:06 PM