Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Unable to setup domain in WHS 2011 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    As above, after going through the setup, it fails and says that the domain name was not setup for your server. Wait a few minutes and run the wizard again.

    I have waited a couple of hours, rebooted my machine but still the same. Previously I was able to set this up without any issues. Is there an outage at homeserver.com?

    Wednesday, July 24, 2013 2:48 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    It appears to have been resolved. Going by the logs, I assume that the servers were rejecting me perhaps I was re-requesting the CA too often.
    • Marked as answer by Jacke JR Thursday, July 25, 2013 12:49 AM
    Thursday, July 25, 2013 12:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Part of the log from SharedServiceHost-DomainManagerServiceConfig.log

    [4588] 130724.174832.9301: DomainManager:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: Starting DnsUpdateTask
[4588] 130724.174832.9301: DomainManager:Service: GetDomainNameConfiguration called
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: updating DnsUpdateTask timer to: TimerSettings: DueTime=-1, Interval=-1
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: Starting QueryDomainStatusTask
[4588] 130724.174832.9301: DomainManager:Service: GetDomainNameConfiguration called
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: updating QueryDomainStatusTask timer to: TimerSettings: DueTime=-1, Interval=-1
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: Starting QueryCertificateStatusTask
[4588] 130724.174832.9301: DomainManager:Service: GetDomainNameConfiguration called
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: updating QueryCertificateStatusTask timer to: TimerSettings: DueTime=-1, Interval=-1
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: Starting CheckCertificateExpirationTask
[4588] 130724.174832.9301: DomainManager:Service: GetDomainNameConfiguration called
[4588] 130724.174832.9301: DomainManager:BackgroundTaskBase: updating CheckCertificateExpirationTask timer to: TimerSettings: DueTime=0, Interval=86400000
[4588] 130724.174832.9301: DomainManager:Service: CommitDomain failed with exception: DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error.  This error has been logged.
   at Microsoft.WindowsServerSolutions.DDNS.LiveDynDnsService.RequestSslCertificate(String pemCertificateRequest) ]
[4588] 130724.174832.9301: DomainManager: Throwing FaultException with detail DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error.  This error has been logged.
   at Microsoft.WindowsServerSolutions.DDNS.LiveDynDnsService.RequestSslCertificate(String pemCertificateRequest) ]
[4588] 130724.174832.9458: ProviderFramework: Information: [0] : ExceptionScreener._ScreenForExceptions: Operation "CommitDomain" threw a FaultException<DomainManagerFault>: (FaultException<DomainManagerFault>) The creator of this fault did not specify a Reason.
[4588] 130724.174832.9458: ProviderFramework: Information: [0] : ProvideFault called for exception: (FaultException<DomainManagerFault>) The creator of this fault did not specify a Reason.
[4588] 130724.174832.9770: ProviderFramework: Information: [0] : PfErrorHandler: IGNORING WCF internal exception: (FaultException<DomainManagerFault>) The creator of this fault did not specify a Reason.
[6648] 130724.174832.9770: DomainManager:CheckCertificateExpirationTask: CheckCertificateExpirationTask action called
[6648] 130724.174832.9770: DomainManager:CheckCertificateExpirationTask: Certificate expiration threshold: 30.00:00:00
[6648] 130724.174832.9770: DomainManagerObjectModel: DomainMaintenanceManager ctor called. InstanceID=21443715
[6648] 130724.174832.9926: DomainManager:DefaultCertificateServiceProvider: IsCertificateNearExpiration called for domain xxx with threshold 30.00:00:00
[6648] 130724.174832.9926: DomainManager:DefaultCertificateServiceProvider: FindCertificateForDomain called for domain xxx
[6648] 130724.174832.9926: DomainManager:DefaultCertificateServiceProvider: Return CN=xxx-CA from CN=xxx-CA : NotAfter 22/6/2052 12:28:30 AM


    Wednesday, July 24, 2013 9:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It appears to have been resolved. Going by the logs, I assume that the servers were rejecting me perhaps I was re-requesting the CA too often.
    • Marked as answer by Jacke JR Thursday, July 25, 2013 12:49 AM
    Thursday, July 25, 2013 12:47 AM