remotewebaccess.com Anywhere access broken on Server 2016 Again?

ChrisWY27 126

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.

Michael Toth 1 Reputation point

2022-05-08T02:56:42.28+00:00

Same here. The kicker is I'm a military member and it's going to be at least 6 weeks before I can physically get in front of the machine.

Hope nothing requires attention between now and then....
Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2022-05-11T22:32:01.573+00:00

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

2022-05-12T02:08:41.38+00:00

Still seeing the same issue. Made sure all updates were applies and rebooted. I attached my dashboard.log with the sensitive data covered in x's. I had to convert it to a pdf as the forum wasn't allowing me to upload it as a .log or .txt file. The server is still trying to update remotewebaccess using my old ip address not my current public ip.201203-dashboard.pdf
Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2022-05-14T00:32:36.617+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
ChrisWY27 126 Reputation points

2022-05-14T02:05:30.043+00:00

Mine just came back online on its own. Thank you for taking care of this!!!

@Samriddhi Chaturvedi I want to ask though. How likely is this issue to return? Will we be good until the 2027 EOL date?
Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2022-05-15T17:05:49.6+00:00

No issue is not likely to come back !

Regards
Samriddhi
ChrisWY27 126 Reputation points

2022-05-16T23:50:34.547+00:00

Thank you @Samriddhi Chaturvedi for your hard work on this. I wish I had your ear several years ago when I reported that the mac client connector was (and still is) broken due to a dependency on Objective-C Garbage collection that Sierra+ doesn't allow but at this point I doubt that will ever be fixed.
ChrisWY27 126 Reputation points

2022-11-14T15:41:18.447+00:00

Seeing related issues again now :( . Made a new thread

https://learn.microsoft.com/en-us/answers/questions/1088241/domain-register-and-update-for-remotewebaccesscom.html

Accepted answer

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
Please sign in to rate this answer.

4 people found this answer helpful.
David and Michelle Kouts 51 Reputation points

2024-05-03T03:07:07.81+00:00

@Samriddhi Chaturvedi , this is happening again. Are you still able to assist?
Sign in to comment

48 additional answers

Rob 61 Reputation points

2022-05-05T09:13:40.907+00:00

I am seeing the same issue after a router reboot changed the external IP address. I am not seeing the same error in my Dashboard.log but I am seeing something odd, the old external IP address is shown

[7788] 220505.095922.2483: ConnectivityCenter: DomainNameProviderCredentials.CredentialsStatus: True
[3512] 220505.095922.2483: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.2483: ConnectivityCenter: Job DomainNameProviderCredentialsDiagnosticsJob complete, 64% done.
[6420] 220505.095922.4824: ConnectivityCenter: DomainServiceReachableInfo.ReachableStatus: True
[11200] 220505.095922.4824: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4824: ConnectivityCenter: Job DomainServiceReachableDiagnosticsJob complete, 71% done.
[4720] 220505.095922.4980: ConnectivityCenter: DomainNameResolveableInfo.ExternalIP: 86.170.204.53
[9816] 220505.095922.4980: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4980: ConnectivityCenter: Job DomainNameResolveableDiagnosticsJob complete, 78% done.
[10260] 220505.095922.4980: ConnectivityCenter: DDNSUpdateAttemptionInfo.DDNSUpdateStatus: False
[7456] 220505.095922.4980: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.4980: ConnectivityCenter: Job DDNSUpdateDiagnosticsJob complete, 85% done.
[10016] 220505.095922.4980: ConnectivityCenter: Global event triggered for port: 80.
[8224] 220505.095922.6543: ConnectivityCenter: Service Call Finished on Port: 443
[8224] 220505.095922.6543: ConnectivityCenter: Global event triggered for port: 443.
[10016] 220505.095922.6543: ConnectivityCenter: ConnectivityInfo.HttpsInbound: True
[10016] 220505.095922.6543: ConnectivityCenter: ConnectivityInfo.Inbound: True
[216] 220505.095922.6543: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095922.6543: ConnectivityCenter: Job InboundConnectivityDiagnosticsJob complete, 92% done.
[7052] 220505.095928.8261: DomainManagerObjectModel: Calling KeepAlive for instanceID=2
[7052] 220505.095928.8261: DomainManagerObjectModel: KeepAlive succeeded for instanceID=2
[7280] 220505.095938.1855: ConnectivityCenter: NdfDiagnoseIncident returns 0x0,
[7280] 220505.095938.1855: ConnectivityCenter: 0 root causes identfied
[7280] 220505.095938.1855: ConnectivityCenter: DoubleNatInfo.DoubleNat: False
[4540] 220505.095938.1855: ConnectivityCenter: Job finish. Result: Success
[10524] 220505.095938.1855: ConnectivityCenter: Job DoubleNatDiagnosticsJob complete, 100% done.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.FirewallConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.InboundConnectivityAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DoubleNatConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: RemoteAccessAnalyzer: VPN server deployment result: InstallationSucceeded
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.RemoteAccessAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameConfigAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameExpireAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameNearlyExpireAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2168: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameProviderCredentialsAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2324: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameResolveableAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2324: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainServiceReachableAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: DDNSUpdateAnalyzer: DDNS update failed, should be manual fixed
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DDNSUpdateAnalyzer analyze completed. 1 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.CertificateAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.IisConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.TsGatewayConfigurationAnalyzer analyze completed. 0 suggestions found.
[6164] 220505.095938.2793: ConnectivityCenter: Current SQM Data is 2064383.
[10524] 220505.095938.2793: ConnectivityCenter: Diagnositcs completed. Status: Success
[10524] 220505.095938.2949: ConnectivityCenter: Suggestion: An error occurred while updating the dynamic DNS information for your server with the information that you gave your domain name service provider. Please try again later. If this problem continues, contact your domain name service provider for support.
[10524] 220505.095938.2949: ConnectivityCenter: Overall status: Error
[10524] 220505.095938.2949: ConnectivityCenter: Properties updated.

I have updated .Net to 4.8 just in case there is something odd there but I can't test that until I restart the server which will be later this evening
Please sign in to rate this answer.

2 people found this answer helpful.
ChrisWY27 126 Reputation points

2022-05-05T11:47:15.1+00:00

The dashboard log might only happen if you try to repair or alter the anywhere access domain name through the wizard.

Where did you find the other log? I'll check mine.

Josh K 16 Reputation points

2022-05-05T20:55:53.803+00:00

Same issue here. Service when down after a router reboot and public IP address change.
If I ping my old domain (domain).remotewebaccess.com it returns the OLD public address I had before.

Very strange.

Rob 61 Reputation points

2022-05-06T08:35:30.44+00:00

So the .Net update didn't have any effect, I suspected it wouldn't but it was worth a shot.

Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2022-05-14T00:33:05.22+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
Sign in to comment
Danny Andonoff 21 Reputation points

2022-05-05T12:52:26.023+00:00

Rebooting the server doesn't fix it.
I have 2 sites with this problem.
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment
Thomas Angermund 36 Reputation points

2022-05-05T14:09:29.66+00:00

Same here in Germany. But 2 servers are ok (2012R2 Essentials) and another has the problems described. All Updates installed on all servers
Please sign in to rate this answer.

2 people found this answer helpful.
ChrisWY27 126 Reputation points

2022-05-05T15:44:48.337+00:00

Perhaps you can nudge this guy to come up with a new fix like they did last year haha

https://sbsland.me/category/computers-and-internet/troubleshooting/

Thomas Angermund 36 Reputation points

2022-05-05T16:06:05.04+00:00

i sent him a massage.

Kevin Bowles 36 Reputation points

2022-05-06T21:15:07.737+00:00

same here in Bermuda, started this morning when one of my isp's went down. I have tried everything

Kevin Bowles 36 Reputation points

2022-05-07T16:13:28.407+00:00

Any update on this? I cant repair or release the domain. This is going to be a nightmare for me.

Thomas Angermund 36 Reputation points

2022-05-07T16:52:41.8+00:00

what i did: I switch to dyndns and a free certifcate. This helps for a moment.

ChrisWY27 126 Reputation points

2022-05-08T01:46:33.56+00:00

Isn't it great when you spend lots of money on an enterprise level product to provision for a customer buying in that the product will at least function until the end of life date only for the company to leave you hanging in the wind half way though it's total shelf life?

Josh K 16 Reputation points

2022-05-08T03:44:37.877+00:00

This is what I ended up doing as well. Hopefully it can be fixed, and I can switch back.

ChrisWY27 126 Reputation points

2022-05-08T12:02:56.237+00:00

This changes the domain name url correct?

Thomas Angermund 36 Reputation points

2022-05-08T13:18:33.88+00:00

Yes it will

Josh K 16 Reputation points

2022-05-08T19:03:08.737+00:00

Like Thomas said, Yes. I would have replied earlier, but the reply button was not available on my phone.
Sign in to comment
Gergely Szabo 26 Reputation points

2022-05-08T19:57:51.463+00:00

Same here in Budapest, Hungary. The regedit workaround did not help, still old IP is shown.
I added the dinamic IP to the host file of the endpoint client and that helped but this is not a solution, as every time IP changes, I need to edit host file on the endpoints.
Let me know if there is a solution.
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment