locked
WHS 2011 Client Connect on Windows 7 Home 64 bit RRS feed

  • Question

  • I am unable to connect one of my Windows 7 home 64 bit clients to WHS 2011.

    I read the other postings and have tried:

    • reinstalling .Net 4.0
    • turning on the services for MC Scheduler service and MC Receiver Service
    • uninstalling Media centre
    • running the client connect as admin

    The error from the log says its looking for a module, but does not specifiy which one.

    The error from the log files is as follows.

    [4472] 120822.064814.6167: ClientSetup: Running Network Join
    [4472] 120822.064814.6167: ClientSetup: Call MachineIdentity.GetCert
    [4472] 120822.064821.4371: ClientSetup: Exiting JoinNetworkTask.Run
    [4472] 120822.064821.4371: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
    [4472] 120822.064821.4371: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
    [4472] 120822.064821.4381: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [984] 120822.064821.4411: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
    [984] 120822.064821.5361: ClientSetup: !!!FATAL!!! Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. --->

    System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)

       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObject.Initialize(Boolean getObject)
       at System.Management.ManagementClass.GetInstances(EnumerationOptions options)
       at Microsoft.WindowsServerSolutions.ClientSetup.WMIHelper.GetPropertyValue(String computer, String classPath, String username, String password, String propertyName)
       at Microsoft.WindowsServerSolutions.ClientSetup.ComputerMgmt.GetLocalComputerDesc()
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.m_wizardPageComputerDescription_PageEnter(Object sender, EventArgs e)
       at Microsoft.WindowsServerSolutions.Wizards.WizardForm.set_CurrentPage(WizardPage value)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.SetNextPageAfterJoinNetwork(TaskStatus status)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.<>c__DisplayClassc.<m_wizardPageComputerAlreadyExists_PageValidating>b__b(Object worker, RunWorkerCompletedEventArgs completedEventArgs)
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Delegate.DynamicInvokeImpl(Object[] args)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Program.Main()

    Wednesday, August 22, 2012 2:32 PM

Answers

  • For any poor sole who has the same problem:

    Repairing the WMI repository was not successful.  I had to repair the win 7 installation.  The WHS Client install works fine now.

    • Marked as answer by TuxAndTails Friday, August 24, 2012 4:20 PM
    Friday, August 24, 2012 4:20 PM

All replies

  • Hi,

    At first, you need to check whether the server and client are both up-to-date. Then you could look into the Event Viewer to verify whether there are some related errors or warnings included on the affected client side.

    At the same time, you might need to look into the log file under the path "C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs" to verify the whether some other errors included in the computerconnector.log and CSetup.log.

    On the server side, you need to install the Windows Server Solutions Log Collector to have a check on the server side configurations, for details, there is a link for your reference:

    Title: Installing the Windows Server Solutions Log Collector

    URL: http://technet.microsoft.com/en-us/library/hh272672.aspx

    Any findings or any clues, please feel free to post back.

    Regards,

    James


    James Xiong

    TechNet Community Support

    Thursday, August 23, 2012 6:01 AM
  • Both server and client are up to date.  This is not an issue on other win7 and XP machines on the same network.

    No errors reported in the computerconnector.log and CSetup.log.

    No errors in client or server event log, other than the error shown above from the client setup log.

    The log collector collected over 100 logs - any in particular I should be looking at?

    In reading the log above, it shows the JoinTask successfully, then the failure right after.  What runs after JoinTask?

    Thursday, August 23, 2012 7:02 PM
  • In looking at the stack dump and at a log from a success win7 machine, there is the following:

    (1) it failed trying to run the Wizard Page

    (2) it failed trying to fetch the client computer description from WMI Helper

    (3) the System.Management was trying to initialize an assembly that could not be found.

    Thursday, August 23, 2012 10:48 PM
  • I reverse engineered the client setup code and found that its failing when calling WMI.  I wrote a small program and no WMI calls work properly on this machine.  I'll either have to repair the WMI repository or repair the OS.

    *sigh*

    • Marked as answer by TuxAndTails Friday, August 24, 2012 4:20 PM
    • Unmarked as answer by TuxAndTails Friday, August 24, 2012 4:20 PM
    Friday, August 24, 2012 1:31 AM
  • For any poor sole who has the same problem:

    Repairing the WMI repository was not successful.  I had to repair the win 7 installation.  The WHS Client install works fine now.

    • Marked as answer by TuxAndTails Friday, August 24, 2012 4:20 PM
    Friday, August 24, 2012 4:20 PM