Problems with WHS Connector

All replies

• 

  

  0

  Sign in to vote

   http://social.microsoft.com/Forums/en-US/whssoftware/thread/c23c1b44-07f4-4f37-a8a3-770bde327789

  Thursday, November 27, 2008 2:53 AM
• 

  

  0

  Sign in to vote

  Tried to reinstall from that location. I have the updated file, but I can not connect when I install it as mentioned above.

  Thursday, November 27, 2008 2:57 AM
• 

  

  0

  Sign in to vote

  Hi,
  while the IP address configuration of the client is only the half (still missing the same infor for the server) there are some configuration parts, which may have a bad influence on functioning name resolution to internal machines.
  DNS suffix search list and Connection specific DNS suffix should be ideally empty (maybe this has to be reconfigured in DHCP settings on the router).
  DNS server should be the IP address of the router (in the very most scenarios).
  Otherwise the client will try to resolve your server name in the Internet, which obviously will fail or in rare cases connect you to a server with the same name somewhere else.
  Please check also the event log of the server for error messages and warnings.
  Did you install any other stuff on the server (i.e. SharePoint Services)?
  Best greetings from Germany
  Olaf

  Thursday, November 27, 2008 8:24 AM

  Moderator
• 

  

  0

  Sign in to vote

  a_Slash_ said:

  Tried to reinstall from that location. I have the updated file, but I can not connect when I install it as mentioned above.

  
  Just to confirm, did you try running setup.exe from that location?

  Thursday, November 27, 2008 6:48 PM

  Moderator
• 

  

  0

  Sign in to vote

  Yes, I ran setup.exe from the server. I also tried to copy the files to the client and run it from there but same result.
  
  Here is the ip info for the server: I am kind of a newb when it comes to these settings so you may have to walk me through it.
  
  

  Windows IP Configuration

     Host Name . . . . . . . . . . . . : server
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Unknown
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
     DNS Suffix Search List. . . . . . : socal.rr.com

  Ethernet adapter Local Area Connection:

     Connection-specific DNS Suffix  . : socal.rr.com
     Description . . . . . . . . . . . : Atheros L1 Gigabit Ethernet 10/100/1000Ba
  se-T Controller
     Physical Address. . . . . . . . . : 00-1E-8C-93-B8-A2
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     IP Address. . . . . . . . . . . . : 192.168.2.102
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Default Gateway . . . . . . . . . : 192.168.2.1
     DHCP Server . . . . . . . . . . . : 192.168.2.1
     DNS Servers . . . . . . . . . . . : 66.75.160.63
                                         66.75.160.64
     Lease Obtained. . . . . . . . . . : Thursday, November 27, 2008 7:13:34 AM
     Lease Expires . . . . . . . . . . : Friday, November 28, 2008 7:13:34 AM

  Thursday, November 27, 2008 6:57 PM
• 

  

  0

  Sign in to vote

  Hi,
  the server lacks the same configuration issues in relation to TCP/IP configuration plus that NetBIOS over TCP/IP is not enabled.
  What for an Internet router do you use?
  Does it have the latest firmware? (If not, you should upgrade for better security and functionality improvements.)
  Does the router support UPnP? 
  Is UPnP support enabled? If not, enable it in the routers Web interface. (Carefull with UPnP configuration, since this can open security holes.)
  Before starting the following changes, save the configuration of your router according to its manual.
  In the DHCP settings you should change the DNS server to the internal IP address of the router (which you see here already as Default Gateway).
  Try also to remove the socal.rr.com where ever in the router you find it.
  (Both changes may affect the Internet connectivity in rare cases.)
  
  After this open a command prompt on client and server and enter the command
  ipconfig /renew
  and reboot the machines.
  
  If this still does not help, you can perform the (unsupported) workaround to edit the hosts file on the client PC.
  It is located in C:\Windows\system32\drivers\etc and can be modified via notepad.
  Add a line containing the IP address and the name of the home server, i.e.
  192.168.2.102       server
  
  The problem with this workaround: It is static. So whenever the server gets another IP address assigned, you have to modify this file. Forgetting about this modification may cause a huge troubleshooting session later.
  
  Best greetings from Germany
  Olaf

  Thursday, November 27, 2008 8:09 PM

  Moderator
• 

  

  0

  Sign in to vote

  I have a cable modem > wireless router > gigabit switch (no settings). The server and clients are plugged into the gigabit switch. There is a laptop that connects wirelessly.
   
  UPnP was enabled and I have updated the firmware.
  
  I changed the 1st static DNS to 192.168.2.1 on the router. Here is what I get on the client now:
  
  

  Windows IP Configuration

     Host Name . . . . . . . . . . . . : Family
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Hybrid
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
     DNS Suffix Search List. . . . . . : socal.rr.com

  Ethernet adapter Local Area Connection:

     Connection-specific DNS Suffix  . : socal.rr.com
     Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
  it Ethernet NIC (NDIS 6.0)
     Physical Address. . . . . . . . . : 00-1D-7D-D4-F9-2D
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     Link-local IPv6 Address . . . . . : fe80::91a5:4ef2:8378:111d%8(Preferred)
     IPv4 Address. . . . . . . . . . . : 192.168.2.103(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Lease Obtained. . . . . . . . . . : Thursday, November 27, 2008 12:56:44 PM
     Lease Expires . . . . . . . . . . : Friday, November 28, 2008 12:56:44 PM
     Default Gateway . . . . . . . . . : 192.168.2.1
     DHCP Server . . . . . . . . . . . : 192.168.2.1
     DNS Servers . . . . . . . . . . . : 192.168.2.1
                                         66.75.160.63
                                         66.75.160.64
     NetBIOS over Tcpip. . . . . . . . : Enabled

  Tunnel adapter Local Area Connection* 6:

     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . : socal.rr.com
     Description . . . . . . . . . . . : Microsoft ISATAP Adapter
     Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes

  Tunnel adapter Local Area Connection* 7:

     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
     Physical Address. . . . . . . . . : 02-00-54-55-4E-01
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:28ce:26c0:3f57:fd98(Pref
  erred)
     Link-local IPv6 Address . . . . . : fe80::28ce:26c0:3f57:fd98%9(Preferred)
     Default Gateway . . . . . . . . . : ::
     NetBIOS over Tcpip. . . . . . . . : Disabled
  

  
  And the server:
  
  

  Windows IP Configuration

     Host Name . . . . . . . . . . . . : server
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Unknown
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No
     DNS Suffix Search List. . . . . . : socal.rr.com

  Ethernet adapter Local Area Connection:

     Connection-specific DNS Suffix  . : socal.rr.com
     Description . . . . . . . . . . . : Atheros L1 Gigabit Ethernet 10/100/1000Ba
  se-T Controller
     Physical Address. . . . . . . . . : 00-1E-8C-93-B8-A2
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     IP Address. . . . . . . . . . . . : 192.168.2.102
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Default Gateway . . . . . . . . . : 192.168.2.1
     DHCP Server . . . . . . . . . . . : 192.168.2.1
     DNS Servers . . . . . . . . . . . : 192.168.2.1
                                         66.75.160.63
                                         66.75.160.64
     Lease Obtained. . . . . . . . . . : Thursday, November 27, 2008 12:53:33 PM
     Lease Expires . . . . . . . . . . : Friday, November 28, 2008 12:53:33 PM

  I still can not connect when installing the console. Is this right or do I have to change all of the DNS servers to 192.168.2.1?
  
  Thank you so much for your help.

  Thursday, November 27, 2008 9:07 PM
• 

  

  0

  Sign in to vote

  Hi,
  external DNS servers should not be configured at all on the PCs within your network in a router scenario via DHCP. Some ISP may have different requirements, but usually name resolution should work that way:
  Client queries for a name.
  

  • Router as first DNS server gets this request (if it is a DNS name, which would it always be with a DNS suffix!) and may resolve or not resolve it on its own.
  • If it does not know the name, it either tells the client so, if the name has no domain extension, otherwise it forwards the request to the DNS server of the ISP.
  • DNS server of ISP answers with his result (maybe some more search involved due to the domain suffix again, and maybe even a wrong result returned due to another server with the same name registered already in this domain).

  So it is enough, that the Router itself knows the first external DNS server.
  With wrong configuration on the DNS client side (which are your PCs and the server) this may cause name resolution issues (server not found) or timeouts (long waiting times between network actions due to searching in wrong place).
  You should remove also the socal.rr.com, since such a suffix makes each name to a DNS name and triggers name resolution attempts via external DNS servers for your internal machines.
  Best greetings from Germany
  Olaf

  Thursday, November 27, 2008 10:09 PM

  Moderator
• 

  

  0

  Sign in to vote

  OK, I purchased a new router (Netgear WMR3500) but I am still having the same problem. I think the new settings are what you wanted, but I am not sure so here they are:
  
  Client:
  
  

  Windows IP Configuration

     Host Name . . . . . . . . . . . . : Family
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Hybrid
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No

  Ethernet adapter Local Area Connection:

     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
  it Ethernet NIC (NDIS 6.0)
     Physical Address. . . . . . . . . : 00-1D-7D-D4-F9-2D
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     Link-local IPv6 Address . . . . . : fe80::91a5:4ef2:8378:111d%8(Preferred)
     IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Lease Obtained. . . . . . . . . . : Friday, November 28, 2008 3:54:03 PM
     Lease Expires . . . . . . . . . . : Saturday, November 29, 2008 3:54:02 PM
     Default Gateway . . . . . . . . . : 192.168.1.1
     DHCP Server . . . . . . . . . . . : 192.168.1.1
     DNS Servers . . . . . . . . . . . : 192.168.1.1
     NetBIOS over Tcpip. . . . . . . . : Enabled

  Tunnel adapter Local Area Connection* 6:

     Media State . . . . . . . . . . . : Media disconnected
     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Microsoft ISATAP Adapter
     Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes

  Tunnel adapter Local Area Connection* 7:

     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
     Physical Address. . . . . . . . . : 02-00-54-55-4E-01
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c10:1e62:3f57:fefd(Prefe
  rred)
     Link-local IPv6 Address . . . . . : fe80::c10:1e62:3f57:fefd%9(Preferred)
     Default Gateway . . . . . . . . . : ::
     NetBIOS over Tcpip. . . . . . . . : Disabled
  
  Server:
  
  

  Windows IP Configuration

     Host Name . . . . . . . . . . . . : server
     Primary Dns Suffix  . . . . . . . :
     Node Type . . . . . . . . . . . . : Unknown
     IP Routing Enabled. . . . . . . . : No
     WINS Proxy Enabled. . . . . . . . : No

  Ethernet adapter Local Area Connection:

     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : Atheros L1 Gigabit Ethernet 10/100/1000Ba
  se-T Controller
     Physical Address. . . . . . . . . : 00-1E-8C-93-B8-A2
     DHCP Enabled. . . . . . . . . . . : Yes
     Autoconfiguration Enabled . . . . : Yes
     IP Address. . . . . . . . . . . . : 192.168.1.3
     Subnet Mask . . . . . . . . . . . : 255.255.255.0
     Default Gateway . . . . . . . . . : 192.168.1.1
     DHCP Server . . . . . . . . . . . : 192.168.1.1
     DNS Servers . . . . . . . . . . . : 192.168.1.1
     Lease Obtained. . . . . . . . . . : Friday, November 28, 2008 4:49:09 PM
     Lease Expires . . . . . . . . . . : Saturday, November 29, 2008 4:49:09 PM
  

  Saturday, November 29, 2008 1:04 AM
• 

  

  0

  Sign in to vote

  Hi,
  I don't think, that purchasing a new router would have been necessary.
  Did you ever check the event log on your server? (in Start/Control Panel/Administrative Tools open the Event Viewer)
  Any errors or warnings around the time of your failed Connector installation would be of interest.
  Do the system times and dates on the client and the server match? (This includes also the time zones, since Windows Home Server after installation defaults to Pacific time and changing the time zone changes the time to a weird one, so that you may still have x hours difference if you aren't carefull.)
  
  Did you install any other software on your server, which may have changed security settings or Windows Firewall settings on the server? Do you use a 3rd party security suite on the clients?
  
  The network settings look indeed near perfect, although on the server you could check the NetBIOS via TCP/IP settings.

  • On your server, open Control Panel/Network.
  • Right click on your network connection and select Properties.
  • Double click the TCP/IP properties of the network adapter.
  • Click Advanced and open the WINS tab. Select NetBIOS over TCP/IP here.
  • Click OK and reboot both the server and clients.

  If this does not help, open on the client PCs the file hosts in C:\Windows\system32\drivers\etc and add a line including the IP address and the name of your home server, as also mentioned before. (Keep this change in mind, because assigned IP addesses may change.)
  
  Another solution I found by searching around has been: 

  1. Go to the "c:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\" folder.
  2. Right Click on the MachineKeys folder and select Properties
  3. Click the Security tab.
  4. Click on "Advanced" button
  5. Go to the permissions tab and make sure that for Administrators and Everyone the "CreateFiles / Write Data" and "Create Folders / Append Data" are marked "Allow" and the "Apply onto" dropdown box is set to "This folder, subfolders and files" for both.

  Best greetings from Germany
  Olaf

  • Edited by Olaf EngelkeModerator Saturday, November 29, 2008 4:56 AM added information

  Saturday, November 29, 2008 4:43 AM

  Moderator
• 

  

  0

  Sign in to vote

  Same thing happened to me yesterday.  I haven't changed anything other then to fire up my x64 laptop which hadn't been on for a few days.  I notice the WHS icon is red, tells me to upgrade but it fails to find the WH server.  When I go to another machine and attempt to browse to http://homeserver I get a certificate error.  I wonder if some automatic update hasn't caused this.

  Saturday, November 29, 2008 5:23 AM
• 

  

  0

  Sign in to vote

   I tried everything that you have suggested but am still having the same problem.
  
  I noticed a couple of other threads where some were having the same problem I am and it was a result of the last update. I am now pretty certain that this is not a result of router settings.
  
  I uninstalled the update and rebooted but I still can not get the connector to install. Where do I go from here?

  Monday, December 1, 2008 5:47 AM
• 

  

  0

  Sign in to vote

   Anymore suggestions? Anyone?? Please Help.

  Tuesday, December 2, 2008 8:29 PM
• 

  

  0

  Sign in to vote

  Hi,
  you want suggestions - but give not the necessary amount of detailed informations (that it does not work, is unfortunately not enough).
  Please logon to the server locally and check it's event log for errors and warnings during the time of the installation attempts. The same for the client.
  Make sure, that the folder \\server\software\Home Server Connector Software contains all components (here a snapshot of my German server after removing OEM folder from the list):
  
  \\server\software\Home Server Connector Software

  04.11.2008  00:58    <DIR>          DOTNETFX20
  04.11.2008  00:58    <DIR>          WindowsInstaller31
  12.07.2008  16:13           226.336 setup.exe
  31.10.2008  18:27        12.762.112 WHSConnector.msi
  12.07.2008  16:13         1.075.744 WHSConnectorInstall.exe
  31.10.2008  11:39        13.782.528 WHSConnector_x64.msi
  12.07.2008  16:12            44.064 WHSVersionUpgrade.dll
  12.07.2008  17:37            46.624 WHSVersionUpgrade_x64.dll
  01.07.2008  20:08            44.097 WHS_ConnectorHelp.chm
  
  \\server\software\Home Server Connector Software\DOTNETFX20

  23.09.2005  14:53            61.632 dotnetchk.exe
  16.11.2005  19:25        23.510.720 dotnetfx.exe
  
  \\server\software\Home Server Connector Software\WindowsInstaller31

  25.04.2006  22:07         2.585.872 WindowsInstaller-KB893803-v2-x86.exe
  
  If this looks not similar on your Home Server, you can try to run the ConnectorInstallAssistant.cmd in C:\WHS on your server to repair the folder.
  
  You could also click Start/Run and type %qlogs% to access the Home Server log files - maybe one of those has some more messages about what is going wrong.
  
  Best greetings from Germany
  Olaf

  Tuesday, December 2, 2008 8:51 PM

  Moderator
• 

  

  0

  Sign in to vote

  Nothing appears in the logs on the server.
  
  There are two dates on the folders that differ from what you posted:
  
  04.11.2008  00:58    <DIR>          DOTNETFX20
  04.11.2008  00:58    <DIR>          WindowsInstaller31
  
  My folders are dated March 28th, 2008 although the files inside of the folders have the same dates as yours. All other files match.
  
  Here is a event I found on the client when trying to install the connector: 

  Log Name:      Application
  Source:        HomeServer
  Date:          12/2/2008 8:42:09 PM
  Event ID:      1794
  Task Category: (7)
  Level:         Warning
  Keywords:      Classic
  User:          N/A
  Computer:      Family
  Description:
  The description for Event ID 1794 from source HomeServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

  If the event originated on another computer, the display information had to be saved with the event.

  The following information was included with the event:

  
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="HomeServer" />
      <EventID Qualifiers="36863">1794</EventID>
      <Level>3</Level>
      <Task>7</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2008-12-03T04:42:09.000Z" />
      <EventRecordID>12943</EventRecordID>
      <Channel>Application</Channel>
      <Computer>Family</Computer>
      <Security />
    </System>
    <EventData>
    </EventData>
  </Event>
  
  
  Here is another:
  
  Log Name:      Application
  Source:        MsiInstaller
  Date:          12/2/2008 8:42:42 PM
  Event ID:      11708
  Task Category: None
  Level:         Information
  Keywords:      Classic
  User:          FAMILY\Sheri
  Computer:      Family
  Description:
  Product: Windows Home Server Connector -- Installation failed.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="MsiInstaller" />
      <EventID Qualifiers="0">11708</EventID>
      <Level>4</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2008-12-03T04:42:42.000Z" />
      <EventRecordID>12945</EventRecordID>
      <Channel>Application</Channel>
      <Computer>Family</Computer>
      <Security UserID="S-1-5-21-2765508551-1505362785-2899256630-1001" />
    </System>
    <EventData>
      <Data>Product: Windows Home Server Connector -- Installation failed.</Data>
      <Data>(NULL)</Data>
      <Data>(NULL)</Data>
      <Data>(NULL)</Data>
      <Data>(NULL)</Data>
      <Data>
      </Data>
      <Data>
      </Data>
      <Binary>7B32314534393739342D374331332D344538342D383635392D3535424433373832363744357D2C2031363032</Binary>
    </EventData>
  </Event>
  
  One more that may be relevant:
  
  Log Name:      Application
  Source:        HomeServer
  Date:          12/2/2008 8:42:58 PM
  Event ID:      1818
  Task Category: (7)
  Level:         Information
  Keywords:      Classic
  User:          N/A
  Computer:      Family
  Description:
  The description for Event ID 1818 from source HomeServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

  If the event originated on another computer, the display information had to be saved with the event.

  The following information was included with the event:

  
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="HomeServer" />
      <EventID Qualifiers="20479">1818</EventID>
      <Level>4</Level>
      <Task>7</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2008-12-03T04:42:58.000Z" />
      <EventRecordID>12949</EventRecordID>
      <Channel>Application</Channel>
      <Computer>Family</Computer>
      <Security />
    </System>
    <EventData>
    </EventData>
  </Event>
  
  There is also the same one for EVENT ID 1817 that says the same as above.

  Wednesday, December 3, 2008 5:04 AM
• 

  

  0

  Sign in to vote

  Ah these unfound events are only properly readable on a client with installed connector software.
  An unsupported trick to keep the software installed is sometimes, to kill the related task (in one of my tries it was discovery.exe, but dependent from the stage of installation it could be different) in task manager under Processes and reboot.
  Best greetings from Germany
  Olaf

  Wednesday, December 3, 2008 9:15 AM

  Moderator
• 

  

  0

  Sign in to vote

   OK, I killed the program before it wanted to uninstall. The WHSC icon is red of course and when I double left click the icon it says a newer version of the connector is available. I can right click, get the popup menu and if I select Windows Home Sever Console I can attempt to login. If I do, I get the dialog box that I can not connect to the server and check my network blah blah blah.
  
  If I click to upgrade I get the "This operation can not be completed at this time" message
  
  Just to make sure they are in the correct directory: \\Server\Software\Home Server Connector Software , this is right isn't it?
  
  I checked the logs at the time I try to login and I do not see any errors of anything at all at the point of the attepted login.
  
  Here is some thing I found in the logs that me be relevant:
  
  
  Created at 12/3/2008 11:52:16 PM
  ***** Started at 12/3/2008 11:52:16 PM ***
  ***** Started at 12/3/2008 11:52:16 PM ***
  [1]081203.235217.7812: Error: Client c7a2ce21-36bd-41c1-8d0a-fd77bcc58374 not found by BackupHelpers.FindClient
  [1]081203.235217.7812: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: c7a2ce21-36bd-41c1-8d0a-fd77bcc58374
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
  [1]081203.235217.7968: Error: Client 57be1171-8836-4f1d-98a8-f315cec68891 not found by BackupHelpers.FindClient
  [1]081203.235217.7968: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 57be1171-8836-4f1d-98a8-f315cec68891
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
  [1]081203.235217.7968: Error: Client 4dc7550d-8519-4cb5-baa9-a2101f004279 not found by BackupHelpers.FindClient
  [1]081203.235217.7968: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 4dc7550d-8519-4cb5-baa9-a2101f004279
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)
     at Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient
  [1]081203.235218.9062: Error: Error -2147023728 in SendMessage
  [5]081203.235220.4687: Error: Cannot invoke RefreshData for HealthControl
  [5]081203.235220.4687: Error: Cannot invoke RefreshData for HealthControl
  [5]081203.235220.4687: Error: Cannot invoke RefreshData for HealthControl
  [5]081203.235220.4687: Error: Cannot invoke RefreshData for HealthControl
  [5]081203.235220.4687: Error: Cannot invoke RefreshData for HealthControl
  [7]081203.235220.4843: Error: Backup percentage is -2147483648
  [7]081203.235220.4843: Error: Cannot invoke RefreshData for HealthControl
  [7]081203.235223.5468: Error: Backup percentage is -2147483648
  [7]081203.235223.5468: Error: Cannot invoke RefreshData for HealthControl
  [1]081203.235223.5781: Error: Cannot invoke RefreshData for HealthControl
  [1]081203.235223.5781: Error: Error -2147023728 in SendMessage
  [14]081203.235231.5625: Error: Backup percentage is -2147483648
  [15]081203.235252.0625: Error: Backup percentage is -2147483648
  [1]081203.235303.8906: Error: Error -2147023728 in SendMessage
  [7]081203.235423.5468: Error: Backup percentage is -2147483648
  [13]081203.235726.0937: Error: Backup percentage is -2147483648
  [1]081204.124404.9218: Error: Error -2147023728 in SendMessage
  

  Thursday, December 4, 2008 9:16 PM
• 

  

  0

  Sign in to vote

  I had a similar problem after installing the November update. Red Icon, upgrade available, can see the shares, etc but it wouldn't actually upgrade. My problem was related to the Windows Installer on the client, not the server, it wouldn't install .msi files which also broke windows updates for that client. I tried many of the fixes found on the internet but nothing worked so I used my WHS backups to restore to an earlier date that I knew Windows Installer worked on. After that, the conector upgraded itself at the next reboot and MS Update started working again too. I'd suggest looking in the event logs of the client to see if there are MSI errors.
  
  There is a possible (and unsupported) work around to install the updated connector but if it's a Windows Intaller issue, like mine was, you'd only be fixing a symptom not the actual problem.
  
  Hope that helps...
  

  ---

  "He who dares not offend cannot be honest." -- Thomas Paine

  Thursday, December 4, 2008 9:33 PM
• 

  

  0

  Sign in to vote

  Hi,
  I don't like these home server specific logs, hard to read for non insiders.
  You still didnt translate the former events, which should now be better readable with the half installed connector.
  Seems you got an outdated version of the Connector - are the dates in \\server\software\home server connector software as shown in my former listings?
  What happens, if you copy the entire folder to your local client and try to run setup from there?
  
  Is there anything potential related in the server event logs (authentication attempts in the security log or DCOM errors in application or system log) around the time of your installation attempts?
  
  Did you try to uninstall the November upgrade for Windows Home Server on the server?
  If not, it could be worth a try - since it broke the connection in some cases in the first attempt.
  To do this, login to your server locally and open Control Panel/Add-Remove Programs.
  Set the mark in Show updates checkbox and find KB957825.
  Uninstall it and reboot.
  (Now you could install it again or first try to get the connector back for the older version.)
  
  Best greetings from Germany
  Olaf

  Thursday, December 4, 2008 9:45 PM

  Moderator
• 

  

  0

  Sign in to vote

  Maybe there is a misunderstanding a_slash_ =  Xcel101. One is my wifes account one is mine. Here is what I posted before regarding the files.
  
  There are two dates on the folders that differ from what you posted:
  
  04.11.2008  00:58    <DIR>          DOTNETFX20
  04.11.2008  00:58    <DIR>          WindowsInstaller31
  
  My folders are dated March 28th, 2008 although the files inside of the folders have the same dates as yours. All other files match.
  
  What do the dates differ but the files in the folders do not?
  
  This is the only thing I can find in the event logs when I just tried to install the connector on my laptop.
  
  Log Name:      Application
  Source:        HomeServer
  Date:          12/4/2008 8:56:23 PM
  Event ID:      1794
  Task Category: Connection
  Level:         Warning
  Keywords:      Classic
  User:          N/A
  Computer:      Laptop-PC
  Description:
  Server ID is not set yet. On the client it means that the server discovery (discovery.exe) was not run or was not run successfully.
  Event Xml:
  <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="HomeServer" />
      <EventID Qualifiers="36863">1794</EventID>
      <Level>3</Level>
      <Task>7</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2008-12-05T04:56:23.000Z" />
      <EventRecordID>9815</EventRecordID>
      <Channel>Application</Channel>
      <Computer>Laptop-PC</Computer>
      <Security />
    </System>
    <EventData>
    </EventData>
  </Event>
  
  I have this same issue with all three of my clients which leads me to believe that this issue is somewhere on the server. All three computers installers work fine and all three were working fine before the update.
  
  I have also tried to uninstall the update, rebooted and tried to install the old version of the connector software but I get the exact same behavior as with the new one. I have reinstalled the update and tried again mutiple times. 
  
  I moved my WHS to a monitor and keyboard to directly log on to the server. I could not access the shared folders from the WHS desktop until I plugged the server into the router. I could open the console while not connected to the network, but if I went into the settings and clicked on the add-ins, I got a blank screen with both the installed and available tabs. Once I  plugged in this was corrected. Is this normal behavior for WHS or does it indicate a problem?

  Friday, December 5, 2008 5:36 AM
• 

  

  0

  Sign in to vote

  Hi,
  "Server ID is not set yet. On the client it means that the server discovery (discovery.exe) was not run or was not run successfully."
  
  This could point to name resolution issues or to a 3rd party security suite blocking the communication between client and server.
  
  "I could not access the shared folders from the WHS desktop until I plugged the server into the router."
  
  This is rather normal with media sense on the network adapter enabled.
  If you pull the cable between the network card and any switch, the network interface is not connected, has no IP address (also not via APIPA) and brings so several services and applications relying on the functional network connection to run into an uncontrolled stage. (There is an registry key to disable media sense, but this makes only sense together with a fixed IP address in a WHS scenario.)
  
  What you could try is to pull the cable from the router to the Internet instead.
  
  Best greetings from Germany
  Olaf

  Friday, December 5, 2008 1:02 PM

  Moderator
• 

  

  0

  Sign in to vote

  Nothing changed on all of my clients. The only change was the update that was pushed to my WHS. After that, it broke all 3 clients. When I uninstalled the offending update, I am still screwed on all 3 clients. Now maybe there was a problem with the WHS or the clients (I highly doubt all 3 client have the same problem) that this update may have exposed, but I have heard others with this same issue after this update.
  
  I seem to be at the point where I may have to reinstall WHS. Should I worry about losing my data during a reinstall? I know you can do a reinstallation while keeping your data, I am just wondering if it is foolproof or am I at risk of borking all of my data.
  
  BTW, thank you very much for all of the help that you have provided thus far.

  Saturday, December 6, 2008 11:22 PM
• 

  

  0

  Sign in to vote

  As long as you get a server reinstall offered (and not only a new installation), leave the DVD in drive all the time and have enough patience for the process of rebuilding tombstones to complete near the end of setup, not much should go wrong.
  If this fails: As long as you do not initiate a new installation and confirm, that all drives are getting formatted, the data is still accessible on the disks in emergency situation.
  Good luck
  Olaf

  • Proposed as answer by kariya21Moderator Sunday, December 7, 2008 7:07 AM
  • Marked as answer by Jonas Svensson -FST- Saturday, January 17, 2009 8:58 PM
  • Marked as answer by Jonas Svensson -FST- Saturday, January 17, 2009 8:58 PM

  Sunday, December 7, 2008 1:46 AM

  Moderator