2012 Essentials Launchpad reports server is offline

I have a new clean install of Windows Server Essentials 2012. The Server apears fully operational and is visable by network explorer and accessable by Windows remote desktop connection. When configuring http;//<myserver>/connect all workstations
Launchpad reports "the server is offline. do you want to connect in offline mode. I can tell it yes, log on again and have access to my server drives however the Launchpad still reports the "server is offline" any sugestions how to correct this?

Check your dashboard.log file (c:\programdata\microsoft\windows server\logs) for any errors please.
Robert Pearman SBS MVP | www.titlerequired.com | www.itauthority.co.uk
Ton of things that don't look right in dashboard log...here are a few:
[8808] 130226.221733.7018: Dashboard.Forms: Creating TabPage for node F0F0CF38-4269-44dd-90D1-A284506C4C2E with display name "USERS" for TabControl
[8808] 130226.221733.9284: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221733.9284: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.MailService.DashboardAddins.UsersTabPageAdorner, HEAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221733.9294: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.MailService.DashboardAddins.UsersTabPageAdorner, HEAddin
[8808] 130226.221733.9294: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\HostedEmailUsersTab.addin
[8808] 130226.221733.9303: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221733.9303: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.O365Integration.DashboardTabs.OIMUserPageAdorner, OIMAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221733.9303: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.O365Integration.DashboardTabs.OIMUserPageAdorner, OIMAddin
[8808] 130226.221733.9303: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\O365UserTabAddin.addin
[8808] 130226.221733.9333: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221733.9333: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.MailService.DashboardTabs.OPEUserPageContentAdorner, OPEAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221733.9333: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.MailService.DashboardTabs.OPEUserPageContentAdorner, OPEAddin
[8808] 130226.221733.9333: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\OPEUserTabAddin.addin
[8808] 130226.221733.9792: ProviderFramework: Information: [0] : (current thread: 0x2268): Installing new PfSynchronizationContext.
[8808] 130226.221734.1833: ProviderFramework: Information: [0] : (current thread: 0x2268): PfSynchronizationContext not needed.
[8808] 130226.221734.1960: StorageOM: StorageBacked created successfully.
[8808] 130226.221734.1979: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221734.1979: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.MailService.DashboardAddins.UsersTabPageAdorner, HEAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221734.1979: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.MailService.DashboardAddins.UsersTabPageAdorner, HEAddin
[8808] 130226.221734.1979: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\HostedEmailUsersTab.addin
[8808] 130226.221734.1979: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221734.1989: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.O365Integration.DashboardTabs.OIMUserPageAdorner, OIMAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221734.1989: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.O365Integration.DashboardTabs.OIMUserPageAdorner, OIMAddin
[8808] 130226.221734.1989: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\O365UserTabAddin.addin
[8808] 130226.221734.1989: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221734.1989: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.MailService.DashboardTabs.OPEUserPageContentAdorner, OPEAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221734.1989: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.MailService.DashboardTabs.OPEUserPageContentAdorner, OPEAddin
[8808] 130226.221734.1989: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\OPEUserTabAddin.addin
[8808] 130226.221735.3952: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221735.3961: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Identity.UI.AddinPage, UserUIAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[8808] 130226.221735.3961: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Identity.UI.AddinPage, UserUIAddin
[8808] 130226.221735.3961: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Users\users.addin
[8808] 130226.221740.8561: Dashboard.Forms: Creating TabPage for node AFA7A628-4DA9-4982-9CCB-10F7458871FD with display name "DEVICES" for TabControl
[8808] 130226.221740.9127: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221740.9127: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.W7PVPComputersTabExtender.PageAdorner, GroupPolicyComputersTabExtender from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221740.9127: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.W7PVPComputersTabExtender.PageAdorner, GroupPolicyComputersTabExtender
[8808] 130226.221740.9127: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Computers\GroupPolicyComputersTabExtension.addin
[8808] 130226.221740.9351: ProviderFramework: Information: [0] : (current thread: 0x2268): PfSynchronizationContext not needed.
[8808] 130226.221740.9518: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221740.9527: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.W7PVPComputersTabExtender.PageAdorner, GroupPolicyComputersTabExtender from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Internal.IContentNode
[8808] 130226.221740.9527: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.W7PVPComputersTabExtender.PageAdorner, GroupPolicyComputersTabExtender
[8808] 130226.221740.9527: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Computers\GroupPolicyComputersTabExtension.addin
[8808] 130226.221741.0338: ProviderFramework: Information: [0] : (current thread: 0x2268): PfSynchronizationContext not needed.
[8808] 130226.221741.0338: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Common.Devices.IDevicesProvider, False,
[8808] 130226.221741.0357: PluginManager: ---- These warnings could be benign if the addin file is not pointing to an adorner. ----
[8808] 130226.221741.0357: PluginManager: Unable to load type Microsoft.WindowsServerSolutions.Console.AddIns.Computers.ComputersPage, ComputersUIAddin from C:\Program Files\Windows Server\Bin\. It cannot be assigned to the requested type Microsoft.WindowsServerSolutions.Administration.ObjectModel.Adorners.PageContentAdorner
[8808] 130226.221741.0357: PluginManager: Unable to obtain plugin type information for type Microsoft.WindowsServerSolutions.Console.AddIns.Computers.ComputersPage, ComputersUIAddin
[8808] 130226.221741.0357: PluginManager: Invalid plugin file: C:\Program Files\Windows Server\Bin\Addins\Computers\computers.addin

Similar Messages

  • How can I upgrade Windows Server 2012 Essentials to Windows Server 2012 R2 Essentials?

    I have just installed Windows Server 2012 Essentials on my Home Network (from the installation DVD).  I have done absolutely no  configuration  Installing Server 2012 was an oversight;  I meant to install Server 2012 R2 Essentials. 
    I tried to correct by installing R2 from its DVD, hoping it would do an upgrade.  That didn't work.
    Is there a simple way to make it possible to install the correct OS?   For example, can I just demote the existing server and remove any roles that were installed, so that the R2 disk will install over top of the existing installation?
    Alternatively, is it safe to just reformat the partition and install R2? 
    http://technet.microsoft.com/en-us/library/dn408635.aspx seems to imply that this is OK.
    David Pike, P.Eng, MCITP

    Hi Larry.   Thanks for the reply.  It didn't work, but I don't believe you are wrong.  Rather I think there is something weird in my system.  I'm marking your reply as answer.
    Some background:  I'm repurposing an older PC (Compaq SR1614X) as a home server, to manage my home network, use as a gateway to my Azure server, and to help my Server 2012 training (on MVA).  I've been messing with it for nearly two months,
    on and off.  From the start, I've had trouble installing the server 2012 software (see previous threads August-27 and August-16
    ), but when I got to the point that I could install Server 2012 Essentials, I thought I could upgrade to Server 2012 R2 Essentials exactly as you suggest.  That was where you helped me a lot, i.e. you confirmed that my expectations were reasonable. 
    So when it didn't work, I spent most of yesterday trying various different procedures.   I got tantalizingly close, but still no cigar. 
    I can install any Windows Client and Server 2012 Essentials, but the R2 Essentials installation never finishes; it goes into an "error 0x000000C4" boot loop.  At first I wondered if it was because I was installing a server over a
    server, but you confirmed that's not the issue.  I later verified that I cannot install R2 over Windows 7 either, whereas R1 over Win7 is fine.  I can only surmise one of two problems:
    I have a bad installation disk  
    There is a hardware issue
    I plan to eliminate (1) by creating a new disk from a new download.  I have verified that the latest ISO file and the one I have been using have identical byte counts,   
    For (2), I had suspected that the problem was that the older system has no UEFI, but since R1 installs OK, I am discounting that.  Today's effort:  to eliminate the DVD drive, I will try booting from a Flash Drive.  To eliminate
    the hard drive, I will try installing to a different drive.
    I am hoping you can help with one more thing.  When I run setup.exe with the /noreboot option, I have a better chance of success.  The option suppresses the first reboot only, but that one (after "Expanding the setup files") always
    fails, so suppressing it gets me almost to the end of the install.  Is there a way to modify setup.exe so the it always runs with the /noreboot option?

  • Launchpad shows "Server is offline" in client PCs

    Hi,
    I've the problem that the Launchpad indicates the server as offline even if it's not.
    In the Server dashboard I can see that all client PCs are shown as offline too, but everything is up and running. I can ping the clients and vice versa. I've looked ino the logfiles and found the following errors in LANConfigSvc.log:
    [2728] 131118.160555.6740: ServerDiscoveryClient: Calling Ping
    [2728] 131118.160555.6740: ServerDiscoveryClient: OM is connected, just Ping
    [6288] 131118.160555.6740: ServerConnectionClient: Calling Ping
    [6288] 131118.160555.6740: ServerConnectionClient: OM is connected, just Ping
    [7136] 131118.160555.7676: VPNClientUpdater: Failed to retrieve VPN server setting. Exception: System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.Networking.NetworkingServiceBackend.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Networking.VPNClientUpdater.TryGetVPNServerSetting(VPNSetting& setting)
    [2292] 131118.160556.1108: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [2292] 131118.160556.1108: SmallBusinessServerPresenceDetector: Ping: retry #25 of 1 failed
    [6184] 131118.160601.2905: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [6184] 131118.160601.2905: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [6184] 131118.160601.2905: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [6184] 131118.160601.2905: ServerDiscoveryProviderBase: Callback successfully completed
    [2988] 131118.160601.2905: LanConfigService:RunnerBase: Server discovery Attempt Failed
    [6288] 131118.160606.2986: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Reset DNS server before discovery
    [6288] 131118.160606.4078: ServerDiscovery:ServerLocator: FindServer: looking for server SERVER02, searchDuration:00:00:05
    [6288] 131118.160611.6342: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: OnServerCandidateDiscovered: Found server SERVER02, will verify
    [6288] 131118.160611.6342: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Set DNS server after discovery.
    [6184] 131118.160611.6342: PInvoke: DnsValidateServerStatus(out serverStatus = 'ERROR_SUCCESS (0x00000000)', serverIP = '192.168.104.34', queryName = '') returns 'NO_ERROR (0x00000000)'
    [6288] 131118.160611.7122: ProviderFramework: Information: [0] : (current thread: 0x1890): PfSynchronizationContext not needed.
    [6288] 131118.160611.7122: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Networking.INetworkingService, True,
    Can someone help please
    Thanks

    Hello -
       I am having exactly the same problem.  Were you able to find a solution?
        Igor.
    Part of my log file below:
    [10596] 140104.193209.2327: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [10596] 140104.193209.2327: SmallBusinessServerPresenceDetector: Ping: retry #158 of 1 failed
    [9052] 140104.193224.0522: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [9052] 140104.193224.0522: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [9052] 140104.193224.0522: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [9052] 140104.193224.0522: ServerDiscoveryProviderBase: Callback successfully completed
    [7844] 140104.193224.0522: LanConfigService:RunnerBase: Server discovery Attempt Failed
    [7968] 140104.193229.0557: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Reset DNS server before discovery
    [7968] 140104.193229.1867: ServerDiscovery:ServerLocator: FindServer: looking for server LENOVO, searchDuration:00:00:05
    [12260] 140104.193229.3326: ServerDiscoveryClient: Calling Ping
    [12260] 140104.193229.3326: ServerDiscoveryClient: OM is connected, just Ping
    [10528] 140104.193229.3946: ServerConnectionClient: Calling Ping
    [10528] 140104.193229.3946: ServerConnectionClient: OM is connected, just Ping
    [7968] 140104.193234.4011: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: OnServerCandidateDiscovered: Found server LENOVO, will verify
    [7968] 140104.193234.4011: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Set DNS server after discovery.
    [7968] 140104.193234.4081: PInvoke: DnsValidateServerStatus(out serverStatus = 'ERROR_SUCCESS (0x00000000)', serverIP = '192.168.2.15', queryName = '') returns 'NO_ERROR (0x00000000)'
    [7968] 140104.193234.5321: ProviderFramework: Information: [0] : (current thread: 0x1f20): PfSynchronizationContext not needed.
    [7968] 140104.193234.5321: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Networking.INetworkingService, True,
    [8384] 140104.193249.2357: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [8384] 140104.193249.2357: SmallBusinessServerPresenceDetector: Ping: retry #159 of 1 failed
    [7968] 140104.193304.5291: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [7968] 140104.193304.5291: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [7968] 140104.193304.5291: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [7968] 140104.193304.5291: ServerDiscoveryProviderBase: Callback successfully completed
    [11672] 140104.193304.5291: LanConfigService:RunnerBase: Server discovery Attempt Failed
    [10528] 140104.193309.5321: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Reset DNS server before discovery
    [10528] 140104.193309.6731: ServerDiscovery:ServerLocator: FindServer: looking for server LENOVO, searchDuration:00:00:05
    [10528] 140104.193314.8871: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: OnServerCandidateDiscovered: Found server LENOVO, will verify
    [10528] 140104.193314.8871: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Set DNS server after discovery.
    [9852] 140104.193314.8951: PInvoke: DnsValidateServerStatus(out serverStatus = 'ERROR_SUCCESS (0x00000000)', serverIP = '192.168.2.15', queryName = '') returns 'NO_ERROR (0x00000000)'
    [10528] 140104.193315.0031: ProviderFramework: Information: [0] : (current thread: 0x2920): PfSynchronizationContext not needed.
    [10528] 140104.193315.0031: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Networking.INetworkingService, True,
    [7528] 140104.193328.9211: VPNClientUpdater: Failed to retrieve VPN server setting. Exception: System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.Networking.NetworkingServiceBackend.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Networking.VPNClientUpdater.TryGetVPNServerSetting(VPNSetting& setting)
    [9516] 140104.193329.2351: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [9516] 140104.193329.2351: SmallBusinessServerPresenceDetector: Ping: retry #160 of 1 failed
    [12260] 140104.193329.3401: ServerDiscoveryClient: Calling Ping
    [12260] 140104.193329.3401: ServerDiscoveryClient: OM is connected, just Ping
    [9052] 140104.193329.4031: ServerConnectionClient: Calling Ping
    [9052] 140104.193329.4031: ServerConnectionClient: OM is connected, just Ping
    [10528] 140104.193345.0031: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [10528] 140104.193345.0031: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [10528] 140104.193345.0031: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [10528] 140104.193345.0031: ServerDiscoveryProviderBase: Callback successfully completed
    [11260] 140104.193345.0031: LanConfigService:RunnerBase: Server discovery Attempt Failed
    [7528] 140104.193350.0101: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Reset DNS server before discovery
    [7528] 140104.193350.1441: ServerDiscovery:ServerLocator: FindServer: looking for server LENOVO, searchDuration:00:00:05
    [7528] 140104.193355.3581: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: OnServerCandidateDiscovered: Found server LENOVO, will verify
    [7528] 140104.193355.3581: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Set DNS server after discovery.
    [9516] 140104.193355.3651: PInvoke: DnsValidateServerStatus(out serverStatus = 'ERROR_SUCCESS (0x00000000)', serverIP = '192.168.2.15', queryName = '') returns 'NO_ERROR (0x00000000)'
    [7528] 140104.193355.4641: ProviderFramework: Information: [0] : (current thread: 0x1d68): PfSynchronizationContext not needed.
    [7528] 140104.193355.4641: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Networking.INetworkingService, True,
    [9852] 140104.193409.2441: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [9852] 140104.193409.2441: SmallBusinessServerPresenceDetector: Ping: retry #161 of 1 failed
    [7528] 140104.193425.4631: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [7528] 140104.193425.4631: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [7528] 140104.193425.4631: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [7528] 140104.193425.4631: ServerDiscoveryProviderBase: Callback successfully completed
    [12100] 140104.193425.4631: LanConfigService:RunnerBase: Server discovery Attempt Failed
    [7968] 140104.193429.3511: ServerDiscoveryClient: Calling Ping
    [7968] 140104.193429.3511: ServerDiscoveryClient: OM is connected, just Ping
    [7528] 140104.193429.4141: ServerConnectionClient: Calling Ping
    [7528] 140104.193429.4141: ServerConnectionClient: OM is connected, just Ping
    [10596] 140104.193430.4601: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Reset DNS server before discovery
    [10596] 140104.193430.5791: ServerDiscovery:ServerLocator: FindServer: looking for server LENOVO, searchDuration:00:00:05
    [10596] 140104.193435.7941: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: OnServerCandidateDiscovered: Found server LENOVO, will verify
    [10596] 140104.193435.7941: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Set DNS server after discovery.
    [7528] 140104.193435.8011: PInvoke: DnsValidateServerStatus(out serverStatus = 'ERROR_SUCCESS (0x00000000)', serverIP = '192.168.2.15', queryName = '') returns 'NO_ERROR (0x00000000)'
    [10596] 140104.193435.8861: ProviderFramework: Information: [0] : (current thread: 0x2964): PfSynchronizationContext not needed.
    [10596] 140104.193435.8861: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.Networking.INetworkingService, True,
    [9516] 140104.193449.2411: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [9516] 140104.193449.2411: SmallBusinessServerPresenceDetector: Ping: retry #162 of 1 failed
    [9052] 140104.193458.9291: VPNClientUpdater: Failed to retrieve VPN server setting. Exception: System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.Networking.NetworkingServiceBackend.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Networking.VPNClientUpdater.TryGetVPNServerSetting(VPNSetting& setting)
    [10596] 140104.193505.8851: ServerDiscovery:Pinger: Ping: TimeoutException in Connect
    [10596] 140104.193505.8851: ServerDiscoveryProvider:SmallBusinessServerDiscoverer: Verification failed
    [10596] 140104.193505.8851: ServerDiscoveryProviderBase: Calling Callback.OnServerDiscoveryAttemptFailed()
    [10596] 140104.193505.8851: ServerDiscoveryProviderBase: Callback successfully completed
    [7620] 140104.193505.8851: LanConfigService:RunnerBase: Server discovery Attempt Failed

  • Cannot upgrade server 2012 essentials to Server 2012 standard

    using dism :
    PS C:\Windows\system32> dism.exe /online /Set-Edition:ServerStandard /ProductKey:XXXXX-HF7PX-XXXXX-2XDPX-XXXXX /AcceptEula
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    Image Version: 6.2.9200.16384
    Error: 0x8a010001
    The specified product key could not be validated.
    Check that the specified product key is valid and that it matches the target edition.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    PS C:\Windows\system32> DISM /online /Get-CurrentEdition
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    Image Version: 6.2.9200.16384
    Current edition is:
    Current Edition : ServerSolution
    The operation completed successfully.
    Bought new key from Ebuyer.com

    Hi,
    Glad the issue was solved by yourself.
    I think it should be an in-place license transition, transitioning from Windows Server 2012 Essentials to Windows Server 2012 Standard.
    https://technet.microsoft.com/en-us/library/jj247582.aspx?f=255&MSPPError=-2147217396
    dism /online /set-edition:ServerStandard /accepteula /productkey:Product Key
    Product Key is the product key for your copy of Windows Server 2012 Standard.
    Regards.
    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 Support, contact [email protected]

  • SQL on Server 2012 Essentials

    What are the options and/or limits for running SQL server (Standard or Express, 2012 or 2008 or 2005) on Server 2012 Essentials? Thank you.

    Most best practice is that it is not a good idea to run SQL on a DC.  However, I am not aware of any negatives, other than the disclaimers about it being a DC and possible RAM or I/O issues.  Were possible, I would use Express as it is
    a LOT less expensive and requires fewer resources.  It was only a generation or two ago that SQL and Exchange and ISA server all ran on "the" DC and could not be relocated by EULA, for up to 75 users.
    From this document:
    http://www.microsoft.com/en-us/server-cloud/windows-server-essentials/default.aspx
    Follow the Learn More at the bottom, for a pdf that reads, in part:
    Q: What applications can I run on Windows Server 2012 Essentials?
    A: Almost all Windows Server 2012 applications should run on Windows Server 2012 Essentials. Windows Server
    2012 Essentials differs from Windows Server 2012 primarily in that several of the roles and features of Windows
    Server are automatically installed and configured according to best practices for a small business environment. In
    some cases, an application that is designed to run on Windows Server 2012 may require that specific roles and/or
    features are not enabled. See the manufacturer’s product information for specific details. 
    Do NOT take what I am about to say as gospel... I am NOT a SQL expert.  But imo, the reason to not run SQL server on the DC is that it is busy enough and in an AD enviornment where there are potentially thousands of users the server would be too busy
    servicing those requests to be a good candidate for SQL.  But in network of 25 users or less..... ??
    Larry Struckmeyer[SBS-MVP]

  • The report server service is not running on reporting service point server ID: 7403 SMS_SRS_REPORTING_POINT

    Hi,
    I'm having a problem when I try to install Report Services point, I can browser my report server from my SCCM site but when I install the Reporting point the reports do not load to report server.
    If I check at my reportserver machine all reports are in the disk.
    I have one machine with SQL Server 2012 Std SP1 and another computer with SCCM 2012 SP1.
    Error at srsrp.log
    SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 3308 (0xCEC).    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:40    3356 (0x0D1C)
    This is a SRS Reporting Point Role as SRSRP registry key exists.    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:40    3308 (0x0CEC)
    Waiting for changes for 0 minutes    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:40    3308 (0x0CEC)
    Timed Out...    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:40    3308 (0x0CEC)
    Reporting Services URL from Registry [http://srv-bd/ReportServer/ReportService2005.asmx]    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    The request failed with an empty response.    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    (!) SRS not detected as running    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=SRV-BD.F1MAIS.LOCAL SITE=F1M PID=2052 TID=3308 GMTDATE=Mon Jan 14 17:15:44.571 2013 ISTR0="SRV-BD.F1MAIS.LOCAL" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    Failures reported during periodic health check by the SRS Server SRV-BD.F1MAIS.LOCAL.    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    Waiting for changes for 1 minutes    SMS_SRS_REPORTING_POINT    14/01/2013 14:15:44    3308 (0x0CEC)
    Timed Out...    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    Reporting Services URL from Registry [http://srv-bd/ReportServer/ReportService2005.asmx]    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    The request failed with an empty response.    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    (!) SRS not detected as running    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    Failures reported during periodic health check by the SRS Server SRV-BD.F1MAIS.LOCAL.    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    Waiting for changes for 1 minutes    SMS_SRS_REPORTING_POINT    14/01/2013 14:16:44    3308 (0x0CEC)
    Timed Out...    SMS_SRS_REPORTING_POINT    14/01/2013 14:17:44    3308 (0x0CEC)
    Thanks!
    Rodrigo Daphanis

    It looks like the MS support team just published a support tip to this problem -
    http://blogs.technet.com/b/configurationmgr/archive/2013/03/06/support-tip-no-reports-show-up-in-the-console-after-installing-a-system-center-2012-configuration-manager-reporting-server.aspx
    Nick Moseley | http://t3chn1ck.wordpress.com

  • Windows 2012 Essentials Upgrade

    When I run "dism /online /set-edition:ServerStandard /accepteula /productkey:<Product Key>" to upgrade from Server 2012 Essentials to Standard, will it accept an OEM R2 product key?
    Thanks!

    Hi,
    à
    "dism /online /set-edition:ServerStandard /accepteula /productkey:<Product Key>"
    Where
    Product Key is the product key for your copy of Windows Server 2012 Standard. For more details, please refer to the following article.
    Transition from Windows Server 2012 Essentials
    to Windows Server 2012 Standard
    à
    an OEM R2 product key
    Was it Windows Server 2012 R2 Essentials OEM product key? Did you mean that want to use it in a new physical
    server where the Windows Server 2012 Essentials installed? For OEM product key, I suggest that you should contact with your vendor. I believe we will get a better assistance.
    Hope this helps.
    Best regards,
    Justin Gu

  • Windows Server 2012 Essentials (not R2) - all client computers offline

    The server is Windows Server 2012 Essentials (not R2). I have had this problem ever since I first installed the Windows Server 2012 Essentials server in the summer of 2013 (before R2 was released). The Windows Server 2012 Essentials server shows offline
    for all Devices under Dashboard. (Allow me to add that I just installed another site with Windows Server 2012 Essentials R2, and it was a breeze - all of the computers at the second install site are online.) I have one Windows 8.1 Pro client and the rest
    are Windows 7 Pro clients. The problem occurs on ALL client computers.
    I have removed computers from Devices in Dashboard on the server, rebooted the server, changed the client computer to a workgroup, rebooted the client computer, and reinstalled the connector software on the client computer. Same result. I
    have tried this on a Windows 7 Pro client and a Windows 8.1 Pro client with the same results.
    After running the connector on a client computer and waiting for the server to update its Devices status, if I look under Devices on the server Dashboard, the Windows 8.1 client computer will say online but within 24 hours it goes offline again. The
    Windows 7 client computers never show online. Both computers stay offline - they NEVER show an online status (referring to the status under Devices in Dashboard).
    I should make it clear that the clients can access the server shares with no problem. File synchronization works great. The clients can ping the server and the server can ping the clients. But client backups on the server fail.
    One of the most troublesome things about this problem is that it prevents the client computers from being accessed remotely using the website setup by Anywhere Access. I can login to get remote access to the shared files on the server, but
    the only computer that says "online" is the server. All of the other computers are "offline".
    The server and clients are only using Windows firewall. The clients all use Microsoft Security Essentials for their anti-virus.
    I used a troubleshooting tool that tells me that there are problems with port 6602 on the server, but the clients are all fine with port 6602. I know port 6602 is important for using Anywhere Access but I am still trying to find out more details on that.
    I have checked all of the firewall settings related to port 6602 on the server, and the firewall settings look like the standard Windows settings for this port. I used netstat to find the PID associated with the port, and I looked up the PID to find the service.
    That all looked standard, too.
    I have been working on this problem since the summer of 2013!! Does anyone have ANY suggestions?!!
    HELP!

    Hi,
    Just addition, please check if all necessary Windows updates are installed on those
    “Offline” client computer.
    When connect client computers to the Windows Server 2012 Essentials server by using the Connector software, there
    will be LAUNCHPAD on the client computer. Was this LAUNCHPAD grayed out? Please check if can access Shared Folders via this LAUNCHPAD. Meanwhile, please ping the Windows Server 2012 Essentials via IP address and server name when client computers show as
    Offline. Any find?
    Get Connected in Windows Server Essentials
    In addition, please follow the path on Server and client computer:
    %programdata%\Microsoft\Windows Server\Logs. Did you check any relevant Server-side logs and
    Client-side Logs if find more clues?
    Windows
    Server Essentials 2012/2012 R2 Log Files
    If any update, please feel free to let us know.
    Hope this helps.
    Best regards,
    Justin Gu
    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 Support, contact [email protected]

  • Boot up of Windows Server 2012 Essentials seems slow (extended Please Wait screen) and there are errors in Health Report

    Dear Sir or Madam,
    I have been experimenting with the evaluation version of WS2012e trying to get the installation and subsequent build into an optimal set up, and once I have everything I want it to do mapped out, I'll set it up with the full version with using the key that
    I bought.
    However, I've noticed that the server seems to experience a delay during cold boot - it sits with a Please Wait screen for about 60-90 seconds before it presents the screen with an option to Log on.  I have also discovered from running Health
    Report, that there are some entries in the event logs which appear to coincide with start up times, and which seem to be interconnected to each other in the issues they are describing, and I have copied an example of one of those health reports below. 
    I assume that everything sorts itself out in due course, because the events say the process will be re-attempted and these errors don't repeat again after the system has booted up.  I also have the server set to suspend when not in use with the Lights
    Out add in, so it shouldn't need to cold boot often - but I wondered if there's a way to correct these errors so that they don't hold up the boot up process?  I'm also concerned that these errors will cause me later problems with storage pools and
    the like at a later date - the disk replication one seems particularly worrying.  Alternatively, are these errors just a normal part of the start up process - the timing of when different processes start relative to each other - and can be safely ignored?
    In trying to understand what the events describe, I thought that WE2012e acted as its own Domain Controller, and yet it seems from the event log entries that it is waiting for another server to respond to AD / DC requests (but there isn't another server
    on my home network).  The other thing I remember from when I first tried out WS2012e, is that it took control of DHCP or DNS from the router, and I found that frustrating when waking up my laptop and it wouldn't connect to the internet until the server
    had fully booted up and re-asserted its network settings.  Is this another symptom of the same problem?  I remember seeing a posting at the SBS Diva's site about how to update the server so that it gave connected PCs a backup option for connecting
    to the internet when the server wasn't available, and was going to try to find that again to see if that helped.
    By way of background - there isn't another server in my home network.  This is an attempt to do a clean install onto the same hardware that I ran the initial trial of WS2012e, now that the trial has expired, so I'm not trying to migrate from an existing
    server.  I moved all the data on the trial server off onto an external disk, with the intention of importing it back once I had the Storage Pools set up the way I wanted on the new build, and since I didn't want to keep anything else about the server
    trial.  Am I correct in thinking that I don't need to go down the Migration route during installation, and can go through a Clean install in this circumstance? 
    I'm running on an Asus P8-H77-i motherboard, with an i5-3470s CPU and 16MB RAM, and I have WS2012e installed on 256Mb SSD formatted under GPT with uEFI boot - the latter being the main reason for the reinstall, instead of just giving the Evaluation
    version the new key on the original MBR set up.  I've also enabled Intel Rapid Storage and Rapid Start - and successfully set aside the hibernate partition on the SSD - but discovered that this is about forcing a hibernate after suspend, allowing
    the system to power down until its needed again, and then resuming from hibernate on the SSD rather than cold boot each time.  That seems to work, but doesn't improve the cold boot times at all, which was what I was hoping for - ideally the way my
    laptop will boot from cold in a few seconds into Windows 8. 
    Yours faithfully,
    Avon
    ======
    Health Report extract.
    Critical Errors in Event Logs in Last 24 Hours
     DFSR
    Event ID: 3221226674
    The DFS Replication service failed to contact domain controller  to access
    configuration information. Replication is stopped. The service will try again
    during the next configuration polling cycle, which will occur in 60 minutes.
    This event can be caused by TCP/IP connectivity, firewall, Active Directory
    Domain Services, or DNS issues.
    Additional Information:
    Error: 160 (One or more arguments are not correct.)
    Last occurrence: 26 May 2014 18:51:28
    Total occurrence(s): 2
     DNS
    Event ID: 2147487661
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS
    data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet
    Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
    Last occurrence: 26 May 2014 18:51:15
    Total occurrence(s): 2
     ADWS
    Event ID: 3221226674
    This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
    Last occurrence: 26 May 2014 18:51:08
    Total occurrence(s): 2
     NTDS General
    Event ID: 2147486534
    The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,
    Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that
    are performed on a cleartext (non-SSL/TLS-encrypted) connection.  Even if no clients are using such binds,
    configuring the server to reject them will improve the security of this server.
    Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection,
    and will stop working if this configuration change is made.  To assist in identifying these clients, if such binds occur this
    directory server will log a summary event once every 24 hours indicating how many such binds
    occurred.  You are encouraged to configure those clients to not use such binds.  Once no such events are observed
    for an extended period, it is recommended that you configure the server to reject such binds.
    For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.
    You can enable additional logging to log an event each time a client makes such a bind, including
    information on which client made the bind.  To do so, please raise the setting for the "LDAP Interface Events" event logging category
    to level 2 or higher.
    Last occurrence: 26 May 2014 18:51:00
    Total occurrence(s): 2
    =======

    Hi KerguelanAvon,
    Based on your description, it seems to be hard to narrow down the cause of this issue. Please refer to following operations and monitor the result. It may help us to go further, and then solve this issue.
    1. Please refer to the following article and troubleshoot slow boot.
    New Slow Logon, Slow Boot Troubleshooting Content
    2. On your server 2012 essentials, please start a BPA scan and fix all that it can find, then monitor the result.
    Regarding to those critical Errors in Health Report, please perform
    Dcdiag on the server. Meanwhile, please refer to the following article and troubleshoot network connectivity, firewall setting and AD DS issue.
    DFSR Event 1202 (DFS Replication)
    Hope this helps.
    Best regards,
    Justin Gu
    Hi Justin,
    I'm reading through the links you referred me to but it's taking a while.  In the meantime I tried running BPA as you suggested.  I'm sure when I ran it before, it didn't say much beyond 81 checks completed, and I couldn't find a way to get any
    more detail.
    Now it says
    Problem:
    The DNS client is not configured to point only to the internal IP address of the server.
    Impact:
    If the DNS client is not configured to point only to the internal IP address of the server, DNS name resolution can fail.
    Resolution:
    To resolve this problem:
    1. From the client computer, open the Properties page for the network connection.
    2. Make sure that DNS is configured to point only to the internal IP address of the server.
    Except that it is.
    Connection-specific DNS Suffix:
    Description: Broadcom 802.11n Network Adapter
    Physical Address: ‎00-1B-B1-28-AE-63
    DHCP Enabled: Yes
    IPv4 Address: 192.168.1.133
    IPv4 Subnet Mask: 255.255.255.0
    Lease Obtained: 03 June 2014 21:56:49
    Lease Expires: 05 June 2014 20:24:20
    IPv4 Default Gateway: 192.168.1.1
    IPv4 DHCP Server: 192.168.1.1
    IPv4 DNS Server: 192.168.1.49
    IPv4 WINS Server:
    NetBIOS over Tcpip Enabled: Yes
    Link-local IPv6 Address: fe80::80ef:48d5:9fde:f10e%14
    IPv6 Default Gateway:
    IPv6 DNS Server:
    I'll try rebooting from the current windows 7 build over to windows 8 on my dual boot laptop, to see if that makes any difference, since it is the only other client PC connected to the server at the moment.
    Thanks, Avon.

  • DirectAccess on Server 2012 Essentials R2 Breaks Client Connectivity

    I recently completed a Windows Server 2012 Essentials > R2 migration. All is well, clients all working and backing up etc.
    I decided to follow the instructions at
    http://technet.microsoft.com/en-us/library/jj204618.aspx for configuring Essentials to act as a DirectAccess server. After completing the guide, all of my on network clients report the server as offline in the connector software and will not process their
    backups.
    If I disable the DirectAccess Server GPO and do a gpupdate /force on the server, the clients connect again and backups work. I've reviewed the contents of the Server GPO and the only settings which it applies are Windows Firewall settings which I cannot
    see would cause any conflict with client connectivity but clearly there is some.
    Clients are running Windows 8.1 Pro at the moment as I haven't looked into the Enterprise client requirements just yet so the Client GPO is not the issue as the WMI filter on the Client GPO is blocking my current clients from applying it, it's definatly
    a server-side issue.
    Has anyone else had any issues with setting up DirectAccess causing local network issues like this?
    Richard Green MCSE Windows Server 2003, MCTS Desktop Virtualization

    This was caused in the past by not excluding port 6602 from NetNatTranisition, in the original instructions it was excluded by having two ranges 6601-6601 6603-10000 (i think)
    they then updated that doc to start at 10,000
    So i would first check that you didnt have a typo in that command and mistakenly set it from 1000.
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Server 2012 Essentials Restore files not working

    I have a brand new install of server 2012 essentials running on hyper-v. have connected 4 test computers using the essentials connect method, 7 Pro and 8.1. backups are working daily with no errors. thought I would test a restore and I am getting the
    message, "Restore Files and Folders wizard has stopped working. 
    unfortunately this is the very first time I tried a restore so I can't say if any updates are the issue.
    anyone else had similar issue?

    2 errors
    Log Name:      Application
    Source:        .NET Runtime
    Date:          2/19/2015 1:31:20 PM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Windows8Eval.xxxxxxxxxxx.com
    Description:
    Application: MountBackupWizard.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Reflection.TargetInvocationException
    Stack:
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
       at Microsoft.WindowsServerSolutions.DataProtection.UI.Program.Main(System.String[])
    Event Xml:
    <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-02-19T18:31:20.000000000Z" />
        <EventRecordID>1224</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Windows8Eval.xxxxxxxxx.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: MountBackupWizard.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Reflection.TargetInvocationException
    Stack:
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
       at Microsoft.WindowsServerSolutions.DataProtection.UI.Program.Main(System.String[])
    </Data>
      </EventData>
    </Event>
    2nd error
    Log Name:      Application
    Source:        Application Error
    Date:          2/19/2015 1:31:21 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Windows8Eval.xxxxxxxxxxxx.com
    Description:
    Faulting application name: MountBackupWizard.exe, version: 6.3.9600.16384, time stamp: 0x5215cf3c
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
    Exception code: 0xe0434352
    Fault offset: 0x0000000000008b9c
    Faulting process id: 0xac
    Faulting application start time: 0x01d04c723d6d8d89
    Faulting application path: C:\Windows\System32\Essentials\MountBackupWizard.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 7fa0d5c8-b865-11e4-8258-080027e87958
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <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-02-19T18:31:21.000000000Z" />
        <EventRecordID>1225</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Windows8Eval.xxxxxxxxxxx.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MountBackupWizard.exe</Data>
        <Data>6.3.9600.16384</Data>
        <Data>5215cf3c</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>6.3.9600.17415</Data>
        <Data>54505737</Data>
        <Data>e0434352</Data>
        <Data>0000000000008b9c</Data>
        <Data>ac</Data>
        <Data>01d04c723d6d8d89</Data>
        <Data>C:\Windows\System32\Essentials\MountBackupWizard.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>7fa0d5c8-b865-11e4-8258-080027e87958</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

  • Windows Server 2012 Essentials Connector version is more current than server

    In trying to connect a new laptop to domain/server, it kept failing with a message indicating that other software was in the process of installing or that a reboot was pending.  Since neither was the case, I downloaded the current version of the Connector
    software from the Microsoft website to try.  That didn't work either.  It turns out that a pre-installed software component called Intel Smart Connect Tech was keeping the laptop from connecting.  I uninstalled this software and installed the
    connector software and it appeared to connect to the server.  However, it is displayed in the Essentials Dashboard as Offline.  The client (Laptop) displays a message saying "The Windows Server 2012 Essentials Connector version that is installed
    on this computer is more recent that the sever.  Contact the administrator to ensure the server is up to date".  I tried uninstalling the Connector software from Control Panel, but I get a message "Could not delete key \software\microsoft\windows
    server.  Verify that you have sufficient access to that key, or contact your support personnel".  I've tried both with domain admin and local admin credentials.  So, I ignored the message and continued the connector install.  It finished
    and appeared to connect successfully.  The connector version displayed in Control Panel\Programs and Features is correct.  However, the registry entry is not updated and the version error pops up with each login and the Dashboard shows the client
    as offline. 

    Hi C.R.Lowe,
    Based on your description, I’m a little confused with this issue. Before going further, would you please let
    me confirm something more? Thanks for your understanding.
    When connect the client to Windows Server 2012 Essentials, did you mean that use
    http://<servername>/Connect
    and then select Download software for Windows option? More descriptions, please refer to the following article.
    To connect a client computer to the
    server
    If I misunderstand, please don’t hesitate to let me know.
    On current situation, please navigate to the registry path as the error message shows. And check
    Version value and let me know. Meanwhile, please right click
    Windows Server folder in Registry Editor and select “Permissions…”, then check if the account was assigned the correct permission to delete key.
    In addition, please check if you have installed the
    Update Rollup 1 for Windows Server 2012 Essentials
    By the way, please check Event Viewer and some related logs if can find some more clues. If any update, please
    feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

    Hi,
    I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
    http://technet.microsoft.com/en-us/library/jj200112.aspx
    I have looked at other threads on the forum but none of them have been too helpful.
    The issue: When
    I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
    Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
    The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
    Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration? 
    On running the Microsoft IT Environment Health Scanner tool it
    reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
    But it did not remove the errors.
    Other steps performed:
    As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
    On running the Best Practices Analyser. It shows 3 warnings.
    - The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
    - Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
    - The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
    I also ran the Ran netdiag.exe, dcdiag.exe commands
    and no failures were reported.
    The Event Viewer does not show any errors.
    Not sure to what extent these warnings would affect the migration. 
    Any help would be appreciated. Thanks!

    The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first.  See:
    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
    -- Al

  • Clients Backup on Server 2012 Essentials Encrypted?

    Hello, I would like to backup a client running win 7 ultimate, with encryption and bit locker enabled onto Server 2012 Essential.
    I am just wondering if the backup on the server will continue to be encrypted? If not is there a way to keep the backup secure? Thanks!

    Let me just check that I understand.
    The Windows 7 Client is Bitlocker Encrypted
    The 2012 Essentials is Bitlocker Encrypted.
    My understanding of BitLocker is limited, but as I believe it only protects the machine when it is offline, ie, protects from someone attempting to put the drive(s) in another machine and access the data, or before Windows has booted.
    In that respect, the backups are protected.
    The backups themselves are stored in a database which is only accessible/useable by Essentials, it is not a normal WindowsImageBackup type folder. However that Client Backup folder can be moved to another essentials Server and effectively compromised, however
    this would need to be done either from a running server that someone gained access to, or by copying the data while windows is offline, see above on that.
    So really it is a question of what you are trying to mitigate. Is it an internal attacker who restores data they should not have access to? (requires admin permissions)
    Or is it someone stealing a computer?
    You can of course backup the server to Bitlocker Enabled drives.
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • SQL Server 2012 Express SP1 will not install on Windows Server 2012 Essentials R2

    I have been attempting to install SQL Server 2012 with SP1 Express Edition for about a two weeks and have been unsuccessful.  My organization recently purchased a new Dell PowerEdge T320 Server (64 Bit) with Intel Xeon Proc.-E5-2420; 2.2Ghz, 32 Gb RAM,
    1 Tb RAID 5 H/D, and Windows Server 2012 R2 Essentials (preinstalled).  The server will be configured as an on premises server.  We are running a small church management application that requires SQL Server 2012 SP1 Express.  Per the direction
    of our application vendor, we downloaded the SQL Server 2012 SP1 Express file (SQLEXPRADV_x64_ENU.exe) from the Microsoft SQL Server Website.  We ran the file "As Administrator" and the SQL Server 2012 Setup program began. 
    We selected New SQL Server Stand-Alone Installation, successfully installed the needed Product Updates, and accepted the MS SQL Server 2013 Express License terms. 
    When the Feature Selection Page appeared we checked only the "Data Base Eng Services".  The
    Instance Configuration Page was displayed and we inserted a "Named Instance= Shelby",then pressed next.  On the
    Server Configuration Page the only change was setting the "sql server browser = automatic".  The Database Engine Configuration Page appeared
    and we inserted the following settings:1] Server Configuration Tab; a) mixed mode, b)inserted SQL Server Admin pswd, c) added current user as administrator: 2] Data Directories Tab; default/no changes: 3] User Instanced Tab; default/no
    changes: and 4] Filestream Tab; default/no changes.  Next the
    Reporting Services Configuration Page came up and the reporting services native mode was set to
    "install and configure".  The Error Reporting Page appeared and was left as the
    "default".  The SQL Server 2012 Setup program proceeded to Installation Progress Page and started to install. Just before the install program ended it displayed a message saying that there
    were errors and the Database Eng Services did not succeed. I uninstalled SQL Server 2012 SP1 Express three (3) times, ran Windows Update after every uninstall, attempted to install the Database Engine and got the same results.  Are there any patches or
    special procedures for correctly installing SQL Server 2012 SP1 Express on my hardware configuration or Windows Server 2012 Essentials R2?  Any insight would be greatly appreciated.

    Can you post the setup Summary and detail logs, which will help to figure out the problem? The details about the location can be found at https://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx
    Satish Kartan www.sqlfood.com

Maybe you are looking for