locked
App-V 5.0 Sync Error HttpRequest SendRequest failed RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Guys,

    Set Beta 1 up without issue at home. Setting up Beta 2 in a different environment. Firewall disabled on Client and Server. Can reach the console and publishing server xml from client without issue. When I perform a sync I get the below error:

    Powershell error:

    Getting the following error:

    sync-AppVPublishingServer : Application Virtualization Service failed to complete requested operation.
    Operation attempted: RefreshPublishingServer.
    Windows Error: 0x80190194 -
    Error module: Publishing. Internal error detail: 45500D2780190194.
    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.SyncAppvPublishingServe
       r

    Event Viewer Log:

    HttpRequest sendRequest failed.
     URL: http://ServerName.com:316/
     Error code: 0x45500D27 - 0x80190194

    Anybody see this yet? I'll keep working away at it myself.

    Getting server publishing data failed.
     URL: http://ServerName.com:316/
     Error code: 0x45500D27 - 0x801901942e?|

    Thanks,

    Rory

    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Monday, August 13, 2012 3:21 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    may check How to troubleshoot publishing server refresh failures in App-V v5  KB2778168 

    /vkleinerde

    Wednesday, November 7, 2012 2:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I too am seeing the exact same symptom when trying to access the Publishing Server from the Client.

    Event Viewer Log:

    Getting server publishing data failed.

    URL: http://DEMO-App-V5/AppVPackages

    Error code: 0x45500D27 - 0x80190194

    I've tried multiple variations of the URL, with and without the port number but nothing changes the outcome.

    I was able to manually pull the package from the publishing server:

    PS C:\Users\MyAlias> Set-AppvClientConfiguration -EnablePackageScripts 1

    Name                                                                      Value                        SetByGroupPolicy
    ----                                                                      -----                        ----------------
    EnablePackageScripts                                                          1                                   False


    PS C:\Users\MyAlias> $pkg=Add-AppVClientPackage "\\demo-app-v5\app-v packages\ProPlusVolume_VisioProVolume_ProjectProV
    olume_en-us_x86.appv"
    PS C:\Users\MyAlias> $pkg


    PackageId            : 639138dd-a4f5-4846-bab2-02e94a87c8a6
    VersionId            : b29da9c2-07d1-4fac-97ca-4f081c487c79
    Name                 : Microsoft Office 15 ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86
    Version              : 0.0.0.0
    Path                 : \\demo-app-v5\app-v packages\ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv
    IsPublishedToUser    : False
    UserPending          : False
    IsPublishedGlobally  : False
    GlobalPending        : False
    InUse                : False
    InUseByCurrentUser   : False
    PackageSize          : 2305305511
    PercentLoaded        : 12
    IsLoading            : False
    HasAssetIntelligence : False

    PS C:\Users\MyAlias> Publish-AppVClientPackage $pkg -Global


    PackageId            : 639138dd-a4f5-4846-bab2-02e94a87c8a6
    VersionId            : b29da9c2-07d1-4fac-97ca-4f081c487c79
    Name                 : Microsoft Office 15 ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86
    Version              : 0.0.0.0
    Path                 : \\demo-app-v5\app-v packages\ProPlusVolume_VisioProVolume_ProjectProVolume_en-us_x86.appv
    IsPublishedToUser    : False
    UserPending          : False
    IsPublishedGlobally  : True
    GlobalPending        : False
    InUse                : False
    InUseByCurrentUser   : False
    PackageSize          : 2305305511
    PercentLoaded        : 13
    IsLoading            : False
    HasAssetIntelligence : False

    David


    Monday, August 13, 2012 8:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you both logged this issue on Connect? This item seems close, but isn't exactly the same as your issue: https://connect.microsoft.com/MDOPTAP/feedback/details/741074/http-500-error-on-publishing-server


    Twitter: @stealthpuppy | Blog: stealthpuppy.com

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

    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.

    Monday, August 13, 2012 8:14 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Don't think that's quite it. Had a look at the 500 error a bit earlier. I did submit it to Microsoft Connect. Thanks

    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Monday, August 13, 2012 11:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you get anywhere with this? I am getting the same error with no avail.

    Tuesday, November 6, 2012 5:07 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    may check How to troubleshoot publishing server refresh failures in App-V v5  KB2778168 

    /vkleinerde

    Wednesday, November 7, 2012 2:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Rorymon,

    I’m also facing same issue, but still I didn’t get any solution. Did you get any solution for this issue?

    Please let me know.

    Thanks

    Ramesh

    Wednesday, November 14, 2012 3:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Er Reddy, are you using the RTM version of APP-V 5?  Did http://support.microsoft.com/kb/2778168 not resolve the issue?

    Steve Bucci Microsoft

    Wednesday, November 14, 2012 10:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Here is the solution i found for the same exact problem i expereinced.

    I was providing wrong port number on the client  on the Publishing server

    When i changed it to point o the right port number everything worked as expected.

    PS : management server port number is different from Publishing Server Port number

    Wednesday, July 31, 2013 2:21 PM