locked
Backup for one computer does not work: backup engine not idle after 60 seconds RRS feed

  • Question

  • I have a little network of a 3 laptops + whs server.
    Everything works fine except that the backup on one laptop does not work! 

    It is connecting to the server but when it comes to the configuration of the backup I get an error like (sorry but I have to translate it from German into English):

    "this computer cannot be backed up because there are no volumes that are configured in ntfs format"

    The harddisk is formated with ntfs
    there is no firewall except the win xp one and i also tried it without firewall
    virus scanner
    Of course I tried chkdsk /r but nothing changed

    the only difference in the pcdiscovery.log compared to the other laptops where the backup works says the following at the end:

    [07.11.2008 10:59:46  924] ERROR: Backup engine not idle after 60 seconds, state=1stateDetail=9!  
    [07.11.2008 10:59:54  924] PASS :CDialog_Finished::GetBackupDetail succeeded (at func: GetTimeFormat, d:\wssg_src\whs_pp1\qhs\src\client\discovery\dialog_finished.cpp (188)  
    [07.11.2008 10:59:54  924] PASS :CDialog_Finished::GetBackupDetail succeeded (at func: GetTimeFormat, d:\wssg_src\whs_pp1\qhs\src\client\discovery\dialog_finished.cpp (196)  
    ERROR: Could not create VDS loader (0x80040154)  
    ERROR: Could not query device number, 1  
    ERROR: Could not query device number, 1  
     
     
    I hope very much that someone can help!
    Friday, November 7, 2008 3:16 PM

Answers

  • I solved the problem with the support of a friend who used to work for MS by making my harddisk an active volume.

    thanks a lot anyway!
    • Marked as answer by eup77 Tuesday, November 11, 2008 5:11 PM
    Tuesday, November 11, 2008 5:11 PM

All replies

  • Is it possible that you have manipulated the partitions on your laptop, using tools like Partition Magic or Disk Director? Or used drive imaging tools like Ghost or True Image? Was your disk originally formatted with FAT32 and converted to NTFS?
    I'm not on the WHS team, I just post a lot. :)
    Friday, November 7, 2008 3:57 PM
    Moderator
  • yes, you are right I used a tool called Acronis Migrate Easy with which I copied the content of my old laptop hard disk to a new and bigger one. If that would be the problem, what can I do about it?
    Thanks, Uli
    Sunday, November 9, 2008 12:39 AM
  • First, before anything else, I'd like to you to submit a bug on Connect. Include logs from both your server and the client laptop tthha re havving problems. You can use the WHS Toolkit to collect and send the logs. (I recommend you read the Toolkit manual, as installation of the server component isn't as obvious as one might wish.) In the description, include what the problem is, and what you did to your laptop. Software versions, hardware, etc. will be important. Microsoft may not consider this a bug, as (if it was the disk imaging software) they may take the position that what you did was an unsupported way of migrating disks.

    If it's the disk imaging tool that caused the problem, was the hard drive replacement recent? If it was within the last few days, and you have a WHS backup of the laptop from before, you could simply use the Restore CD to restore the disk as of the last backup. You'll get the option to erase any partitions already on the drive, which is what you will want to do. Then simply restore the most recent backup, using the full drive.


    I'm not on the WHS team, I just post a lot. :)
    Sunday, November 9, 2008 3:14 AM
    Moderator
  • I do not have a backup of the laptop in WHS which I could restore so I have to find another solution.

    Here are the logs of my computer (Laptop HP-Compaq nx5000, Pentium 1,6Ghz, 1 Gb Ram, 250Gb HD, XP Prof. SP3) -
    Connector:

    TraceCleanup: discarding log C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\Microsoft\Windows Home Server\logs\Connector.110108.log  
    TraceCleanup: discarding log C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\Microsoft\Windows Home Server\logs\Connector.110208.log  
     
     
    ********** Starting log, build Jul 12 2008 13:25:44 (6.0.1800.0), Process Id 670 **********  
     
     
     
    *************************** WHSConnector SERVICE STARTED ************************************  
     
    [10.11.2008 08:51:51  688] CTransportConfig::ServerID Server ID is ad4420cc-6d0f-4c7b-8661-7fb44d34f401  
    [10.11.2008 08:51:51  560] NetworkStatus::getNetworkStatus Available address: 192.168.178.27 (1bb2a8c0)  
    [10.11.2008 08:51:51  560] NetworkStatus::getNetworkStatus Available address: 127.0.0.1 (0100007f)  
     
    [2008/11/10 08:51:51  560]   CTransportConfig::RecoverConfig Verifying 2 clients  
    [10.11.2008 08:51:56  560] CTransportConfig::ServerName reslen=0, Server name is <LR-SERVER-1>.  
    [10.11.2008 08:51:57  560] Version 6.0.1800.0  
     
    [2008/11/10 08:51:57  560]   CTransportPipe::Open Pipe 1 to {AD4420CC-6D0F-4C7B-...} is opened, hr=00000000 
    [10.11.2008 09:32:05  778] Partner shut down the connection  
    [10.11.2008 09:32:05  778] Read 0 bytes, hr=80004004 
     
    [2008/11/10 09:32:05  560] + CTransportSinkManager::ShutDown   
    [2008/11/10 09:32:05  560] - CTransportSinkManager::ShutDown   
    [10.11.2008 09:32:05  688] ----- WHSConnector SERVICE ENDED -----  
     
     
    ********** Starting log, build Jul 12 2008 13:25:44 (6.0.1800.0), Process Id 1240 **********  
     
     
     
    *************************** WHSConnector SERVICE STARTED ************************************  
     
    [10.11.2008 09:32:05 12e4] CTransportConfig::ServerID Server ID is ad4420cc-6d0f-4c7b-8661-7fb44d34f401  
    [10.11.2008 09:32:05 1300] NetworkStatus::getNetworkStatus Available address: 192.168.178.27 (1bb2a8c0)  
    [10.11.2008 09:32:05 1300] NetworkStatus::getNetworkStatus Available address: 127.0.0.1 (0100007f)  
     
    [2008/11/10 09:32:06 1300]   CTransportConfig::RecoverConfig Verifying 2 clients  
    [10.11.2008 09:32:11 1300] CTransportConfig::ServerName reslen=0, Server name is <LR-SERVER-1>.  
    [10.11.2008 09:32:11 1300] Version 6.0.1800.0  
     
    [2008/11/10 09:32:11 1300]   CTransportPipe::Open Pipe 1 to {AD4420CC-6D0F-4C7B-...} is opened, hr=00000000 
    [10.11.2008 09:51:21 1250] Partner shut down the connection  
    [10.11.2008 09:51:21 1250] Read 0 bytes, hr=80004004 
     
    [2008/11/10 09:51:21 1300] + CTransportSinkManager::ShutDown   
    [2008/11/10 09:51:21 1300] - CTransportSinkManager::ShutDown   
    [10.11.2008 09:51:21 12e4] ----- WHSConnector SERVICE ENDED ----- 

    and here is the laptops pcdiscovery.log again:

    [10.11.2008 09:50:58 1280] ERROR: wWinMain failed, HR=0x80070002 (at func: RegDeleteValue, d:\wssg_src\whs_pp1\qhs\src\client\discovery\main.cpp (170)  
    [10.11.2008 09:50:58 1280] m_PartnerManager.CoCreateInstance.  
    [10.11.2008 09:50:59 1280] Calling m_PartnerManager.StopServerDiscovery.  
    [10.11.2008 09:50:59 1280] m_PartnerManager.StopServerDiscovery returns 0x8000FFFF.  
    [10.11.2008 09:50:59 1280] Calling m_PartnerManager.StartServerDiscovery.  
    [10.11.2008 09:50:59 1280] m_PartnerManager.StartServerDiscovery returns 0x0.  
    [10.11.2008 09:51:05 1280] Calling m_PartnerManager.CheckServer, serverName=LR-SERVER-1, manual=0.  
    [10.11.2008 09:51:05 1280] m_PartnerManager.CheckServer returns 0x0.  
    [10.11.2008 09:51:10 1280] Calling m_PartnerManager.GetServerDetails.  
    [10.11.2008 09:51:10 1280] m_PartnerManager.GetServerDetails returns 0x0.  
    [10.11.2008 09:51:10 1280] WARN : JoinServer - admin name is Administrator.  
    [10.11.2008 09:51:10 1280] Calling m_PartnerManager.JoinServer, serverName=LR-SERVER-1, manual=0.  
    [10.11.2008 09:51:11 1280] m_PartnerManager.JoinServer returns 0x0.  
    [10.11.2008 09:51:21 1280] Calling m_PartnerManager.CheckServer, serverName=LR-SERVER-1, manual=0.  
    [10.11.2008 09:51:21 1280] m_PartnerManager.CheckServer returns 0x0.  
    [10.11.2008 09:51:21 17a0] Stopping WHSConnector.  
    [10.11.2008 09:51:21 17a0] PASS :ConfigManager::Restart succeeded (at func: ServiceManager::StopService, d:\wssg_src\whs_pp1\qhs\src\client\common\inc\configmanager.h (40)  
    [10.11.2008 09:51:21 17a0] Starting WHSConnector.  
    [10.11.2008 09:51:23 17a0] PASS :ConfigManager::Restart succeeded (at func: ServiceManager::StartService, d:\wssg_src\whs_pp1\qhs\src\client\common\inc\configmanager.h (44)  
    [10.11.2008 09:51:29 1280] ERROR: Backup engine not idle after 60 seconds, state=1stateDetail=9!  
    [10.11.2008 09:51:31 1280] PASS :CDialog_Finished::GetBackupDetail succeeded (at func: GetTimeFormat, d:\wssg_src\whs_pp1\qhs\src\client\discovery\dialog_finished.cpp (188)  
    [10.11.2008 09:51:31 1280] PASS :CDialog_Finished::GetBackupDetail succeeded (at func: GetTimeFormat, d:\wssg_src\whs_pp1\qhs\src\client\discovery\dialog_finished.cpp (196)  
    ERROR: Could not create VDS loader (0x80040154)  
    ERROR: Could not query device number, 1  
    ERROR: Could not query device number, 1  
     

    here the server`s homeserverconsole.log:

    Created at 10.11.2008 10:02:35  
    ***** Started at 10.11.2008 10:02:35 ***  
    ***** Started at 10.11.2008 10:02:35 ***  
    [1]081110.100707.4687: Error: Client 772ade96-f11d-48d2-8644-6f79582489fd not found by BackupHelpers.FindClient  
    [1]081110.100707.4687: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 772ade96-f11d-48d2-8644-6f79582489fd  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient  
    [1]081110.100707.5156: Error: Client a14cf35b-3a16-44e3-9a71-cc8f00ee8b66 not found by BackupHelpers.FindClient  
    [1]081110.100707.5156: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: a14cf35b-3a16-44e3-9a71-cc8f00ee8b66  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient  
    [1]081110.100707.5156: Error: Client 5bd38e1a-17f7-4ebd-bbde-a91c16daf26d not found by BackupHelpers.FindClient  
    [1]081110.100707.5156: Error: Client Microsoft.HomeServer.HomeServerConsoleTab.Health.ClientNotFoundException: 5bd38e1a-17f7-4ebd-bbde-a91c16daf26d  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClient(ConfigurationRoot configurator, Guid pcGuid)  
       bei Microsoft.HomeServer.HomeServerConsoleTab.Health.BackupHelpers.FindClientNoThrow(ConfigurationRoot configurator, Guid pcGuid) not found by BackupHelpers.FindClient  
    [1]081110.100713.1093: Error: Error -2147023728 in SendMessage  
    [8]081110.100714.9531: Error: Backup percentage is -2147483648  
    [8]081110.100714.9531: Error: Cannot invoke RefreshData for HealthControl  
    [5]081110.100714.9843: Error: Cannot invoke RefreshData for HealthControl  
    [5]081110.100714.9843: Error: Cannot invoke RefreshData for HealthControl  
    [5]081110.100715.0000: Error: Cannot invoke RefreshData for HealthControl  
    [8]081110.100717.9531: Error: Backup percentage is -2147483648  
    [8]081110.100717.9531: Error: Cannot invoke RefreshData for HealthControl  
    [1]081110.100723.3750: Error: Cannot invoke RefreshData for HealthControl  
    [1]081110.100723.3750: Error: Error -2147023728 in SendMessage  
    [13]081110.100725.9843: Error: Backup percentage is -2147483648  
    [15]081110.100746.4531: Error: Backup percentage is -2147483648  
    [16]081110.100916.9531: Error: Backup percentage is -2147483648  
    [1]081110.101040.3281: Error: Error -2147023728 in SendMessage  
    [1]081110.101119.6406: Error: Exception thrown  
    Microsoft.HomeServer.Controls.ModalException: Second SetWindowPos  
     
    [1]081110.101119.6406: Error: Error 1400  
    [1]081110.101119.6406: Error: Exception thrown  
    Microsoft.HomeServer.Controls.ModalException: Second SetWindowPos  
       bei Microsoft.HomeServer.Controls.ModalProcess.MakeModal(IntPtr hProc, Form f)  
       bei Microsoft.HomeServer.Controls.ModalProcess.Start(ProcessStartInfo psi)  
     
    [18]081110.101217.4531: Error: Backup percentage is -2147483648  
    [1]081110.101820.3281: Error: Error -2147023728 in SendMessage  
     

    I hope this helps to identify the problem.
    Thanks, Uli

    Monday, November 10, 2008 9:22 AM
  • Please submit a bug on Connect, as I requested previously, including logs uploaded using the WHS Toolkit. This will give Microsoft a chance to actually look at your issue. Posting logs in the forums isn't as helpful as one might wish, because nobody here has access to Microsoft's internal tools or source code.

    I'm only guessing that it was the disk imaging tool that caused your problem. The "Not formatted with NTFS" error can be caused by converting a FAT32 disk to NTFS, and it can also be caused by some disk/partition management tools. The end result is a disk partition that fails to meet some requirement of the WHS backup tool. As for fixing it, I would have to have the hardware sitting in front of me, and even then it's likely that (as a practical matter) it would be better to back everything up using a tool like NTBackup, wipe the drive entirely, reinstall making sure to format the partition as NTFS during installation, and go from there.

    Not what you want to hear, I know...

    I'm not on the WHS team, I just post a lot. :)
    Monday, November 10, 2008 12:48 PM
    Moderator
  • Ken Warren said:

    Please submit a bug on Connect, as I requested previously, including logs uploaded using the WHS Toolkit. This will give Microsoft a chance to actually look at your issue. Posting logs in the forums isn't as helpful as one might wish, because nobody here has access to Microsoft's internal tools or source code.

    I'm only guessing that it was the disk imaging tool that caused your problem. The "Not formatted with NTFS" error can be caused by converting a FAT32 disk to NTFS, and it can also be caused by some disk/partition management tools. The end result is a disk partition that fails to meet some requirement of the WHS backup tool. As for fixing it, I would have to have the hardware sitting in front of me, and even then it's likely that (as a practical matter) it would be better to back everything up using a tool like NTBackup, wipe the drive entirely, reinstall making sure to format the partition as NTFS during installation, and go from there.

    Not what you want to hear, I know...


    I'm not on the WHS team, I just post a lot. :)



    Thanks Ken. In addition to the tools we can also assign the bugs directly to the developers for review. It is a much faster proces.


    Lara Jones [MSFT] Windows Home Server Team
    Monday, November 10, 2008 5:04 PM
    Moderator
  • I solved the problem with the support of a friend who used to work for MS by making my harddisk an active volume.

    thanks a lot anyway!
    • Marked as answer by eup77 Tuesday, November 11, 2008 5:11 PM
    Tuesday, November 11, 2008 5:11 PM
  • I'm having the same Issue with 3 computers and a WHS...What is the fix? PLEASE HELP!!!!!!!
    Tuesday, December 29, 2009 10:31 PM