Windows Server Essentials Email Service Won't Start SharedServiceHost.exe Unhandled exception from operation

Gday Everyone,
Two weeks ago we installed a new Server 2012 R2 with the Essentials Experience role. It was fully patched at time of deployment. We enabled O365 integration and password sync was working fine last week. This morning I went to the Dash Board to add a new
user and after clicking the O365 tab all fields show "Not available".
The system event log shows
"The Windows Server Essentials Email Service service terminated unexpectedly.  It has done this 3 time(s)."
The application event log shows the following.
System.InvalidOperationException: Nullable object must have a value.
   at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<GetSubscriptions>b__37(Subscription sub)
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<>c__DisplayClass32.<GetCompanyInfo>b__30(AccountSkuDetails s)
   at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.GetCompanyInfo()
   at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.QueryO365Information()
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
   at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.InvokeOperationWrapperAsyncWithLocalAdminPrivilege[TResult](String operationName, Func`1 func)
   at SyncInvokeQueryO365Information(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener._ScreenForExceptions(GeneralInvoker invokeMe, Object instance, Object[] inputs, Object[]& outputs)
Stack:
   at System.Environment.FailFast(System.String, System.Exception)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener._ScreenForExceptions(GeneralInvoker, System.Object, System.Object[], System.Object[] ByRef)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener.Invoke(System.Object, System.Object[], System.Object[] ByRef)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(System.ServiceModel.Dispatcher.MessageRpc ByRef)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(System.ServiceModel.Dispatcher.MessageRpc ByRef)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(System.ServiceModel.Dispatcher.MessageRpc ByRef)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean)
   at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(System.ServiceModel.Channels.RequestContext, Boolean, System.ServiceModel.OperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(System.ServiceModel.Channels.RequestContext, System.ServiceModel.OperationContext)
   at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(System.IAsyncResult)
   at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.AsyncResult`1[[Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.InputChannelRequeuer`1+TryReceiveResult[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089]], Sku, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]].Complete(Boolean, System.Func`1<TryReceiveResult<System.__Canon>>)
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.CoalescingAsyncResult`1[[Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.InputChannelRequeuer`1+TryReceiveResult[[System.__Canon, mscorlib, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089]], Sku, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]._MyCallback(System.IAsyncResult)
   at System.Runtime.AsyncResult.Complete(Boolean)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel+TryReceiveAsyncResult.OnReceive(System.IAsyncResult)
   at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
   at System.Runtime.AsyncResult.Complete(Boolean)
   at System.ServiceModel.Channels.SynchronizedMessageSource+ReceiveAsyncResult.OnReceiveComplete(System.Object)
   at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(System.Object)
   at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32, Byte[], Int32, Int32, System.Net.AsyncProtocolRequest)
   at System.Net.Security.NegotiateStream.ReadCallback(System.Net.AsyncProtocolRequest)
   at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32)
   at System.Net.FixedSizeReader.ReadCallback(System.IAsyncResult)
   at System.Runtime.AsyncResult.Complete(Boolean)
   at System.ServiceModel.Channels.ConnectionStream+IOAsyncResult.OnAsyncIOComplete(System.Object)
   at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(System.Object, System.Net.Sockets.SocketAsyncEventArgs)
   at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(System.Net.Sockets.SocketError, Int32, System.Net.Sockets.SocketFlags)
   at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
The only thing we did a few days ago was enable the Azure Backup integration. I am not sure if this broke the O365 integration as I didn't go back to the O365 tab in the dashboard after installing the Azure backup.
I have spent a considerable amount of time on google, however, majority of the posts talk about Update 1 which disables the password sync service. I have checked and all services are started with exception of Windows Server Essentials Email Service (WseEmailSvc).
The Azure Backup module is working fine and the registry location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity seems to hold the correct configuration information throughout the various keys.
I am at a loss as to how to proceed with this issue? I have checked but there are no pending updates and I have attempted a server reboot numerous times.
Would appreciate external input if you have seen this issue before or know where we can look to further establish what is going on.
Cheers,
Chiper

I have a similar if not identical situation - I'm currently migrating from WS2012 Essentials to WS2012 R2 Standard w/Essentials role installed. The 'wseemailsvc' service continues to fail over and over, and I am unable to manage O365 accounts from within
the Essentials dashboard on the R2 server. 
System Event Log:
Error 7031 - The Windows Server Essentials Email Service service terminated unexpectedly ... [repeats twice]
Error 7034 - The Windows Server Essentials Email Service service terminated unexpectedly. It has done this 3 time(s)
Application Event Log:
Source:        .NET Runtime
Date:          2015-04-20 08:27:28
Event ID:      1026
Task Category: None
Level:         Error
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-20T14:27:28.000000000Z" />
<EventRecordID>21137</EventRecordID>
<Channel>Application</Channel>
<Computer>redacted</Computer>
<Security />
</System>
<EventData>
<Data>Application: SharedServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.UnauthorizedAccessException
Stack:
at System.DirectoryServices.Interop.UnsafeNativeMethods+IAds.SetInfo()
at System.DirectoryServices.DirectoryEntry.CommitChanges()
at Microsoft.WindowsServerSolutions.MailService.ActiveDirectoryHelper+&lt;&gt;c__DisplayClass3.&lt;SetLocalUserPrincipleName&gt;b__1()
at Microsoft.WindowsServerSolutions.MailService.ActiveDirectoryHelper.InvokeOperationImpersonateWrapper(System.Action)
at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.CleanUpMappingData(Microsoft.WindowsServerSolutions.O365Integration.O365User[])
at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.Run()
at Microsoft.WindowsServerSolutions.O365Integration.BackgroundTask.TimerCallback(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
</Data>
</EventData>
</Event>
This error is followed immediately by:
Source:        Application Error
Date:          2015-04-20 08:27:28
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-20T14:27:28.000000000Z" />
<EventRecordID>21138</EventRecordID>
<Channel>Application</Channel>
<Computer>redacted</Computer>
<Security />
</System>
<EventData>
<Data>SharedServiceHost.exe</Data>
<Data>6.3.9600.16384</Data>
<Data>5215ca62</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.3.9600.17415</Data>
<Data>54505737</Data>
<Data>e0434352</Data>
<Data>0000000000008b9c</Data>
<Data>20e4</Data>
<Data>01d07b761ad593b2</Data>
<Data>C:\Windows\System32\Essentials\SharedServiceHost.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>5f028783-e769-11e4-80c4-00155d10040b</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Any assistance with this would be greatly appreciated!
mcbundus

Similar Messages

  • Windows Server Essentials Storage Service and Windows Server Essentials Email Service eating memory

    Hi
    I have Windows Server 2012 R2 with Essentials Role installed. I have integrated server with Azure AD, Office 365 and Intune using the Essentials Dashboard integration tools.
    I can see that Windows Server Essentials Storage Service and Windows Server Essentials Email Service are eating much of server memory. What are these services for and why they use a lot of memory? Specially I am wondering about the Email Service. What is
    it for? Server dont handle email in any way so what is this service for? I tried to google it but found nothing.

    Hi
    I have 6GB of memory.
    When I check from Resource Monitor, for Essentials Storage Service, Commit Set is 4G and Working Set is 1,8G.
    Email Service Commit is about 1,8G and Working Set is just below 1G.
    So these two services are reserving almost all the memory.
    Memory is about 85-90% in use all the time, whether it be night or day.
    Server have about 12 users and at the office there is about 2-6 person at the time. Link between server and office is 100M. There are no other services installed but the basic ones. We use server for AD (O365 integration) and file shares. Traffic in File
    Shares are not big. They are more kind of an warehouse that in busy day-to-day use.
    This server is about couple of months old and it has been like this since it was fired up.
    I dont know what to look for from Event Logs and Process Monitor dont give me anything useful.

  • Microsoft Forefront Server Protection Eventing Service won't start?

    Hi Guys,
    When Forefront Protection for Exchange was integrated/enabled on our SBS 2008 server, Microsoft Forefront Server Protection Eventing Service won’t start. Even when we try to start it manually we are getting this message (see attached). During this attempt,
    we got these events in the event viewer. In this case, in order to have our email working, we have to temporarily disable Forefront. Any suggestion how to fix this? Please advise.
    Event 465
    Source: ESENT
    FSCEventing (9324) Corruption was detected during soft recovery in logfile C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server\Data\Incidents\inc.log. The failing checksum record is located at position END. Data not matching the log-file
    fill pattern first appeared in sector 450 (0x000001C2). This logfile has been damaged and is unusable.
    Event 301
    Source: ESENT
    FSCEventing (9324) The database engine has begun replaying logfile C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server\Data\Incidents\inc.log.
    Event 454
    Source: ESENT
    FSCEventing (9324) Database recovery/restore failed with unexpected error - 501.
    Event 1076
    Source: FSCEventing
    The Forefront Protection Eventing Service has stopped.
    Thank you very much!
    Arnel

    Hi Arnel,
    Based on error messages, it indicates a log file (inc.log) has become corrupted. Please restore the log file
    from a backup copy, and then check if this issue can be solved. For more details, please refer to the following article.
    Event Id 465
    Hope this helps.
    Best regards,
    Justin Gu

  • Lync Server Audio Test Service won't start

    Hi,
    I am unable to start the audio test service on my Lync 2013 server.
    Running the command Get-CsAudioTestServiceApplication returns a warning: "RegistrarPool" with the identity "1351738413" assigned to "sip:RtcApplication-bunch of numbers and letters@domain" has been removed from the configuration
    store.
    So I'm guessing the fact is it is looking at the incorrect Registrar Pool but I am unsure on how to change that.
    I'm not sure if this is related but the Lync Server Event log is full of this error
    Log Name:      Lync Server
    Source:        LS Call Park Service
    Date:          13/09/2013 8:47:28 AM
    Event ID:      31035
    Task Category: (2002)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      PLYNC01.gwmwater.org.au
    Description:
    Time-out getting primary application end point.
    Error: No provisioning data received for the primary application contact within the time frame specified.
    Cause: The server could not get primary application.
    Resolution:
    Check if Call Park Service contact object exists in Central Management Store (CMS) and in Active Directory.
    Event Xml:
    < Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Call Park Service" />
        <EventID Qualifiers="51154">31035</EventID>
        <Level>2</Level>
        <Task>2002</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-09-12T22:47:28.000000000Z" />
        <EventRecordID>1617</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>PLYNC01.gwmwater.org.au</Computer>
        <Security />
      </System>
      <EventData>
        <Data>No provisioning data received for the primary application contact within the time frame specified.</Data>
      </EventData>
    < /Event>
    Any help would be great.
    Thanks
    Todd

    The solution is in Portuguese but easy to understand: 
    http://www.wellingtonagapto.org/2014/08/audio-test-service-nao-inicia-no-lync-server-2013-event-id-32003.html 
    Wellington Agápto
    Consultor de Comunicações Unificadas & Mobilidade
    ITIL, CCNA, MCP, MTA, MCITP, MCTS, MCSA, MCSE Communication
    Edefense Segurança Digital
    Site: http://www.edefense.com.br
    Blog: http://www.wellingtonagapto.org

  • CF 7.02 won't install ond Windows Server Enterprise 2003, Service Pack 1, IIS 6.0

    CF 7.02 won't install on Windows Server Enterprise 2003,
    Service Pack 1, IIS 6.0. When I run the Administrator the message
    indicates that MX has been installed but when I open the page with
    the web browser the message is Service Unavailable.

    I get the message when I open try to load ColdFusion
    Administrator page or the index page on the cold fusion web site
    that I am installing.

  • Password service won't start

    Following an unplanned hard restart of our server (Mac OS X 10.9.5, Server 3.2.2), the password service won't start, so our staff can't log into mail, calendars or file sharing.
    When I launch Open Directory, the main window has the message "Unable to load replica list", then it switches itself off after a minute or so.
    I've looked at the certificates in Server and they have the green tick so presumably are OK.
    DNS is working OK and running the command "sudo changeip -checkhostname" reports success.
    Here's the section of log that repeats every few seconds as PasswordService repeatedly starts up and exits:
    13/03/2015 20:55:00.617 com.apple.launchd[1]: (com.apple.PasswordService[5890]) Exited with code: 1
    13/03/2015 20:55:00.617 com.apple.launchd[1]: (com.apple.PasswordService) Throttling respawn: Will start in 10 seconds
    13/03/2015 20:55:02.540 xscertd[249]: Failed sending LookupCRLByCARecordName command to com.apple.xscertd.helper: The operation couldn’t be completed. (com.apple.certificateserver error 42005.)
    13/03/2015 20:55:08.708 com.apple.launchd[1]: (org.openldap.slapd[5894]) Exited with code: 1
    13/03/2015 20:55:08.708 com.apple.launchd[1]: (org.openldap.slapd) Throttling respawn: Will start in 7 seconds
    13/03/2015 20:55:10.206 xscertd-helper[5897]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
    13/03/2015 20:55:10.207 com.apple.launchd[1]: (com.apple.xscertd-helper[5897]) Exited with code: 1
    13/03/2015 20:55:10.207 com.apple.launchd[1]: (com.apple.xscertd-helper) Throttling respawn: Will start in 10 seconds
    13/03/2015 20:55:10.639 PasswordService[5901]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server
    13/03/2015 20:55:10.639 PasswordService[5901]: -[PasswordServerPrefsObject loadXMLData]: Unable to locate passwordserver config record's plist attribute: -1 Can't contact LDAP server
    13/03/2015 20:55:10.640 PasswordService[5901]: -[PasswordServerPrefsObject getSearchBase]: Unable to locate search base: -1 Can't contact LDAP server
    13/03/2015 20:55:10.640 PasswordService[5901]: -[PasswordServerPrefsObject saveXMLData]: ldap_modify_ext_s of the passwordserver config record's plist attribute: -1 Can't contact LDAP server
    13/03/2015 20:55:10.684 PasswordService[5901]: int pwsf_GetPublicKey(char *): ldap_search_ext_s cn=authdata for Public Key returned -1
    13/03/2015 20:55:10.687 com.apple.launchd[1]: (com.apple.PasswordService[5901]) Exited with code: 1
    I have backups (both Time Machine and clones of the hard drive) that I could use to restore the corrupted bit of the configuration, if necessary, but I don't know what to restore.

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
    1. The OD master must have a static IP address on the local network, not a dynamic address. It must not be connected to the same network with more than one interface; e.g., Ethernet and Wi-Fi.
    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
    3. The primary DNS server used by the server must be itself, unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
    4. If you have accounts with network home directories, make sure the URL's are correct in the user settings. A return status of 45 from the authorizationhost daemon in the log may mean that the URL for mounting the home directory was not updated after a change in the hostname.
    5. Only if you're still running Mavericks server, follow these instructions to rebuild the Kerberos configuration on the server.
    6. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases. Otherwise delete all certificates and create new ones.
    7. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
    8. Reboot the master and the clients.
    9. Don't log in to the server with a network user's account.
    10. Disable any internal firewalls in use, including third-party "security" software.
    11. If you've created any replica servers, delete them.
    12. If OD has only recently stopped working when it was working before, you may be able to restore it from the automatic backup in /var/db/backups, or from a Time Machine snapshot of that backup.
    13. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.
    If you get this far without solving the problem, then you'll need to examine the logs in the Open Directory section of the log list in the Server app, and also the system log on the clients.

  • Dashboard services won't start (ServiceProviderRegistry)

    I am working with a fresh install, and after windows update finished, I have 5 services related to Dashboard that no longer start. This is preventing me from accessing any of the backup and client imaging features, along with basically all dashboard functions.
    The problem seems to stem from The Windows Server Essentials Provider Registry Service, which the other services are dependent on.
    The Windows Server Essentials Provider Registry Service service terminated with the following error:
    %%2148734209
    Which results in the Notification, Media Streaming, Health, and Management services not starting.
    I am a novice when it comes to Server 2012 R2, if anyone has an idea, it would be appreciated.

    Found a little more detail, it does seem to be NetTcpPortSharing service that is causing an issue. (Even though it is running)
    The 'Windows Server Essentials Provider Registry Service' service (ServiceProviderRegistry) failed while starting.
    Additional error information: Problems opening ServiceHost: Error opening ServiceHost (2 tries left): System.ServiceModel.AddressAlreadyInUseException: The TransportManager failed to listen on the supplied URI using the NetTcpPortSharing service: the service
    failed to listen.
       at System.ServiceModel.Channels.SharedConnectionListener.SharedListenerProxy.Register()
       at System.ServiceModel.Channels.SharedConnectionListener.SharedListenerProxy.Open(Boolean isReconnecting)
       at System.ServiceModel.Channels.SharedConnectionListener.StartListen(Boolean isReconnecting)
       at System.ServiceModel.Channels.SharedTcpTransportManager.OnOpenInternal(Int32 queueId, Guid token)
       at System.ServiceModel.Channels.SharedTcpTransportManager.OnOpen()
       at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
       at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
       at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.CommunicationObjectWrapper`1.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderRegistry.ServiceShell.OpenHost()

  • Windows Server Essentials error occurred while configuring on Windows Server 2012 R2 Standard

     am attempting to install the Windows Server Essentials on a new domain controller in a new domain and forest.   I go to add roles and features and select essentials.  The config wizard says it is Updating and Preparing the Server and
    That is all the information that you need to provide. Your server is being prepared for use and may restart more than once. This may take up to 30 minutes.
    It goes to 3% and the encounters an error saying An error occurred while configuring Windows Server Essentials. Please try again.  I don't seem to find anything in the log to indicate why it fails.

    Hi boe_d,
    Based on your description, did you mean that this error was occurred in process of installing the Windows Server
    Essentials Experience Role on Windows Server 2012 R2 Standard? If I misunderstand, please don’t hesitate to let me know.
    If it is, have you re-tried the role installation? Please check if still go to 3% and then get the same error
    message.
    In addition, please add
    ServerAdmin$ account to the Logon as a service Group Policy, and then monitor the result. For more details, please refer to the following article.
    You may be unable to run post-deployment configuration wizard after you install the Windows Server Essentials
    Experience role
    http://blogs.technet.com/b/sbs/archive/2013/12/04/you-may-be-unable-to-run-post-deployment-configuration-wizard-after-you-install-the-windows-server-essentials-experience-role.aspx
    If this issue still exists, please navigate to: %windir%\Logs\CBS folder and check the CBS log file if you
    can find any error that depend on the Essentials Experience Role setup time.
    Hope this helps.
    Best regards,
    Justin Gu

  • [Forum FAQ] How to install and configure Windows Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely

    As we all know,
    the Windows Server Essentials Experience role is available in Windows Server 2012 R2 Standard and Windows Server 2012 R2 Datacenter. We can add the Windows Server
    Essentials Experience role in Server Manager or via Windows PowerShell.
    In this article, we introduce the steps to install and configure Windows
    Server Essentials Experience role on Windows Server 2012 R2 Standard via PowerShell locally and remotely. For better analyze, we divide this article into two parts.
    Before installing the Windows Server Essentials Experience Role, please use
    Get-WindowsFeature
    PowerShell cmdlet to ensure the Windows Server Essentials Experience (ServerEssentialsRole) is available. (Figure 1)
    Figure 1.
    Part 1: Install Windows Server Essentials Experience role locally
    Add Windows Server Essentials Experience role
    Run Windows PowerShell as administrator, then type
    Add-WindowsFeature ServerEssentialsRole cmdlet to install Windows Server Essentials Experience role. (Figure 2)
    Figure 2.
    Note: It is necessary to configure Windows Server Essentials Experience (Post-deployment Configuration). Otherwise, you will encounter following issue when opening Dashboard.
    (Figure 3)
    Figure 3.
      2. Configure Windows Server Essentials Experience role
    (1)  In an existing domain environment
    Firstly, please join the Windows Server 2012 R2 Standard computer to the existing domain through the path:
    Control Panel\System\Change Settings\”Change…”\Member of. (Figure 4)
    Figure 4.
    After that, please install Windows Server Essentials Experience role as original description. After installation completed, please use the following command to configure Windows
    Server Essentials:
    Start-WssConfigurationService –Credential <Your Credential>
    Note: The type of
    Your Credential should be as: Domain-Name\Domain-User-Account.
    You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory when using the command above to configure Windows Server Essentials. (Figure 5)
    Figure 5.
    Next, you can type the password for the domain account. (Figure 6)
    Figure 6.
    After setting the credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 7)
    Figure 7.
    By the way, you can use
    Get-WssConfigurationStatus
    PowerShell cmdlet to
    get the status of the configuration of Windows Server Essentials. Specify the
    ShowProgress parameter to view a progress indicator. (Figure 8)
    Figure 8.
    (2) In a non-domain environment
    Open PowerShell (Run as Administrator) on the Windows Server 2012 R2 Standard and type following PowerShell cmdlets: (Figure 9)
    Start-WssConfigurationService -CompanyName "xxx" -DNSName "xxx" -NetBiosName "xxx" -ComputerName "xxx” –NewAdminCredential $cred
    Figure 9.
    After you type the commands above and click Enter, you can create a new administrator credential. (Figure 10)
    After creating the new administrator credential, please type “Y” to continue to configure Windows Server Essentials. (Figure 11)
    After a reboot, all the configurations will be completed and you can open the Windows Server Essentials Dashboard without any errors. (Figure 12)
    Figure 12.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Part 2: Install and configure Windows Server Essentials Experience role remotely
    In an existing domain environment
    In an existing domain environment, please use following command to provide credential and then add Server Essentials Role: (Figure 13)
    Add-WindowsFeature -Name ServerEssentialsRole
    -ComputerName xxx -Credential DomainName\DomainAccount
    Figure 13.
    After you enter the credential, it will start install Windows Server Essentials role on your computer. (Figure 14)
    Figure 14.
    After the installation completes, it will return the result as below:
    Figure 15.
    Next, please use the
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with a remote computer. You can use the commands below:
    Enter-PSSession –ComputerName
    xxx –Credential DomainName\DomainAccount (Figure 16)
    Figure 16.
    Then, please configure Server Essentials Role via
    Add-WssConfigurationService cmdlet and it also needs to provide correct credential. (Figure 17)
    Figure 17.
    After your credential is accepted, it will update and prepare your server. (Figure 18)
    Figure 18.
    After that, please type “Y” to continue to configure Windows Server Essentials. (Figure 19)
    Figure 19.
    2. In a non-domain environment
    In my test environment, I set up two computers running Windows Server 2012 R2 Standard and use Server1 as a target computer. The IP addresses for the two computers are as
    below:
    Sevrer1: 192.168.1.54
    Server2: 192.168.1.53
    Run
    Enable-PSRemoting –Force on Server1. (Figure 20)
    Figure 20.
    Since there is no existing domain, it is necessary to add the target computer (Server1) to a TrustedHosts list (maintained by WinRM) on Server 2. We can use following command
    to
    add the TrustedHosts entry:
    Set-Item WSMan:\localhost\Client\TrustedHosts IP-Address
    (Figure 21)
    Figure 21.
    Next, we can use
    Enter-PSSession
    cmdlet and provide the correct credential to start an interactive session with the remote computer. (Figure 22)
    Figure 22.
    After that, you can install Windows Server Essentials Experience Role remotely via Add-WindowsFeature ServerEssentialsRole cmdlet. (Figure 23)
    Figure 23.
    From figure 24, we can see that the installation is completed.
    Figure 24.
    Then you can use
    Start-WssConfigurationService cmdlet to configure Essentials Role and follow the steps in the first part (configure Windows Server Essentials Experience in a non-domain environment) as the steps would be the same.
    The figure below shows the status of Windows Server Essentials.
    Figure
    25.
    Finally, we have successfully configured Windows Server Essentials on Server1. (Figure 26)
    Figure 26.
    More information:
    [Forum
    FAQ] Introduce Windows Powershell Remoting
    Windows Server Essentials Setup Cmdlets
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Windows Server Essentials Connector issue

    I cannot get the computer connector program to complete successfully. Had to add my 6 Pcs manually through the Properties screen on the PCs.  As a result, Computers are not listed on the Anywhere Access screen and no-one can remote into their PC.
    I have both, a self-signed certificate for the servername.domainname.local and a purchased certificate for the public domain on the server.
    here is the computerconnector log and the clientdeployment log:
    [05/27/2014 21:28:21 117c] --------------------------------------------------------------------------------------------------
    [05/27/2014 21:28:21 117c] wmain: Start of Computerconnector
    [05/27/2014 21:28:21 117c] GlobalData::Initialize (192.168.0.3, C:\Users\mmorton.MARCHITECTS\AppData\Local\Microsoft\Windows\INetCache\IE\8M2RXD56\ComputerConnector(192.168.0.3).exe)
    [05/27/2014 21:28:21 117c] =================================
    [05/27/2014 21:28:21 117c] Current Os information:
    [05/27/2014 21:28:21 117c] Suite = [256]
    [05/27/2014 21:28:21 117c] Type = [1]
    [05/27/2014 21:28:21 117c] Architecture = [9]
    [05/27/2014 21:28:21 117c] IsStarterEdition = [0]
    [05/27/2014 21:28:21 117c] IsHomeSku = [0]
    [05/27/2014 21:28:21 117c] Major = [6]
    [05/27/2014 21:28:21 117c] Minor = [3]
    [05/27/2014 21:28:21 117c] Build = [9600]
    [05/27/2014 21:28:21 117c] SPMajor = [0]
    [05/27/2014 21:28:21 117c] SPMinor = [0]
    [05/27/2014 21:28:21 117c] =================================
    [05/27/2014 21:28:21 117c] ExpandEnvironmentStrings return (C:\Windows\Temp\ClientDeploymentTempFiles\)
    [05/27/2014 21:28:21 117c] SetPackageDlcUrl: .NET url is set to
    http://go.microsoft.com/?linkid=9816306
    [05/27/2014 21:28:21 117c] SetPackageDlcUrl: Connector url is set to
    http://go.microsoft.com/fwlink/p/?LinkId=275102
    [05/27/2014 21:28:21 117c] wmain: Calling Computerconnector::ShowWizard()
    [05/27/2014 21:28:21 117c] CComputerconnector::ShowWizard: Initializing common controls
    [05/27/2014 21:28:21 117c] CComputerconnector::ShowWizard: Done initializing common controls
    [05/27/2014 21:28:21 117c] Displaying the wizard
    [05/27/2014 21:28:21 117c] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [05/27/2014 21:28:21 117c] Current user default UI lang setting is 1033
    [05/27/2014 21:28:21 1340] CComputerconnector::Run: Installation is ready to run
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
    [05/27/2014 21:28:25  cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [05/27/2014 21:28:25  cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [05/27/2014 21:28:25  cf0] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [05/27/2014 21:28:25  cf0] Connector installation state is 1
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [05/27/2014 21:28:25  cf0] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Starting the Windows Server Essentials Connector setup... Index=  5
    [05/27/2014 21:28:25  cf0] RunShellExecute: ShellExecute [C:\Windows\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.0.3 -LaunchedFrom:installer]
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [05/27/2014 21:28:25 117c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Starting the Windows Server Essentials Connector setup...
    [05/27/2014 21:28:25  cf0] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
    [05/27/2014 21:28:26  cf0] CComputerconnector::Run: WaitForSingleObject RetVal = 0
    [05/27/2014 21:28:26 117c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
    [05/27/2014 21:28:26 117c] wmain: End of Computerconnector: hr=0x0
    [3808] 140527.212825.8067: ClientSetup: Start of ClientDeploy
    [3808] 140527.212825.8267: General: Initializing...C:\Windows\system32\Essentials\ClientDeploy.exe
    [3808] 140527.212825.8317: ClientSetup: Create client deployment registry subkey if necessary
    [3808] 140527.212825.8367: ClientSetup: The initial launching way: -LaunchedFrom:installer
    [3808] 140527.212825.8367: ClientSetup: The initial state is set
    [3808] 140527.212825.8367: ClientSetup: The initial serverName: 192.168.0.3
    [3808] 140527.212825.8367: ClientSetup: Loading Wizard Data
    [3808] 140527.212825.8467: ClientSetup: Saving Wizard Data
    [3808] 140527.212825.8467: ClientSetup: Current DeploymentStatus=Start
    [3808] 140527.212826.0317: ClientSetup: Showing the Client Deployment Wizard
    [3808] 140527.212826.1167: ClientSetup: Machine name:M16, length:3
    [3808] 140527.212826.1267: ClientSetup: The input server name is 192.168.0.3
    [5052] 140527.212826.1417: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5052] 140527.212826.1417: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
    [3808] 140527.212826.1417: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
    [3808] 140527.212826.1417: ClientSetup: Set the Deployment Sync Event
    [5052] 140527.212826.1467: ClientSetup: The configuration cab will be downloaded from 192.168.0.3
    [5052] 140527.212826.1517: ClientSetup: Download file Setup.cab from server
    [5052] 140527.212826.1567: ClientSetup: Making web request:
    https://192.168.0.3//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [5052] 140527.212826.1767: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException:
    The remote certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
    [5052] 140527.212826.1767: ClientSetup: Cannot get configuration file with https, will try http...
    [5052] 140527.212826.1767: ClientSetup: Download file Setup.cab from server
    [5052] 140527.212826.1767: ClientSetup: Making web request:
    http://192.168.0.3//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [5052] 140527.212826.2418: ClientSetup: Downloaded file C:\Windows\Temp\ClientDeploymentTempFiles\Setup.cab
    [5052] 140527.212826.2418: ClientSetup: The configuration cab is downloaded to C:\Windows\Temp\ClientDeploymentTempFiles\Setup.cab
    [5052] 140527.212826.3118: ClientSetup: Adding Server Info data in the Product Registry
    [5052] 140527.212826.3218: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.3, normal environment
    [5052] 140527.212826.3218: ClientSetup: Exiting PreConfigTask.Run()
    [5052] 140527.212826.3218: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [5052] 140527.212826.3218: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [5052] 140527.212826.3218: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6040: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [5192] 140527.212859.6040: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6040: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [5192] 140527.212859.6141: ClientSetup: Entering InstallRootCertTask.Run
    [5192] 140527.212859.6191: ClientSetup: Install root cert to local trusted store
    [5192] 140527.212859.6290: ClientSetup: Exiting InstallRootCertTask.Run
    [5192] 140527.212859.6290: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [5192] 140527.212859.6290: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [5192] 140527.212859.6290: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6290: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [5192] 140527.212859.6290: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6290: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [5192] 140527.212859.6340: ClientSetup: Entering SetupVpnAndDATask.Run
    [5192] 140527.212859.6491: ClientSetup: Deploy VPN profile
    [5192] 140527.212859.6891: ClientSetup: Exting SetupVpnAndDATask.Run
    [5192] 140527.212859.6891: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
    [5192] 140527.212859.6991: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [5192] 140527.212859.6991: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6991: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [5192] 140527.212859.6991: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5192] 140527.212859.6991: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [5192] 140527.212859.7041: ClientSetup: Entering ValidateUserTask.Run
    [5192] 140527.212859.7041: ClientSetup: Validating User
    [5192] 140527.212859.7041: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [5192] 140527.212859.7491: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure
    channel with authority 'marchsbs:65500'. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote
    certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---
    Server stack trace:
       at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.ICertService.GetMachineStatus(GetMachineStatusRequest request)
       at Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.CertServiceClient.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
       at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       --- End of inner exception stack trace ---
       at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
    [5192] 140527.212859.7491: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\ipconfig.exe"  /all
    [5840] 140527.212859.7641: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7641: ClientSetup: Standard Ouptput: Windows IP Configuration
    [5840] 140527.212859.7641: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7641: ClientSetup: Standard Ouptput:    Host Name . . . . . . . . . . . . : M16
    [5840] 140527.212859.7641: ClientSetup: Standard Ouptput:    Primary Dns Suffix  . . . . . . . : MARCHITECTS.local
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Node Type . . . . . . . . . . . . : Hybrid
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    IP Routing Enabled. . . . . . . . : No
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    WINS Proxy Enabled. . . . . . . . : No
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    DNS Suffix Search List. . . . . . : MARCHITECTS.local
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Ethernet adapter Ethernet:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Connection-specific DNS Suffix  . : MARCHITECTS.local
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Physical Address. . . . . . . . . : 34-17-EB-9A-DF-A4
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    DHCP Enabled. . . . . . . . . . . : Yes
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Autoconfiguration Enabled . . . . : Yes
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    IPv4 Address. . . . . . . . . . . : 192.168.0.52(Preferred)
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Lease Obtained. . . . . . . . . . : Tuesday, May 27, 2014 3:40:29 PM
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Lease Expires . . . . . . . . . . : Wednesday, June 4, 2014 3:40:52 PM
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Default Gateway . . . . . . . . . : 192.168.0.1
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    DHCP Server . . . . . . . . . . . : 192.168.0.3
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    DNS Servers . . . . . . . . . . . : 192.168.0.3
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    NetBIOS over Tcpip. . . . . . . . : Enabled
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput: Tunnel adapter isatap.MARCHITECTS.local:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Media State . . . . . . . . . . . : Media disconnected
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Connection-specific DNS Suffix  . : MARCHITECTS.local
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    DHCP Enabled. . . . . . . . . . . : No
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:    Autoconfiguration Enabled . . . . : Yes
    [5840] 140527.212859.7691: ClientSetup: Standard Ouptput:
    [5340] 140527.212859.7691: ClientSetup: Standard Error:
    [5192] 140527.212859.7691: ClientSetup: The exit code of the process (C:\Windows\system32\ipconfig.exe) is: 0
    [5192] 140527.212859.7691: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\route.exe"  print
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Interface List
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   3...34 17 eb 9a df a4 ......Intel(R) Ethernet Connection I217-LM
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   1...........................Software Loopback Interface 1
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   6...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: IPv4 Route Table
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Active Routes:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Network Destination        Netmask          Gateway       Interface  Metric
    [6116] 140527.212859.7841: ClientSetup: Standard Error:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:           0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.52    
    10
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:         127.0.0.0        255.0.0.0         On-link        
    127.0.0.1    306
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:         127.0.0.1  255.255.255.255         On-link         127.0.0.1   
    306
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:       192.168.0.0    255.255.255.0         On-link      192.168.0.52    266
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:      192.168.0.52  255.255.255.255         On-link      192.168.0.52    266
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:     192.168.0.255  255.255.255.255         On-link      192.168.0.52    266
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:         224.0.0.0        240.0.0.0         On-link        
    127.0.0.1    306
    [5192] 140527.212859.7841: ClientSetup: The exit code of the process (C:\Windows\system32\route.exe) is: 0
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:         224.0.0.0        240.0.0.0         On-link      192.168.0.52   
    266
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   255.255.255.255  255.255.255.255         On-link      192.168.0.52    266
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Persistent Routes:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   None
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: IPv6 Route Table
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Active Routes:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:  If Metric Network Destination      Gateway
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   1    306 ::1/128                  On-link
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   1    306 ff00::/8                 On-link
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: ===========================================================================
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput: Persistent Routes:
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:   None
    [3080] 140527.212859.7841: ClientSetup: Standard Ouptput:
    [5192] 140527.212859.7841: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\Windows\system32\nslookup.exe" MARCHSBS
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Server:  marchsbs.marchitects.local
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Address:  192.168.0.3
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Name:    MARCHSBS.MARCHITECTS.local
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput: Address:  192.168.0.3
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
    [6116] 140527.212859.7991: ClientSetup: Standard Error:
    [5340] 140527.212859.7991: ClientSetup: Standard Ouptput:
    [5192] 140527.212859.7991: ClientSetup: The exit code of the process (C:\Windows\system32\nslookup.exe) is: 0
    [5192] 140527.212859.7991: ClientSetup: Set CD Fail reason 10 for SQM in ClientDeployment.exe
    [5192] 140527.212859.8041: ClientSetup: RecordClientDeploymentFailReason: Save registry failed in ClientDeployment.exe : System.UnauthorizedAccessException: Cannot write to the registry key.
       at Microsoft.Win32.RegistryKey.EnsureWriteable()
       at Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
       at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RecordClientDeploymentFailReason(UInt32 failReason)
    [5192] 140527.212859.8041: ClientSetup: Exiting ValidateUserTask.Run
    [5192] 140527.212859.8041: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
    [5192] 140527.212859.8041: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [5192] 140527.212859.8041: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [3808] 140527.212910.2736: ClientSetup: Back from the Client Deployment Wizard
    [3808] 140527.212910.2786: ServerDiscovery:HostsFileUpdater: Removing hosts file entry: MARCHSBS
    [3808] 140527.212910.2836: ClientSetup: Saving Wizard Data
    [3808] 140527.212910.2836: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Hooray!
    testing the certificates and not finding any errors, I stumbled across the Basic Settings button that highlighted an authorization problem. I manually set the authorization to the admin account and by problems disappeared. I am now able to successfully
    join client PCs to the domain thru the //Server/connect method.

  • SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

    SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The virtual directory 'ecp' already exists under 'server/name'.
    Parameter name: VirtualDirectoryName".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    Error:
    The following error was generated when "$error.Clear();
              $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
              $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              if ($be -eq $null)
              new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
              set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
              . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
            " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
    !! And now transport service won't start and mail is unavailable !!
    Any help would be appreciated.
    I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

    Hi,
    Thanks for your response.
    From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Web services won't start - error 100002

    Hi there
    I have done a freash install of Leopard Server 10.5.4 and updated to 10.5.8 on an Xserve G5. Added a 2nd web site (in addition to default) and now web services won't start returning the error:
    A service has encounted an error.
    Try to refresh the view (mysever.com/Web)
    (Could not start web service - details in error log.)
    100002
    Below is in the error log for both web sites:
    Syntax error on line 1310 of /private/etc/httpd/httpd.conf:
    Invalid command '<Proxy', perhaps mis-spelled or defined by a module not included in the server configuration
    The following is a Console Message:
    10/4/09 10:50:18 PM com.apple.launchd[1] (org.apache.httpd-1.3[4682]) Exited with exit code: 1
    10/4/09 10:50:18 PM com.apple.launchd[1] (org.apache.httpd-1.3) Throttling respawn: Will start in 10 seconds
    Any pointer of how to solve this would be appreciated.
    Cheers, Paul

    Thanks for the reply. line 1310 is <Proxy disabled_proxy>
    #NoCache a_domain.com another_domain.edu joes.garage_sale.com
    <Directory "disabled_proxy">
    Allow from example.com
    Order Deny,Allow
    Deny from all
    </Directory>
    <Proxy disabled_proxy>
    Allow from example.com
    Order Deny,Allow
    Deny from all
    </Proxy>
    </IfModule>

  • Windows 2008 R2 WDS service is not start.

    Hi,
    Windows 2008 R2 WDS service is not start.
    I am facing the below error on it.
    Please help to resolve.
    -Thanks
    Ashish Dubey

    Hi Ashish,
    Before going further, we can open Event Viewer to see whether some related error events were logged.
    For now, we can refer to the article and thread below to troubleshoot the issue.
    Microsoft WDS Error "the service did not respond to the start or control request in a timely fashion
    http://linkdottech.wordpress.com/2011/12/04/microsoft-wds-error-the-service-did-not-respond-to-the-star-or-control-request-in-a-timely-fashion/
    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.
    Windows Deployment Services Error: The service did not respond to the start or control request in a timely fashion.
    http://social.technet.microsoft.com/Forums/en-US/5f71f652-ac73-4290-817e-5a251b7852b4/windows-deployment-services-error-the-service-did-not-respond-to-the-start-or-control-request-in-a?forum=winservergen
    Besides, if the server has more than 20 logical processors, the Windows Deployment Service cannot be started and we apply the hotfix in the following article to fix
    the issue.
    The Windows Deployment Service cannot be started on a computer that has more than 20 logical processors and that is running Windows Server 2008 R2 or Windows Server
    2008
    http://support.microsoft.com/kb/2121690/en-us
    Best regards,
    Frank Shen

  • Can't Update to 10.0.1, Bonjour Service Won't Start--PLEASE help!

    All I want to do is update my iTunes but I cannot. It won't work from within iTunes, and when I try to do it manually it said "The Service Bonjour Service" won't start." In Services, I could not start it either, though I am admin.
    So I deleted Bonjour (from within the Control Panel), thinking that'd take care of it, but it did not. I still get ALL the same messages. I even tried re-installing Bonjour (bonjour64.msi), and I get the same "won't start" message. It's not my firewall--I set that to always allow.
    What is going on here? I've searched and searched, but to no avail (though they are plenty of Bonjour problems out there), and I really don't want to uninstall/reinstall iTunes, if that would even do it. I'm new to Apple, and this just makes no sense to me.
    Please, help?? THANKS in advance~

    There are remants of Bonjour in the program files, and I guess I could delete these to clean it up, but I doubt that would make the difference.
    Actually, that could make a difference. If there is leftover componentry from the previous version still on the PC when the new version tries to install, the version mismatch could cause trouble with the new service starting. That could then roll back the attempted install.
    There's a bunch of different stuff on 64-bit systems for BonJour (there's both 64-bit and 32-bit componentry stashed on a 64-bit system. We'll also try a cleaner version of an uninstall than the Apple instructions provide.
    In Computer, open your C drive (or whichever drive your program files are installed on).
    Open the "Program Files" folder.
    Right-click on the "BonJour" folder (if it still exists) and select "Delete".
    Go back into your C drive (or whichever drive your program files are installed on).
    Open the "Program Files (x86)" folder.
    Right-click on the "BonJour" folder (if it still exists) and select "Delete".
    Go back into your C drive (or whichever drive your operating system is installed on).
    Open the "Windows" folder.
    Open the "System32" folder.
    Right-click on the dnssd.dll and dns-sd.exe files (if they still exist), and select "Delete".
    Go back into the "Windows" folder.
    Open the "SysWOW64" folder.
    Right-click on the dnssd.dll and dns-sd.exe files (if they still exist), and select "Delete".
    Empty your recycle bin.
    Restart the PC and try another BonJour install. Any better luck restarting the service this time?

  • Integrate On-Premises Exchange Server With Windows Server Essentials

    I have Exchange Server 2013 installed on Win Server 2012 R2 joined to Windows Server Essentials domain.  Attempting to integrate the Exchange Server into the Essentials domain from the Essentials Dashboard using the wizard fails with the error, "Cannot
    locate an Exchange Server on the network. Make sure that your Exchange Server is setup and that it is connected to the network".  I can communicate with the server in multiple ways from the Essentials Server and other computers on the domain.  Mail
    flow in and out of the Exchange Server works without issue.  I can use the various management tools to administer the Exchange Server.  The only task I cannot complete is integrating it into the Essentials environment which I need to do to move on
    to creating user mailboxes for user accounts setup in AD.
    All research to date has come up empty handed.
    Help!

    Hi RSUL,
    Any update?
    On current situation, would you please let me confirm something more? It may help me to understand this issue
    clearly.
    Would you please let me know how join the Windows Server 2012 R2 (which had been installed Exchange Server 2013) to Windows Server Essentials domain? Did use Connector software
    (type http://servername/connect)?
    On server essentials, please open Dashboard and navigate to DEVICES. Then check the Status of this server which had been installed Exchange Server 2013.
    Currently, the Services Integration features, including on-premises Exchange integration, are only supported in a single domain controller environment. Meanwhile, the integration
    wizard must be run on a domain controller.
    In addition, please refer to the following article and check if can help you.
    On
    Premises Exchange Integration Windows Server 2012 Essentials
    Integrate an On-Premises Exchange Server
    with Windows Server Essentials
    By the way, please check Event Viewer and some relevant logs if you can find some more clues.
    Hope this helps.
    Best regards,
    Justin Gu

Maybe you are looking for