Не удалось запустить службу sql server код ошибки 945

«Database [database name] cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details. (Microsoft SQL Server, Error: 945)»

What Is SQL Error 945

SQL Server error 945 happens when a database is marked as «IsShutdown» or when the attaching and detaching of MDF file is not properly done and the recovery procedure fails to bring the database to a consistent state.

It may occur due to different reasons:

• Disproportionate storage consumed by memory-optimized tables
• SQL database repair failure due to some missing files
• Using corrupt backup
• Improper shutdown of the database
• Malware attacks

When you are bothered by the SQL Server error 945, there are six solutions to try.

How to Fix SQL Error 945 Database Cannot Be Opened Due to Inaccessible Files or Insufficient Memory or Disk Space in 6 Ways

According to user experience, there are effectiveness-based solutions to error 945 in SQL Server — Database cannot be opened due to inaccessible files. At the very beginning, you can restart your SQL database through ALTER DATABASE query. This query will help you to set the SQL Server database to online. If this doesn’t work, figure out with the following methods. 

Fix 1. Enlarge Hard Drive Space

As you can see in the error notification, the SQL database may not be opened due to insufficient disk space, getting rid of the unnecessary files on the corresponding hard drive or add a larger hard drive is a potential solution to the SQL Server error 945. If you are worried about data loss, you can back up the hard drive with free backup software in advance before the removal.

Fix 2. Make Sure Autogrowth Is On

Since the database must be set to Autogrowth, you need to check and make sure the option is enabled. Here is the way to enable Autogrowth:

Step 1. Open SQL Server Management Studio and connect to the problematic database.

Step 2. Click «View» > «Object Explorer».

Step 3. Expand the «Database» folder.

Step 4. Right-click the database and choose «Properties».

Step 5. Under «Select a Page», choose «Files» and look for the Autogrowth settings and check the option «Enable Autogrowth».

Fix 3. Check the Account Permission

You need to check the account you are using and make sure you have the correct permission to perform operations.

Fix 4. Check the MDF/NDF File of the Database

If the MDF or NDF file of the database is marked as read-only, you may encounter the SQL error 945. Thus, be sure that the MDF and NDF files are not shown as read-only. To remove read-only on the MDF or NDF file:

Step 1. Find and right-click the «.mdf «or «.ndf» file of your database. Choose «Properties» > «Security», then you will see Group or Username.

Step 2. Select the user you want to give access to the file and check the permission.

Step 3. If the permission is not set to Full Control, you need to change it by clicking «Edit».

Step 4. Then you will see the Group or Username box. In that box, select the user and choose «Full Control».

Fix 5. Use SQL Database Repair Tool

Go to the error log and see why the database goes wrong. If it is due to a persistent I/O error related to Application Programming Interface, a torn page, or other hardware issues then resolved it by restoring the database from backup. If you don’t have any backup available, you can repair your SQL database with the professional MS SQL repair tool — EaseUS MS SQL Recovery.

• Repairs corrupted SQL database files (MDF/NDF files)
• Repairs corrupted SQL server database components — tables, triggers, indexes, keys, rules & stored procedures
• Recovers deleted/dropped records from SQL Database

Let’s see how to repair your database with it:

Step 1. Stop MS SQL Server service

Press «Windows + R» and enter services.msc.

Find and double-click «SQL Server (instant name)».

In the Properties windows, click «Stop» to end the SQL Server and click «Apply» to confirm.

Step 2. Run EaseUS SQL repair tool. In the main interface, click «Browse» (the two dots) to choose the corrupted MDF/NDF file. Then click «Repair» to start analyzing your MDF/NDF file. 

If you know the exact location of the file, click «Browse» to locate the database.

If you don’t know the file location, click «Search» to search for the .mdf or .ndf file in.

Step 3. When it has done, you will see all the database objects listed in the left pane of the window. Choose the database objects you’d like to repair and click «Export».

Step 4. Choose a preferred way to export the database data: «Export to database» or «Export as SQL scripts». If you select «Export to database», you need to further select the server information, log into your account, and select a destination database, either a new one or an existing one.

Step 5. Before you click «OK», now you need to restart the SQL Server.

Press «Windows + R» and enter services.msc.

Find and double-click «SQL Server (instant name)».

In the Properties windows, click «Start» to restart the SQL Server service and click «Apply» to confirm.

Step 6. Click «OK» to save the repaired files to your desired SQL database.

Fix 6. Try DBCC CHECKDB Repair Option

If there is no backup available, you can also try the DBCC CHECKDB repair option. However, it is not recommended since it may induce the Suspect Mode of your SQL database, which may further lead to another SQL Server database error 926. (Click to see more SQL database errors.)

Wrap Things Up

We focused on one of the most common SQL server issues, error 945. We have discussed the possible reasons and solutions to fixing database that cannot be opened due to inaccessible files or insufficient memory or disk space issue. You can try the manual methods to fix SQL server error 945 like enlarge hard drive space, checking account permission, checking database files, and trying DBCC CHECKDB. 

For an easier approach, EaseUS SQL repair tool is worth trying. It offers the simplest way to repair corrupted  (.mdf and.ndf) files, fix database log files, and recover damaged objects.

More Info: How to Fix SQL Server Error 926

Similar to SQL error 945, SQL error 926 can also occur due to improper connection to SQL Server or using the RESTORE database or RESTORE LOG procedures, showing the error message «Database cannot be opened. It has been marked SUSPECT by recovery».  Take the following ways to solve this problem. 

• Check DBCC CHECKDB: Check the error report and solve the issue with provided solutions
• Restore from database backup: Restore databases if you have any available backup
• Contact error logs: If you can’t restore the SQL database from backup, you can try to contact primary support or contact the error logs for SQL Server.

«Database [database name] cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details. (Microsoft SQL Server, Error: 945)»

What Is SQL Error 945

SQL Server error 945 happens when a database is marked as «IsShutdown» or when the attaching and detaching of MDF file is not properly done and the recovery procedure fails to bring the database to a consistent state.

It may occur due to different reasons:

• Disproportionate storage consumed by memory-optimized tables
• SQL database repair failure due to some missing files
• Using corrupt backup
• Improper shutdown of the database
• Malware attacks

When you are bothered by the SQL Server error 945, there are six solutions to try.

How to Fix SQL Error 945 Database Cannot Be Opened Due to Inaccessible Files or Insufficient Memory or Disk Space in 6 Ways

According to user experience, there are effectiveness-based solutions to error 945 in SQL Server — Database cannot be opened due to inaccessible files. At the very beginning, you can restart your SQL database through ALTER DATABASE query. This query will help you to set the SQL Server database to online. If this doesn’t work, figure out with the following methods. 

Fix 1. Enlarge Hard Drive Space

As you can see in the error notification, the SQL database may not be opened due to insufficient disk space, getting rid of the unnecessary files on the corresponding hard drive or add a larger hard drive is a potential solution to the SQL Server error 945. If you are worried about data loss, you can back up the hard drive with free backup software in advance before the removal.

Fix 2. Make Sure Autogrowth Is On

Since the database must be set to Autogrowth, you need to check and make sure the option is enabled. Here is the way to enable Autogrowth:

Step 1. Open SQL Server Management Studio and connect to the problematic database.

Step 2. Click «View» > «Object Explorer».

Step 3. Expand the «Database» folder.

Step 4. Right-click the database and choose «Properties».

Step 5. Under «Select a Page», choose «Files» and look for the Autogrowth settings and check the option «Enable Autogrowth».

Fix 3. Check the Account Permission

You need to check the account you are using and make sure you have the correct permission to perform operations.

Fix 4. Check the MDF/NDF File of the Database

If the MDF or NDF file of the database is marked as read-only, you may encounter the SQL error 945. Thus, be sure that the MDF and NDF files are not shown as read-only. To remove read-only on the MDF or NDF file:

Step 1. Find and right-click the «.mdf «or «.ndf» file of your database. Choose «Properties» > «Security», then you will see Group or Username.

Step 2. Select the user you want to give access to the file and check the permission.

Step 3. If the permission is not set to Full Control, you need to change it by clicking «Edit».

Step 4. Then you will see the Group or Username box. In that box, select the user and choose «Full Control».

Fix 5. Use SQL Database Repair Tool

Go to the error log and see why the database goes wrong. If it is due to a persistent I/O error related to Application Programming Interface, a torn page, or other hardware issues then resolved it by restoring the database from backup. If you don’t have any backup available, you can repair your SQL database with the professional MS SQL repair tool — EaseUS MS SQL Recovery.

• Repairs corrupted SQL database files (MDF/NDF files)
• Repairs corrupted SQL server database components — tables, triggers, indexes, keys, rules & stored procedures
• Recovers deleted/dropped records from SQL Database

Let’s see how to repair your database with it:

Step 1. Stop MS SQL Server service

Press «Windows + R» and enter services.msc.

Find and double-click «SQL Server (instant name)».

In the Properties windows, click «Stop» to end the SQL Server and click «Apply» to confirm.

Step 2. Run EaseUS SQL repair tool. In the main interface, click «Browse» (the two dots) to choose the corrupted MDF/NDF file. Then click «Repair» to start analyzing your MDF/NDF file. 

If you know the exact location of the file, click «Browse» to locate the database.

If you don’t know the file location, click «Search» to search for the .mdf or .ndf file in.

Step 3. When it has done, you will see all the database objects listed in the left pane of the window. Choose the database objects you’d like to repair and click «Export».

Step 4. Choose a preferred way to export the database data: «Export to database» or «Export as SQL scripts». If you select «Export to database», you need to further select the server information, log into your account, and select a destination database, either a new one or an existing one.

Step 5. Before you click «OK», now you need to restart the SQL Server.

Press «Windows + R» and enter services.msc.

Find and double-click «SQL Server (instant name)».

In the Properties windows, click «Start» to restart the SQL Server service and click «Apply» to confirm.

Step 6. Click «OK» to save the repaired files to your desired SQL database.

Fix 6. Try DBCC CHECKDB Repair Option

If there is no backup available, you can also try the DBCC CHECKDB repair option. However, it is not recommended since it may induce the Suspect Mode of your SQL database, which may further lead to another SQL Server database error 926. (Click to see more SQL database errors.)

Wrap Things Up

We focused on one of the most common SQL server issues, error 945. We have discussed the possible reasons and solutions to fixing database that cannot be opened due to inaccessible files or insufficient memory or disk space issue. You can try the manual methods to fix SQL server error 945 like enlarge hard drive space, checking account permission, checking database files, and trying DBCC CHECKDB. 

For an easier approach, EaseUS SQL repair tool is worth trying. It offers the simplest way to repair corrupted  (.mdf and.ndf) files, fix database log files, and recover damaged objects.

More Info: How to Fix SQL Server Error 926

Similar to SQL error 945, SQL error 926 can also occur due to improper connection to SQL Server or using the RESTORE database or RESTORE LOG procedures, showing the error message «Database cannot be opened. It has been marked SUSPECT by recovery».  Take the following ways to solve this problem. 

• Check DBCC CHECKDB: Check the error report and solve the issue with provided solutions
• Restore from database backup: Restore databases if you have any available backup
• Contact error logs: If you can’t restore the SQL database from backup, you can try to contact primary support or contact the error logs for SQL Server.

Troubleshooting MS SQL Server Error 945 – Reasons & Solutions

Let’s take a scenario to understand the SQL Server error 945: Database cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server Error Log for details.

“I received a query saying the SQL database is not accessible and the database goes in suspect mode. Also, Database operation was ceased and the SQL Server database stopped the transactions. Does anyone know the solution, please help me out? Why is this happening and how to resolve it?”

According to an above-discussed scenario, it is found SQL error 945 occurs when the attaching and detaching of MDF file is not properly done and recovery procedure fails to bring the database in a consistent state. Improper shutdown of the database and malware attacks is also the responsible reasons for this error.

Here, we will discuss the suspect database and the possible reasons behind why database becomes suspect. Also, we will cover the method to resolve SQL Server error 945.

What is Suspect Database in SQL Server?

Microsoft SQL Server serves as a store for data that is required for different applications either on a single system or across a network. But, sometimes users may face difficulty when the SQL Server database is running under the state marked as suspect. Because this condition will lead to a failure in creating a connection with the database. Database marked as Suspect can be accessed by removing the causes for this SQL Server 945 error.

SQL Server Database is in Suspect Mode- Possible Reasons

There are several reasons that can make the SQL Server database suspected. Some of the common reasons are:

• If SQL database files are used by the operating system.
• If SQL Server Database is corrupted.
• Insufficient space available in SQL server.
• SQL files are used by any other backup software.
• Sudden SQL Server Shutdown.
• Hardware or Power Failure.

How to Fix Microsoft SQL Server Error 945?

Perform the following steps to resolve “Windows could not start the SQL server error 945” :

1. At first, you should try to add more hard drive space either by removing of unnecessary files from the hard drive or add a new hard drive with the larger size.
2. Check if the database is set to Auto growth.
3. Check if the account which is trying to use the database has enough permission to perform any operation.
4. Make sure that MDF and LDF files are not marked as read-only.

An Effortless Solution to Resolve Microsoft SQL Error 945

If your SQL Database file is found to be severely corrupted, it could be the possibility that the above method gets failed to fix SQL Server code 945. In order to fix Microsoft SQL Server error 945 quickly, you can go for an automated solution i.e SysTools SQL MDF Recovery Tool. The tool repair corrupt SQL MDF file and give two options to export your recovered SQL Server database. Moreover, by using this Professional software, you can easily make your database from suspect mode to normal mode.

Download Now Purchase Now

How to Use SysTools Database Recovery Software?

Step 1. Launch SQL Recovery Software on your local machine.

Step 2. Click Open and Load MDF file that you want to recover.

Step 3. After that, click on Advance Scan and click Auto Detect if you don’t know MDF file version. The user can check the option preview deleted records in red color.

Step 4. After scanning, the software will display the preview of data items.

Step 5. Click on Export to save the recovered database.

Wrapping Up

In this article, we have discussed the most common SQL user and DBA faces MS SQL error 945. The blog discusses the possible reason why SQL database becomes inaccessible. It also covers the manual approach to fix SQL Server error 945. For simple, easy and effortless solution, SQL recovery Tool is recommended above. It is the easiest approach to fix SQL error 945 from the MS SQL server.

Frequently Asked Questions

Get Rid of Suspect SQL Server Error 926 and 945

SQL Server databases can experience a lot of issues with its integrity and if there is any inconsistency with the database in its Read or Write operation can cause a fatal error. SQL Server error 926 and 945 also belong to such error types where certain associated files are either missing or has some other issues. The case is rare but can happen while connecting the SQL Instance using SA login. What happens is when you try to connect it, an error message is thrown depicting that the ‘msdb’ cannot be opened and it is marked as suspect. Both of SQL error 926 and error 945 are caused due to different reasons. We will discuss about these errors one by one.

SQL Error 926

Severity Level 14

Error Message: SQLDatabase ‘%.*ls’ cannot be opened. This database is marked as SUSPECT by recovery. Refer SQL Server errorlog for more details.

Description:

Such type of error resembles that the database has integrity issues and that is why the database is marked as SUSPECT. It might have failed the recovery process which brings the database to consistent state. SQL Server Error 926 can be displayed while performing the mentioned operations like; while starting the Microsoft SQL Server instance, or while attaching any database or while performing RESTORE or RESTORE LOG procedures.

Error Resolution:

SQL Error 926 can be rectified at user’s end and the database can be then accessed without any error. As soon as this error message is detected, one can check for Microsoft SQL Server error log and check for the root cause for SQL Server error 926 to occur. In case recovery was not possible due to other reasons like I/O error, hardware issue, or torn page, etc.

For such error one can consider the integrity check utility DBCC CHECKDB which will report the error and provide a solution for it. One can opt to restore the backup if updated backup is available. In case backup is not available or the integrity check tool is unable to resolve the problem, one can contact primary support provider or can also contact the error logs for SQL Server.

SQL Server Error 945

Error 945

Severity Level 16

Error Message:

SQL Server Database ‘%.*ls’ is not opening because of inaccessible files. This can also be caused if there is not enough disk space or memory on the system then also this error can be generated. See the error log of SQL Server for more details.

Description:

SQL server error 945 is displayed when the database is marked as IsShutdown. This error occurs when a database cannot be recovered due to missing files. The error can also be caused as some resource error was not corrected successfully.

SQL Server Error 945 Resolution:

Check if database is flagged as IsShutdown with DATABASEPROPERTY. Afterwards, you can examine the cause of error by checking the errorlog and perform below mentioned steps;

If data/log files are missing;

• Search for the missing files, and bring the database OFFLINE.
• Use ALTER DATABASE in order to bring it ONLINE.

If log space is not enough;

• Utilize sp_add_log_file_recover_suspect_db() for adding new log file.

Database will be recovered and will be mounted online.

In case memory is not sufficient;

While recovering the multiple databases, this error can be displayed. One can retry the operation which might fix this issue.

• Try the operation again with ALTER DATABASE for bringing the .db OFFLINE.
• Then utilize ALTER DATABASE for bringing .db ONLINE.

Common Solutions – SQL Server Error 926& 945

Both the SQL Server error 926 and error 945 can be correct by these following steps:

Hardware Issues:

Windows system can have system issues and if there is corruption problem, databases mounted on the system will also be inaccessible. In such condition one can contact the Microsoft product service provider and fix the components.

Fetch Database from Backup:

In case users are having an updated backup of the SQL databases then one can easily restore the databases from the backup. Once the databases are restored, erroneous messages will not be displayed.

Repair Solution:

The very first step which must be taken is trying the inbuilt integrity check DBCC CHECKDB command. This integrity utility will check if there is any error issue and will report it to you and if the error still persist after applying above mentioned procedures then one can also go with third party utilities to recover SQL database from suspect mode and fix SQL Server error 926.

December 13, 2014
December 13, 2014

After doing a fresh installation of SQL2014 Express on a Windows 2012R2 standard server i got an error while connecting to the server instance.
After looking in the eventlog i found these messages stating that the SQL instance service terminated
(The SQL server (SQLEXPRESS) service terminated with the following service -specific eror: %%945)

System log:

Application log:

The errors in the application log seem odd because the server had no e drive!
During testing i found out that could only start the instance in single user mode and when i tried connecting through SQL management tools the service would crash.

So I tried figuring out where the sql instance installed all the databases by using these commands

• NET START MSSQL$SQLEXPRESS /f /T3608
• SQLCMD -S .SQLEXPRESS

once the connection was made to the sql instance

• SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY database_id;
• go

Then the following output was generated

After reviewing the output it looks that some of the databases where configured on a non existing drive for reasons unkown..
I used these commands to get the databases on the right drive/directory.

• NET START MSSQL$SQLEXPRESS /f /T3608
• SQLCMD -S .SQLEXPRESS

Once the connection was made to the SQL instance I used these commands to set the correct drives/path settings

• ALTER DATABASE model MODIFY FILE ( NAME = modeldev, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAmodel.mdf’);
• ALTER DATABASE model MODIFY FILE ( NAME = modellog, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAmodellog.ldf’);
• go

Be aware that the model database needs to be set first otherwise the other databases wont’t be changed and you’ll get lots of errors!

• ALTER DATABASE tempdb MODIFY FILE ( NAME = tempdev, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAtempdb.mdf’);
• ALTER DATABASE tempdb MODIFY FILE ( NAME = templog, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAtemplog.ldf’);
• ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBData, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAMSDBData.mdf’);
• ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBLog, FILENAME = ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQLEXPRESSMSSQLDATAMSDBLog.ldf’);
•  go
•  exit

After that I restarted the SQL service and it would now start without issues!

Next step was connecting with SQL management studio where i got this error (with sa account and windows integrated authentication)

After tripple checking all the passwords it seems that the SA account wasn’t created properly so that needs to be fixed..

So here’s how thats done:
Restart the database in single user mode

• NET STOP MSSQL$SQLEXPRESS
• NET START MSSQL$SQLEXPRESS /m

Connect to the master database in single user mode and create a new user with the correct database admin rights

• SQLCMD -S .SQLEXPRESS
• CREATE LOGIN noob WITH PASSWORD = ‘whatever’
•  GO
•  sp_addsrvrolemember ‘security’, ‘sysadmin’
•  GO
• quit

Restart the sql service in normal mode

• NET STOP MSSQL$SQLEXPRESS
• NET START MSSQL$SQLEXPRESS

Now connect to the instance with the SQL management tool and user noob and whatever as username and password. You can then change the SA users password and add the domain members you want with the specific required rights. After that is done don’t forget to disable or remove the noob account for security reasons!

Tracing back the installation steps I found out that during the installation there was a warning indicating there was a problem executing sql scripts.