Information borrowed from:
http://www.wegotserved.co.uk/2008/08/21 ... ct-errors/
Microsoft Investigating Power Pack 1 File Conflict Errors
Thu, Aug 21, 2008 | Bodog
A number of Windows Home Server users on WGS and Microsoft’s WHS forums are reporting a File Conflict error occuring in their WHS systems with PP1 installed.
When this occurs it has proven difficult and in some cases impossible to fix the conflict by deleting the files identified as being the cause. This error also seems to be effecting the Backup database with a Backup service is not running also being reported.
Could this be a bug introduced by PP1?
I have experienced these issues myself and found that a Server reinstall has been the only way to “fix” it - however it reoccurs. The other options appears to be to delete the Backup database which I’ve been reluctant to do and start over as it currently has over 3 months of backups in it.
If you are experiencing these issues Lara Jones of Microsoft’s Windows Home Server team has asked users to log a bug report via Connect under the WHS beta program - this is the sticky post on Microsofts Windows Home Server forums:
I would like to take this opportunity to point everyone towards the release notes for Windows Home Server Power Pack 1. This document provides helpful information regarding improvements in PP1 and known issues. In addition, WHS with PP1 is now more active in monitoring the health of your server, specifically storage. This may result in more messages from the server:
Windows Home Server proactively checks the health of all files stored in shared folders during a migration pass. If any issues are discovered, a yellow health notification is sent that contains a detailed conflict reason for each file.
That being said, we would still like to review any file conflict errors that are being reported in the forums. If you are receiving errors, please file a bug. In order for the bug to be actionable on our end, we will need the following:
1. 2 (two) screenshots of the error message. One that is right justified and one that is left justified in order to capture the entire error message so that none of the text is clipped.
2. Server CABs (you can use the toolkit found here) to obtain these. If you need to use the cheat sheet to obtain the files, it’s here.
3. Clear, and preferably enumerated repro steps.
If you are not already registered on Connect, please go here and register and then add yourself to our beta here.
Thank you for your assistance and feedback.
Lara Jones
Windows Home Server Team.
There is a thread on this issue on the WGS forums - if you are experiencing these issues head on over and let us know about it.