locked
Problem with Backups RRS feed

  • Question

  • Windows Home Server AppPool is off
    Hi. I installed WHS a week ago and have already run into problems with backups. At the moment the network consists of a wired XP Home and a wired Vista Premium PC. The XP machine seems to do auto backups ok - it causes both computers to loose contact with the server at 97% but the server reports the backup was successful. The real problem is with the Vista machine. Automatic backups do not run. Manual backups fail at 31% (Reorganising data on the server). The toolkit on the Vista PC reports one error but doesn't show what it is on the html page. When run on the server it reports two fails. One is remote access - thats ok, I haven't set it up and the second is "Windows Home Server AppPool is off". I've searched for a possible solution to no avail. The error logs show nothing.
    Any help would be greatly appreciated.
    Philip
    Monday, May 11, 2009 9:50 AM

All replies

  • Hi Philip,
    please check the event viewer on both the client and the server (in Control Panel/Administrative Tools) for more clear errors in relation to the backup.
    Also check the version numbers on the Console in Settings/Console.
    If it does not end with .2030, use the Update button after each reboot again until you do not get updates any more.
    In case backup fails on a certain drive (if you have more than one on the clients) run chkdsk /r /f against that drive, otherwise check the system drive with that command.
    Best greetings from Germany
    Olaf
    Monday, May 11, 2009 6:00 PM
    Moderator
  • Hi Olaf,
    Many thanks for your reply. It's helped me make some progress. The event viewer on my PC gave some errors with event id 770 or 773 - these seem to relate to the server and PC loosing contact (more of that later) but the Microsoft support site knows nothing of these codes! The error logs on the server show nothing I can see as significant.
    The version number is indeed .2030
    I hadn't spotted that I could look at a report of the backup. When I did, I discovered that the C: drive had been processed correctly, but that two other drives hadn't. Removing those for the backup partly solved the problem. Now, the C: drive is a SATA RAID array, the other drives are a PATA RAID array split into two drives. I would suspect that that's problem but for two facts. 1) The very first backup I did backed up all drives successfully and 2) my laptop which I've now added is one physical drive split into two volumes.
    The other two issues, namely backups not starting automatically on the Vista machines and the server logging off on all computers after the first successful backup remain.
    I'd be interested to hear your thoughts.
    Kind regards
    Philip

    Tuesday, May 12, 2009 9:29 PM
  • Hi Philip,
    have to leave my computer alone to get some sleep, so only a quick statement:
    If backup fails on one drive, it will not resume on the next drive. So if you exclude only the drive, on which backup failed recently, would it complete for drive 1 and 3 selected for backup only?
    If that works, try to run chkdsk /r /f against that drive, on which backup failed.
    May also be something else on that drive, which causes backup to hickup. And once in that uncontrolled state, ("speculation here") subsequent automated backups could fail (you should see attempts in the event log, since backups will be initiated by the clients Connector software).
    If chkdsk does not find anything and solve the issue, I would recommend to copy the content of that drive to some other place, reformat the volume and copy the data back.
    Automatic backups will not start, if the computer is attached to an UPS or running on battery or if the computer is sleeping and Connector is either not configured to wake up the computer for backup or the wakeup attempt fails.

    Connectivity loss must not always mean a network issue, although this also could be the case. But I would not think so for a subsequent backup, since you already succeeded one time with the full backup.

    RAID arrays are always a bit difficult, especially if it comes to recovery.

    Best greetings from Germany
    Olaf
    Tuesday, May 12, 2009 10:19 PM
    Moderator
  • Hi Olaf,
    Thanks for your reply yesterday.
    I knew I would forget to tell you something. I ran chkdsk on the disks in the PATA array and it reported no errors. I didn't worry about the C: SATA array.
    Acting on a hunch, I have just run separate backups on all three drives, and guess what - they all backed up ok!! Except that I lost connectivity each time in the mid 90% of the backup and had to reboot the server. The server always reports a successful backup though. No automatic backups yet though.
    This loss of connectivity happens on both of the Vista machines and on the XP. Confusingly, the Vista laptop backs up ok even though the drive is partitioned.
    The last backup of C: has just stopped at 95%. The backup status window says "The backup failed because of a problem with your Windows Home Server Connector software. The system event log contains more details". What should I be looking for in the logs?
    Kind regards
    Philip
    Wednesday, May 13, 2009 8:04 AM
  • Hi Philip,
    around the time of the failed backup you should find related errors in the event log.
    Double click those and post the content.

    Maybe, if not already done, register on Microsoft Connect as outlined in this thread and issue a bug report, including the CAB files created with the Windows Home Server toolkit.
    So the developers can have a look into the issue.

    Best greetings from Germany
    Olaf
    Wednesday, May 13, 2009 8:51 AM
    Moderator
  • Hi Olaf

    Right, I've not long tried another backup and checked the logs on the server and my PC. The server one is lists an unexpected shutdown (probably me rebooting)
    There are two in the PC log. Here they are

    Error 1

    System
    - Provider
    [ Name ] HomeServer
    - EventID 770
    [ Qualifiers ] 53247
    Level 2
    Task 3
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime ] 2009-05-13T18:04:12.000Z
    EventRecordID 197083
    Channel Application
    Computer philips-desktop
    Security
    - EventData
    17
    TERRY-SERVER
    Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lost at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration) at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.ReadWithReconnect() at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.ReadByte() at Microsoft.HomeServer.Common.Client.BinaryReaderEx.ReadLong() at Microsoft.HomeServer.Common.Client.BinaryReaderEx.ReadInt() at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.GetResponse() at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoWorking(BackupVolumePhase phase) at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch() at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run() at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.RunWithoutCatch() at Microsoft.HomeServer.Backup.BackupOp.BackupSetOperation.Run()

    Error 2

    - System
    - Provider
    [ Name ] HomeServer
    - EventID 773
    [ Qualifiers ] 53247
    Level 2
    Task 3
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime ] 2009-05-13T17:58:41.000Z
    EventRecordID 197081
    Channel Application
    Computer philips-desktop
    Security
    - EventData
    17
    C:
    TERRY-SERVER
    Microsoft.HomeServer.Backup.Protocol.ProtocolException: Client / Server connection lost at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration) at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.ReadWithReconnect() at Microsoft.HomeServer.Backup.Protocol.ReconnectableStream.ReadByte() at Microsoft.HomeServer.Common.Client.BinaryReaderEx.ReadLong() at Microsoft.HomeServer.Common.Client.BinaryReaderEx.ReadInt() at Microsoft.HomeServer.Backup.Protocol.BackupProtocol.GetResponse() at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoWorking(BackupVolumePhase phase) at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch() at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()
    Hope that makes some sense to you!
    Kind regards
    Philip
    Wednesday, May 13, 2009 7:06 PM
  • Forgot to say that one the home page of the toolkit is a message about connectivity errors. Looking at them I see that "Windows Home Server AppPool is off"

    Philip
    Wednesday, May 13, 2009 7:09 PM
  • Hi Philip,
    "Windows Home Server AppPool is off" may point to a crash of IIS. (which in it's own way would represent a connection loss, but we don't know, if it is cause or result). So I am still out of a clear idea how to fix this.

    How much disk space is free on drive C: of your server and how much memory does your server have?
    Are the drivers for storage and network the most up to date for Windows Server 2003 (or Windows XP) and the clients?
    Also the firmware on the router?
    If your network adapters are all GigaBit capable, it may help to include a GigaBit switch in your network (I assume your machines are connected to the router, and the most switches in routers are still 10/100 MB).

    Did you install any other stuff on your server?
    The backup-xxx.log file could also offer some more information. You get to that log, while logged in on the server desktop click Start/Run and type %qlogs%. This opens a folder with WHS specific logfiles, which you can open in notepad.

    Eventually, as a last resort for testing, you could also try to delete the entire backup database and start from the scratch (just in case, there is an issue with your backup database, which I don't see from your events).
    To do this, login to your server.
    Open a command prompt and type the following commands:
    net stop PDL
    net stop WHSBACKUP
    Delete all files in D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.
    Restart your server.

    Best greetings from Germany
    Olaf
    Thursday, May 14, 2009 7:09 AM
    Moderator
  • Hi Olaf.
    Thanks.
    A lot to work through there. The connectivity loss problem shows up as soon as I log into the server toolkit - before a backup starts. Pressing the "restart IIS" button does not solve the problem.
     Can I log into the server desktop from my PC, if so how?
    Kind regards
    Philip
    Thursday, May 14, 2009 10:56 AM
  • You can login from your PC - simply use the Remote Desktop Client  in Start/Programs/Accessories with account name Administrator and the console password.
    Be carefull working on desktop, since the warning you will get is not out of the blue.
    Best greetings from Germany
    Olaf
    Thursday, May 14, 2009 12:02 PM
    Moderator
  • Thanks Olaf,
    I'm learning all the time!
    I'll work through your list and report back ASAP
    Regards
    Philip
    Thursday, May 14, 2009 12:47 PM
  • Hi Olaf,

    Once again, many help for your support. I'll now attempt to answer your questions.
    The C: drive of the server has 854 GB free and the server has 2GB of memory.
    As far as I can tell, I have up to date drivers. The ethernet connection is a nvidia nforce networking controller and frustratingly the Nvidia site is not very helpful. I may have to contact their support.
    What you say about a switch is interesting. I don't know much about them, so I've been doing a bit of research. Lets see if I've got this right. The computers/server are pumping out data at gigabit speeds but hitting a brick wall in the router which only works at 10/100, so slowing the data down like a tap controls water flow. We have noticed that internet speeds drop significantly whilst backups are happening - does a swich help that or is that  just a natural consequence  of the backup activity?
    Software so far installed on the server is WHS toolkit 1.1 and Asoft's Auto Exit.

    I have got the backup file from today as you suggested. It's rather large, so I have only posted the piece that seems to me to be relavent:-
    [17/05/2009 13:39:40  6d4] Backup of PHILIPS-DESKTOP C:\ has finished successfully.
    [17/05/2009 13:40:24  6d4] Error 10054 receiving data from partner
    [17/05/2009 13:40:24  6d4] Breaking TLS sesssion...
    [17/05/2009 13:40:24  6d4] Read 0 bytes, hr=80072746
    [17/05/2009 13:40:24  6d4] ReconnectableStream: Read failed, reconnecting {3865EEC9-6FB6-41B9-91C1-4162581C834B}, generation 1
    [17/05/2009 13:40:24  6d4] ReconnectableStream: Awaiting reconnection for session {3865EEC9-6FB6-41B9-91C1-4162581C834B}
    [17/05/2009 13:45:24  6d4] ReconnectableStream: Reconnect wait for {3865EEC9-6FB6-41B9-91C1-4162581C834B} timed out.
    [17/05/2009 13:45:24  6d4] ReconnectableStream: TryReconnect failed
    [17/05/2009 13:45:24  6d4] ReconnectableStream: Read permanently broken for session {3865EEC9-6FB6-41B9-91C1-4162581C834B}

    I've also got the following file
    HomeServerConsole.0905152201546875.1336.log which I post in full.

    Created at 15/05/2009 19:40:43
    ***** Started at 15/05/2009 19:40:43 ***
    ***** Started at 15/05/2009 19:40:43 ***
    [1]090515.194047.1718: BackupConfig: Error: Disconnected Backup Config
    [1]090515.194047.3125: BackupConfig: Error: Disconnected Backup Config
    [1]090515.194047.3437: Error: Client fb637cd9-3cad-43a0-8e26-fba9508849ce not found by BackupHelpers.FindClient
    [1]090515.194047.3437: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: fb637cd9-3cad-43a0-8e26-fba9508849ce
       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]090515.194047.3906: Error: Client bfa36b4b-0d7e-453d-80c8-112d71549d82 not found by BackupHelpers.FindClient
    [1]090515.194047.3906: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: bfa36b4b-0d7e-453d-80c8-112d71549d82
       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]090515.194047.3906: Error: Client 2ac032dd-767a-4d50-8997-eae6fbd38be7 not found by BackupHelpers.FindClient
    [1]090515.194047.3906: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 2ac032dd-767a-4d50-8997-eae6fbd38be7
       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]090515.194047.4687: BackupConfig: Error: Disconnected Backup Config
    [1]090515.194048.1718: Error: Error -2147023728 in SendMessage
    [13]090515.194050.2187: Error: Backup percentage is -2147483648
    [13]090515.194050.2187: Error: Cannot invoke RefreshData for HealthControl
    [7]090515.194050.2187: Error: Cannot invoke RefreshData for HealthControl
    [7]090515.194050.2187: Error: Cannot invoke RefreshData for HealthControl
    [7]090515.194050.2187: Error: Cannot invoke RefreshData for HealthControl
    [13]090515.194053.2187: Error: Backup percentage is -2147483648
    [13]090515.194053.2187: Error: Cannot invoke RefreshData for HealthControl
    [1]090515.194053.3750: Error: Add-in \\TERRY-SERVER\Software\Add-ins\WHSToolkit.msi does not fit WHS requirements
    [1]090515.194053.4687: Error: Cannot invoke RefreshData for HealthControl
    [1]090515.194053.4687: Error: Error -2147023728 in SendMessage
    [1]090515.194058.9687: Error: Error -2147023728 in SendMessage
    [12]090515.194100.2187: Error: Backup percentage is -2147483648
    [19]090515.194121.2187: Error: Backup percentage is -2147483648
    [20]090515.194251.7187: Error: Backup percentage is -2147483648
    [21]090515.194552.2187: Error: Backup percentage is -2147483648
    I haven't tried your last resort .... yet!
    Best Wishes
    Philip
    • Edited by philip56 Monday, May 18, 2009 7:21 PM
    Sunday, May 17, 2009 2:19 PM
  • Hi Olaf
    Just a quick update. Yesterday (Sunday) for the first time my Vista Desktop did an automatic backup. (The XP machine always has). It still logged all pc out at the end of the backup though.
    Does this help?
    Best wishes
    Philip
    Monday, May 18, 2009 7:20 PM
  • Hi Philip,
    I don't think that logging off has any influence on backups of other clients.
    Which version of the WHS Toolkit is installed on your server?
    According to your log your server has difficulties with that version - either you have still the outdated and no longer supported version 1.0 (at least in the Add-Ins folder) or you have not installed version 1.1 according to the guideline available with the toolkit (install on client first and from there publish to the server).
    Best greetings from Germany
    Olaf
    Monday, May 18, 2009 8:42 PM
    Moderator
  • Hi Philip,
    I don't think that logging off has any influence on backups of other clients.
    Which version of the WHS Toolkit is installed on your server?
    According to your log your server has difficulties with that version - either you have still the outdated and no longer supported version 1.0 (at least in the Add-Ins folder) or you have not installed version 1.1 according to the guideline available with the toolkit (install on client first and from there publish to the server).
    Best greetings from Germany
    Olaf

    Hi Olaf.
    Thanks for your reply.
    According to the server, The toolkit is 1.1. In software/add-Ins I have Toolkit and WHSToolkit.  I assume we are talking about the latter. When you say "publish to the server" to you mean run (ie double click) on the client? As I can't remember how are installed it< I assume in would be worth deleting and reinstalling.
    The Vista machines are back to only accepting maanual requests for backups. XP on auto as normal.

    Kind regards
    Philip
    Tuesday, May 19, 2009 7:11 PM
  • Hi,
    first uninstall any of the Toolkit versions and delete the WHSToolkit files in Software\Add-Ins folder on your server.
    Install the toolkit on a client.
    In Start/All Programs/Windows Home Server Toolkit on the client you find a shortcut Publish Server Add-In.
    This is the only supported way to install the toolkit.
    Best greetings from Germany
    Olaf
    Tuesday, May 19, 2009 7:19 PM
    Moderator
  • Hi,
    first uninstall any of the Toolkit versions and delete the WHSToolkit files in Software\Add-Ins folder on your server.
    Install the toolkit on a client.
    In Start/All Programs/Windows Home Server Toolkit on the client you find a shortcut Publish Server Add-In.
    This is the only supported way to install the toolkit.
    Best greetings from Germany
    Olaf
    Hi Olaf

    Right WHS Toolkit is now correctly installed. Backups still stopping at the end of C: (47%). The server then logs out to all attached computers and the window pops up giving 20 reconnection attempts, which of course don't work. The only way to reconnect is to reboot the server. Nothing else to report!!

    Kind regards

    Philip
    Wednesday, May 20, 2009 8:51 PM
  • Hi Philip,
    did you already send a bug report via Microsoft Connect together with the CAB files created by the WHS Toolkit on server and client?
    Can you check the servers event log for errors again? Server services crashing is something, which should not happen and can have many reasons, not the least hardware related troubles.
    Best greetings from Germany
    Olaf
    Wednesday, May 20, 2009 9:33 PM
    Moderator
  • Hi Philip,
    did you already send a bug report via Microsoft Connect together with the CAB files created by the WHS Toolkit on server and client?
    Can you check the servers event log for errors again? Server services crashing is something, which should not happen and can have many reasons, not the least hardware related troubles.
    Best greetings from Germany
    Olaf
    Hi Olaf,

    No I did't - I got got too focused on working through your suggestions, but I will over the weekend.  What happens- do they respond or modify the software is  You remember that I talked about a popup that comes up talking about a back-up failure due to a problem with the connector. This only comes up when I try to backup multiple drives in the Vista  Desktop. If I backup just one drive, the backup gets to about 94% and then stops, the server goes go off line and starts to attempt to reconnect.

    I'll repeat both forms of backup over the weekend. I have to get up at 4:00am to go to work and I'm a bit too tired to do them properly now, and then send a bug report. What logs in particular should I be looking at? If you have no objection, I'll post them here for you perusal.

    Is it worth my while reinstalling the connector? If so what's the  best way to remove the existing version?

    Many thanks

    Philip
    Thursday, May 21, 2009 7:20 PM
  • Hi Philip,
    I don't think, that the situation you are exeriencing is Connector related, so a reinstall would not change anything.
    I would say, it's either hardware, backup database corruption (potentially caused by hardware or driver issues on the server) or network connectivity (this would not get stuck on the same position all the time).
    What happens, if you exclude other drives, is backup also stopping at 94%?
    Best greetings from Germany
    Olaf
    Friday, May 22, 2009 11:27 AM
    Moderator
  • Hi Olaf.
    Thanks.

    Yes - actually that's the only time it sticks at 94% - multiple drives give a backup failure popup (see above) alough you we will remember there was no problem with the very first backup.
    Even though it appears to stop at 94% the server reports a successful backup.

    Kind regards

    Philip
    Friday, May 22, 2009 8:42 PM
  • Hi Olaf,

    On Monday, I did both types of backup ie one of all active drives followed by C: on it's own. I attach the three homeserver logs for that day. Unfortunately, the backup log is too large to post here - what parts are the most relavent?
    Kind regards
    Philip

    Homeserver1

    Created at 25/05/2009 17:03:22
    ***** Started at 25/05/2009 17:03:22 ***
    ***** Started at 25/05/2009 17:03:22 ***
    [1]090525.170325.2031: BackupConfig: Error: Disconnected Backup Config
    [1]090525.170325.2500: BackupConfig: Error: Disconnected Backup Config
    [1]090525.170325.2656: Error: Client fb637cd9-3cad-43a0-8e26-fba9508849ce not found by BackupHelpers.FindClient
    [1]090525.170325.2656: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: fb637cd9-3cad-43a0-8e26-fba9508849ce
       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]090525.170325.2812: Error: Client bfa36b4b-0d7e-453d-80c8-112d71549d82 not found by BackupHelpers.FindClient
    [1]090525.170325.2812: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: bfa36b4b-0d7e-453d-80c8-112d71549d82
       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]090525.170325.2812: Error: Client 2ac032dd-767a-4d50-8997-eae6fbd38be7 not found by BackupHelpers.FindClient
    [1]090525.170325.2812: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 2ac032dd-767a-4d50-8997-eae6fbd38be7
       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]090525.170325.3437: BackupConfig: Error: Disconnected Backup Config
    [1]090525.170325.9843: Error: Error -2147023728 in SendMessage
    [10]090525.170326.1406: Error: Backup percentage is -2147483648
    [10]090525.170326.1406: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.170326.1875: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.170326.1875: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.170326.1875: Error: Cannot invoke RefreshData for HealthControl
    [10]090525.170329.1406: Error: Backup percentage is -2147483648
    [10]090525.170329.1406: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.170331.3593: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.170331.3593: Error: Error -2147023728 in SendMessage
    [11]090525.170336.1406: Error: Backup percentage is -2147483648
    [13]090525.170357.1406: Error: Backup percentage is -2147483648
    [14]090525.170527.6406: Error: Backup percentage is -2147483648
    [15]090525.170828.1406: Error: Backup percentage is -2147483648
    [1]090525.171135.7343: Error: Error -2147023728 in SendMessage
    [14]090525.173548.0000: Error: Backup percentage is -2147483648
    [11]090525.173551.0000: Error: Backup percentage is -2147483648
    [10]090525.173558.0000: Error: Backup percentage is -2147483648
    [14]090525.173618.0468: Error: Backup percentage is -2147483648
    [19]090525.173748.1406: Error: Backup percentage is -2147483648
    [13]090525.174048.6406: Error: Backup percentage is -2147483648


    Homeserver2

    Created at 25/05/2009 17:50:21
    ***** Started at 25/05/2009 17:50:21 ***
    ***** Started at 25/05/2009 17:50:21 ***
    [1]090525.175024.6406: BackupConfig: Error: Disconnected Backup Config
    [1]090525.175024.7812: BackupConfig: Error: Disconnected Backup Config
    [1]090525.175024.8125: Error: Client fb637cd9-3cad-43a0-8e26-fba9508849ce not found by BackupHelpers.FindClient
    [1]090525.175024.8125: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: fb637cd9-3cad-43a0-8e26-fba9508849ce
       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]090525.175024.8437: Error: Client bfa36b4b-0d7e-453d-80c8-112d71549d82 not found by BackupHelpers.FindClient
    [1]090525.175024.8437: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: bfa36b4b-0d7e-453d-80c8-112d71549d82
       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]090525.175024.8437: Error: Client 2ac032dd-767a-4d50-8997-eae6fbd38be7 not found by BackupHelpers.FindClient
    [1]090525.175024.8437: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 2ac032dd-767a-4d50-8997-eae6fbd38be7
       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]090525.175024.9218: BackupConfig: Error: Disconnected Backup Config
    [1]090525.175025.6250: Error: Error -2147023728 in SendMessage
    [13]090525.175027.7500: Error: Backup percentage is -2147483648
    [13]090525.175027.7500: Error: Cannot invoke RefreshData for HealthControl
    [7]090525.175027.7500: Error: Cannot invoke RefreshData for HealthControl
    [7]090525.175027.7500: Error: Cannot invoke RefreshData for HealthControl
    [7]090525.175027.7500: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.175030.5937: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.175030.5937: Error: Error -2147023728 in SendMessage
    [14]090525.175030.7500: Error: Backup percentage is -2147483648
    [13]090525.175037.7500: Error: Backup percentage is -2147483648
    [1]090525.175039.2031: Error: Error -2147023728 in SendMessage
    [1]090525.175045.5312: Error: Error -2147023728 in SendMessage
    [19]090525.175058.7343: Error: Backup percentage is -2147483648
    [1]090525.175210.1093: Error: Error -2147023728 in SendMessage
    [15]090525.180140.6875: Error: Backup percentage is -2147483648
    [20]090525.180143.6875: Error: Backup percentage is -2147483648
    [15]090525.180150.6875: Error: Backup percentage is -2147483648
    [13]090525.180210.7343: Error: Backup percentage is -2147483648
    [5]090525.180341.2343: Error: Backup percentage is -2147483648
    [23]090525.180641.7343: Error: Backup percentage is -2147483648


    Homeserver3

    Created at 25/05/2009 19:16:52
    ***** Started at 25/05/2009 19:16:52 ***
    ***** Started at 25/05/2009 19:16:52 ***
    [1]090525.191656.2343: BackupConfig: Error: Disconnected Backup Config
    [1]090525.191656.2656: BackupConfig: Error: Disconnected Backup Config
    [1]090525.191656.2812: Error: Client fb637cd9-3cad-43a0-8e26-fba9508849ce not found by BackupHelpers.FindClient
    [1]090525.191656.2812: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: fb637cd9-3cad-43a0-8e26-fba9508849ce
       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]090525.191656.2968: Error: Client bfa36b4b-0d7e-453d-80c8-112d71549d82 not found by BackupHelpers.FindClient
    [1]090525.191656.2968: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: bfa36b4b-0d7e-453d-80c8-112d71549d82
       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]090525.191656.2968: Error: Client 2ac032dd-767a-4d50-8997-eae6fbd38be7 not found by BackupHelpers.FindClient
    [1]090525.191656.2968: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 2ac032dd-767a-4d50-8997-eae6fbd38be7
       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]090525.191656.3593: BackupConfig: Error: Disconnected Backup Config
    [1]090525.191656.9531: Error: Error -2147023728 in SendMessage
    [14]090525.191659.0000: Error: Backup percentage is -2147483648
    [14]090525.191659.0000: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.191659.0000: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.191659.0156: Error: Cannot invoke RefreshData for HealthControl
    [8]090525.191659.0156: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.191701.8906: Error: Cannot invoke RefreshData for HealthControl
    [1]090525.191701.8906: Error: Error -2147023728 in SendMessage
    [13]090525.191702.0000: Error: Backup percentage is -2147483648
    [14]090525.191709.0000: Error: Backup percentage is -2147483648
    [1]090525.191709.5625: Error: Error -2147023728 in SendMessage
    [1]090525.191721.1406: Error: Error -2147023728 in SendMessage
    [19]090525.191730.0000: Error: Backup percentage is -2147483648
    [13]090525.191815.3281: Error: Backup percentage is -2147483648
    [13]090525.191818.3281: Error: Backup percentage is -2147483648
    [21]090525.191825.3437: Error: Backup percentage is -2147483648
    [23]090525.191845.5000: Error: Backup percentage is -2147483648
    [24]090525.192016.0000: Error: Backup percentage is -2147483648
    [25]090525.192316.5000: Error: Backup percentage is -2147483648
    [1]090525.212324.0937: Error: Error -2147023728 in SendMessage
    [1]090525.212340.8437: BackupConfig: Error: Disconnected Backup Config
    [1]090525.212340.8437: BackupConfig: Error: Disconnected Backup Config
    [1]090525.212350.8437: BackupConfig: Error: Disconnected Backup Config
    [1]090525.212350.8437: Error: Stale transport, The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
    [1]090525.212350.9062: Error: Exception thrown
    System.Runtime.InteropServices.COMException (0x8007045B): Retrieving the COM class factory for component with CLSID {3AA6FAC6-558C-4A4A-A60A-AC40B048C393} failed due to the following error: 8007045b.
       at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
       at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
       at System.Windows.Forms.Control.Invoke(Delegate method)
       at Microsoft.HomeServer.HomeServerConsoleTab.Health.HomeServerTabExtender.Health_DetailedView.RefreshData()



    Wednesday, May 27, 2009 7:56 PM
  • Hi Philip,
    if you have a chance, try another network card with explicit Windows Server 2003 drivers in your server. (Intel cards are claimed to be reliable and performant.)
    Best greetings from Germany
    Olaf
    Wednesday, May 27, 2009 8:07 PM
    Moderator
  • Hi Philip,
    if you have a chance, try another network card with explicit Windows Server 2003 drivers in your server. (Intel cards are claimed to be reliable and performant.)
    Best greetings from Germany
    Olaf

    I have bought another network card (but not installed it yet.  I couldn't find one with a server driver (Didn't think of Intel) but it will have XP ones. I do  not trust the onboard NVIDIA network adaptor - could'nt even find a site for updated drivers.

    Philip
    Thursday, May 28, 2009 4:07 PM
  • Hi Olaf

    I'm still plugging away at this problem!.
    I have now bought a Intel ethernet card and plan to install it over the weekend.
    I ran the connector troubleshooter again the other day and this time got something sensible from it. It advised that my version of connector software does not match the version of WHS. It advises deleting the Program Files\Windows Home Server Folder and then reinstalling from \\MY Server\Software\Home Server Connector Software.
    When I try and delete the WHS I get the denied because folder is open in another program message. I'm guessing that if I try with the server off, I will be allowed to do it, but then how will I be able to connect to the shared folders to get the new software? Or do I copy setup.exe to my computer first?
    Hope you can help, again.
    Kind regards
    Philip
     
    Thursday, June 11, 2009 10:39 PM
  • Hi Philip,
    access to the shared folders depends not from the Connector software, only from user name and password.
    Also without credentials you should be able to access the software installation source via http://server:55000.

    If I understand you right, something is denieing you access to the Windows Home Server folder in Program Files on the client.
    Don't you have full admin rights?
    Eventually disable user account control temporary before trying again.

    Best greetings from Germany
    Olaf

    Friday, June 12, 2009 1:52 PM
    Moderator
  • Hi Philip,
    access to the shared folders depends not from the Connector software, only from user name and password.
    Also without credentials you should be able to access the software installation source via http://server:55000 .

    If I understand you right, something is denieing you access to the Windows Home Server folder in Program Files on the client.
    Don't you have full admin rights?
    Eventually disable user account control temporary before trying again.

    Best greetings from Germany
    Olaf

    Thanks Olaf.
    Yes I originally installed the connector software from http://my server:55000. I am now being instructed to run setup.exe form the software shared folder.
    Witin regards to deleting the Windows Homer server folder, I am logged in as administrator. I have already tried turning off UAC and it didn't help.

    Kind regards

    Philip

    Friday, June 12, 2009 5:27 PM
  • Hi Philip,
    would it work if you start the client PC in safe mode?
    You might also try to use the freeware Unlocker to check, if there is a running application blocking the access (given we are talking about the client PC).
    Best greetings from Germany
    Olaf
    Saturday, June 13, 2009 2:58 PM
    Moderator
  • Hi Olaf.
    Yes starting the client (Vista) PC in safe mode worked.
    I then reinstalled the connector from the software folder as instructed and re-ran the troubleshooter - it still reports the wrong version!!
    I give up!! (Not really).
    Best Wishes
    Philip
    Sunday, June 14, 2009 2:24 PM
  • Hi Olaf.
    Yes starting the client (Vista) PC in safe mode worked.
    I then reinstalled the connector from the software folder as instructed and re-ran the troubleshooter - it still reports the wrong version!!
    I give up!! (Not really).
    Best Wishes
    Philip

    That's a known issue.  You can disregard that message.  The big question is do your backups work now? :)
    Sunday, June 14, 2009 2:37 PM
    Moderator
  • Hi Olaf.
    Yes starting the client (Vista) PC in safe mode worked.
    I then reinstalled the connector from the software folder as instructed and re-ran the troubleshooter - it still reports the wrong version!!
    I give up!! (Not really).
    Best Wishes
    Philip

    That's a known issue.  You can disregard that message.  The big question is do your backups work now? :)
    Hi kariya
    No. But, I'm not convinced I did the reinstall properly.  I mad the mistake of saving the old connector folder contents in another one I thing that may have confused things. (It seem to be using files form both). So, I'm going to try again and then install my lovely new Intel network connector.
    Philip
    Sunday, June 14, 2009 3:03 PM
  • "That's a known issue.  You can disregard that message.  The big question is do your backups work now? :) " (Quote from kariya.)

    Just a thought. Which is the more up to date version then. That available from Shared Files/Software//setup.exe or that from http://my server:55000?

    Philip
    • Edited by philip56 Sunday, June 14, 2009 7:19 PM accuracy
    Sunday, June 14, 2009 7:18 PM
  • The known issue may happen, if you use the WHS toolkit and the versions are different.
    This is not the case, if the connector icon itself cries for an update.

    The version in \\server\software\home server connector software and that you get via the http://server:55000 are the same source, so if you delete or alter something in the share, the download will also not function any more.

    You find also a copy of the installer files in C:\WHS on your server. The batch file ConnectorInstallAssistant.cmd located in that folder at least partially restores the installation files, as long as the folder home server connector software is still existing (but will miss the subfolders DOTNETFX20 and WindowsInstaller31, although those should be obsolete for up to date systems).

    Best greetings from Germany
    Olaf
    Sunday, June 14, 2009 9:02 PM
    Moderator
  • The known issue may happen, if you use the WHS toolkit and the versions are different.
    This is not the case, if the connector icon itself cries for an update.

    The version in \\server\software\home server connector software and that you get via the http://server:55000 are the same source, so if you delete or alter something in the share, the download will also not function any more.

    You find also a copy of the installer files in C:\WHS on your server. The batch file ConnectorInstallAssistant.cmd located in that folder at least partially restores the installation files, as long as the folder home server connector software is still existing (but will miss the subfolders DOTNETFX20 and WindowsInstaller31, although those should be obsolete for up to date systems).

    Best greetings from Germany
    Olaf
     
    Right,thanks Olaf.
    Well updating from \\server\software\home server connector software didn'tsolver the problem, so tomorrow I'll press on with replacing the ethernet card.
    Kind regards
    Philip
    Sunday, June 14, 2009 9:10 PM
  • Hi Olaf
    Right, first the good news! The Intel card has solved the backup problem. I haven't seen an automatic backup yet but I probably haven't left it long enough. However the Server now disconnects anywhere between 2 and 5 minutes at any time. I've used the remote connection to ensure that the adaptor does not shut down to save power. I tested by streaming audio to my laptop and the best I could manage was two tracks.
    One interesting thing I noticed was that after the server "logged out" pressing the reboot button on the case has no effect - you have to cut the power and restart. Should I be looking at something in the BIOS?
    Regards
    Philip
    Update
    I've been experimenting and discovered that this phenomena also happens with the on-board ethernet connector I was using. It never used to. I also added a couple of extra drives today. Is there a connection?
    • Edited by philip56 Monday, June 15, 2009 8:43 PM Additional Information
    Monday, June 15, 2009 8:00 PM
  • Hi Philip,
    such issues can be caused either by flaky hardware (including a weak power supply or thermal issues on the board - was it an older mainboard or a new?) or mad drivers, so the reason is hard to determine remotely. Are there any related entries in the event log?
    If you have changed settings in the Bios, you may reset the Bios to default values and only readjust the SATA controller settings, if they have been set to IDE compatility before.
    Can you shutdown the server from it's desktop using the normal start menu?
    Also consider, that not only the server is part of the network. Also the cables, the router/switch (did you try a separate GBit Switch already?) and the network interface/driver of the client may play a role.
    Also since you have added a new network adapter to your server, disable the onboard adapter in Bios or at least in device manager to avoid certain conflicts.
    Best greetings from Germany
    Olaf
    Tuesday, June 16, 2009 8:09 AM
    Moderator
  • Hi Olaf
    Thanks for your reply. To answer a few of your questions - It's a brand new  Abit motherboard with a 450w PSU. I'll check the Abit site for driver updates. With the Intel network adaptor I used the Intel driver package - I assume it installed the sevver driver. There does not seem to be a way to confirm that. I did obtain a Gbit Switch.
    Action so far. I've disabled the onboard adaptor and removed the two additional disc drives, first from the storage pool and then physically. These actions don't seem to have made any difference. I seem to remember that I had this problem of the server box refusing to reboot when I was building it - before I even loaded the software. I though I had sorted it. Tomorrow, I'm going to hook up a monitor and keyboard and have a look in the BIOS.
    Two questions.
    Are there any related entries in the event log? What sort of entries should I be looking for?
    Can you shutdown the server from it's desktop using the normal start menu? Do you mean via the Remote Desktop Connection or the Console on the client?
    Kind regards
    Philip
    Tuesday, June 16, 2009 8:15 PM
  • Are there any related entries in the event log? What sort of entries should I be looking for?
    Can you shutdown the server from it's desktop using the normal start menu? Do you mean via the Remote Desktop Connection or the Console on the client?

    Question 1: As usual - warnings and errors.
    Question 2: Both would be interesting. Remote Desktop, since the WHS console is also a Remote Desktop session. Console not on the client, but on the server, just for testing.

    Another test would be, to use the one spare disk you now have exclusively and perform a clean install of WHS on it. Update that machine and try, if it is now working.
    Seems to become one of these endless stories ...
    Best greetings from Germany
    Olaf
    Tuesday, June 16, 2009 9:29 PM
    Moderator
  • Yes, I'm sorry about the length of this - I think we are getting somewhere though. I plugged in a monitor and keyboard today and had a peek. I monitored the BIOS temperatures first - they seemed pretty stable. After about  5-10 minutes the monitor goes blank and the box refuses to respond to the reboot key until you cut the power at the switch on the back of the PSU. I then ran the console on the sever monitor and the same thing happened. So I need to investigate this. I'm not sure where to start - I may have to take the box in somewhere, which is a bit like admitting defeat.
    All the messing about adding new drives means that I have to reactivate and I need a new activation code. I can't find the right website - do you know where it is?
    Regards
    Philip
    Wednesday, June 17, 2009 8:36 PM
  • Are you talking about the Trial version? In this case its on connect.microsoft.com, as described in the text on the download page. (Not sure, if it is easy to request a new key there.)
    Check your PC, maybe you have a circuit somewhere? I once experienced strange instabilities, because a screw walking around on the board screwed up the system. On self built systems you have also screw holders on the downside of the mainboard, which are not used, but causing a circuit.

    Interesting would be, to boot from a Vista DVD or the WHS recovery disk and see, if Vista PE starts also to act strange after leaving it a while alone.
    Or install another OS (XP?) - if this is also becoming instable, the issue may be narrowed down to hardware or driver reasons.
    Best greetings from Germany
    Olaf
    • Marked as answer by philip56 Saturday, July 25, 2009 3:58 PM
    • Unmarked as answer by philip56 Saturday, July 25, 2009 3:59 PM
    Wednesday, June 17, 2009 11:21 PM
    Moderator
  • Hi Olaf.
    My sincere apologies for the delay in replying to you.
    I'm pretty sure the problem is hardware related - probably temperature. The cooler the room the longer the server runs. The room temperature must not exceed 25C. 23C is ideal. I think I'll take the machine into a repairer for their verdict.
    Many thanks for your all your help and advice.
    Kind regards
    Philip
    Saturday, July 25, 2009 4:03 PM