Entourage Database Recovery Software will help you to recover the database from any type of corruption issues like header corruption, application malfunctioning, virus attacks etc. It’s quite hard to repair the corrupted, damaged database because it doesn’t have any file format so that the data are stored in it. The Office System Drivers are only supported under certain scenarios, including: Desktop applications which read from and write to various files formats including Microsoft Office Access, Microsoft Office Excel and text files. To transfer data between supported file formats and a database repository, such as SQL Server. From Finder, open the Applications folder. Ctrl+click or right-click Microsoft Outlook and select Show Package Contents. Open Contents SharedSupport and launch Outlook Profile Manager. Highlight the profile and click the - button to delete the profile. (Move the profile to the trash bin if asked.) Relaunch Outlook. Rebuild the Microsoft Store Cache via the Registry. Open an elevated Command Prompt. This can be done by searching for cmd in the Windows search bar, right-clicking the first result, and selecting Run as administrator. Once the Windows Console comes into view, run the below command: wmic useraccount get name,sid.
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
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
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
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
Rebuild Microsoft Office Database Online
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
- JalapenoT-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. - JalapenoEmerson1 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 - Poblanodlw111111111 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 PepperBDunbar5012 Dec 14, 2015 at 06:30pm
I had no idea this was happening. I'm glad I know ahead of time, now. Thanks!
- JalapenoJoeB13 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!
- PimientoBigEinNM 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.
- ChipotleCanadian 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
- JalapenoBringerOfLaw 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...
- AnaheimChristian9499 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
- ChipotleSteven61 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. :)
- DatilBenSetliff Jun 2, 2016 at 07:01pm
Thank you! Just used this for my home computer that upgraded from 8.1 to 10.
- Pimientorecrujo Jan 17, 2017 at 08:25pm
After trying everything else, found that this 'simple' solution worked !!! Thank you
- PimientoCmdrSpiner 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!
- JalapenoRich 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!
- MaceBiscuitKing May 14, 2019 at 01:33pm
I haven't seen this happen yet but have saved this as a favorite just in case.
Applies to: SQL Server (all supported versions)
System databases must be rebuilt to fix corruption problems in the master, model, msdb, or resource system databases or to modify the default server-level collation. This topic provides step-by-step instructions to rebuild system databases in SQL Server.
In This Topic
Before you begin:
Procedures:
Follow Up:
Before You Begin
Limitations and Restrictions
When the master, model, msdb, and tempdb system databases are rebuilt, the databases are dropped and re-created in their original location. If a new collation is specified in the rebuild statement, the system databases are created using that collation setting. Any user modifications to these databases are lost. For example, you may have user-defined objects in the master database, scheduled jobs in msdb, or changes to the default database settings in the model database.
Prerequisites
Microsoft Office Rebuild Database Mac
Perform the following tasks before you rebuild the system databases to ensure that you can restore the system databases to their current settings.
Record all server-wide configuration values.
Record all hotfixes applied to the instance of SQL Server and the current collation. You must reapply these hotfixes after rebuilding the system databases.
Record the current location of all data and log files for the system databases. Rebuilding the system databases installs all system databases to their original location. If you have moved system database data or log files to a different location, you must move the files again.
Locate the current backup of the master, model, and msdb databases.
If the instance of SQL Server is configured as a replication Distributor, locate the current backup of the distribution database.
Ensure you have appropriate permissions to rebuild the system databases. To perform this operation, you must be a member of the sysadmin fixed server role. For more information, see Server-Level Roles.
Verify that copies of the master, model, msdb data and log template files exist on the local server. The default location for the template files is C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLBinnTemplates. These files are used during the rebuild process and must be present for Setup to succeed. If they are missing, run the Repair feature of Setup, or manually copy the files from your installation media. To locate the files on the installation media, navigate to the appropriate platform directory (x86 or x64) and then navigate to setupsql_engine_core_inst_msiPfilesSqlServrMSSQL.XMSSQLBinnTemplates.
Rebuild System Databases
The following procedure rebuilds the master, model, msdb, and tempdb system databases. You cannot specify the system databases to be rebuilt. For clustered instances, this procedure must be performed on the active node and the SQL Server resource in the corresponding cluster application group must be taken offline before performing the procedure.
This procedure does not rebuild the resource database. See the section, 'Rebuild the resource Database Procedure' later in this topic.
To rebuild system databases for an instance of SQL Server:
Insert the SQL Server installation media into the disk drive, or, from a command prompt, change directories to the location of the setup.exe file on the local server. The default location on the server is C:Program FilesMicrosoft SQL Server130Setup BootstrapSQLServer2016.
From a command prompt window, enter the following command. Square brackets are used to indicate optional parameters. Do not enter the brackets. When using a Windows operating system that has User Account Control (UAC) enabled, running Setup requires elevated privileges. The command prompt must be run as Administrator.
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [ /SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]
Parameter name Description /QUIET or /Q Specifies that Setup run without any user interface. /ACTION=REBUILDDATABASE Specifies that Setup re-create the system databases. /INSTANCENAME=InstanceName Is the name of the instance of SQL Server. For the default instance, enter MSSQLSERVER. /SQLSYSADMINACCOUNTS=accounts Specifies the Windows groups or individual accounts to add to the sysadmin fixed server role. When specifying more than one account, separate the accounts with a blank space. For example, enter BUILTINAdministrators MyDomainMyUser. When you are specifying an account that contains a blank space within the account name, enclose the account in double quotation marks. For example, enter NT AUTHORITYSYSTEM. [ /SAPWD=StrongPassword ] Specifies the password for the SQL Server sa account. This parameter is required if the instance uses Mixed Authentication (SQL Server and Windows Authentication) mode.
** Security Note ** The sa account is a well-known SQL Server account and it is often targeted by malicious users. It is very important that you use a strong password for the sa login.
Do not specify this parameter for Windows Authentication mode.[ /SQLCOLLATION=CollationName ] Specifies a new server-level collation. This parameter is optional. When not specified, the current collation of the server is used.
** Important ** Changing the server-level collation does not change the collation of existing user databases. All newly created user databases will use the new collation by default.
For more information, see Set or Change the Server Collation.[ /SQLTEMPDBFILECOUNT=NumberOfFiles ] Specifies the number of tempdb data files. This value can be increased up to 8 or the number of cores, whichever is higher.
Default value: 8 or the number of cores, whichever is lower.[ /SQLTEMPDBFILESIZE=FileSizeInMB ] Specifies the initial size of each tempdb data file in MB. Setup allows the size up to 1024 MB.
Default value: 8[ /SQLTEMPDBFILEGROWTH=FileSizeInMB ] Specifies the file growth increment of each tempdb data file in MB. A value of 0 indicates that automatic growth is off and no additional space is allowed. Setup allows the size up to 1024 MB.
Default value: 64[ /SQLTEMPDBLOGFILESIZE=FileSizeInMB ] Specifies the initial size of the tempdb log file in MB. Setup allows the size up to 1024 MB.
Default value: 8.
Allowed range: Min = 8, max = 1024.[ /SQLTEMPDBLOGFILEGROWTH=FileSizeInMB ] Specifies the file growth increment of the tempdb log file in MB. A value of 0 indicates that automatic growth is off and no additional space is allowed. Setup allows the size up to 1024 MB.
Default value: 64
Allowed range: Min = 8, max = 1024.[ /SQLTEMPDBDIR=Directories ] Specifies the directories for tempdb data files. When specifying more than one directory, separate the directories with a blank space. If multiple directories are specified the tempdb data files will be spread across the directories in a round-robin fashion.
Default value: System Data Directory[ /SQLTEMPDBLOGDIR=Directory ] Specifies the directory for the tempdb log file.
Default value: System Data DirectoryWhen Setup has completed rebuilding the system databases, it returns to the command prompt with no messages. Examine the Summary.txt log file to verify that the process completed successfully. This file is located at C:Program FilesMicrosoft SQL Server130Setup BootstrapLogs.
RebuildDatabase scenario deletes system databases and installs them again in clean state. Because the setting of tempdb file count does not persist, the value of number of tempdb files is not known during setup. Therefore, RebuildDatabase scenario does not know the count of tempdb files to be re-added. You can provide the value of the number of tempdb files again with the SQLTEMPDBFILECOUNT parameter. If the parameter is not provided, RebuildDatabase will add a default number of tempdb files, which is as many tempdb files as the CPU count or 8, whichever is lower.
Post-Rebuild Tasks
After rebuilding the database you may need to perform the following additional tasks:
Restore your most recent full backups of the master, model, and msdb databases. For more information, see Back Up and Restore of System Databases (SQL Server).
Important
If you have changed the server collation, do not restore the system databases. Doing so will replace the new collation with the previous collation setting.
If a backup is not available or if the restored backup is not current, re-create any missing entries. For example, re-create all missing entries for your user databases, backup devices, SQL Server logins, end points, and so on. The best way to re-create entries is to run the original scripts that created them.
Important
We recommend that you secure your scripts to prevent their being altered by unauthorized by individuals.
If the instance of SQL Server is configured as a replication Distributor, you must restore the distribution database. For more information, see Back Up and Restore Replicated Databases.
Move the system databases to the locations you recorded previously. For more information, see Move System Databases.
Verify the server-wide configuration values match the values you recorded previously.
Rebuild the resource Database
The following procedure rebuilds the resource system database. When you rebuild the resource database, all hot fixes are lost, and therefore must be reapplied.
To rebuild the resource system database:
Launch the SQL Server Setup program (setup.exe) from the distribution media.
In the left navigation area, click Maintenance, and then click Repair.
Setup support rule and file routines run to ensure that your system has prerequisites installed and that the computer passes Setup validation rules. Click OK or Install to continue.
On the Select Instance page, select the instance to repair, and then click Next.
The repair rules will run to validate the operation. To continue, click Next.
From the Ready to Repair page, click Repair. The Complete page indicates that the operation is finished.
Create a New msdb Database
If the msdb database is damaged and you do not have a backup of the msdb database, you can create a new msdb by using the instmsdb script.
Warning
Rebuilding the msdb database using the instmsdb script will eliminate all the information stored in msdb such as jobs, alert, operators, maintenance plans, backup history, Policy-Based Management settings, Database Mail, Performance Data Warehouse, etc.
Stop all services connecting to the Database Engine, including SQL Server Agent, SSRS, SSIS, and all applications using SQL Server as data store.
Start SQL Server from the command line using the command:
NET START MSSQLSERVER /T3608For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.
In another command line window, detach the msdb database by executing the following command, replacing <servername> with the instance of SQL Server:
SQLCMD -E -S<servername> -dmaster -Q'EXEC sp_detach_db msdb'Using the Windows Explorer, rename the msdb database files. By default these are in the DATA sub-folder for the SQL Server instance.
Using SQL Server Configuration Manager, stop and restart the Database Engine service normally.
In a command line window, connect to SQL Server and execute the command:
SQLCMD -E -S<servername> -i'C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLInstallinstmsdb.sql' -o'C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLInstallinstmsdb.out'Replace <servername> with the instance of the Database Engine. Use the file system path of the instance of SQL Server.
Using the Windows Notepad, open the instmsdb.out file and check the output for any errors.
Re-apply any hotfix installed on the instance.
Recreate the user content stored in the msdb database, such as jobs, alert, etc.
Backup the msdb database.
Rebuild the tempdb Database
If the tempdb database is damaged and the database engine fails to start, you can rebuild tempdb without the need to rebuild all system databases.
Rename the current tempdb.mdf and templog.ldf files, if not missing.
Start SQL Server from a Command Prompt by using the following command.
For a default instance name use MSSQLSERVER, for named instance use MSSQL$<instance_name>. Trace flag 4022 disables execution of startup stored procedures. The -mSQLCMD allows only sqlcmd.exe to connect to the server (see Other Startup Options)
Note
Make sure that the command prompt window remains open after the SQL Server starts. Closing the command prompt window will terminate the process.
Connect to the server by using sqlcmd, and then use the following stored procedure to reset the status of the tempdb database.
Shut down the server by pressing CTRL+C in the command prompt window
Restart the SQL Server service. This creates a new set of tempdb database files, and recovers the tempdb database.
Troubleshoot Rebuild Errors
Syntax and other run-time errors are displayed in the command prompt window. Examine the Setup statement for the following syntax errors:
Missing slash mark (/) in front of each parameter name.
Missing equal sign (=) between the parameter name and the parameter value.
Presence of blank spaces between the parameter name and the equal sign.
Presence of commas (,) or other characters that are not specified in the syntax.
After the rebuild operation is complete, examine the SQL Server logs for any errors. The default log location is C:Program FilesMicrosoft SQL Server130Setup BootstrapLogs. To locate the log file that contains the results of the rebuild process, change directories to the Logs folder from a command prompt, and then run findstr /s RebuildDatabase summary*.*. This search will point you to any log files that contain the results of rebuilding system databases. Open the log files and examine them for relevant error messages.