none
Cannot connect this computer to the network. The server is not available.

    Question

  • At home I have a Windows Server 2012 Essentials server (not R2), with all security updates installed, and in the past I have installed the connector software for Windows Server Essentials on all my PC’s and portables.

    At the time there was no problem connecting the workstations to the server with the connector software.

     

    Now I have a new MS Surface Pro 4 (a replacement under warranty for a connected Surface Pro 4) and I cannot connect the replacement system with the server anymore.

    The connector seems to be working because I get several screens (finding server, getting started, username and password selection) but after I have entered the username and password I get the following error: Cannot connect this computer to the network. The server is not available. Try connecting this computer again, or for more information, see Troubleshoot connecting computers to the server.

     

    On the server I have run the troubleshooter from Robert Pearman (https://windowsserveressentials.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter) and that does not report any errors.

     

    On the workstation I have found the following logs (in the folder C:\ProgramData\Microsoft\Windows Server\Logs) after the connector has run:

    ClientDeploy.log

    ---------------------------------------------------------

    [3180] 180704.225854.8316: ClientSetup: Start of ClientDeploy

    [3180] 180704.225854.9645: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe

    [3180] 180704.225854.9827: ClientSetup: Loading Wizard Data

    [3180] 180704.225855.0295: ClientSetup: Current DeploymentStatus=Running

    [3180] 180704.225855.7936: ClientSetup: Showing the Client Deployment Wizard

    [3180] 180704.225856.2881: ClientSetup: Adding Server Info data in the Product Registry

    [3180] 180704.225856.3212: ClientSetup: Set the Deployment Sync Event

    [10176] 180704.225906.5180: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred

    [10176] 180704.225906.5278: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [10176] 180704.225906.5422: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask

    [10176] 180704.225906.5519: ClientSetup: Entering InstallRootCertTask.Run

    [10176] 180704.225906.5882: ClientSetup: Install root cert to local trusted store

    [10176] 180704.225906.6173: ClientSetup: Exiting InstallRootCertTask.Run

    [10176] 180704.225906.6183: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success

    [10176] 180704.225906.6183: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot

    [10176] 180704.225906.6183: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [10176] 180704.225906.6183: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred

    [10176] 180704.225906.6193: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [10176] 180704.225906.6193: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask

    [10176] 180704.225906.6235: ClientSetup: Entering SetupVpnAndDATask.Run

    [10176] 180704.225906.7393: ClientSetup: Exting SetupVpnAndDATask.Run

    [10176] 180704.225906.7393: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success

    [10176] 180704.225906.7393: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot

    [10176] 180704.225906.7393: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [10176] 180704.225906.7393: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred

    [10176] 180704.225906.7414: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [10176] 180704.225906.7424: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser

    [10176] 180704.225906.7550: ClientSetup: Entering ValidateUserTask.Run

    [10176] 180704.225906.7562: ClientSetup: Validating User

    [10176] 180704.225906.7562: ClientSetup: Call MachineIdentityManager.GetMachineStatus

    [10176] 180704.225908.1279: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1

    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

     

    Server stack trace:

       bij System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)

       bij System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

       bij System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

       bij System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

       bij System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

     

    Exception rethrown at [0]:

       bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

       bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

       bij Microsoft.WindowsServerSolutions.Devices.Identity.ICertService.GetMachineStatus(MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum, String userName, String password, String machineName)

       bij Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)

       --- Einde van intern uitzonderingsstackpad ---

       bij Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)

       bij Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)

    [10176] 180704.225908.1299: ClientSetup: Exiting ValidateUserTask.Run

    [10176] 180704.225908.1299: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed

    [10176] 180704.225908.1299: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot

    [10176] 180704.225908.1299: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [3180] 180704.225908.1526: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed

    [3180] 180704.230520.3360: ClientSetup: Back from the Client Deployment Wizard

    [3180] 180704.230520.5604: ClientSetup: Saving Wizard Data

    [3180] 180704.230520.8919: ClientSetup: End of ClientDeploy: ErrorCode=1603

     

    Computerconnector.log

    [07/04/2018 22:58:44 1d28] --------------------------------------------------------------------------------------------------

    [07/04/2018 22:58:44 1d28] wmain: Start of Computerconnector

    [07/04/2018 22:58:44 1d28] wmain: Calling Computerconnector::ShowWizard()

    [07/04/2018 22:58:44 1d28] CComputerconnector::ShowWizard: Initializing common controls

    [07/04/2018 22:58:44 1d28] CComputerconnector::ShowWizard: Done initializing common controls

    [07/04/2018 22:58:44 1d28] Displaying the wizard

    [07/04/2018 22:58:44 1d28] CComputerconnector::AnotherInstallationErrorDlgProc: IDD_ANOTHER_INSTALLATION_ERR Page Initialization

    [07/04/2018 22:58:44 1f90] CComputerconnector::Run: Installation is ready to run

    [07/04/2018 22:58:44 1f90] GlobalData::Initialize (192.168.0.190, , C:\Users\marij\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\TempState\Downloads\ComputerConnector(192.168.0.190) (3).exe, 1043)

    [07/04/2018 22:58:44 1f90] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\Client Deployment Files\)

    [07/04/2018 22:58:44 1f90] CComputerconnector::Run: Running Task: Id=1 Description=Downloads the Setup.cab file

    [07/04/2018 22:58:44 1f90] NetworkUtil::DownloadFile (https://192.168.0.190:443/Connect/default.aspx?Get=Setup.cab&64bit=1&LanguageId=1043, C:\Users\marij\AppData\Local\Temp\Setup.cab)

    [07/04/2018 22:58:44 1f90] NetworkUtil::DownloadFile - Create directory [C:\Users\marij\AppData\Local\Temp] if not exist.

    [07/04/2018 22:58:44 1f90] NetworkUtil::_WinInetDownloadFile (https://192.168.0.190:443/Connect/default.aspx?Get=Setup.cab&64bit=1&LanguageId=1043, C:\Users\marij\AppData\Local\Temp\Setup.cab)

    [07/04/2018 22:58:44 1d28] CComputerconnector::AnotherInstallationErrorDlgProc: DIALOG_UPDATE: PreCheckPass

    [07/04/2018 22:58:44 1d28] CComputerconnector::ConnecttingDlgProc: IDD_CONNECTING Page Initialization

    [07/04/2018 22:58:44 1f90] InternetOpenUrl (https://192.168.0.190:443/Connect/default.aspx?Get=Setup.cab&64bit=1&LanguageId=1043) returns 12038

    [07/04/2018 22:58:44 1f90] _WinInetDownloadFile returns 0x80072f06.

    [07/04/2018 22:58:44 1f90] DownloadFile failed using https. Try http.

    [07/04/2018 22:58:44 1f90] NetworkUtil::DownloadFile (http://192.168.0.190:80/Connect/default.aspx?Get=Setup.cab&64bit=1&LanguageId=1043, C:\Users\marij\AppData\Local\Temp\Setup.cab)

    [07/04/2018 22:58:44 1f90] NetworkUtil::DownloadFile - Create directory [C:\Users\marij\AppData\Local\Temp] if not exist.

    [07/04/2018 22:58:44 1f90] NetworkUtil::_WinInetDownloadFile (http://192.168.0.190:80/Connect/default.aspx?Get=Setup.cab&64bit=1&LanguageId=1043, C:\Users\marij\AppData\Local\Temp\Setup.cab)

    [07/04/2018 22:58:47 1f90] ExtractCabinet: Extract (C:\Users\marij\AppData\Local\Temp\Setup.cab, C:\WINDOWS\Temp\Client Deployment Files\)

    [07/04/2018 22:58:48 1f90] SetRegValue [C:\WINDOWS\Temp\Client Deployment Files\].

    [07/04/2018 22:58:48 1f90] Deleting [C:\Users\marij\AppData\Local\Temp\Setup.cab].

    [07/04/2018 22:58:48 1f90] RunShellExecute: ShellExecute [C:\WINDOWS\Temp\Client Deployment Files\CSetup.exe] with parameters [(null)]

    [07/04/2018 22:58:48 1f90] CSetup::Run: Waiting upto 30secs for Sync Event to be signaled

    [07/04/2018 22:58:49 1f90] CComputerconnector::Run: WaitForSingleObject RetVal = 0

    [07/04/2018 22:58:49 1d28] CComputerconnector::ConnecttingDlgProc: DIALOG_UPDATE: Success

    [07/04/2018 22:58:49 1d28] wmain: End of Computerconnector: hr=0x0

     

    CSetup.log

    [07/04/2018 22:58:48 1968] --------------------------------------------------------------------------------------------------

    [07/04/2018 22:58:48 1968] wmain: Start of CSetup

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: HPMICROSERVER

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: Intranet

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: 192.168.0.190

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: 50

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: Administrator

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: en-US

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: 1033

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: DOMAINDILAVA

    [07/04/2018 22:58:48 1968] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:48 1968] CServer::GetNodeValue - SysAllocString value: http://192.168.0.190:80

    [07/04/2018 22:58:48 1968] GlobalData::Initialize (192.168.0.190, http://192.168.0.190:80, C:\WINDOWS\Temp\Client Deployment Files\CSetup.exe, 1033)

    [07/04/2018 22:58:48 1968] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\Client Deployment Files\)

    [07/04/2018 22:58:48 1968] wmain: Calling CSetup::ShowWizard()

    [07/04/2018 22:58:48 1968] CSetup::ShowWizard: Initializing common controls

    [07/04/2018 22:58:48 1968] CSetup::ShowWizard: Done initializing common controls

    [07/04/2018 22:58:48 1968] Displaying the wizard

    [07/04/2018 22:58:49 1968] CSetup::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Initialization

    [07/04/2018 22:58:49 1968] CSetup::WelcomeDlgProc: Set the Deployment Sync Event

    [07/04/2018 22:58:53 1968] CSetup::RunTasksDlgProc: IDD_PROPPAGE_TASKS Page Initialization

    [07/04/2018 22:58:53 101c] CSetup::Run: Deployment Stage = DeploymentStage_VerifyingRequirements

    [07/04/2018 22:58:53 101c] CSetup::RunTasks: Running Task: Id=-1 Description=Check OS Version and SP Index=  0

    [07/04/2018 22:58:53 101c] OsChecker::CreateInstance ([C:\WINDOWS\Temp\Client Deployment Files\SupportedOs.Xml])

    [07/04/2018 22:58:53 101c] =================================

    [07/04/2018 22:58:53 101c] Current Os information:

    [07/04/2018 22:58:53 101c] Suite = [256]

    [07/04/2018 22:58:53 101c] Type = [1]

    [07/04/2018 22:58:53 101c] Architecture = [9]

    [07/04/2018 22:58:53 101c] IsStarterEdition = [0]

    [07/04/2018 22:58:53 101c] IsHomeSku = [0]

    [07/04/2018 22:58:53 101c] Major = [6]

    [07/04/2018 22:58:53 101c] Minor = [2]

    [07/04/2018 22:58:53 101c] Build = [9200]

    [07/04/2018 22:58:53 101c] SPMajor = [0]

    [07/04/2018 22:58:53 101c] SPMinor = [0]

    [07/04/2018 22:58:53 101c] =================================

    [07/04/2018 22:58:53 101c] OSRule::CreateRules  (C:\WINDOWS\Temp\Client Deployment Files\SupportedOs.Xml, .)

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] OsChecker::QuerySupportedOsStatus - Major: 6 Minor: 2

    [07/04/2018 22:58:53 101c] CSetup::RunTasks: Running Task: Id=-1 Description=Check Net Join Index=  1

    [07/04/2018 22:58:53 101c] NetJoinChecker::CreateInstance ([C:\WINDOWS\Temp\Client Deployment Files\ServerInfo.Xml])

    [07/04/2018 22:58:53 101c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1

    [07/04/2018 22:58:53 101c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1

    [07/04/2018 22:58:53 101c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: HPMICROSERVER

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: Intranet

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: 192.168.0.190

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: 50

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: Administrator

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: en-US

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: 1033

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: DOMAINDILAVA

    [07/04/2018 22:58:53 101c] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - selectSingleNode

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_firstChild

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - get_nodeValue

    [07/04/2018 22:58:53 101c] CServer::GetNodeValue - SysAllocString value: http://192.168.0.190:80

    [07/04/2018 22:58:53 101c] Checking self-test hook...  2  0

    [07/04/2018 22:58:53 101c] NetJoinChecker::QueryNetJoinStatus - Joining a Sbs server

    [07/04/2018 22:58:53 101c] NetJoinChecker::QueryNetJoinStatus - Not Domain Joined

    [07/04/2018 22:58:53 101c] CSetup::RunTasks: Running Task: Id=-1 Description=Check Pending Reboot Index=  2

    [07/04/2018 22:58:53 1968] CSetup::JoinComputerDlgProc: IDD_PROPPAGE_JOIN_COMPUTER Initialization

    [07/04/2018 22:58:54 1968] CSetup::RunTasksDlgProc: IDD_PROPPAGE_TASKS Page Initialization

    [07/04/2018 22:58:54  d00] CSetup::Run: Deployment Stage = DeploymentStage_InstallingPreRequistes

    [07/04/2018 22:58:54  d00] CSetup::RunTasks: Running Task: Id=-1 Description=Check DotNet Fwk Index=  0

    [07/04/2018 22:58:54  d00] DotnetRule::CreateRules  (C:\WINDOWS\Temp\Client Deployment Files\SupportedOs.Xml, .)

    [07/04/2018 22:58:54  d00] CoCreateInstance CLSID_DOMDocument60 succeeded.

    [07/04/2018 22:58:54  d00] DotNet::QueryInstallState - The installed .NET framework version is 4.7.

    [07/04/2018 22:58:54  d00] CSetup::RunTasks: Running Task: Id=4 Description=Download Dot Net Index=  1

    [07/04/2018 22:58:54  d00] CSetup::RunTasks: Running Task: Id=5 Description=Install Dot Net Index=  2

    [07/04/2018 22:58:54  d00] RunShellExecute: ShellExecute [C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe] with parameters [(null)]

    [07/04/2018 22:58:54  d00] CSetup::Run: Waiting upto 60secs for Sync Event to be signaled

    [07/04/2018 22:58:56  d00] CSetup::Run: WaitForSingleObject RetVal = 0

    [07/04/2018 22:58:56 1968] wmain: End of CSetup: hr=0x0

     

    Any idea what goes wrong?
    Wednesday, July 4, 2018 9:23 PM

Answers

  • I have run the 5 steps in the article: https://support.microsoft.com/nl-be/help/2828269/the-web-configuration-file-may-become-corrupted-when-you-run-the-sfc-c and restarted te server.

    After that I could add the 2 systems to the server. Finally!!!

    Robert, thanks for all the support and for the ultimate tip in the right direction!


    Saturday, July 14, 2018 2:03 PM

All replies

  • ClientDeploy.log
    ErrorCatalog:NetworkError ErrorCode:-1
    ClientSetup: End of ClientDeploy: ErrorCode=1603
    From your information of ClientDeploy.log ,it is network problem,and errorcode=1603 tell that this problem is very serious during Client deploy。
    You can do a test in command prompt and ping your wse2012 server name on new MS Surface Pro 4 ,and see if the return information is relevant to ipv6.if it is yes, disable the ipv6 on client first.

    There are some suggestions:
    1verify logon AD user account is enable now
    2 verify new computer name is not the same as old MS Surface Pro 4 
    3 Synchronize client time and time zone with wse2012 server
    4 uninstall old the framework and it will be reinstall when the client is installed connector computer software.
    5 Copy logs file to another partition and clear old log file which is in the C:\ProgramData\Microsoft\Windows Server\Logs
    6 uninstall essential connector software and restart your computer
    7 reinstall computer connector software again
    If problem is still exist, please the supply ClientDeploy.log ,Computerconnector.log,CSetup.log again and system version on MS Surface Pro 4(enter winver in command prompt ). 

    You also can refer these solutions in Forums.
    https://social.technet.microsoft.com/Forums/en-US/b6eab6b0-5c4e-433b-97a4-e3d7ad6985fe/cannot-connect-this-computer-to-the-network-the-server-is-not-available

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


    Thursday, July 5, 2018 6:23 AM
  • Thanks for the response.

    What do you mean with "verify logon AD user account"?

    Is this on the server or the workstation?

    Thursday, July 5, 2018 7:03 AM
  • Run this on your server please.

    https://gallery.technet.microsoft.com/Password-Expiry-Email-177c3e27?redir=0


    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 5, 2018 9:52 AM
    Moderator
  • Robert,

    Is your suggestion related to my original problem or to my question to Andy?

    Has password expiration anything to do with my problems?

    Thursday, July 5, 2018 3:01 PM
  • Your original question.

    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 5, 2018 4:02 PM
    Moderator
  • Robert, I have run your script, hereby the result:

    cmdlet PasswordChangeNotification.ps1 at command pipeline position 1
    Supply values for the following parameters:
    smtpServer: XXX.XXX
    expireInDays: 30
    from: XXX.XXX@XXX.XXX
    Script Loaded
    *** Settings Summary ***
    SMTP Server          : XXX.XXX
    Expire in Days       : 30
    From                 : XXX.XXX@XXX.XXX
    Logging              : False
    Log Path             :
    Testing              : False
    Test Recipient       :
    Report Recipient     :
    Intervals            :
    *************************
    Found 5 User Objects
    Domain Default Password Age: 0
    Process User Objects
    5 Users processed
    5 Users with expiring passwords within 30 Days

    UserName Name    EmailAddress PasswordSet         DaysToExpire ExpiresOn
    -------- ----    ------------ -----------         ------------ ---------
    1111     1111                 10/11/2013 23:31:59        -1698 10/11/2013 23:31:59
    2222222  2222222              10/11/2013 23:32:26        -1698 10/11/2013 23:32:26
    333      333                  10/11/2013 13:02:20        -1698 10/11/2013 13:02:20
    44       44                   10/11/2013 23:31:25        -1698 10/11/2013 23:31:25
    5555555  5555555              11/11/2013 15:36:36        -1697 11/11/2013 15:36:36

    All passwords are expired.

    In the past I have changed the setting on the server so that the passwords never expire.

    That is shown when I run a 'net user <username> /domain'

    I didn't know this setting could give problems.

    What have I got to do next?

    It is the '2222222' user that I'm setting up the system for.

    Thursday, July 5, 2018 7:23 PM
  • Im really sorry i sent you the wrong link.

    https://gallery.technet.microsoft.com/Windows-Server-Essentials-556159c3?redir=0

    This is the one i meant to send!


    Robert Pearman @titlerequired Windows Server Essentials.com

    Friday, July 6, 2018 6:20 AM
    Moderator
  • No problem, I have already run your troubleshooter (tasks 1 and 2) as indicated in my original post.

    hereby the results:

    ************************************************

    * Essentials Server Configuration Tester *

    ************************************************

     

    OS Detected: Microsoft Windows Server 2012 Essentials

     

    This tool will check your current Configuration against known Essentials Server Values.

    Written by Robert Pearman (TitleRequired.com) January 2018

     

    Version Info: Version: 2.10

     

    1. Test IIS

    2. Test CA Infrastructure

    3. Test Services

    4. Test Service Ports

    0. Quit

     

    Enter Task..

    1

    Only Errors will be shown.

     

    Checking Websites..

     

    Checking Connect Site..

     

    Checking Virtual Directories..

     

    Checking AppPools..

     

    Checking ISAPI Filters..

     

    Checking IIS SSL..

     

    Checking TLS Version 1.0

     

    Checking IIS Bindings..

     

    Checking IIS Authentication..

     

    Review your results, items in red should be investigated.

     

    ************************************************

    * Essentials Server Configuration Tester *

    ************************************************

     

    OS Detected: Microsoft Windows Server 2012 Essentials

     

    This tool will check your current Configuration against known Essentials Server Values.

    Written by Robert Pearman (TitleRequired.com) January 2018

     

    Version Info: Version: 2.10

     

    1. Test IIS

    2. Test CA Infrastructure

    3. Test Services

    4. Test Service Ports

    0. Quit

     

    Enter Task..

    2

    Testing CA Name..

    Certificate Authority Online  : OK

    Certificate Authority Name    : OK

    Certificate Authority Cert    : OK

     

    Testing /Connect Certificate Package..

    Connect Computer Certificate  : OK

     

    Testing CRL Download..

    CRL Location                  : http://HPMICROSERVER/CertEnroll/DOMAINDILAVA-HPMICROSERVER-CA.crl

    CRL Destination               : c:\windows\temp\crl.crl

    CRL Download                  : OK

     

    Testing CRL Distribution Configuration..

    419.6169.0:<2018/7/4, 20:07:28>: 0x80070002 (WIN32: 2)

    437.2144.0:<2018/7/4, 20:07:28>: 0x80070002 (WIN32: 2)

     

    It is normal to see some 'File Not Found' messages above when using this CmdLet (Get-CACrlDistributionPoint)

     

    CRL Extension (CDP)           : OK

    CRL Extension (CRL)           : OK

     

    Testing Dashboard Certificate..

    Current Dashboard Certificate : CFE48266520CCF8C149D47613A5DC4C7CAC1FB3A

    Dashboard Certificate         : OK

     

    Review your results, items in red should be investigated.

    Friday, July 6, 2018 6:37 AM
  • Sorry - did not see that.

    Can you run the other tests as well?

    Are you connected via ethernet or wifi?


    Robert Pearman @titlerequired Windows Server Essentials.com

    Friday, July 6, 2018 7:18 AM
    Moderator
  • Until now I have connected wia wifi. This evening (Belgium time) I will try it via ethernet.

    Hereby the results of tasks 3 and 4:

    ************************************************

    * Essentials Server Configuration Tester *
    ************************************************

    OS Detected: Microsoft Windows Server 2012 Essentials

    This tool will check your current Configuration against known Essentials Server Values.

    Written by Robert Pearman (TitleRequired.com) January 2018

    Version Info: Version: 2.10
    1. Test IIS
    2. Test CA Infrastructure
    3. Test Services
    4. Test Service Ports
    0. Quit
    Enter Task..
    3
    Testing Services on:  HPMICROSERVER
    Active Directory Certificate Services         : Running Auto
    WSS Addins Infrastructure Service             : Running Auto
    WSS Client Computer Backup Provider Service   : Running Auto
    WSS Client Computer Backup Service            : Running Auto
    WSS Client File Backup Provider Service       : Running Auto
    WSS Devices Provider                          : Running Auto
    WSS Domain Name Management                    : Running Auto
    WSS Health Service                            : Running Auto
    WSS Hosted Email Service                      : Stopped Disabled
    WSS Identity Management Service               : Running Auto
    WSS Initialization Service                    : Running Auto
    WSS Media Streaming Service                   : Running Auto
    WSS Networking Helper Service                 : Running Auto
    WSS Notifications Provider Service            : Running Auto
    WSS Office 365 Integration Service            : Stopped Disabled
    WSS On-Premises Exchange Integration Service  : Stopped Disabled
    WSS Password Synchronization Service          : Stopped Disabled
    WSS Remote Connection Management Service      : Running Auto
    WSS Remote Web Access Administration Provider : Running Auto
    WSS Server Backup Service                     : Running Auto
    WSS Service Provider Registry                 : Running Auto
    WSS Settings Provider                         : Running Auto
    WSS SQM Service                               : Running Auto
    WSS Storage Service                           : Running Auto
    WSS UPnP Device Service                       : Running Auto

    Review your results, items in red should be investigated.

    ************************************************
    * Essentials Server Configuration Tester *
    ************************************************
    OS Detected: Microsoft Windows Server 2012 Essentials
    This tool will check your current Configuration against known Essentials Server Values.
    Written by Robert Pearman (TitleRequired.com) January 2018
    Version Info: Version: 2.10
    1. Test IIS
    2. Test CA Infrastructure
    3. Test Services
    4. Test Service Ports
    0. Quit
    Enter Task..
    4
    Testing Service Ports on :  HPMICROSERVER
    TCP 80 (Used for Websites)       : OK
    TCP 443 (Used for Websites)      : OK
    TCP 6602 (Used for Status)       : OK
    TCP 8912 (Used for Backups)      : OK
    TCP 65520 (Used for Mac Website) : OK
    TCP 65500 (Used for CA Website)  : OK
    Review your results, items in red should be investigated.

    Friday, July 6, 2018 11:41 AM
  • What OS is the client in question?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Friday, July 6, 2018 12:22 PM
    Moderator
  • Edition: Windows 10 Pro

    Version: 1803

    OS Build: ??? -> up-to-date (don't have the system by the hand to see the correct buildn°)

    Friday, July 6, 2018 12:28 PM
  • And the server is fully patched?

    The client connector install file, what version is that?



    Robert Pearman @titlerequired Windows Server Essentials.com

    Friday, July 6, 2018 2:05 PM
    Moderator
  • Hereby the requested versions

    Server
    Microsoft Windows Server 2012 Essentials
    2018-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4284855) installed

    Workstation
    Edition: Windows 10 Pro
    Version: 1803
    OS Build:17134.137

    Computer Connector Software
    6.2.9805.0

    I now have run the connector software via wifi and via ethernet, same result.

    Friday, July 6, 2018 11:05 PM
  • Just going to set this up in my lab.

    Robert Pearman @titlerequired Windows Server Essentials.com

    Monday, July 9, 2018 9:22 AM
    Moderator
  • Do you have any third party software installed on the server, any Essentials Addins?


    Robert Pearman @titlerequired Windows Server Essentials.com

    Monday, July 9, 2018 4:54 PM
    Moderator
  • Nope.
    Monday, July 9, 2018 5:00 PM
  • Can you confirm the version number of 'ClientDeploy.exe' in the folder:

    c:\program files\Windows Server\Bin\WebApps\Client\Package


    Robert Pearman @titlerequired Windows Server Essentials.com

    Monday, July 9, 2018 5:15 PM
    Moderator
  • Hereby the content of the "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\" folder on the server:

    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\en"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\nl"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\pt"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\resources"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\sv"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\tr"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\x86""C:\Program Files\Windows Server\Bin\WebApps\Client\Package\ClientDeploy.exe" Product version 6.2.9805.6
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\ClientDeploy.exe.config"
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\CSetup.exe" Product version 6.2.9805.0
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\dotNetFx45_Full_x86_x64.exe" Product version 4.5.50709.17929
    "C:\Program Files\Windows Server\Bin\WebApps\Client\Package\supportedOS.xml"

    Monday, July 9, 2018 7:55 PM
  • Can you provide all the logs from the c:\programdata\microsoft\windows server\logs folder on the client pc?

    I have just rebuilt a Server 2012 Essentials (Fully Patched) and Win 10 1803, and don't have any issue.


    Robert Pearman @titlerequired Windows Server Essentials.com

    Tuesday, July 10, 2018 6:59 AM
    Moderator
  • I have deleted all the files in c:\programdata\microsoft\windows server\logs folder on the client pc and rerun the connector software. You can find the logs on my Onedrive via https://1drv.ms/u/s!At-A7Tk_voOS1cZfGQFNSjzPntrHBg
    • Edited by JanDidden1 Tuesday, July 10, 2018 4:15 PM
    Tuesday, July 10, 2018 4:14 PM
  • Are there any errors in the server event logs around the same time as the failure on the client?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Wednesday, July 11, 2018 10:24 AM
    Moderator
  • On the server there are no errors in the Windows logs.

    But there is an error in the 'Applications and Services Logs' every time the connector software is run on the client PC.

    Under Microsoft\Windows\Application Server-Applications\Operational there is the following error:

    Level Date and Time Source Event ID Task Category
    Error 11/07/2018 19:52:49 Microsoft-Windows-Application Server-Applications 57405 None "Handling an exception. Exception details: System.IO.FileNotFoundException: Could not load file or assembly 'IdentityManaged, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
    File name: 'IdentityManaged, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
       at CertWebService.CertService.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
       at SyncInvokeGetMachineStatus(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    "

    On my Onedrive you can find a ZIP-file with the same error in evtx- and txt-format via the link https://1drv.ms/u/s!At-A7Tk_voOS1cZmaqFE2tPsqGcWaw

    Wednesday, July 11, 2018 6:11 PM
  • Is it just this one client that wont join? Do you have any others you can test?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 12, 2018 9:04 AM
    Moderator
  • I have the same problem with a Surface 3 since last year, but that system is not as critical as this one. At the time I have commented on your website, see https://windowsserveressentials.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter/#comment-48610

    When I run the connector software now again on the Surface 3, I get the same error, see below:

    Level Date and Time Source Event ID Task Category

    Error 12/07/2018 18:13:43 Microsoft-Windows-Application Server-Applications 57405 None "Handling an exception. Exception details: System.IO.FileNotFoundException: Could not load file or assembly 'IdentityManaged, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
    File name: 'IdentityManaged, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
       at CertWebService.CertService.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
       at SyncInvokeGetMachineStatus(Object , Object[] , Object[] )
       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    "

    On my Onedrive you can find a ZIP-file with the same error in evtx- and txt-format of the Surface 3 via the link https://1drv.ms/u/s!At-A7Tk_voOS1cZp-S52cDobatXqsQ

    Thursday, July 12, 2018 4:31 PM
  • Can you go to https://yourservername and see if it connects?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 12, 2018 4:36 PM
    Moderator
  • No it does not connect on those systems, but it also doesn't connect on my connected systems.

    Hereby the error:

    Server Error in '/' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="Off"/>
        </system.web>
    </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
        </system.web>
    </configuration>

    Thursday, July 12, 2018 6:07 PM
  • Can you change the code there to enable errors to display?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 12, 2018 6:48 PM
    Moderator
  • I have gone to https://yourservername on the server.

    There i got the following error.
    Is that enough or do I have to change the code?

    Server Error in '/' Application.


    Could not load file or assembly 'Wssg.Web.Internal, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Wssg.Web.Internal, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    Source Error:
    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

    1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

      <%@ Page Language="C#" Debug="true" %>

    or:

    2) Add the following section to the configuration file of your application:

    <configuration>
       <system.web>
           <compilation debug="true"/>
       </system.web>
    </configuration>

    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

    Assembly Load Trace: The following information can be helpful to determine why the assembly 'Wssg.Web.Internal, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    

    Stack Trace:
    [FileNotFoundException: Could not load file or assembly 'Wssg.Web.Internal, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
       Microsoft.WindowsServerSolutions.Web.RootSite._Default.InitializeCulture() +0
       ASP.default_aspx.__BuildControlTree(default_aspx __ctrl) +29
       ASP.default_aspx.FrameworkInitialize() +35
       System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +52
       System.Web.UI.Page.ProcessRequest() +75
       System.Web.UI.Page.ProcessRequest(HttpContext context) +70
       System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +498
       System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +195
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +88
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2623.0         

    Thursday, July 12, 2018 7:23 PM
  • I think that is pointing us to the issue.

    Are you able to track down that file?


    Robert Pearman @titlerequired Windows Server Essentials.com

    Thursday, July 12, 2018 7:34 PM
    Moderator
  • A Google search relating to the problem found the following article: https://support.microsoft.com/nl-be/help/2828269/the-web-configuration-file-may-become-corrupted-when-you-run-the-sfc-c

    I cannot remember that i have run the SFC command in the past, but it is possible.

    Could this be the problem?

    Thursday, July 12, 2018 10:19 PM
  • Yes it could, can you check if the solution applies to your server?

    Robert Pearman @titlerequired Windows Server Essentials.com

    Friday, July 13, 2018 8:03 AM
    Moderator
  • I have run the 5 steps in the article: https://support.microsoft.com/nl-be/help/2828269/the-web-configuration-file-may-become-corrupted-when-you-run-the-sfc-c and restarted te server.

    After that I could add the 2 systems to the server. Finally!!!

    Robert, thanks for all the support and for the ultimate tip in the right direction!


    Saturday, July 14, 2018 2:03 PM
  • Cool.

    I have updated my tester to include a check for this error.


    Robert Pearman @titlerequired Windows Server Essentials.com

    Saturday, July 14, 2018 2:32 PM
    Moderator