locked
System.ArgumentOutOfRangeException When Performing Backup of Vista Client RRS feed

  • Question

  • I "moved up" about 3 months ago from my beta test unit to an HP EX475 with 2 500GB drives. It is unchanged from the factory ship and has been functioning fine since a 13 January 2008 "factory reset" done to clean it up and put it nto production use.

     

    On Wednesday evening, 2/27, I installed PerfectDisk 2008 on my Vista Ultimate client and on the MSS. I set the MSS up to run it on Sunday mornings -- well after any backup/cleanup activity. I set the Vista client up to run it "silently". And I ran a one-time manual operation on the Vista machine, followed by a start-up scan. Took some time but things on the client seemed perkier. Went to bed.


    On Thursday morning I found my automatic backup on the Vista client failed. Very first time this has happened. I figured PerfectDisk and the backup were probably competing for a file, smiled and (successfully) executed a manual backup. Then I installed and ran PerfectDisk on my WinXP Home laptop. No problems.

    On Friday morning the Vista backup failed again and the XP backup was successful. But now the manual backup is also failing "because of a problem with [my] Windows Home Server Connector software.: There is a reference to the Event Log, but the MSS/WHS log is of no help and the Vista log is rather confusing.

    I ran the tests in the MSS toolkit - all "passed". ALL OTHER FUNCTIONS ARE WORKING PROPERLY, shares, etc... Tried the client-side of the toolkit and it indicated it could not find the server. Tried "Discover" but, naturally that failed (Friday was 2/29....). It being early in the day no one had yet reported the leap year problem so I tried to reinstall the client. And once I realized the problems there I waited for morning to prusue this further.

    On Saturday I successfully re-installed the client, configured the backups, and tested the other functions. All looked good and the XP machine backed up normally again. Tried a manual backup -- but, again, it fails.

    There have been no other changes that I am aware of on the Vista Client or the MSS -- just the addition of PerfectDisk 2008. And definitely no router changes. I use a fixed IP address for the MSS/WHS unit and it is in the same WorkGroup as my two clients.

    The Vista Client Toolkit does have problems with uPnP discovery but does find the client with the backup beacon. This is a new "red X" from the toolkit and may indicate the problem area. At least I think this is new, but I know of no recent changes in this area. No help on the right. What it did find with the beacon is correct.

    I also get a warning on left side for "Check Application Compatibility", but I see nothing flagged on the right. II would not have been surprised to see AdAware flagged here as Windows OneCare does not like AdAware being around.  

     

    Here are the MSS Event Application Log entries (5) from a manual this morning, following a restart of both Vista and MSS units:

    Quote:
      1. Backup set 55 for VISTA-PC has started. (Info)
      2. Backup of VISTA-PC D:\ has started. Info)
      3. Received abort message from VISTA-PC with reason 7. (Error)

      4. Backup of VISTA-PC D:\ has failed. (Error)
      5. Backup set 55 for VISTA-PC has finished. (Info)

    From the Vista Client Event Viewer --> Custom Views --> Administrative Events:

    First Message:

    Quote:
    Backup of volume D: to SERVER-HP failed: System.ArgumentOutOfRangeException: Number was less than the array's lower bound in the first dimension.
    Parameter name: srcIndex
    at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
    at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.InitializeBitMaps()
    at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()
    at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()

    Second Message:

    Quote:
    Backup set 55 on VISTA-HP failed: System.ArgumentOutOfRangeException: Number was less than the array's lower bound in the first dimension.
    Parameter name: srcIndex
    at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
    at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.InitializeBitMaps()
    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()


    The same messages appear in other Event log Views. I did not notice any others that appeared to be relevent, but if there is something specific that I should look for please let me know. The "System.ArgumentOutOfRangeException" seems to be the key...

    I have also executed CHKDSK C: /f /r and CHKDSK D: /f /r via RDP on the MSS/WHS unit. Did not help.

     

    I have also upgraded PerfectDisk to the very latest build (as of yesterday). Did not expect that to help -- and it didn't!

     

    Can ANYONE shed any light on this? I posted this sequence to MediaSmartServer.net and to WeGotServed several days ago but have not gotten any meaningful assistance, only unexpected silence!


    (Apologies for the length of this post. Documenting steps taken to this point to save some time later!)

    Wednesday, March 5, 2008 9:57 PM

Answers


  • @ekutter 

    The original problem was fixed in PP1.  If your server says “Power Pack 1” and your client icon is green, then you should be running Power Pack 1 (BackupEngine.exe build 6.0.01800)  The fix was specific to failures with System.ArgumentOutOfRangeException including a reference at “Microsoft.HomeServer.Backup.BackupOp.BackupOperation.InitializeBitMaps()”. 

    It sound like this may be a different problem.  Please provide TALQ reports (CAB #'s) from each failing client computer and file a bug for further investigation.


    -j
    Monday, September 8, 2008 11:33 PM

All replies

  • Thanks for the clear and lengthy post.  Just so I understand:

     

    • Backups are working fine on your Windows XP PC - or did they also stop working?
    • Backups are failing with above error message on your Windows Vista PC, but have worked previously
    • What happens if you remove PerfectDisk from the Vista PC and try to run a Backup Now?

     

    Thursday, March 6, 2008 11:01 PM
  •  T. Headrick wrote:
    • Backups are working fine on your Windows XP PC - or did they also stop working?
    • Backups are failing with above error message on your Windows Vista PC, but have worked previously
    • What happens if you remove PerfectDisk from the Vista PC and try to run a Backup Now?

      Yes, backups are working fine on the Windows XP Client

       

      Yes, they are failing now -- after the installation (and use) of PerfectDisk 2008 (WHS version). They had been running fine for a couple months.

       

      Same failure if I remove PerfectDisk ad re-run it. (Af6er re-booting Vista Client and the WHS box.

      Friday, March 7, 2008 4:28 AM
    • Do you have the Windows Home Server Toolkit installed on this Vista PC and your home Server?  It would be great if you could Send the Logs for your PC running Vista and your home server and post the CAB number here.

       

      Link to Toolkit Manual --> http://go.microsoft.com/fwlink/?LinkId=108364

       

      Link to downloadable toolkit --> http://go.microsoft.com/fwlink/?LinkID=98601

       

      Friday, March 7, 2008 9:32 PM
    •  JohnBick wrote:
       T. Headrick wrote:
      • Backups are working fine on your Windows XP PC - or did they also stop working?
      • Backups are failing with above error message on your Windows Vista PC, but have worked previously
      • What happens if you remove PerfectDisk from the Vista PC and try to run a Backup Now?

        Yes, backups are working fine on the Windows XP Client

         

        Yes, they are failing now -- after the installation (and use) of PerfectDisk 2008 (WHS version). They had been running fine for a couple months.

         

        Same failure if I remove PerfectDisk ad re-run it. (Af6er re-booting Vista Client and the WHS box.



        Not that you should do this, but it would be curious to see if this worked:

        1. Copy backup data base to external drive (use instructions from backup whitepaper)
        2. Remove all backups for the Vista computer that fails to backup (or clear the database)
        3. Try to do a new backup of the Vista computer.

        Friday, March 7, 2008 9:47 PM
      • I have been getting the exact same errors but in reverse.  My Vista machines are working/backing up fine but my XP machine started having problems almost the exact same time as this report, 2/29/08 was my last successfull backup.  Both manual and automatic backups are failing the with "out of range" error.  I am not running any third party software on my WHS.  All of my backups on all machines had been working fine for over a month before this.

         

        The one oddity that WHS diagnostics on my XP machine shows is "No DHCP server, or DHCP server is not reachable".  The XP machine does have a static IP address but the DHCP (my router) is definitely visible from the machine.  The XP machine is connected directly into the router.  All my other machines (Vista and XP) use dynamic IP addresses.

         

        Wednesday, March 12, 2008 5:58 PM
      • I need to add that I am getting eactly the same issue with a long running Win XP MCE machine. It is the only one of four machines on my network that is not able to backup. I get the same exact error. All my machines are using DHCP but their are using permanently assigned addresses on the router..
        I installed the EX470, added a 750GB drive (backup failure was occuring both before and after the drive installation).

        my error is
        An unexpected exception occurred on the computer
        ArgumentOutOfRangeException
        Number was less than the array's lower bound in the first dimension.
        Parameter name: srcIndex
        at System.Aray.Copy (Array sourceArray,Int32sourceIndex,Array
        destinationArray,Int32destinationIndex,Int32length,Boolean
        reliable

        The other pc's on my network are running vista ultimate, and xp pro. THe problem pc is using roughly 50% of the installed hd and otherwise is working fine. The cable from the problem pc is connected to a switch which is connected to the router the HP Mediaserver is connected to. All the other machines are also connected to this switch. The network is a cat 6 Gig setup.
        I have seen someone suggest that this issue was seen with some onboard LAN cards.. This machine is not using an onboard lan card, but a add on PCI card to support a Gig connection. INcase it was that add on nic card I disabled it and enabled the onboard nic card and have gotten the same error.

        Any help is appreciated, by EVERYONE who is getting this error. I know there are a few of us.

        John


        Thursday, March 13, 2008 12:45 PM
      •  T. Headrick wrote:

        Do you have the Windows Home Server Toolkit installed on this Vista PC and your home Server?  It would be great if you could Send the Logs for your PC running Vista and your home server and post the CAB number here.

         

        Link to Toolkit Manual --> http://go.microsoft.com/fwlink/?LinkId=108364

         

        Link to downloadable toolkit --> http://go.microsoft.com/fwlink/?LinkID=98601

         

         

        WHS CAB # 452662659

        Vista CAB # 452668116

         

        The Vista Connector Troubleshooter showed green checks for all tests on left EXCEPT for a warning on "[5.8] Check Application Compatibility". Here is the upper right screen when that is selected on the left:

         

        ID: 2000 TurboTax Deluxe; DisplayName: 2000 TurboTax Deluxe
        ID: 2001 TurboTax Premier; DisplayName: 2001 TurboTax Premier
        ID: Adobe Flash Player ActiveX; DisplayName: Adobe Flash Player ActiveX
        ID: Adobe Flash Player Plugin; DisplayName: Adobe Flash Player Plugin
        ID: Advanced WindowsCare V2 Personal_is1; DisplayName: Advanced WindowsCare 2.56 Personal
        ID: AIM_6; DisplayName: AIM 6
        ID: ALchemy X-Fi; DisplayName: Creative ALchemy (X-Fi Edition)
        ID: AOL Toolbar; DisplayName: AOL Toolbar 5.0
        ID: AudioCS; DisplayName: Creative Audio Console
        ID: CameraWindowDVC6; DisplayName: Canon Camera Window DC_DV 6 for ZoomBrowser EX
        ID: CameraWindowMC; DisplayName: Canon Camera Window MC 6 for ZoomBrowser EX
        ID: Canon G.726 WMP-Decoder; DisplayName: Canon G.726 WMP-Decoder
        ID: Canon RAW Codec; DisplayName: Canon RAW Codec
        ID: CdaC13Ba; DisplayName: SafeCast Shared Components
        ID: Console Launcher; DisplayName: Creative Console Launcher
        ID: Creative Jukebox Driver; DisplayName: Creative Jukebox Driver
        ID: Desktop Encyclopedia; DisplayName: Desktop Encyclopedia
        ID: Duplicate File Finder_is1; DisplayName: Duplicate File Finder 1.1.0.3
        ID: EOS 20D WIA Driver; DisplayName: EOS 20D WIA Driver
        ID: EOS Utility; DisplayName: Canon Utilities EOS Utility
        ID: Family Lawyer 2002; DisplayName: Family Lawyer 2002
        ID: FL 2002 Registration; DisplayName: FL 2002 Registration
        ID: InCharge; DisplayName: InCharge
        ID: InfraRecorder; DisplayName: InfraRecorder
        ID: InstallShield_{589D17BB-C997-48C0-BCD2-CC8DC3375FE8}; DisplayName: Canon Utilities EOS Capture 1.5
        ID: Locked Programs; DisplayName: Locked Programs
        ID: Mosby's Medical Encyclopedia; DisplayName: Mosby's Medical Encyclopedia
        ID: MovieEditTask; DisplayName: Canon MovieEdit Task for ZoomBrowser EX
        ID: Mozilla Firefox (2.0.0.12); DisplayName: Mozilla Firefox (2.0.0.12)
        ID: Mozilla Thunderbird (2.0.0.12); DisplayName: Mozilla Thunderbird (2.0.0.12)
        ID: My Web Search WB Uninstall; DisplayName: WeatherBug Browser Bar - powered by MyWebSearch
        ID: NVIDIA Drivers; DisplayName: NVIDIA Drivers
        ID: Organizer Conversion Utility; DisplayName: Organizer Conversion Utility
        ID: PC Pitstop Erase_is1; DisplayName: PC Pitstop Erase 1.1
        ID: PC Pitstop Exterminate_is1; DisplayName: PC Pitstop Exterminate 1.0
        ID: PC Pitstop Optimize_is1; DisplayName: PC Pitstop Optimize 1.5
        ID: PCPitstop Panda AntiVirus Scan; DisplayName: PCPitstop Panda AntiVirus Scan (remove only)
        ID: PhotoStitch; DisplayName: Canon Utilities PhotoStitch
        ID: PrimoPDF3.1; DisplayName: PrimoPDF
        ID: RAW Image Task; DisplayName: Canon RAW Image Task for ZoomBrowser EX
        ID: RemoteCaptureTask; DisplayName: Canon RemoteCapture Task for ZoomBrowser EX
        ID: Savings Bond Wizard; DisplayName: Savings Bond Wizard
        ID: TeraCopy_is1; DisplayName: TeraCopy 1.22
        ID: The Plain-Language Law Dictionary; DisplayName: The Plain-Language Law Dictionary
        ID: TurboTax Deluxe 2004; DisplayName: TurboTax Deluxe 2004
        ID: TurboTax Deluxe 2005; DisplayName: TurboTax Deluxe 2005
        ID: TurboTax Deluxe Deduction Maximizer 2006; DisplayName: TurboTax Deluxe Deduction Maximizer 2006
        ID: TurboTax Premier 2002; DisplayName: TurboTax Premier 2002
        ID: TurboTax Premier 2003; DisplayName: TurboTax Premier 2003
        ID: TurboTax Premier 2007; DisplayName: TurboTax Premier 2007
        ID: tv_enua; DisplayName: Lernout & Hauspie TruVoice American English TTS Engine
        ID: Ultimate Label Maker v2; DisplayName: Ultimate Label Maker v2
        ID: Uninstaller_B516B000_Creative ALchemy for X-Fi; DisplayName: Creative ALchemy for X-Fi (Shared Components)
        ID: ViewpointMediaPlayer; DisplayName: Viewpoint Media Player
        ID: WeatherBug; DisplayName: WeatherBug
        ID: Webshots Desktop; DisplayName: Webshots Desktop
        ID: WinSS; DisplayName: Windows Live OneCare
        ID: ZoomBrowser EX; DisplayName: Canon Utilities ZoomBrowser EX
        ID: {0008546E-DF6E-4CC1-AFD0-2CB8E16C95A2}; DisplayName: Notifier
        ID: {00212357-3B02-4C78-BCCB-45F635DABAC3}; DisplayName: Microsoft Office Live Meeting 2005
        ID: {03EDED24-8375-407D-A721-4643D9768BE1}; DisplayName: kgchlwn
        ID: {073F22CE-9A5B-4A40-A604-C7270AC6BF34}; DisplayName: ESSSONIC
        ID: {084AF11D-CF20-4FD3-AE25-BC655B467BEA}; DisplayName: HP MediaSmart Server
        ID: {0A4DF5B0-983C-4691-9D4A-9FD1D4B2A69F}; DisplayName: Secunia PSI (BETA)
        ID: {113EECD6-9A04-11D4-811D-00805F923B86}; DisplayName: Lotus NotesSQL 3.01 driver
        ID: {11F3F858-4131-4FFA-A560-3FE282933B6E}; DisplayName: kgchday
        ID: {14D4ED84-6A9A-45A0-96F6-1753768C3CB5}; DisplayName: ESSPCD
        ID: {16115E10-502B-4EA0-BD39-4DA329AD89E2}; DisplayName: BELKIN F5U109
        ID: {167E980B-3197-409F-ABD6-971165C769C3}; DisplayName: PTS
        ID: {1F698102-5739-441E-96F0-74F4EA540F06}; DisplayName: Attansic Giga Ethernet Utility
        ID: {21E49794-7C13-4E84-8659-55BD378267D5}; DisplayName: Windows Home Server Connector
        ID: {2318C2B1-4965-11d4-9B18-009027A5CD4F}; DisplayName: Google Toolbar for Internet Explorer
        ID: {2B6EC03E-6FA0-4D7C-9CCE-1B03819AB613}; DisplayName: PerfectDisk 2008 Professional
        ID: {2D03B6F8-DF36-4980-B7B6-5B93D5BA3A8F}; DisplayName: essvatgt
        ID: {2E7595EC-4FB1-4E29-93D4-9083C8A9B107}; DisplayName: TurboTax ItsDeductible 2005
        ID: {310BC5E2-31AF-49BB-904D-E71EB93645DC}; DisplayName: AI Suite
        ID: {3248F0A8-6813-11D6-A77B-00B0D0160010}; DisplayName: Java(TM) SE Runtime Environment 6 Update 1
        ID: {3248F0A8-6813-11D6-A77B-00B0D0160030}; DisplayName: Java(TM) 6 Update 3
        ID: {340D61BB-350A-40F4-8CFD-4F860E12066E}; DisplayName: SSA Benefit Calculator
        ID: {36495C59-089C-49D1-BD15-9E5BD86DC9A1}; DisplayName: ItsDeductible Express
        ID: {37477865-A3F1-4772-AD43-AAFC6BCFF99F}; DisplayName: MSXML 4.0 SP2 (KB927978)
        ID: {3851147E-5A91-4469-BA4D-13FFFCC8A920}; DisplayName: Microsoft Windows OneCare Live v2.0.2500.14 Idcrl Install
        ID: {3B0F52AC-EF5C-4831-B221-06C782E41280}; DisplayName: Quicken 2008
        ID: {44734179-8A79-4DEE-BB08-73037F065543}; DisplayName: Apple Mobile Device Support
        ID: {4537EA4B-F603-4181-89FB-2953FC695AB1}; DisplayName: netbrdg
        ID: {4F726761-6E69-7A65-7236-2E31302D0409}; DisplayName: IBM Lotus Organizer 6 - English
        ID: {511D773E-88A2-4AA5-9D92-77DB51887BFD}; DisplayName: Greeting Card Factory Deluxe
        ID: {536D6172-7453-7569-7465-392E38300409}; DisplayName: Lotus SmartSuite - English
        ID: {5660022E-F3F2-4126-8CC5-9726C47150EB}; DisplayName: Microsoft Windows Live OneCare Resources v2.0.2500.22
        ID: {587178E7-B1DF-494E-9838-FA4DD36E873C}; DisplayName: AsusUpdate
        ID: {589D17BB-C997-48C0-BCD2-CC8DC3375FE8}; DisplayName: EOS Capture 1.5
        ID: {5A0C892E-FD1C-4203-941E-0956AED20A6A}; DisplayName: APC PowerChute Personal Edition
        ID: {605A4E39-613C-4A12-B56F-DEFBE6757237}; DisplayName: SHASTA
        ID: {63BEF36D-1782-4506-ABA6-6672B54641E0}; DisplayName: Microsoft Office Live Meeting 2007
        ID: {6513E869-647F-40FD-A55D-CFC92579B9BA}; DisplayName: PX Engine
        ID: {693C08A7-9E76-43FF-B11E-9A58175474C4}; DisplayName: kgckids
        ID: {69FDFBB6-351D-4B8C-89D8-867DC9D0A2A4}; DisplayName: Windows Media Player Firefox Plugin
        ID: {716E0306-8318-4364-8B8F-0CC4E9376BAC}; DisplayName: MSXML 4.0 SP2 Parser and SDK
        ID: {72690A58-4C2A-4CDE-928C-DF925B125F43}; DisplayName: GTOneCare
        ID: {7DD9A065-2C86-4A9F-A5FF-796EC1B99DCA}; DisplayName: AnswerWorks 4.0 Runtime - English
        ID: {7F231232-C309-4401-964A-2A002B6E1ED9}; DisplayName: Microsoft Baseline Security Analyzer 2.0.1
        ID: {80FD852F-5AAC-4129-B931-06AAFFA43138}; DisplayName: iTunes
        ID: {822A8730-86A7-4CAA-BDE1-7337169BFF2B}; DisplayName: Sound Blaster X-Fi Xtreme Audio
        ID: {885744A4-1A01-44B0-858A-0AE6738CBCF7}; DisplayName: PrimoPDF Redistribution Package
        ID: {8943CE61-53BD-475E-90E1-A580869E98A2}; DisplayName: staticcr
        ID: {89F4137D-6C26-4A84-BDB8-2E5A4BB71E00}; DisplayName: Microsoft Silverlight
        ID: {8A502E38-29C9-49FA-BCFA-D727CA062589}; DisplayName: ESSTOOLS
        ID: {8A8664E1-84C8-4936-891C-BC1F07797549}; DisplayName: kgcvday
        ID: {8BF9A588-B2C8-4DFB-A340-2A7060BDF1E1}; DisplayName: TV Software
        ID: {8C6027FD-53DC-446D-BB75-CACD7028A134}; DisplayName: HP Update
        ID: {8D9702F1-1BEB-4F51-96CC-2E9B5A000FA1}; DisplayName: medfiltr
        ID: {8E92D746-CD9F-4B90-9668-42B74C14F765}; DisplayName: ESSini
        ID: {90120000-0020-0409-0000-0000000FF1CE}; DisplayName: Compatibility Pack for the 2007 Office system
        ID: {90120409-6000-11D3-8CFE-0050048383C9}; DisplayName: Microsoft Office XP Standard
        ID: {903A0409-6000-11D3-8CFE-0050048383C9}; DisplayName: Microsoft Project Standard 2002
        ID: {90510409-6000-11D3-8CFE-0150048383C9}; DisplayName: Microsoft Office Visio Professional 2003
        ID: {9068B2BE-D93A-4C0A-861C-5E35E2C0E09E}; DisplayName: Intel(R) Matrix Storage Manager
        ID: {91517631-A9F3-4B7C-B482-43E0068FD55A}; DisplayName: ESSgui
        ID: {91710409-8000-11D3-8CFE-0150048383C9}; DisplayName: Microsoft Application Error Reporting
        ID: {982B2A0F-7679-41D6-A584-C8E735F4A8CD}; DisplayName: Windows Home Server Toolkit
        ID: {999D43F4-9709-4887-9B1A-83EBB15A8370}; DisplayName: VPRINTOL
        ID: {9BD54685-1496-46A5-AB62-357CD140ED8B}; DisplayName: kgcinvt
        ID: {9D8FEE90-0377-49A9-AEFB-525BDE549BA4}; DisplayName: ESScore
        ID: {A0E54EC6-EA51-4088-A6EE-BEF1D1D128AB}; DisplayName: Lotus Notes 7.0.2
        ID: {A1588373-1D86-4D44-86C9-78ABD190F9CC}; DisplayName: kgcmove
        ID: {A9CF9052-F4A0-475D-A00F-A8388C62DD63}; DisplayName: MSXML 4.0 SP2 (KB925672)
        ID: {AC76BA86-7AD7-1033-7B44-A81200000003}; DisplayName: Adobe Reader 8.1.2
        ID: {AE1FA02D-E6A4-4EA0-8E58-6483CAC016DD}; DisplayName: ESSCDBK
        ID: {AFF1EA96-9C23-4249-B7D4-CD4B54D4582F}; DisplayName: TurboTax ItsDeductible 2006
        ID: {B162D0A6-9A1D-4B7C-91A5-88FB48113C45}; DisplayName: OfotoXMI
        ID: {B4B44FE7-41FF-4DAD-8C0A-E406DDA72992}; DisplayName: CCScore
        ID: {B5688129-7595-4E5B-9990-CEF981A31264}; DisplayName: SyncToy
        ID: {B74F042E-E1B9-4A5B-8D46-387BB172F0A4}; DisplayName: Apple Software Update
        ID: {B80CC46C-5839-4A48-B051-3CACF23A2718}_is1; DisplayName: Eraser 5.82
        ID: {BEEFC4F8-2909-48B3-AFAA-55D3533FDEDD}; DisplayName: Creative MediaSource 5
        ID: {BFD96B89-B769-4CD6-B11E-E79FFD46F067}; DisplayName: QuickTime
        ID: {C04E32E0-0416-434D-AFB9-6969D703A9EF}; DisplayName: MSXML 4.0 SP2 (KB936181)
        ID: {C523D256-313D-4866-B36A-F3DE528246EF}; DisplayName: MSXML 4.0 SP2 (KB941833)
        ID: {D07A8E7E-D324-4945-BA8C-E532AD008FF3}; DisplayName: Microsoft Windows OneCare Live v2.0.2500.22
        ID: {D32470A1-B10C-4059-BA53-CF0486F68EBC}; DisplayName: Kodak EasyShare software
        ID: {D6F7EA4B-B06B-4F39-8F65-AEDC3F3F1933}; DisplayName: Microsoft File Transfer Manager
        ID: {DB02F716-6275-42E9-B8D2-83BA2BF5100B}; DisplayName: SFR
        ID: {DBCC73BA-C69A-4BF5-B4BF-F07501EE7039}; DisplayName: AnswerWorks 5.0 English Runtime
        ID: {DBEA1034-5882-4A88-8033-81C4EF0CFA29}; DisplayName: Google Toolbar for Internet Explorer
        ID: {DED53B0B-B67C-4244-AE6A-D6FD3C28D1EF}; DisplayName: Ad-Aware 2007
        ID: {DF6A13C0-77DF-41FE-BD05-6D5201EB0CE7}_is1; DisplayName: AusLogics Disk Defrag
        ID: {E18B549C-5D15-45DA-8D8F-8FD2BD946344}; DisplayName: kgcbaby
        ID: {E44BD710-B71A-11d3-9F79-006008A88EC8}; DisplayName: VBA
        ID: {E6A31482-989E-4E3C-B0C0-1ED4DBD5BC83}; DisplayName: Microsoft Windows OneCare Live AntiSpyware and AntiVirus
        ID: {E79987F0-0E34-42CC-B8FF-6C860AEEB26A}; DisplayName: tooltips
        ID: {EB21A812-671B-4D08-B974-2A347F0D8F70}; DisplayName: HP Photosmart Essential
        ID: {F0B430D1-B6AA-473D-9B06-AA3DD01FD0B8}; DisplayName: Microsoft SQL Server 2005 Compact Edition [ENU]
        ID: {F22C222C-3CE2-4A4B-A83F-AF4681371ABE}; DisplayName: kgcbase
        ID: {F3B58D4E-7324-44E4-A6B3-65D2DB8D1FE9}; DisplayName: Microsoft Protection Service
        ID: {F4A2E7CC-60CA-4AFA-B67F-AD5E58173C3F}; DisplayName: SKINXSDK
        ID: {F6B2ED65-7378-4065-802D-F2E5689F3A4E}; DisplayName: Photo Viewer
        ID: {F7338FA3-DAB5-49B2-900D-0AFB5760C166}; DisplayName: PC Probe II
        ID: {F9593CFB-D836-49BC-BFF1-0E669A411D9F}; DisplayName: WIRELESS
        ID: {FD18677D-2CEA-4FC7-A082-8D00D8466D11}; DisplayName: World Community Grid - BOINC Client
        ID: {FDF9943A-3D5C-46B3-9679-586BD237DDEE}; DisplayName: SKIN0001

         

        My apologies for the delay in responding. Off for some skiing over the weekend and busy putting together a presentation on WHS for a user group meeting this evening!

        Thursday, March 13, 2008 3:15 PM
    •  Lliam wrote:

      Not that you should do this, but it would be curious to see if this worked:

      1. Copy backup data base to external drive (use instructions from backup whitepaper)
      2. Remove all backups for the Vista computer that fails to backup (or clear the database)
      3. Try to do a new backup of the Vista computer.

       

      Tried something similar: I went to the WHS Toolkit and deleted ALL the backups; I did not try to delete only those from the Vista machine. At the moment the MSS/WHS is backing up the Vista machine (up to 15% now). I suspect this will be successful but will report progress here. In another forum I had received suggestions to reset .NET but that was not successful. Since it worked after deleting the backups I am suspecting something in WHS. I have a 2-disk system (vanilla HP EX475) -- could this be the dreaded "data corruption bug"??

       

      I had not done this before now as I had a demonstration of the unit scheduled for a local user group last evening (Thursday evening) and did not want to try anything radical before the demo! (It went well!)

       

       

      Friday, March 14, 2008 5:45 AM
    •  JohnBick wrote:

       Lliam wrote:

      Not that you should do this, but it would be curious to see if this worked:

      1. Copy backup data base to external drive (use instructions from backup whitepaper)
      2. Remove all backups for the Vista computer that fails to backup (or clear the database)
      3. Try to do a new backup of the Vista computer.

       

      Tried something similar: I went to the WHS Toolkit and deleted ALL the backups; I did not try to delete only those from the Vista machine. At the moment the MSS/WHS is backing up the Vista machine (up to 15% now). I suspect this will be successful but will report progress here. In another forum I had received suggestions to reset .NET but that was not successful. Since it worked after deleting the backups I am suspecting something in WHS. I have a 2-disk system (vanilla HP EX475) -- could this be the dreaded "data corruption bug"??

       

      I had not done this before now as I had a demonstration of the unit scheduled for a local user group last evening (Thursday evening) and did not want to try anything radical before the demo! (It went well!)

       

       



      Glad the demo went well. Smile

      The reason I suggested clearing the database is because after the initial backup of a client computer, the backup sytem monitors the the clients file system for changes.  Consecutive backups only backup the changes.  Your defragment program is probably causing a lot of changes to occur to the file system.  Perhaps enough to cause these errors you're seeing.  Please read the backup white paper (accessible through the official WHS website) for some more insight into the backup system.  It sounds like a problem with WHS, you should submit a bug report.

      Since consecutive backups depend on the preceding backup, corruption of earlier backups can ruin all backups after that one.  I guess the best preventative measure is to make backups of your backup database regularly.
      Friday, March 14, 2008 6:07 AM
    • Hi,

       

      I have had similar problems on 2 laptops after installing Vista SP1.
      The solution turned out to be running a boot time defrag using PerfectDisk.

      I hope this will help you solving the problem.

      Bauke

       

      Friday, March 14, 2008 11:30 AM
    • OK, time for an update. The manual backup last evening ran fine on the Vista machine. And then on the XP laptop. This morning I decided to kick off another manual backup of the Vista machine to confirm it was still working. It fails with the same error. I Rebooted the server, reset the backups yet again, rebooted the server, configured the backups, rebooted the server and tried another backup. Same error again... Resetting the backups does not result in a permanent fix. FYI, the XP backup ran fine.

       

      BAUKE: "The boot time defrag using PerfectDisk" had already been done -- a couple times. This was actually done immediately after running PerfectDisk the first time. And I had tried it again later with no success. Probably should have mentioned this above.

       

      LLIAM: I am familiar with the backup whitepaper and have read it a couple times. I chose to reset the backups altogether as it was a bit more "extreme" and I felt I could sacrifice the backups.

      Friday, March 14, 2008 3:24 PM
    • John,

       

      Thanks for sending the CAB numbers, and your detailed repro steps.  This is the first step that needs to be taken so a thorough investigation can be started.  I have filed an issue in our internal tracking database, just as an FYI, the issue number is 59100. 

       

       

      Friday, March 14, 2008 4:33 PM
    • Thanks for your response. If you need any further information please feel free to contact me.

       

      Friday, March 14, 2008 4:57 PM
    • Since resetting the backups failed I finally decided to go to the extreme last evening and did a factory reset on my MSS EX475 WHS server, removing all software from the clients, reformatting the server and starting everything all over. At this point I had a completely "virgin" installation - no Add-Ins or additional software whatever.

       

      Same error at first attempt to back up the Vista machine.

       

      Beginning to get frustrating...

      Saturday, March 15, 2008 6:54 PM
    • Also tried and not mentioned above was a check on .NET on the Vista machine using:

       

      sfc /scannow

       

      No integrity problems were found....

      Saturday, March 15, 2008 9:39 PM
    • At least one source of a problem which produces this error report has been identified, and the fix is expected to be included in the upcoming Power Pack 1 release.  For that case, there's nothing you could do on your end without reformatting the client's drive.

      Monday, March 17, 2008 1:08 PM
    • When can we expect to see the Power Pack 1 release?  Is this Power Pack specific to WHS?  Is the fixed bug generic to the OS, meaning might it fix the problems seen on both Vista and XP?

       

      Monday, March 17, 2008 3:23 PM
    • I don't know the schedule.  I think it's "first half 2008".  Power Pack 1 is just for Windows Home Server.  This particular bug is unique to the WHS client PC backup and is the same for Windows XP as Windows Vista.

       

      Tuesday, March 18, 2008 1:49 AM
    • VERY INTERESTING.... I upgraded the Vista client to SP1 this afternoon and tried the backup again a few minutes ago....

       

      It's running!!!!! Will append later (tomorrow?) with the final results, but it has definitely passed to point where it failed before!

       

      (And I had been seriously debating whether to reformat and rebuild....!)

       

      Saturday, March 29, 2008 1:07 AM
    • A very frustrating evening, to say the least. But educational!

      The backup went 25% of the way through and then hit the wall with the same error as before. Looked at the details and realized it had completed backing up one of my four drives (the one I keep Windows backups on).

      It seems that the order of the drives being backed up changed when I installed SP1 and it was now failing on the SECOND drive in the list -- my D: (data) drive. I then tried backing up each drive individually, confirming that the other three drives backed up just fine. Of course the biggest question is whether it was D: or C: first before -- and I really do not recall. This time the first was F: -- and it most definitely was not that before!

      So.... Reformatting C: (2x150 Raptor mirrored RAID) and reinstalling Vista is not going to help my situation. Looks like I need to look at my 4x320 RAID5 data array instead. Will likely run diagnostics there I have a 1 TB WD drive shipping from Newegg and will off-load everything to that, reformat D: and try the backup again. Will also do a CHKDSK /F on D:.

      Others in this situation may ALSO want to look at which drive is failing to back up if you have more than one on the failing client.

      Saturday, March 29, 2008 3:16 AM
    • Until you have Power Pack 1, this will continue to fail whenever it gets to that drive.  It's not something wrong with the drive, and CHKDSK isn't going to fix it.  It's just something that was not anticipated in the Windows Home Server backup engine.  Short term the only option would be to exclude the client drive (sounds like it's your D: drive) which exhibits the problem, or to migrate that drive's files elsewhere while you reformat it.  (Reformat is very likely to lay out the drive data as WHS backup expects it.)

      Saturday, March 29, 2008 3:33 AM
    • Two comments:

       

      1. I would have expected the WHS software to realize that only one disk was impacted and to continue to back up the other disks on the client while also providing a warning as to which disk failed. To me this is a major shortcoming.

       

      2. What would have caused the change on my hard drive (a 4x320 RAID 5 array)? It had been functioning fine all thru beta, RC-1 and since December on an HP MSS? Was it due to a "rearrangement" of the disk due to defragmentation? (I had just installed PerfectDisk 2008 (WHS version).

       

      Saturday, March 29, 2008 1:39 PM
    • WHS Backup will skipped over things like a missing drive, but in this case, it hit an actual error in the software, literally, an unexpected situation.  There's something of a religious debate possible here, but it's often just not a good idea to keep going, because you might be taking the whole system into untested territory.

       

      In the earlier case, the situation is known to have first occured just after installing PerfectDisk 2008.  This is NOT a problem in that product either.  It's something legit which might have been induced by PerfectDisk's work, but not anticipated in WHS Backup.  In the earlier case, it was related to a partition which had been expanded, though it could probably be reproduced without going through that.

      Saturday, March 29, 2008 6:34 PM
    •  What ever came of this?  With all the recent updates, this is still an issue.  I still can't backup two of my 5 machines running Vista Ultimate and still get this error.  How can I even verify that the client software has been updated?  When I click on Settings - Resources, it shows Windows Home Server with Power Pack 1.  Any help would be great as 6 months is too long to go without being able to back up machines.
      Monday, September 8, 2008 9:32 PM

    • @ekutter 

      The original problem was fixed in PP1.  If your server says “Power Pack 1” and your client icon is green, then you should be running Power Pack 1 (BackupEngine.exe build 6.0.01800)  The fix was specific to failures with System.ArgumentOutOfRangeException including a reference at “Microsoft.HomeServer.Backup.BackupOp.BackupOperation.InitializeBitMaps()”. 

      It sound like this may be a different problem.  Please provide TALQ reports (CAB #'s) from each failing client computer and file a bug for further investigation.


      -j
      Monday, September 8, 2008 11:33 PM