Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
An error occurred while setting up your domain name RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Just had to reinstall the server because the client backup service broke. I have installed the OS, updated it, and tried to enable remote access through a web browser. Every time I try to set this up, I get the error:

    An error occurred while setting up your domain name.

    The domain name was not set up for your server. Wait a few minutes and run the wizard again.

    An unexpected or unknown problem occurred. Please wait a few minutes, and then try again.

    I have tried, and tried again, and it is not working. What I have done:

    1. configured my router to give my server a static internal IP address

    2. configured my router to let HTTP, HTTPS, and RDP point to my server's static internal IP address

    3. run the wizard from the dashboard

    4. rdp into the server and run the wizard through the dashboard on the server

    5. update/syncronize the time with microsoft's servers

    6. updated my password to not include odd characters 

    Looking at the dashboard log under Server\ProgramData\Microsoft\Windows Server\Logs I see the following:

    [10224] 160822.222427.6854: DomainConfigWizard: Next Page: Live_SignInPage
    [10224] 160822.222441.4296: DomainConfigWizard: Leaving Page: Live_SignInPage
    [10224] 160822.222441.4296: DomainConfigWizard: Wizard Model Value: Wizard Model dictionary[BusinessMode]:False
    Wizard Model dictionary[DomainConfigured]:False
    Wizard Model dictionary[UnsupportedDomainNameOnTheSKU]:False
    Wizard Model dictionary[LiveFlow]:True
    Wizard Model dictionary[OemFlow]:False
    Wizard Model dictionary[GitMeFlow]:False
    Wizard Model dictionary[CreateANewDomain]:True
    Wizard Model dictionary[ConnectedToInternet]:True
    Wizard Model dictionary[OemFlowWithOneProvider]:False
    CurrentOffering:Offering: [Name:Windows Server domain name,Provider:15f4c1c4-44c9-4218-822f-6fe3ca60a262]
    DomainRoots:

    DomainNameSuggestions:

    UserLiveDomainNames:

    RetrievedWholeOfferingList:True

    [10224] 160822.222441.4920: DomainConfigWizard: Next Page: progressPage
    [11740] 160822.222443.0053: 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:ValidateCredentials failed, Detail:AuthIdentityToService ]).
    [11740] 160822.222443.0053: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs
    [10224] 160822.222443.0209: 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:ValidateCredentials failed, Detail:AuthIdentityToService ]).
    [10224] 160822.222443.0209: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure

    Tuesday, August 23, 2016 2:33 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    According to your description, my understanding is that it failed to enable remote access on WHS 2011 with error “An error occurred while setting up your domain name. The domain name was not set up for your server. Wait a few minutes and run the wizard again.”.

    Make sure your ISP does not block port 80(http), or 443(https).

    Try to change it to a complex enough password of your Microsoft Account(Windows Live account), then, try to configure the Wizard again. Also, check to see if related email is sent to your Microsoft Account mail. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 24, 2016 6:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Eve,

    Using http://www.canyouseeme.org/ it looks like my ISP is not blocking ports 80 or 443. I also changed my password to something more complex. I do not have a related email sent to my Microsoft Account mail.

    I reinstalled the operating system, and navigated to the url associated with my homeserver, and the webpage said remote access was not configured.

    So I plugged my server directly into my cable modem, set up remote access, and I still got the same error: 

    An error occurred while setting up your domain name

    BUT navigating to the url associated with my homeserver, I have the ability to enter my login credentials, and login successfully. But still the Dashboard shows my domain name has not been set up.



    • Edited by Gammit10 Wednesday, August 24, 2016 7:21 PM
    Wednesday, August 24, 2016 6:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello? Any more suggestions, Eve?

    Edit: removed snarky comment


    • Edited by Gammit10 Tuesday, August 30, 2016 1:27 PM
    Sunday, August 28, 2016 3:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Open Windows Home Server Console, click Settings – Remote Access – Domain name section, is the link is displayed, click Details bottom and check the details to see if any error mentioned. 

    >Windows 10 start menu button not working.
    Reference KB to have a further identify.

    Troubleshoot problems opening the Start menu or Cortana:
    https://support.microsoft.com/en-us/help/12385/windows-10-troubleshoot-problems-opening-start-menu-cortana

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 30, 2016 6:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Open Windows Home Server Console, click Settings – Remote Access – Domain name section, is the link is displayed, click Details bottom and check the details to see if any error mentioned. 


    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    There is no link displayed. The only link is the "More details" link below the "Router" section, which shows the server's MAC and IP addresses, and Default Gateway.

    Is there any other place I can use to gather error reports other than this and the initial log I mentioned?

    Tuesday, August 30, 2016 10:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Check to see if any related log file in below location:
    C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs

    Detail you may reference “Log File Locations in WHS 2011”:
    http://www.mswhs.com/2012/05/log-file-locations-in-whs-2011/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 1, 2016 9:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Eve,

    I got the following from the NetworkHealthPlugin-DomainManagementFeature.2 log when I tried to connect again. Towards the bottom, I see "DomainNameConfigAnalyzer: Domain name configuration failed, should be manual fixed". Is there a way to manually fix this?

    I also noticed that if I purposefully mistype my Live password, I immediately see a "The user name or password is incorrect. Retype your user name and password." So I know the Dashboard is connecting in some way successfully. But the moment I type in the correct password,  that's when I get the message saying there was an error setting up the domain.

    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : GetChannelFactory ()
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : Address: [net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.DomainProviderManager]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [10468] 160903.180204.1243: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [13992] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [13992] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.Common.SqmProvider.Services.ISqmProviderService
    [10060] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [10060] 160903.180204.1243: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [10468] 160903.180204.1399: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IDomainMaintenanceManager], binding = [CustomBinding], EndpointAddress = [net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager], AllowedConnectionType = [AllowRemoteAccess], EndpointCredentialType = [User]
    [10468] 160903.180204.1399: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : GetChannelFactory ()
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : Address: [net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.DomainProviderManager]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IDomainMaintenanceManager], binding = [CustomBinding], EndpointAddress = [net.tcp://valar:6602/Microsoft.WindowsServerSolutions.DomainProviderManager/Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager], AllowedConnectionType = [AllowRemoteAccess], EndpointCredentialType = [User]
    [15828] 160903.180204.1399: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [10060] 160903.180204.1555: DomainManagerObjectModel: Starting KeepAlive timer for instanceID=3
    [4512] 160903.180204.1555: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [4512] 160903.180204.1555: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [4512] 160903.180204.1555: DomainManagerObjectModel: Starting KeepAlive timer for instanceID=6
    [12400] 160903.180204.1555: ConnectivityCenter: DomainNameResolveableInfo.ExternalIP: 127.0.0.1
    [16584] 160903.180204.1711: ConnectivityCenter: DomainNameProviderCredentials.CredentialsStatus: True
    [9508] 160903.180204.1711: ConnectivityCenter: Job finish. Result: Success
    [9508] 160903.180204.1711: ConnectivityCenter: Job DomainNameProviderCredentialsDiagnosticsJob complete, 100% done.
    [15828] 160903.180204.1711: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [15828] 160903.180204.1711: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager
    [15828] 160903.180204.1711: DomainManagerObjectModel: Starting KeepAlive timer for instanceID=7
    [3728] 160903.180204.1711: ConnectivityCenter: Job finish. Result: Success
    [3728] 160903.180204.1711: ConnectivityCenter: Job DomainNameResolveableDiagnosticsJob complete, 100% done.
    [15684] 160903.180204.1711: ConnectivityCenter: DDNSUpdateAttemptionInfo.DDNSUpdateStatus: True
    [14396] 160903.180204.1711: ConnectivityCenter: Job finish. Result: Success
    [14396] 160903.180204.1711: ConnectivityCenter: Job DDNSUpdateDiagnosticsJob complete, 100% done.
    [9748] 160903.180204.2023: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DDNSUpdateAnalyzer analyze completed. 0 suggestions found.
    [9748] 160903.180204.2023: ConnectivityCenter: Current SQM Data is 1044479.
    [14396] 160903.180204.2023: ConnectivityCenter: Diagnositcs completed. Status: Success
    [14396] 160903.180204.2023: ConnectivityCenter: Overall status: Good
    [14396] 160903.180204.2023: ConnectivityCenter: Properties updated.
    [7420] 160903.180204.2647: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameProviderCredentialsAnalyzer analyze completed. 0 suggestions found.
    [7420] 160903.180204.2647: ConnectivityCenter: Current SQM Data is 1044479.
    [13992] 160903.180204.2647: ConnectivityCenter: Diagnositcs completed. Status: Success
    [13992] 160903.180204.2647: ConnectivityCenter: Overall status: Good
    [13992] 160903.180204.2647: ConnectivityCenter: Properties updated.
    [17276] 160903.180204.2647: ConnectivityCenter: DomainNameConfigAnalyzer: Domain name configuration failed, should be manual fixed
    [17276] 160903.180204.2647: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameConfigAnalyzer analyze completed. 1 suggestions found.
    [17276] 160903.180204.2803: ConnectivityCenter: Microsoft.WindowsServerSolutions.Connectivity.Analyzers.DomainNameResolveableAnalyzer analyze completed. 0 suggestions found.
    [17276] 160903.180204.2803: ConnectivityCenter: Current SQM Data is 1044479.
    [17276] 160903.180204.2803: ConnectivityCenter: Diagnositcs completed. Status: Success
    [17276] 160903.180204.2803: ConnectivityCenter: Suggestion: To set up the domain name, on the server Dashboard, click Server settings, click Remote Web Access, and then click Set up in the Domain name section.
    [17276] 160903.180204.2803: ConnectivityCenter: Overall status: Error
    [17276] 160903.180204.2803: ConnectivityCenter: Properties updated.


    • Edited by Gammit10 Saturday, September 3, 2016 10:50 PM more information
    Saturday, September 3, 2016 10:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I am trying to involve someone familiar with this topic to further look at this issue. 

    There might be some time delay. And appreciate your patience.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 6, 2016 9:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I am trying to involve someone familiar with this topic to further look at this issue. 

    There might be some time delay. And appreciate your patience.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Hi Eve. That's fine. Thank you for notifying me about the potential delay.
    Wednesday, September 7, 2016 2:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    You have noticed that “5. update/syncronize the time with microsoft's servers”, I would recommend you to manually setup the time source, such as the official NTP time server “Pool.ntp.org”, and do the sync time again.

    Reference below steps to have a time synchronization:
    1. Launch an Administrative command prompt.
    2. Type the following commands one at a time and hit Enter after each command:

        w32tm /config /manualpeerlist: <IP address or FQDN of the time source> /syncfromflags:MANUAL

        w32tm /config /update

    3. To immediately synchronize time with an external source, type the following command and hit Enter:

        w32tm /resync

    After completing above steps, try to configure the remote access again and check the result. 

    Best Regards,
    Eve Wang

    Please remember to <b>mark the replies as answers</b> if they help and <b> unmark</b> them if they provide no help.<br/> If you have feedback for TechNet Subscriber Support, contact <a href="mailto:tnmff@microsoft.com"> tnmff@microsoft.com</a>.

    Thursday, September 8, 2016 8:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Eve,

    I manually synced the time, as requested, via a Remote Desktop Connection. I then launched the Dashboard and tried to configure the remote access and got the same error.

    Thursday, September 8, 2016 10:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Please collect all related log files on WHS2011 server. File location is:

    C:\PorgramData\Microsoft\Windows Server\Logs

    Copy the Logs folder to desktop and then compress the folder into a Zip file. 

    If you are unable to upload file via reply on this forum, please upload the file to OneDrive(https://onedrive.live.com/), share it and provide me the access link.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 9, 2016 7:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Please collect all related log files on WHS2011 server. File location is:

    C:\PorgramData\Microsoft\Windows Server\Logs

    Copy the Logs folder to desktop and then compress the folder into a Zip file. 

    If you are unable to upload file via reply on this forum, please upload the file to OneDrive(https://onedrive.live.com/), share it and provide me the access link.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Here are the logs: https://1drv.ms/u/s!Aq2fO2uDw9d-g9Quhxuva2VJWzAwdA
    Friday, September 9, 2016 11:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Find service is using port 80, turn it off, then it'll work find


    Saturday, September 10, 2016 1:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Find service is using port 80, turn it off, then it'll work find


    Are you saying there is a service on the server using port 80, and that is causing the problem?
    Saturday, September 10, 2016 4:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    There is a lot error message like below are recorded in SharedServiceConfig.log:

    ===================================
    [15160] 160909.123148.3199: ProviderFramework: Information: [0] : PfErrorHandler: IGNORING WCF internal exception: (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (IOException) The read operation failed, see inner exception. ==> (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (SocketException) An existing connection was forcibly closed by the remote host
    =================================

    Check to see if the hotfix mentioned in KB 2600907 will be helpful. 

    FIX: A .NET Framework 3.0-based WCF service may crash with a System.ServiceModel.CommunicationException exception if the service uses the netTcpBinding binding:
    https://support.microsoft.com/en-us/kb/2600907

    This problem is very odd, and complex, we have searched and studied on this problem, if above method is still not working, I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

    You may find phone number for your region accordingly from the link below: 
    Global Customer Service phone numbers 
    https://support.microsoft.com/en-in/help/13948/global-customer-service-phone-numbers

    I truly understand how inconvenient you feel about the issue , thank you for the efforts you've done so far and your continuing patience. 

    Also, thank you for your understanding.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 13, 2016 2:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    There is a lot error message like below are recorded in SharedServiceConfig.log:

    ===================================
    [15160] 160909.123148.3199: ProviderFramework: Information: [0] : PfErrorHandler: IGNORING WCF internal exception: (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (IOException) The read operation failed, see inner exception. ==> (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (SocketException) An existing connection was forcibly closed by the remote host
    =================================

    Check to see if the hotfix mentioned in KB 2600907 will be helpful. 

    FIX: A .NET Framework 3.0-based WCF service may crash with a System.ServiceModel.CommunicationException exception if the service uses the netTcpBinding binding:
    https://support.microsoft.com/en-us/kb/2600907

    This problem is very odd, and complex, we have searched and studied on this problem, if above method is still not working, I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

    You may find phone number for your region accordingly from the link below: 
    Global Customer Service phone numbers 
    https://support.microsoft.com/en-in/help/13948/global-customer-service-phone-numbers

    I truly understand how inconvenient you feel about the issue , thank you for the efforts you've done so far and your continuing patience. 

    Also, thank you for your understanding.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    That hotfix did not work. I hope the customer service doesn't charge.
    Thursday, September 15, 2016 1:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, I reinstalled the server OS from scratch again, and tried to set up the Domain. Same error. This time, I saw the following in the log file named ConfigSvcVerbose

    Notifications:  Information:  [0] LNX01: Neightbor RNx04 says it is no longer interested in the following categories: "Initial Configuration website".

    Notifications:  Information:  [0] LNx01: Removing one instance of each of the following categories from all neighbors filters except RNx04: "Initial Configuration Website".

    Notifications:  Information:  [0]  LNx01: _RemoveCategoriesFromNeighbor: categories we've previously requested from FNx03:  IDENTITY.USER (1); Setup (1); Initial Configuration Website (1)

    Notifications:  Information:  [0]  LNx01: Will tell neighbor FNx03 that we are no longer interested in the following categories:  "Initial Configuration website".  (breadcrumb LNx01_RemoveCategoriesFromNeighbor_0x9)

    Is this relevant?

    Saturday, September 17, 2016 12:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I installed the trial of Windows Server 2012 Server Essentials on the same computer, and Remote Access configured correctly the first time.

    With that, I think there is something wrong either with Home Server 2011 setting up the Remote Access, or the servers rejecting the Remote Access first-time configuration.

    Monday, September 19, 2016 11:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    is there solution to this problem? My Home Server's boot drive died and I was forced to reinstall it and now I can't set up domain name for my server. Everything else is up and configured with only two warnings:

    1. Domain name is not set up (same failure as in this thread).
    2. Windows Update failed to install two updates:

    ===========================================

    Security Intelligence Update for Windows Defender Antivirus - KB915597 (Version 1.317.1178.0)

    Installation date: ‎6/‎13/‎2020 12:02 AM

    Installation status: Failed

    Error details: Code 8050800C

    Update type: Important

    Install this update to revise the files that are used to detect viruses, spyware, and other potentially unwanted software. Once you have installed this item, it cannot be removed.

    More information: 
    https://go.microsoft.com/fwlink/?linkid=2007160

    Help and Support: 
    https://go.microsoft.com/fwlink/?LinkId=52661
    =========================================
    2020-01 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 (KB4535102)

    Installation date: ‎6/‎13/‎2020 12:02 AM

    Installation status: Failed

    Error details: Code 80092004

    Update type: Important

    A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

    More information: 
    http://support.microsoft.com/kb/4535102

    Help and Support: 
    http://support.microsoft.com

    Saturday, June 13, 2020 7:07 AM