none
Home Server Information Collector error on client PC RRS feed

  • Question

  • After, doing a reinstall of WHS on my server machine (to solve a lost connection problem during backups), I decided it was best to uninstall and reinstall the connector on my client PC's.  One of them now has an error.  When the PC boots up I get a "Home Server Information Collector error".  I tried uninstalling and reinstalling the connector several times but the error won't go away.

    The Event Viewer on my client PC shows an application error as follows:

    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1004
    Date:  2/22/2009
    Time:  8:22:59 PM
    User:  N/A
    Computer: HOME-DESKTOP-1
    Description:
    Faulting application ClientInfo.exe, version 6.0.1800.24, faulting module ClientInfo.exe, version 6.0.1800.24, fault address 0x00013bfd.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 43 6c 69   ure  Cli
    0018: 65 6e 74 49 6e 66 6f 2e   entInfo.
    0020: 65 78 65 20 36 2e 30 2e   exe 6.0.
    0028: 31 38 30 30 2e 32 34 20   1800.24
    0030: 69 6e 20 43 6c 69 65 6e   in Clien
    0038: 74 49 6e 66 6f 2e 65 78   tInfo.ex
    0040: 65 20 36 2e 30 2e 31 38   e 6.0.18
    0048: 30 30 2e 32 34 20 61 74   00.24 at
    0050: 20 6f 66 66 73 65 74 20    offset
    0058: 30 30 30 31 33 62 66 64   00013bfd

    If I can solve this one, I will be in good shape.  I appreciate any help you can give me.

    Thanks,
    Michael

    Monday, February 23, 2009 6:07 PM

All replies

  • MDwyer said:

    After, doing a reinstall of WHS on my server machine (to solve a lost connection problem during backups), I decided it was best to uninstall and reinstall the connector on my client PC's.  One of them now has an error.  When the PC boots up I get a "Home Server Information Collector error".  I tried uninstalling and reinstalling the connector several times but the error won't go away.

    The Event Viewer on my client PC shows an application error as follows:

    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1004
    Date:  2/22/2009
    Time:  8:22:59 PM
    User:  N/A
    Computer: HOME-DESKTOP-1
    Description:
    Faulting application ClientInfo.exe, version 6.0.1800.24, faulting module ClientInfo.exe, version 6.0.1800.24, fault address 0x00013bfd.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 43 6c 69   ure  Cli
    0018: 65 6e 74 49 6e 66 6f 2e   entInfo.
    0020: 65 78 65 20 36 2e 30 2e   exe 6.0.
    0028: 31 38 30 30 2e 32 34 20   1800.24
    0030: 69 6e 20 43 6c 69 65 6e   in Clien
    0038: 74 49 6e 66 6f 2e 65 78   tInfo.ex
    0040: 65 20 36 2e 30 2e 31 38   e 6.0.18
    0048: 30 30 2e 32 34 20 61 74   00.24 at
    0050: 20 6f 66 66 73 65 74 20    offset
    0058: 30 30 30 31 33 62 66 64   00013bfd

    If I can solve this one, I will be in good shape.  I appreciate any help you can give me.

    Thanks,
    Michael



    Perhaps the hard drive on that PC is having issues.  Have you tried running chkdsk /r on that drive?
    Tuesday, February 24, 2009 1:15 AM
    Moderator
  • Yes, I ran chkdsk /r and no errors were found with the drive.


    Michael
    Tuesday, February 24, 2009 4:30 AM
  • Is this client a x64 client? I've seen this before but only for users on RAS.

    There is an update being pushed down via WU within the next few days. Can you make sure that you have automatic updates enabled on your server and verify whether or not this behavior continues with the new update?

    Thanks.
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Tuesday, February 24, 2009 10:09 PM
    Moderator
  • Lara,

    No, the client is a Windows XP 32 bit client.  I always have WU on automatic, so we'll see when the update is pushed out.

    Thanks,
    Michael
    Wednesday, February 25, 2009 1:44 AM
  • Lara,

    I received and installed the updates, but I still have the problem.

    Michael

    Friday, February 27, 2009 5:47 PM
  • MDwyer said:

    Lara,

    I received and installed the updates, but I still have the problem.

    Michael


    Hi Michael,

    Please submit a bug for this on Connect and include client and server CABs. When the watson report pops up indicating that clientinfo has crashed, please check the following location for a dump file: %SystemDrive%\Users\All Users\Microsoft\Windows\WER\ReportQueue

    I hit a bug very similiar to this morning on Windows 7 but I was able to resolve it by reinstalling the software. It appears you are hitting something different.

    Thanks


    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Friday, February 27, 2009 6:30 PM
    Moderator
  • Lara,

    Where can I find the cab files?

    Thank you,
    Michael
    Saturday, February 28, 2009 4:26 PM
  • Michael,

    The Cabs are normally as follows:


    How to get the CAB number on your home server

    1.     Open the Windows Home Server Console

    2.       Go to Settings->Toolkit->Support tab, and click the Send->Collect and Send to upload the logs for your home server to Microsoft.

    3.       Write down the CAB number and include the CAB number in your Connect bug report

     

    How to get the CAB number on your home computer

    1.       On your home computer, go to Start Menu->All Programs->Windows Home Server Toolkit->Error Reporting

    2.       Type y to send the home computer’s log files to Microsoft

    3.       Write down the CAB number and include the CAB number in your Connect bug report

    4.       Press ENTER to quit

    HTH,

    Colin


    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Saturday, February 28, 2009 5:44 PM
    Moderator