Rebuild Microsoft Office Database

1. Rebuild Microsoft Office Database Software
2. Rebuild Microsoft Office Database Download
3. Microsoft Office Rebuild Database Mac
4. Rebuild Microsoft Office Database Free

Unable to rebuild Microsoft Office 2008 database. I've never heard of Excel or Word having a database. The only database utility the comes with Office 2008 is for.

Microsoft Graph API; Office 365 Connectors; Office 365 REST APIs; SharePoint Add-ins; Office UI Fabric. TFS - Rebuild Warehouse & Analysis Database. I can not rebuild office database - Answered by a verified Microsoft Office Technician We use cookies to give you the best possible experience on our website. By continuing to use this site you consent to the use of cookies on your device as described in our cookie policy unless you have disabled them. Quit all Microsoft Office apps including Outlook and quit Messenger for Mac. Close Outlook, hold down Option key and select the Outlook icon in the Dock to open the Microsoft Database Utility. Select the identity of the database you want to rebuild and then select Rebuild.

This article describes how to manually rebuild the performance counter library values.

Applies to: Windows 10 - all editions, Windows Server 2012 R2
Original KB number: 300956

Important

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

When you use the System Monitor tool, some counters may be missing or don't contain counter data. The base set of performance counter libraries may become corrupted and may need to be rebuilt. Additionally, you may need to rebuild any custom (Microsoft .NET Framework application created) counters or any extensible counters.

This behavior may occur in the following situations:

• certain extensible counters corrupt the registry.
• some Windows Management Instrumentation (WMI)-based programs modify the registry.

Rebuild the base performance counters

Extensible counter information is stored in both of the following locations:

• The registry subkey: HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionPerflib009.

• The %Systemroot%System32Perfc009.dat file and the %Systemroot%System32Perfh009.dat file.

To rebuild the base performance counter libraries manually, follow these steps:

1. Expand the Perfc009.dat file and the Perfh009.dat file. These files are located on the Windows Installation Disc. The compressed files are found at DriveLetter:i386perfc009.da_ and at DriveLetter:i386perfh009.da_. Replace the files that are in the %Systemroot%System32 folder.

2. Start Registry Editor, and then locate the following key in the registry:
   HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionPerflib

3. In the registry, change the Last Counter value to 1846 (decimal), and change the Last Help value to 1847 (decimal).

4. Locate the following registry key to search for services that have a Performance subkey:
   HKEY_LOCAL_MACHINESystemCurrentControlSetServices

5. Remove the following values from the Performance subkey (if they exist):

   • First Counter
   • First Help
   • Last Counter
   • Last Help

   You can also use the Exctrlst.exe tool to locate the performance counter dynamic-link library files (DLLs) that are installed. Then access the registry to remove the DWORD values. You now have a workable performance registry that contains only system base counters.

   Note

   Removing the values from the Performance subkey in the registry may cause any installed .NET Framework applications not to work the next time that they are started. If this occurs, use the lodctr /R command in the Re-add the extensible counters section to rebuild the Performance counters. If you continue to have problems when you start a .NET Framework application, see the Reinstall custom .NET Framework assembly performance counters section in this article.

Re-add the extensible counters

You must add the extensible counters again from the list of services. Before you do so, you must identify the .ini file that is used to load the counters:

1. Open a Command Prompt window.

2. At the command prompt, type cd %Systemroot%System32, and then press ENTER.

3. At the command prompt, type findstr drivername *.ini, and then press ENTER.

4. Note the name of the .ini file for each driver name in the list.

5. At the command prompt, type the lodctr <inifile> command, and then press ENTER.

   Note

   In this command, <inifile> represents the name of the .ini file for the driver that you want to reload.

   For example, if you want to reload the ASP driver, the list that you noted in step 4 shows that Axperf.ini is the .ini file for the ASP driver (axperf.ini:drivername=ASP). To reload the ASP driver, type lodctr axperf.ini at the command prompt, and then press ENTER.

6. Repeat step 5 for each .ini file in the list.

7. Restart your computer.

To rebuild all Performance counters including extensible and third-party counters in Windows Server type the following commands at a command prompt. Press ENTER after each command.

Note

• /R is uppercase. You must have administrative rights on the computer to successfully perform this command.
• On a computer that is running a 32-bit edition of Windows, the Lodctr /R:<filename> command is the standard method to restore performance counter registry strings and information by using a file name.

Windows Server rebuilds all the counters because it reads all the .ini files in the C:Windowsinf009 folder for the English operating system.

Note

• If you are running a Cluster or Datacenter product, you must fail over the node to refresh the counter list. You must do this after you perform the steps under Re-add the extensible counters for both base counters and extensible counters.
• On systems that are running applications that add their own performance counters, such as Exchange or SQL Server, the .ini file that is used to load the performance counter may not be located in %Systemroot%System32. These .ini files can usually be found under the applications folder structure.
• If you receive an error message about the performance library when you use the previous steps, you may have to unload and reload the IIS performance dynamic link libraries (DLLs).
• If you continue to experience problems when you start a .NET Framework application, see the Reinstall custom .NET Framework assembly performance counters section.

Reinstall custom .NET Framework assembly performance counters

If you continue to have problems when you start a .NET Framework application after you perform the procedures that are listed here, you may have to rebuild the Performance counters for the custom .NET Framework application. To do so, use the /i option in the .NET Framework Installer Tool (Installutil.exe). You must know the file names of the DLL files that create the performance counters.

If you follow these procedures and remove the counters from the registry for all services installed on a system that has Microsoft System Center Operations Manager 2007 installed, you might have a broken Management Server. The counters for the Config Service, SDK Service, and Database Write modules aren't provided in the form of extensible counters in INI files. Instead, they are registered at the time of installation. So, when you try to start System Center Operations Manager 2007, you may receive an error message similar to the following example because the performance counters are missing:

To resolve this problem in System Center Operations Manager 2007, you must reinstall the .NET Framework assemblies that created the performance counters. To do so, use the /i option in the .NET Framework Installer Tool (Installutil.exe) to reinstall the following assemblies:

• Microsoft.Mom.ConfigService.dll
• Microsoft.Mom.Sdk.ServiceDataLayer.dll
• Microsoft.Mom.DatabaseWriteModules.dll
• Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll

For example, at the command prompt, type the following commands, and then press ENTER after each command:

Note

You must have administrative rights on the computer to successfully perform these commands.

Yesterday my start menu suddenly stopped working on my Windows 10 machine. After rebooting, running sfc /SCANNOW, multiple PowerShell commands, and recreating my user profile, I could not get the start menu to come back up. In addition, the search didn't work, Microsoft Edge, and Settings. This wasn't related to a bad Windows Update. It was due to a corrupted live tile database. I found a guide online which walked you through how to create a new database and overwrite the existing but it needed some help. This is my attempt to rewrite the how-to to include more information and be easier to follow for those experiencing similar issues.

6 Steps total

Step 1: Create two new profiles

Rebuild Microsoft Office Database Software

If there's only one user present on the machine, you will need to log into two additional users to create new profiles. You have to do this because you will log into one to copy the database of another to fix the database of the troubled user. You can't copy the database of an account you're logged in since it will be 'in use'.

I logged into the domain administrator and local administrator account. You can log into either new account, just be sure that one of them is an administrator and can access other user profile folders.

Step 2: Reboot

This is important. The corrupted database will say it's still in use if you try to replace it without rebooting. This will make sure that the process that's accessing that database is terminated. This also assures that all users have been signed out.

Step 3: Login as an administrator

Rebuild Microsoft Office Database Download

I logged in as the domain administrator to copy the local administrator's database to replace mine.

Step 4: Replace the corrupted database

Browse to C:UsersOtherNewAccountYouAreNotUsingAppDataLocalTileDataLayer

Right click on the folder Database and click copy.

Now browse to C:UsersUserAccountExperiencingProblemsAppDataLocalTileDataLayer

Microsoft Office Rebuild Database Mac

Rename the Database folder in that account to Database.old

Now paste the Database folder you copied from the other user account. This will remove all modifications and shortcuts you've added to the start menu but hey...at least it'll work now!

Step 5: Reboot for the last time

Hopefully you have a SSD to make this less painful :)

Step 6: Sign into the user account that originally had the problem

The start menu will now work, as well as everything else that wouldn't respond. As described above, you'll lose all modifications and shortcuts to the start menu since you copied the style from another user account. You'll also notice that the locally installed apps will NOT show under All Apps. This is a quick fix, simply pin anything as a shortcut to the start menu (browse to Program Files to pin a program). Suddenly all of your apps will appear under Recently added and show up again under All Apps.

It's an easy fix but a strange problem. I can understand how this will affect Cortana but I don't understand why it would make Microsoft Edge disappear and make Settings unresponsive. I'm not aware of the cause either. At least if you're challenged with this in the future...the fix is here!

References

• Original how-to

15 Comments

Rebuild Microsoft Office Database Free

• Jalapeno
  T-RAV89 Dec 14, 2015 at 02:15pm

  Nice write up.
  I have two windows 10 machines and my start menu, search and task bar always stop working if the computer isn't restarted for about a week. After a restart everything is fine. I wonder if your steps will help this less extreme situation. If I try it I'll let you know.

• Jalapeno
  Emerson1 Dec 14, 2015 at 03:05pm

  There is also a file that Microsoft put out that helps to fix this issue, I don't recall if it kept my settings and such or not
  CSSEmerg67758.diagcab

• Poblano
  dlw111111111 Dec 14, 2015 at 03:18pm

  My solution is not use the Windows Start Bar with all those busy tiles. I removed all the tiles and placed the programs I use on the task bar. Easy. My Start Bar is bare as can be.
  I don't use the 'apps' or download any new items from the apps store.
  I did notice since the PDF extension defaults to a MS Edge extension and I figured out how to change it. (I don't use Edge either) and when I looked at my Adobe program it was for MS 8. Guess MS assumed everyone would use Edge to open pdf's. Meh.
  I downloaded the new version from the Adobe website. Added program to task bar and works great.
  Thank you for the nice write up though. Leave it to MS to fu a start bar.

• Thai Pepper
  BDunbar5012 Dec 14, 2015 at 06:30pm

  I had no idea this was happening. I'm glad I know ahead of time, now. Thanks!

• Jalapeno
  JoeB13 Dec 26, 2015 at 05:43pm

  I've been fighting this problem on my home PC for 2 days and was about to format/reload. Mother of God, thank you.

  I'd run the SCF/DCIM/SCF gauntlet, and the CSSEmerg67758.diagcab troubleshooter had all done nothing to help resolve. I'd assumed that it had to be user-specific because only one of the two user accounts on the machine was being affected; but was running into a dead end there.

  You are a saint, starg33ker, and my the new year bring you all of the finest things!

• Pimiento
  BigEinNM Dec 28, 2015 at 06:35pm

  I was able to solve the problem simply by adding another user account (admin), restarting, logging into the new account, launching a couple of the programs that weren't opening (Outlook 2010 and Chrome), restarting and logging into the original account experiencing the problem. Somehow that jarred something loose and fixed the problem without copying the database folders.

• Chipotle
  Canadian Tech Guy Mar 16, 2016 at 08:21pm

  Thanks for this. We are later adopters and are about to deploy. This had never come up in my testing, so thanks for making me aware of both the issue and the fix.

  CTG

• Jalapeno
  BringerOfLaw Apr 7, 2016 at 02:54pm

  Banging my head against the wall on this one.... I've followed the steps above to no avail. Tried renaming the DB folder to 'old', no luck. Tried naming the entire TileDataLayer folder to 'old', no luck. Created a new User acct, verified that I could launch programs from its Start Menu, followed the 6 steps above, still no luck. At this point, I start rolling it back with System Restore, since the Start Menu was working fine last week. May have stumbled across the answer during that process. I rolled it back one point at a time, scanning for affected programs each time before pulling the trigger. The Start Menu started working again after I rolled it back past a Chrome update. Chrome was the only program affected by that particular restore point, and once it was out of the way, Start began working again. Here's my guess (and it's just that): There was a shortcut to Chrome on the Start Menu after the System Restore was performed. Chrome updates in the background without notification. The shortcut in the Start Menu is somehow version specific, and craps out when the connection between it and the actual Chrome application is broken. Now, that doesn't explain why a new copy of a clean TileDataLayer DB won't fix it (since the Chrome shortcut wasn't on the other accounts), but there may be something else in the profile that ties in somewhere. That might also explain why the Admin and Domain Admin acct Start Menus continue to work, since they're basically at default. Your mileage may vary...

• Anaheim
  Christian9499 Apr 25, 2016 at 01:44pm

  I followed all the steps but also without any luck.I am evaluating Win10 for our Company and this is the only problem I couldn't find a fitting workaround for. ...
  What I found out is, that this error somehow announces itself.
  Before I am no more able to click onto the start menu button without getting this odd error, I cannot access specific mapped DFS-drives/folders any more. This DFS-Folders (m:admindata ; m:kaspersky ) are mapped to hidden shares on my admin-Server and i should have RW-rights.
  I am still able to access DFS-folders within m:/ that are mapped to shares on other servers. AND I am able to access the M: shares to the admin-server from other computers I am still logged in.
  All shares are on servers with server 2012R2
  After a reboot the start menu is still dead but the shares are working again.
  Maybe this behavior will help someone findig a solution.

  Right now I am doing a bare metal restore from my network based Veeam Endpoint Storage every time this happens (about 8 times the last 3 months). This costs me 'only' 80 minutes at this workstation. Deleting and recreating/restoring the userprofile would take up to 3 hours. so you can see - not a very good workaround businesswise

• Chipotle
  Steven61 May 4, 2016 at 03:04pm

  I have had this happen to two different systems (an End User and Mine), it happened to my system about a month ago and I had not seen this post (not sure how I missed it) I simply reinstalled Windows 10 right over the top of the running version like an upgrade and that fixed the problem, my only issues with this is that of course it reinstalled all the Crap that Microsoft feels we need on a work system (xbox, solitaire...) but fortunately I have a couple PowerShell scripts (including the DeCrappifier in the SW script repository) that remove that stuff quickly. It also removed my Pinned Documents from the Applications pinned to my taskbar but that is a fairly small price to pay.

  I found this post while looking for an alternative to reinstalling Windows for my End Users system, Hadn't considered the Google Chrome aspect, but based on the steps above I may stick with simply reinstalling Windows 10 Again. :)

• Datil
  BenSetliff Jun 2, 2016 at 07:01pm

  Thank you! Just used this for my home computer that upgraded from 8.1 to 10.

• Pimiento
  recrujo Jan 17, 2017 at 08:25pm

  After trying everything else, found that this 'simple' solution worked !!! Thank you

• Pimiento
  CmdrSpiner Mar 24, 2017 at 11:58pm

  The PowerShell script restored the base Windows apps and shortcuts. Adding %appdata%MicrosoftWindowsStart Menu to the indexing options restored all my installed programs. This solution restored complete Start menu functionality including the system icon and the tile screen. Brilliant! Thank you!

• Jalapeno
  Rich Stop May 9, 2017 at 06:18pm

  I had been having this issue for a couple of months and stumbled upon this solution. So far so good!

• Mace
  BiscuitKing May 14, 2019 at 01:33pm

  I haven't seen this happen yet but have saved this as a favorite just in case.