How Do I Resolve SQL Server Error 913 Level 16 State 4?

 

Occasionally, your computer may display SQL Server Error 913, Severity 16, State 4. This problem can have several causes.

 

 

This site is the result of a Skype conversation with one of the my patients. The problem they reached out to me was that they really couldn’t help but discover the SQL services assigned to the database. I asked for access to SQL Server ERRORLOG files in the following blog post SQL SERVER – Where is ERRORLOG located? Various ways to find the ERRORLOG location

SQL SERVER - FIX: Error: 913, Severity: 07 Cannot find - Database ID 3. The database may not be activated yet or is in transition process - SQL Service error-red

Maybe this is some information that I have seen.

2017-04-02 16: 38: 02.40 Error spid11s: 913, Severity: Status: 20, 6.
2017-04-02 16: 38: 02.40 spid11s Database ID not found 3 the database may not yet be activated or is in the process of being migrated. Repeat the question as soon as the database is available. If you believe the persistent failure is not related to a change in database state, but the failure persists, contact your primary support provider. Please providePlease file a Microsoft SQL Server error log and any additional instructions pertaining to the circumstances if you see an error has occurred.

The above post is very scary because it says it won’t be a good database with id = flavors. If you look at the documentation, it was the model list id. We know that this is a real system database that is needed to search for SQL at startup, and any deal with this database will result in SQL startup errors. In my case, the client did not know at all where to relieve himself. Well, the next step is what we have to do. No backup. We had MDF and LDF files. So I tried below.

Solution / Workaround:

  • I started an SQL instance with trace flag 3608, which is usually described in e-books. Then we tried to connect the vehicle database and got the following error:

Failed to create database
Error: 33401, severity: 16, FILESTREAM database parameters usually do not work with system databases data, for example, because template.

  • We tortured I tried to select website template files from different servers, but to no avail.
  • Since there was no backup, many people couldn’t try what to restore.

Finally, I asked them to finally rebuild the system databases, making the MDF and LDF files for all databases a good backup. / QUIET

setup / ACTION = REBUILDDATABASE / INSTANCENAME = MSSQLSERVER / SQLSYSADMINACCOUNTS = “BUILTIN Administrators” / SAPWD = AVeryStrongP @ $$ word123 / SQLCOLLATION = “GCI_AS_Latin>

After executing the above SQL Server. Then we connected all user databases and created all system objects.

sql server error 913 severity 16 state 4

Link: Pinal Dave (http://blog.SQLAuthority.com)

sql server error 913 severity 16 state 4

This blog is the start of a Skype conversation with some of my clients. The problem they contacted me to help me was that they could not advertise the SQL service because the database was not activated. I asked to share the used SQL Server ERRORLOG files at the bottom of the blog. SQL SERVER – Where does ERRORLOG appear most often? Various search methodserror log locations

SQL SERVER - FIX: Error: 913, Severity: 16 Cannot find database ID 3. Database error may not yet be activated or is in the process of migrating - SQL service error -red

Here is information about what I have seen.

2017-04-02 16: 38: 02.40 spid11s error: 913, severity: Status: 16, 6.
2017-04-02 16: 38: 02.40 spid11s id index 3 not found … The database may not be running yet or is in the process of being modified. Re-run the query as soon as the database becomes available. If you do not believe this error is due to the database overriding its own state and the error continues to occur positively, contact your primary support agency. Please prepare a dedicated Microsoft SQL Server error log for review so that additional information pertains to the circumstances in which the error occurred.

The whole message is scary because it says that it is impossible. Database ID = 3. If you are reading the documentation, this is the model data.Database clerk. We know which model is the system database needed to tune SQL, and any problem with that storage system will result in SQL startup errors. In my case, the client did not know how he knew he was suspended. Well, the next step is what are we going to do? NO backup available. We had MDF-LDF and computer data files. So, I tried the following.

Solution / Workaround:

  • I started a SQL instance by running a trace for flag 3608, which was documented in online books. Then we tried to attach to the retrieved model database and also got the following error:

Failed to create database
Error: 33401, Severity: 16, FILESTREAM collection options could not be set for the database device as a model.

  • We selected the model database files on several different servers, no, but lucky.
  • Since there is still no backup, we didn’t really try to restore.

Finally, I asked them to rebuild the body databases by copying the MDF and LDF files for almost all databases intoas a backup ./QUIET

setup / ACTION = REBUILDDATABASE / INSTANCENAME = MSSQLSERVER / SQLSYSADMINACCOUNTS = “BUILTIN Administrators” / SAPWD = AVeryStrongP @ $$ word123 / SQLCOLLATION = “As soon as the order is completed.

SQL_Latin1_General_CP1_pCI was no worse than a fresh SQL Server installation at first. Later, we connected the virtual user databases and created all the unit objects.

Link: Pinal Dave (http://blog.SQLAuthority.com)

This blog is undoubtedly the result of a Skype connection with one of my clients. The problem they linked to came to my mind that they could not find the SQL service because the database might not have been activated. I asked for access to SQL Server ERRORLOG files in the following blog. SQL SERVER – Where is the error log? Ways to find the location of ERRORLOG

04/02/2017 16: 38: 02.40 spid11s Error: 913, Severity: Status: 16, 6.
04/02/2017 16: 38: 02.40 spid11s Database ID 3 was not found. The database may not yet be activated or is in a forward transition state. Resubmit the query when the database becomes available. If you think this error is not related to the database,which changes state and the error occurs last, contact your primary seeding provider. Prepare a Microsoft SQL Server error report and any additional information about the circumstances under which the error occurred for assessment.

The above message is scary because it indicates that it might not be correct. Database ID = 3. When clients view the documentation, this is the specific ID of the database model. We are familiar with simulating the system record required to restart SQL and any database problems can cause SQL to fail to run. In my case, the buyer did not know where he was from. Well, the next step is what should we do? There is NO backup. We had MDF LDF and files with it. So I tried below.

Solution For Each Workaround:

  • I started a SQL instance with trace flag 3608, which is known in online books. Then we tried to connect the model database and got the following error:

Failed to create database
Error: 33401, Severity: 16, FILESTREAM database parameters cannot These are set for system databases such as template.

  • We tried to select the template database files from different servers, with no success.
  • Since there was usually no backup, at first we were unable to try to restore.

Finally, I asked them to rebuild the system databases, keeping a backup of the MDF and LDF files to keep all databases as backups.

After running the above command, SQL Server was considered recently installed. Later we connected all operator databases and created all PC objects.

 

 

 

 

 

Errore Del Server Sql 913 Gravita 16 Stato 4
Error Del Servidor Sql 913 Gravedad 16 Estado 4
Erreur De Serveur Sql 913 Gravite 16 Etat 4
Oshibka Servera Sql 913 Sereznost 16 Sostoyanie 4
Sql Serverfout 913 Ernst 16 Staat 4
Sql Server Fehler 913 Schweregrad 16 Status 4
Erro Do Servidor Sql 913 Gravidade 16 Estado 4
Sql 서버 오류 913 심각도 16 상태 4
Sql Serverfel 913 Allvarlighetsgrad 16 Tillstand 4
Blad Serwera Sql 913 Poziom Waznosci 16 Stan 4