Wednesday, March 28, 2012

Windows could not set the offline locale information error during install

Problem

You are performing a clean installation of Windows 7 (any version) and experience the following error at some point during the installation:
Windows could not set the offline locale information. Error code 0x80FF0000
You then attempt to repeat the installation, but experience the same error, though it may occur at somewhat different points during the installation process.  You were able to re-partition and even format the target drive during the installation process without issue.  Other possible experiences you may have had with this machine prior to this error include:
  • Suddenly displayed a blue screen, without warning. On restart, BIOS would load fine, but then became stuck during Windows loading.
  • Suddenly loaded extremely slowly or even remained stuck in the Windows loading phase of the boot process.
You would like to recover the system, but in the least costly manner possible.

Discussion

All of these issues point to a possible problem with the hard disk and likely involves the failure of one or more sectors on the disk.  While the hard disk is likely the culprit, and it may degrade further, it is still possible to recover the use of your machine without the purchase of any new software or hardware.  This article shows you how.

You will need your system recovery disk.

The primary method for accomplishing this is to isolate the problem.  Most of the hard drive is likely still functional.  You just need to configure the hard drive in such a way that the operating system will neither be installed to nor operate using those sectors.  You accomplish this through appropriate partitioning.

Rather than trying to re-install your system to the drive configured as a single partition, you will instead create multiple partitions on the hard drive with the intent of capturing those bad sectors within one of those partitions and using the other partition as your system partition.

The Windows 7 installation enables you to create and delete partitions during the installation process.  You don't know where the bad sectors may lie, whether they are towards the outer rim of the disk or inner portions, so you'll need to progressively work your way inwards with partitions of varying sizes, until you create a partition set that isolates the problem and allows you to perform the installation without issue.

Take, for example, a 3-year old (just out of warranty) laptop having a 450 GB hard disk. Try creating two partitions, each 225 GB.  Format the partitions.  Now, install the system to the first partition.  If the installation proceeds without issue, you have successfully isolated the sector failure to the second partition.  If it doesn't, try to repeat the installation attempt to the second partition.  If this succeeds, you've successfully isolated the issue to the first partition.  Otherwise, you may have found the issue midway on the disk.

Continue this process, trying different partition sizes, until you can get the installation to proceed without issue.  Once the system is installed, you can perform a disk check using Windows tools in order to recover the bad partition. 
NOTE: Given the fact that this hard disk has likely evidenced sector failure once, it is even more likely to do so again in the future.  Thus, the recovery procedure discussed here is a temporary measure.
Summary

This article has discussed one method for possibly recoverying from Error code 0x80FF0000, if experienced during clean installation.  It provides a least-cost method of recovery, enabling you to regain the use of the system, if temporarily, without the purchase of new software or hardware.

References

Tuesday, March 27, 2012

SharePoint 2010 Health Analyzer: Missing server side dependencies

Problem

You find the following entry (in whole or in part) in the SharePoint 2010 Central Administration Review problems and solutions All Reports listing:

TitleMissing server side dependencies.
Severity1 - Error
CategoryConfiguration
Explanation[MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [22] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9eba9c17-3b89-a2e7-a3cf-0ee3d7c2adb1] (class [Microsoft.Office.Server.Search.WebControls.SearchTopologyView] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [b36f9dfe-325a-1b44-e6bb-645dcf79c770] (class [Microsoft.Office.Server.Search.WebControls.FarmSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [9f56656f-6aa3-0d55-a812-711bf65864ea] is referenced [107] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [926a1a3e-d1ff-f58f-8b3a-854974660703] (class [Microsoft.Office.Server.Search.WebControls.ContentSourcesStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [de8c8afc-7c6e-e9fc-91c2-aa4a291c3623] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [5cc5df3a-29a8-a713-5898-e52e2dce72a8] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationShortcutsList] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [874f5460-71f9-fecc-e894-e7e858d9713e] is referenced [65] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
[MissingWebPart] WebPart class [ff79cbb5-48cf-96ee-3f74-f22cc1b00fbd] (class [Microsoft.Office.Server.Search.WebControls.FarmSearchApplicationList] from assembly [Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [CentralAdminContentDatabase], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [CentralAdminContentDatabase], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
RemedyFor more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142689".
Failing Servers 
Failing ServicesSPTimerService (SPTimerV4)
Rule SettingsView
 
Additionally, in the Windows Server Application log, you may find related error events.

Solution
  1. Launch Central Administration.
  2. Navigate to: General Application Settings > Search > Farm Search Administration. 
  3. Refresh the page.
  4. Navigate to: General Application Settings > Farm Search Administration > Search Administration.
  5. Refresh the page.
  6. Navigate to: Monitoring > Health Analyzer > Review problems and solutions.
  7. Click on the error, Missing server side dependencies.
  8. Click the Re-analyze Now button.
  9. Click Close.
  10. Wait a minute or two.
  11. Click the error link again.
References
  1. Missing Server Side Dependencies - 8d6034c4-a416-e535-281a-6b714894e1aa
  2. MSDN Blogs: SharePoint 2010: Missing Server Side Dependencies
  3. Microsoft TechNet: Web Part Error on a clean SP2010 install in Document Center
  4. Microsoft SharePoint Products
  5. SharePoint 2010: Missing Server Side Dependencies
  6. [MissingWebPart] WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [25] times in the database
  7. Health Analyzer showing “missing server side dependency” after performing In-Place upgrade
  8. [MissingWebPart] WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced [6] times
Notes
  • See the references above for additional technical detail on this error.
  • UPDATE (10/11/12): I've added some additional references you may find useful on this error.  Note that it's not limited to just the pages discussed above but may occur on other pages and involve other web parts.  The error does not appear to indicate actual loss of functionality that I have been able to tell and thus I recommend disabling the rule for now, as I do for my customer.
  • UPDATE (3/4/14): I have found that just navigating to the page isn't always sufficient to resolve this error.  Instead, I found that refreshing the page once or twice after navigating to it ensured that the error was resolved.
  • UPDATE (3/17/14): This error re-appeared. Performed same procedure to resolve. Unclear why the circumstances generating this error should manifest themselves again.