locked
App-V Sync-AppvPublishingServer error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello All,

    Any ideas on the error below error. I am getting this on non domain joined systems only. Works fine when I run it on domain joined systems. I am App V 5.0 Sp3.

    I tried the link https://support.microsoft.com/en-us/kb/2778168 however it didn't help.

    Sync-AppvPublishingServer

    cmdlet Sync-AppvPublishingServer at command pipeline position 1
    Supply values for the following parameters:
    ServerId: 1
    Sync-AppvPublishingServer : Application Virtualization Service failed to complete requested operation.
    Operation attempted: RefreshPublishingServer.
    Windows Error: 0x80190191 -
    Error module: Publishing. Internal error detail: 45500D2780190191.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1 + Sync-AppvPublishingServer

    Tuesday, April 14, 2015 12:59 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Found the issue & resolved it.

    The applications were published using hostname i.e PackageUrl was like

    \\ HOSTNAME\packages\teamviewerapp\teamviewerapp.appv and credential Manager on App-V client machine was added credentials with FQDN.

    After adding credentials with HOSTNAME it started syncing.

    Thanks a lot for your help. Really Appreciate.


    • Edited by SrujanaV Wednesday, April 15, 2015 12:31 PM
    • Proposed as answer by SrujanaV Wednesday, April 15, 2015 12:31 PM
    • Marked as answer by VishalP97 Wednesday, April 15, 2015 12:39 PM
    Wednesday, April 15, 2015 12:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Try opening the following site: HTTP://*yourpublishingserver*:*port*

    If it is correct, you see an XML formatted site with the packages you are allowed to start.

    Tuesday, April 14, 2015 1:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Thanks for your reply. I am able to browse the site and do get a valid xml response.

    Tuesday, April 14, 2015 1:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, with or without a username/password prompt?

    Are the virtual applications on a UNC path or a web server?

    Run the following PowerShell command lines on those non-domain joined systems:

    Get-AppvPublishingServer -Name * | Remove-AppvPublishingServer

    Add-AppvPublishingServer -Name MyServer -URL HTTP://*yourpublishingserver*:*port*


    If you did receive a username/password prompt when opening the publishing server address,  open Windows Credential Manager and select "Add a Windows credential"


    Add the address of your Publishing Server and username. Publishing server with http(s)://servername:port / Username with DOMAIN\Username.

    Then add the Publishing Server address to the local intranet zone so it can use the local credentials.


    Run the PowerShell command: Sync-AppvPublishingServer -ServerId 1

    Tuesday, April 14, 2015 7:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for your reply.

    I have tried all the steps mentioned by you,  But still getting following error when I try to Run the PowerShell command :Sync-AppvPublishingServer -ServerId 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 -ServerId 1

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

        + FullyQualifiedErrorId : RefreshPublishingServerError,Microsoft.AppV.AppvClientPowerShell.SyncAppvPublishingSer

    Virtual Applications are on UNC shared path on a different server than publishing server.

    In windows credential manager specified the address of Publishing Server and username. Publishing server with publishing server name    / Username with DOMAIN\Username. 

    Publishing server name is specified in Windows Credential manager as URL is not accepted in Windows Credential Manager.

    Are we missing anything. Our Non-domain joined desktop is windows 2012 R2 and Win 8 machines on which App-v 5.0 Sp3 desktop Client is installed. Do we need to run any hotfixes on App-v server or app-v client for resolving sync issues.


    • Edited by SrujanaV Wednesday, April 15, 2015 7:34 AM
    Wednesday, April 15, 2015 7:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can the non-domain joined clients open the UNC path?

    Do you redirect %LOCALAPPDATA%\Microsoft\AppV ?

    Did you change the PackageInstallationRoot?

    Wednesday, April 15, 2015 8:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can the non-domain joined clients open the UNC path? - Ans: yes

    Do you redirect %LOCALAPPDATA%\Microsoft\AppV ?  Ans: - no, its default

    Did you change the PackageInstallationRoot? Ans: no, its default

    Wednesday, April 15, 2015 10:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you use the correct port?  The Management Server port number is different from Publishing Server Port number.

    Any 3th party profile solutions that copy files to %LOCALAPPDATA%?

    The only update I can find is this one

    Is it a production environment, maybe re-install the publishing server or create a second?

    Wednesday, April 15, 2015 11:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, publishing server and Management server ports are different. We are using the current Port Number.

    We are not using any 3rd party solutions to copy files to %LOCALAPPDATA%.

    It is not production environment, it is our Testing Environment.

    As per the link KB2533623 does not support windows 8 and windows 2012 R2.

    Also, when I tried to publish using the following powershell

    $pkg=Add-AppvClientPackage <UNC path of Appv Package>

    Publish-AppVClientPackage $pkg -Global

    It is able to get the appv packages on the app-v client desktop.

    But Sync-AppvPublishingServer -ServerId 1 still fails

    Wednesday, April 15, 2015 11:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Found the issue & resolved it.

    The applications were published using hostname i.e PackageUrl was like

    \\ HOSTNAME\packages\teamviewerapp\teamviewerapp.appv and credential Manager on App-V client machine was added credentials with FQDN.

    After adding credentials with HOSTNAME it started syncing.

    Thanks a lot for your help. Really Appreciate.


    • Edited by SrujanaV Wednesday, April 15, 2015 12:31 PM
    • Proposed as answer by SrujanaV Wednesday, April 15, 2015 12:31 PM
    • Marked as answer by VishalP97 Wednesday, April 15, 2015 12:39 PM
    Wednesday, April 15, 2015 12:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, great !

    Wednesday, April 15, 2015 1:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi everyone:

    We have the exact same setup as described above - with one difference - we are using HTTP.

    When we try to sync with the publishing server, we get AppV Error Code: 070000000B

    When we sync on a PC that is one the same network - the sync works fine. Also, when we open the sync URL in a browser, the download works fine. 

    What could be causing this problem?

    Thanks,

    Antony

    Monday, June 13, 2016 5:57 PM