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

49 additional answers

Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2023-09-18T17:40:41.3+00:00

Thanks for bringing this issue in our notice.

We are actively looking into this issue.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
The Office Maven 111 Reputation points

2024-03-16T14:50:18.01+00:00
Can anyone confirm if this is broken once again?

On a brand new/clean Windows Server 2016 Essentials install (with the "SystemDefaultTlsVersions" and "SchUseStrongCrypto" .NET Framework registry settings set to 1) I'm consistently getting an unknown timeout error when attempting to configure a Microsoft personalized domain name within Anywhere Access.

These are the events that are logged in the server's Dashboard.log file:

[4316] 240225.082530.7179: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ]). [4316] 240225.082530.7179: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs [4192] 240225.082530.7179: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ]). [4192] 240225.082530.7179: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

It appears that the Anywhere Access config wizard is able to successfully sign in to the Microsoft Live account, but then times out with a "CommunicationFailure" error when calling the "SubmitCertificateRequest" method. Looks to me like it's an issue occurring over on Microsoft's backend.
Please sign in to rate this answer.
ChrisWY27 126 Reputation points

2024-03-20T18:55:04.17+00:00

I haven't tried to set up a new WSE 16 box but my existing remotewebaccess domains still seem to be working, though I also pay for no-ip to have a backup dynamic dns.

I have this note I made to myself from Sept of 2022 (the last time I installed WSE16) to add these values via PowerShell but not sure if that would fix it for you.

# PowerShell New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

ChrisWY27 126 Reputation points

2024-03-20T19:02:14.1433333+00:00

Also found this post of mine where it looks like I reported a similar inability to register in Nov '22 and Samriddhi Chaturvedi from Microsoft responded resolving it internally:

https://learn.microsoft.com/en-us/answers/questions/1088241/domain-register-and-update-for-remotewebaccess-com?page=2#answers

The Office Maven 111 Reputation points

2024-03-26T15:21:10.97+00:00

@ChrisWY27 Thank you for your responses.

Yes, I've already added all of the required .NET Framework registry keys that you've mentioned (and restarted the server), but that makes no difference here. The registry keys do allow the Microsoft (Live) Account to be successfully signed into, but they do not prevent the timeout error from occurring when the domain name setup wizard attempts to communicate with the Microsoft personalized domain name provider service.

For me, the timeout issue appears any time I try to either set up a remotewebaccess.com domain name for the very first time (on a newly setup 2016 Essentials server), or whenever I attempt to change an existing remotewebaccess.com domain name when one has already been set up previously on the Essentials server (i.e. open Settings, go to the Anywhere Access tab, click the Set up button under the domain name section, in the domain name set up wizard that appears click Next -> choose “Use another domain name or domain name service provider” (do not choose the release option or you may loose your existing domain prefix) -> choose “I want to set up a new domain name” -> click Next -> Next -> sign in to your Live account -> choose “Choose a registered name” and select your existing domain prefix from the drop-down list -> click Next -> timeout error happens every time after about 30 seconds or so).

Thus, it definitely appears to be an issue taking place over on Microsoft's (back)end to me. I'm just wondering if others are able to reproduce the issue. I have lots of customers running Windows Server 2016 Essentials that are reporting the issue to me, but I'm not seeing anyone else reporting it over here on these Microsoft forums (which seems a bit odd). Thanks again for your input.

ChrisWY27 126 Reputation points

2024-03-28T14:23:03.55+00:00

My best guess is either not many are changing domains, or there are few users like us freshly installing WSE '16. Perhaps I can spin up a VM later and try to verify the same is happening on my end, though if multiple customers are reporting it to you it's most likely an issue on the Microsoft end. Perhaps @Samriddhi Chaturvedi can chime in if they still work there.

ChrisWY27 126 Reputation points

2024-03-28T17:59:44.6733333+00:00

@The Office Maven I found a VM with WSE already installed and attempted to set up a domain name unfortunately also seeing the following:

The error in the Dashboard.log was "The request channel timed out while waiting for a reply".

The Office Maven 111 Reputation points

2024-03-29T13:48:40.8933333+00:00

@ChrisWY27 Yes, that's the (generic timeout) error I'm seeing as well... So it's definitely reproducible by others. Hopefully someone from Microsoft sees this thread and can get the issue resolved for everyone. Thanks again.

Olaf Brachvogel 0 Reputation points

2024-04-07T15:53:47.82+00:00

Hello Yes, Essentials also stopped working on my Server 2016Essentials since April 4th, 2024. All Netframework registry settings are present

With (Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full").Version the currently installed version is displayed from .net version 4 onwards. With (Get-ItemProperty "HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5").Version the currently installed version is displayed from .net version 3.5 onwards. # PowerShell New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v2.0.50727" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v2.0.50727" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force v4.5.23026 v4.5.1 -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ------------ New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.1" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.1" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.23026" -Name "SystemDefaultTlsVersions" -Value 1 -PropertyType DWORD -Force New-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.5.23026" -Name "SchUseStrongCrypto" -Value 1 -PropertyType DWORD -Force

TLS 1.0., 1.1, 1.2 on

The DNS information for the server cannot be updated because it cannot connect to the domain name provider. Contact the domain name provider

Domain Name Provider pleas help Thanks
Sign in to comment
Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2024-04-03T22:00:35.6833333+00:00

We are looking into this. Nothing has changed from our end so trying to figure out what's broken.

Note : SBS or WSE is almost near its end of life. So, it would be a good idea to start moving on to the other Microsoft solutions
Please sign in to rate this answer.
The Office Maven 111 Reputation points

2024-04-03T23:46:29.0633333+00:00

@Samriddhi Chaturvedi I really appreciate you guys looking into this one for everyone. AFAIK, Windows Server Essentials 2016 does not reach end of support until January, 2027 and so there's still close to three years of life left in it. I have thousands of customers who are still using Essentials and so it'd sure be nice if the remotewebaccess.com Microsoft personal domain names continued to work for the remainder of that time.

That being said... I do agree that folks should probably begin to move over to using a custom/vanity domain name (as opposed to using a remotewebaccess.com domain name) in order to avoid these types of interruptions. However, folks really do seem to love how easy the Microsoft personal domain names are to use and so they're still very popular amongst the SBS/WSE crowd.

Thanks again for any help that you can offer on this one. ;-)

Arkadiusz Wąsikiewicz 10 Reputation points

2024-04-07T01:17:12.71+00:00

I have same problem 07-Apr-2024 !?

The error in the Dashboard: The domain name was not set up for your server.Wait .....

Evershine ACC 36 Reputation points

2024-04-09T03:42:44.43+00:00

Until 9 Apr 2024, issue still persisted.

Error: Dynamic DNS Cannot be Update (Windows 2012 R2 Essential)
@Samriddhi Chaturvedi, Hi Support can assist on this matter.

Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2024-04-09T16:20:41.7433333+00:00

Are all these issues related to RemoteWebAccess workflows ?

Do the other workflows seem to be ok ?

The Office Maven 111 Reputation points

2024-04-09T20:43:51.9933333+00:00

@Samriddhi Chaturvedi I'm not exactly sure what other "workflows" it is that you are referring to there, but for myself, and my customers, it's all related to the Remote Web Access functionality in Windows Server Essentials (and more specifically to the underlying handling of the GoDaddy-based SSL certs and/or the dynamic DNS functionality of the remotewebaccess.com Microsoft personalized domain names feature). I haven't tested any of the other online services functionality of Windows Server Essentials in quite a while now (such as the Microsoft/Office 365 integration stuff), and so I don't know if any of that is having any issues as well. I'm also not sure about the VPN functionality as I haven't tested that in quite a long time either.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

The Office Maven 111 Reputation points

2024-04-09T20:58:56.0266667+00:00

LOL I'm not sure why my last comment was auto-deleted... It must have had something to do with the portion of the Dashboard.log error log file that it contained. Basically, I was just trying to alert folks that the errors getting logged when setting up a remotewebaccess.com Microsoft personalized domain name seem to have changed over the last week or so (from what I reported previously) and so something must have changed on Microsoft's (back)end recently.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2024-04-09T22:05:57.9366667+00:00

Thanks @The Office Maven .. We will investigate this.

Kevin Bowles 41 Reputation points

2024-04-18T19:32:47.5533333+00:00

our sbs 2016 essentials anywhere access is failing, Dynamic DNS cannot be updated. Cannot repair, configure or release name. Another client's 2012 sbs essentials had same issue begining of the week but appears to be working again

Dan Hansen 11 Reputation points

2024-04-26T15:12:04.6766667+00:00

My Server 2016 has been "Dynamic DNS cannot be updated" for about 3 weeks as well. Existing system been setup for some time, not a new installation. Well, working since the last time remotewebaccess.com went down. Samriddhi, is there any news?

Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2024-04-26T17:42:15.71+00:00

We are still actively investigating. Thank you for your patience.

Susan E Bradley, CPA/CITP/CFF, GSEC 0 Reputation points

2024-05-02T18:19:26.31+00:00

It's not related to TLS is it?

https://www.askwoody.com/forums/topic/essentials-servers-fix-up-to-get-remotewebaccess-renewed/

David and Michelle Kouts 51 Reputation points

2024-05-03T03:11:45.4133333+00:00

Still an issue for me.
Sign in to comment
Giorgio 0 Reputation points

2024-04-29T13:24:07.54+00:00

Still not working its desolating , what a service microsoft gives , shame on microsoft
Please sign in to rate this answer.
Samriddhi Chaturvedi 216 Reputation points Microsoft Employee

2024-05-03T21:31:13.22+00:00

We are still actively investigating this. Thanks for your patience.
Sign in to comment