How to Fix SharePoint Event ID Error 5586?

event id 5586 error

Are you the one unable to access your Central Administration or any SharePoint website and keep getting the event id 5586 in SharePoint foundation? Then this article is for you, here check out the event id 5586 SharePoint foundation.

MS SharePoint makes use of the Server database for storing configuration settings and most of the website content. All pages in the website, document library file, files adjoined to list, and details in the list are amassed in the database content, and even configuration and permission settings are accumulated in the configuration database.

A service is being used by the MS database for the purpose of communication when requested by a user. This account could be either a specific password or user name or could be a predefined system account, like a limited system or network service.

When a Server database has shaped a value for maximum database size is set. Every database has a separate size setting and one of those might also be associated with a Web application.

Symptoms of SharePoint Event ID 5586: 

This error emerges in the event record

Event ID: 5586 Description full error on SQL Server instance <instance name>.

Supplementary information regarding error from SQL server is involved beneath which includes possible causes leading to this error along with the appropriate resolution.

What Causes SharePoint Event ID 5586?

  • Inadequate permission of SQL server database
  • Server database of SQL is compact
  • Erroneous MDAC version
  • SQL Server Database not found
  • SQL Server version is incorrect
  • Collation of SQL Server is not supported
  • The database is set to read-only

Please Note: You must be a member of the SharePoint Administrators group to perform this task.

How to Fix Event id 5586 SharePoint Foundation?

In order to get rid of the event id 5586 error, follow the solutions given one by one, and resolve SharePoint Event ID Error 5586.

Therefore separate solution has been provided below for every possible cause that can lead to Event ID error 5586.

Solution 1 – Inadequate permission of SQL server database

To solve this issue allocate a database access account and then authenticate that account has correct authorization in SQL server. And to accomplish this task do as follows:

  • Click Security, and then in General Security go to Configure Service Accounts on the Central Administration Website of SharePoint.
  • Opt for the appropriate Web application pool in Credential Management on the account page of Configure Service.
  • In the segment of account selection, pick the domain account that you desire to correlate with the application pool of Web, or hit Register New Account in order to adjoin a fresh domain name along with the application pool.
  • Once it’s done click OK for the changes to take effect.

Confirm that account has accurate permission

  • Log in as Administrator on PC from SQL is being accessed.
  • In Studio of SQL Management, go to Object Explorer Navigation Pane and enlarge the Security node and then the Login
  • If the account survives then click Roles after expanding the Database and Security
  • After expanding Database Roles, right-click on db_owner and choose Properties.
  • In the Roles Properties of Database check whether role list members include access account or not. If not the hit Add and list it.

Solution 2 – Server database of SQL is compact

Solution: If a database has reached its utmost size then SharePoint foundation won’t be able to write in it. Therefore to solve this issue you can augment the maximum size setting for the database to be occupied, which’s named in the message of the event. In order to enhance the size of the database;

  • Click on Properties by expanding the server and database node in Studio of SQL Server Management that you can find in the Object Explorer steering pane.
  • Click on Files in the dialog box of Properties.
  • Into the Autogrowth column, in the files of Database, hit the ellipses.
  • Under the Autogrowth Column, in the Maximum File Size, if the Restricted File Growth option is preferred, amplify the utmost file from the box on the right side of it. Also, you can opt for the Unrestricted Growth Option.
  • Now press OK for the changes to be implemented.

Solution 3 – Erroneous MDAC version

Solution: MDAC stands for Microsoft Data Access Components. If your version is outdated then have got the latest version installed. Although the lowest required version is 2.8.1022.0 that you can get from the Download Center of Microsoft.

Solution 4 – SQL Server Database not found

Solution: If the SQL server is inaccessible or not present on PC, then reinstate the database using the back-up and rejoin it to SharePoint Foundation.

For restoring a database using back-up:

For reconnecting database in Central Administration

  • Go to Manage Content Database, by clicking Database segment into the Application Management.
  • On the page of Manage Content Database, pick web application after hitting Add a Content Database.
  • In the sector of Verification and Database Name, insert server name in the text box of Database Server and name in the text box of Database Name.
  • Click OK for the alterations to take action.

Solution 5 – SQL server version is incorrect

Solution: The system that hosts the function of the server database must comprise of SQL Server Pack 3, Cumulative Update 3, or SQL Server 2008 Service Pack 1 cumulative update 2 installed. Either install or upgrade to the most suitable version of SQL Server.

Solution 6 – Collation of SQL Server is not supported

Solution: All you have to do is to opt for the most appropriate SQL Server collation

Switch on the system on which the SQL server is being admitted by making use of db_owner agreement.

Again go to Server Mgt. Studio, and then Object Explorer and Expand Database node. Then click on the specific database that was indicated in the 4972 events and move to its Properties.

  • Collation is listed on the Maintenance part of the General tab.
  • Access the Options page to alter the collation.
  • Make a selection of the correct collation from the Box of Collation.

Solution 7 – Database is set to Read-Only

Solution: Modify the database so that it can act for both read-write operations by enlarging the database size. To increase the size of the database:

  • Inflate Server and Database node from Object Explorer Navigation Pane using Studio of SQL Server Management.
  • Go to your desired database and switch to its Properties. Event message will display to you the name of the database.
  • Click Files from the navigation pane of the dialog box Database Properties.
  • Now hit ellipses, in the Autogrowth column from Database Files Segment.
  • Transform Autogrowth Dialog box from a fragment of Maximum file Size if the restricted file growth option has opted. Use the right box to increase the file size to utmost capacity or make use of Unrestricted File Growth
  • Press OK to for saving changes.

Hopefully, the solution provided above will be helpful for you to get rid of any sort of error in relation to SharePoint Event ID 5586.

Easy Solution to Fix Error Event ID 5586 in SharePoint Foundation

If you are still getting the SharePoint Event ID 5586 error then feel free to run the professional recommended SharePoint File Repair Tool

This tool is designed with an advanced algorithm to fix various SharePoint errors and recover the database. It effectively scans the damaged database files and repairs them to recover inaccessible objects in MDF database files.

With this tool, users can also retrieve SharePoint databases like tables, indexes, documents, labels, and stored procedures from inaccessible MDF files. This software is incorporated with a simple and rich graphical user interface to offer easy SharePoint recovery.

Steps to Run the SharePoint Repair Tool

  • Firstly, download, install, and launch the SharePoint Recovery Tool.
  • The interface screen displays two options to recover SharePoint data: ‘Complete Repair‘ and ‘Document Recovery‘. Select as per your requirement.

  • If you choose ‘Complete Repair‘, the screen will show the options for selecting and searching SQL Server (.MDF) files. Click on ‘Browse‘ to select a SharePoint database for repair.
  • If you do not know the actual path of the database which you want to repair, click on the ‘Find‘ to locate the MDF file in a specific drive.
  • After selecting the desired file initiate the scanning process.

  • After finishing the scan, the software would generate a tree of all SharePoint database tables and will display it in the left pane. You can select the table in the tree and can have the entire preview in the right pane. Then click on ‘Repair‘ to begin repairing for the selected database.
  • After clicking on ‘Repair‘, this dialog box will appear. Specify the SQL Server name or Instance name and the desired destination path.
  • Click on the ‘Browse‘ option to choose the destination path. And select the ‘OK‘ button.
  • Once this process gets completed, you would find a dialog box that displays this message ‘Recovered file saved at the desired location.” This shows that Recovery Process has successfully completed’.
  • Select the ‘OK‘ button.
  • You would find another dialog box that asks whether you want to attach the repaired database to the web application. If you click on the ‘Yes‘ button, the above dialog box will be displayed.
  • In the web application type URL, the name of the corrupt database and SQL Server Instance name.
  • Then select the ‘OK‘ button and proceed.
  • When the process gets finished, you would be able to access the repaired database by opening the web application.


So, this is all about the SharePoint foundation event id 5586 error. I tried my best to list down the complete fixes to fix the event id 5586 error in SharePoint.

All the solutions given are easy, make sure to follow them one by one till you find the one that works for you. Hope the article works for you in solving the event id 5586 error.

But if in case the manual solutions won’t work for you, then feel free to use the automatic SharePoint Repair Tool.

If you have any other queries or suggestions, then share it with us on the Facebook page. Also, if you like this article, then share it with the users going through the same issue.