Event ID - 3759

Event Id3759
SourceWindows SharePoint Services 3
DescriptionDatabase '%1' on SQL Server instance '%2' is not empty and does not match current database schema.
Event InformationAccording to Microsoft :
Cause :
This event is logged when SQL Server instance database does not match current schema.
Resolution :
Restore database from backup
The SQL Server database is not present or accessible on the computer running SQL Server. Confirm that the database is online. If it is not, you will need restore the database from a backup, and re-connect it to Windows SharePoint Services 3.0. For information about restoring the database see the Windows SharePoint Services 3.0 documentation.
Note :
You must be a member of the SharePoint Administrators group to perform these tasks.
To restore the database from a previous backup
1.In Central Administration, on the left navigation pane, click Operations.
2.On the Operations page, in the Backup and Restore section, click Restore from backup.
3.On the Restore from Backup page, type the backup share path in the Backup location box, and then click OK.
4.Select the backup from the list.
Note :
The backup must be of at least the database and the accompanying Web application.

5.Click Continue Restore Process.
6.Select the check box next to the database and click Continue Restore Process.
7.Under Restore Options, select the Same configuration option. This will overwrite the existing database.
8.Click OK.
To reconnect the database in Central Administration
1.In Central Administration, on the left navigation pane, click Application Management.
2.On the Application Management page, in the SharePoint Web Application Management section, click Content databases.
3.On the Manage Content Databases page, click Add a content database.
4.On the Add Content Database page, in the Web Application section, select the Web application from the Web application drop-down list.
5.Under Database Name and Authentication, type the name of the server in the Database Server box and the database name in the Database Name box.
6.Click OK to save the changes.
Verify :
You must be a member of the SharePoint Administrators group to perform this task.
To ensure that any database issues have been resolved
1.Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.
2.Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.
3.In Central Administration, on the left-hand navigation pane, click Application Management.
4.On the Application Management page, in the SharePoint Site Management section, click Quota templates.
5.On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.
6.Click OK to save the quota template.
7.Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.
8.Click Delete to delete the quota template.
Reference LinksEvent ID 3759 from Source Windows SharePoint Services 3

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.