Share via

remotewebaccess.com Anywhere access broken on Server 2016 Again?

ChrisWY27 126 Reputation points
2022-05-04T19:46:51.657+00:00

Last year a similar issue occurred and by manually applying the registry edits from these two threads most seemed to resolve their issues:

https://learn.microsoft.com/en-us/answers/questions/319165/remotewebaccesscom-down-again.html?childToView=836766#answer-836766

https://learn.microsoft.com/en-us/answers/questions/318584/are-the-problems-with-remotewebaccesscom-domain-an.html?page=2&pageSize=10&sort=oldest

The problem is as of yesterday (May 3 2022) I am now experiencing the issue again. Re-applying the registry tweaks does not solve the issue either unfortunately. More so, I am not able to un-register my domain through the wizard or change to a new one, I am seeing the same issue as this user on their fresh install: https://learn.microsoft.com/en-us/answers/questions/814489/cloud-services-integration-amp-anywhere-access-not.html?childToView=836816#answer-836816

Looking at my Dashboard.log in the ProgramData\Microsoft\Windows Server\Logs folder I see the below:

[5840] 220504.122339.7059: DomainConfigWizard: Next Page: progressPage
[6024] 220504.122340.0497: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:CommitDomain failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> Microsoft.Rest.Azure.CloudException: The access token is from the wrong issuer 'https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/'. It must match the tenant 'https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later. at Microsoft.WindowsServerSolutions.DDNS.AzureRmDnsServer.GetARecords(String domainName) in E:\WSE-ServicesAndTools\src\ServicesAndTools\DDNS\DDNS\AzureR...). [6024] 220504.122340.0497: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs [5840] 220504.122340.0653: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:CommitDomain failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. This error has been logged. ---> Microsoft.Rest.Azure.CloudException: The access token is from the wrong issuer 'https://sts.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/'. It must match the tenant 'https://sts.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/33e01921-4d64-4f8c-a055-5bdaffd5e33d' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later.
at Microsoft.WindowsServerSolutions.DDNS.AzureRmDnsServer.GetARecords(String domainName) in E:\WSE-ServicesAndTools\src\ServicesAndTools\DDNS\DDNS\AzureR...).
[5840] 220504.122340.0653: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

This gives some insight to the root cause but I am not sure how to go from here to fix this.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,238 questions
Accepted answer
  1. Samriddhi Chaturvedi 216 Reputation points Microsoft Employee
    2022-05-14T00:32:02.177+00:00

    We were able to get things working on our local test setups.
    Can you please verify your setups and see if the issue went away for you.

    Thanks and Regards
    Samriddhi

    4 people found this answer helpful.

49 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. ChrisWY27 126 Reputation points
    2022-05-05T13:42:33.067+00:00

    I did a fresh install of Server 2016 in a VM to test and even an out of the box non-updated version has the same issue so I don't think this has to do with a recent update, it seems some endpoint the feature depends on has changed.

    1 person found this answer helpful.
  2. ChrisWY27 126 Reputation points
    2022-05-09T18:52:15.413+00:00
    1 person found this answer helpful.
    0 comments
  3. Samriddhi Chaturvedi 216 Reputation points Microsoft Employee
    2022-05-11T22:31:09.393+00:00

    Hi
    We have made some changes and expect the issue to go away.
    Can you please verify at your end/setups ?

    1 person found this answer helpful.
  4. Samriddhi Chaturvedi 216 Reputation points Microsoft Employee
    2022-05-12T23:04:44.693+00:00

    We are working actively on this issue and will keep you all posted.
    Thanks a lot for your patience!

    Thanks, and Regards
    Samriddhi

    1 person found this answer helpful.