Learn how to resolve the 17204 error in SQL Server from our experts. Our SQL Server Support team is here to help you with your questions and concerns.

17204 error in SQL Server | Resolved

According to our experts, the 17204 error tends to appear when the SQL Server instance or any database operation tries to start the database. In fact, this specific error is an example of Operating System error type 5.

We will chance upon this error at the starting of a SQL Server instance or during a database action that is trying to start the database. In other words, the error 17204 means that the SQL Server is not able to start a database as it cannot open the database or transaction log files.

Furthermore, if a user runs into this error, the database may be in RECOVERY_PENDING state, thereby making the database inaccessible.

However, if the error appears in the System Database it means that the SQL Server instance is refusing to start and we cannot connect to the instance.

Additionally, the SQL Server failover cluster resource may go into an offline state, leading to error 17204.

Caused Behind Error 17204 FCB

• If the service account password has been changed, and not yet updated on the server where the SQL Server instance is installed, the error is likely to pop up.
• The Model Database may be corrupted.
• System data files are missing or corrupted.
• The TempDB database has been moved.
• Incorrect file path or permission issues can also cause SQL Server error 17204.

How to resolve SQL Server Error 17204

• Service account password is changed

  In this scenario, we have to use the SQL Server Configuration Manager to enter a new password under the Log On tab.
• Login failed for user

  If the server is in single user mode, only a single administrator can connect at a single time.

  NET START MSSQLSERVER /f /mSQLCMD
• Model database is corrupted

  In case the model database is corrupted we, have to rebuild the master database or recover it from the backup.
• TemP_db Moved to the incorrect path

  In this case, we have to find the exact location of specific files.

  SQLCMD -S -E

  We can use the following ALTER commands to modify according to our environment:

  
1 ALTER DATABASE tempdb Modify FILE (Name = ‘tempdev’,FileName = ‘C:\tempDB\tempdb.mdf’)
1 ALTER DATABASE tempdb Modify FILE (Name = ‘templog’,FileName = ‘C:\tempDB\templog.ldf’)

• Port is in use by another SQL instance

  Here, we have to change the port of the processor or modify the port of the SQL Server which is not working.