locked
AppV 5: Publishing server stopped working RRS feed

  • Question

  • My publishing server was working fine yesterday - left for the evening, came in...

    I sequenced a new package, imported, disconnected a connection group / etc...

    When I did a refresh on the client, nothing new happened.  So I checked the webpage for the publishing server:

    <Publishing Protocol="1.0">
      <Packages>
        <Package PackageId="e5f4fac6-d55a-47f1-b4ef-58eff2212435" VersionId="8be87acb-4b8d-4292-8acf-ae2993625d0d" PackageUrl="\\path\to\file.appv" /> 
        <Package PackageId="08ff4333-a707-4fc4-836a-2e27c22e2b97" VersionId="0ec31f5f-66a7-4b00-9c22-937669f35192" PackageUrl="\\path\to\file.appv" />
      </Packages>
      <Groups>
        <Group GroupId="12c52c7b-bfa7-4203-90a2-9e0e61967de9" VersionId="9a32e643-49d8-4efb-90ef-9d6907ffcca3" Priority="0" Name="Test Group">
          <Package PackageId="e5f4fac6-d55a-47f1-b4ef-58eff2212435" /> 
          <Package PackageId="08ff4333-a707-4fc4-836a-2e27c22e2b97" /> 
        </Group>
      </Groups>
    </Publishing>

    That's the information from yesterday, when I left.  It doesn't appear to be updating, even though the management database is (I manually checked the tables in the DB)

    I can't seem to figure out when or why this started happening - the server was not rebooted overnight, nothing extra was installed.

    Infrastructure:

    (THIS IS A TEST ENVIRONMENT, NOT PRODUCTION)

    Single server, acting as Management, Publishing, and Reporting

    DFS for package store, rights are correct / verified

    I have already checked http://support.microsoft.com/kb/2778168, as well as ran 

    ALTER DATABASE [AppVManagement] SET ALLOW_SNAPSHOT_ISOLATION ON
    GO

    Importing the applications, assigning access, etc has no problem on the management webpage.  It just doesn't seem to be making its way to the publishing xml.  Any ideas would be appreciated.




    Friday, April 12, 2013 6:16 PM

Answers

  • Turns out the server team saw an unrecognized server, bounced it to a different OU, GPO took hold and blasted all local user accounts - after all was said and done, SQL Services wouldn't even start due to denied logon.....

    Rebuilding....

    • Marked as answer by Justin Mangum Friday, April 12, 2013 7:10 PM
    Friday, April 12, 2013 7:10 PM

All replies

  • Hello,

    Have you verified the logs for the Publishing Server if there are any issues connecting to the Management Server?


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

    Friday, April 12, 2013 6:19 PM
  • Turns out the server team saw an unrecognized server, bounced it to a different OU, GPO took hold and blasted all local user accounts - after all was said and done, SQL Services wouldn't even start due to denied logon.....

    Rebuilding....

    • Marked as answer by Justin Mangum Friday, April 12, 2013 7:10 PM
    Friday, April 12, 2013 7:10 PM