Меню

Microsoft sql server ошибка 9001

  • Remove From My Forums

  • Question

  • I have SQL 2012 database on availability group environment

    Due to lack of space on SQL log partition. I have added to new hard drive configures on RAID1

    Moved the ldf files from active partition to newly created partition.

    SMS change the path for log drive to new drive

    Restart SQL server services

    I cannot connect to databases anymore and I have also lost all setting of Availability group

    Error message

     

    Event logs for Application

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          16/07/2015 8:32:22 a.m.
    Event ID:      5123
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ***.Local
    Description:
    CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file ‘D:SQL Logstemplog.ldf’.
    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»MSSQLSERVER» />
        <EventID Qualifiers=»49152″>5123</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2015-07-15T20:32:22.000000000Z» />
        <EventRecordID>368973</EventRecordID>
        <Channel>Application</Channel>
        <Computer>****.Local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3(The system cannot find the path specified.)</Data>
        <Data>D:SQL Logstemplog.ldf</Data>
        <Binary>03140000100000000B0000004E005A00490054005300530051004C0030003400000000000000</Binary>
      </EventData>
    </Event>

    New location for D:SQL Logstemplog.ldf is into L:SQL Logstemplog.ldf

    Muhammad Mehdi

    • Edited by

      Wednesday, July 15, 2015 8:50 PM
      More information

Answers

  • looks like you forgot to alter the database files for tempdb and it is looking for the file in the old location..

    heres what you can to fix it

    1. start sql server in minimal configuration mode — i.s in the configuration manager — go to advanced start up parameters and add -f to it

    2. start the sql server and in the ssms — ALter database tempdb MODIFY FILE ( NAME = templog, FILENAME = ‘L:SQL
    Logstemplog.ld    f’ )

    3. remove the paraameter added in step 1 and restart . it shoulf work.

    or follow this article..

    https://www.xtivia.com/start-sql-server-lost-tempdb-data-files/

    Hope it Helps!!

    • Marked as answer by
      MM from AUS
      Thursday, July 16, 2015 8:54 PM

Источник

Over the weekend a website I run stopped functioning, recording the following error in the Event Viewer each time a request is made to the website:

Event ID: 9001

The log for database ‘database name‘ is not available. Check the event log for related error messages. Resolve any errors and restart the database.

The website is hosted on a dedicated server, so I am able to RDP into the server and poke around. The LDF file for the database exists in the C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLDATA folder, but attempting to do any work with the database from Management Studio results in a dialog box reporting the same error — 9001: The log for database is not available…

This is the first time I’ve received this error, and I’ve been hosting this site (and others) on this dedicated web server for over two years now.

It is my understanding that this error indicates a corrupt log file. I was able to get the website back online by Detaching the database and then restoring a backup from a couple days ago, but my concern is that this error is indicative of a more sinister problem, namely a hard drive failure.

I emailed support at the web hosting company and this was their reply:

There doesn’t appear to be any other indications of the cause in the Event Log, so it’s possible that the log was corrupted. Currently the memory’s resources is at 87%, which also may have an impact but is unlikely.

Can the log just «become corrupted?»

My question: What are the next steps I should take to diagnose this problem? How can I determine if this is, indeed, a hardware problem? And if it is, are there any options beyond replacing the disk?

Thanks

Источник

Let’s take a closer look at SQL Server Fatal Error 9001 and some fixes available for the error. At Bobcares, with our Server Management Services, we can handle your SQL Server issues.

What Is An SQL Server Fatal Error 9001?

When the SQL server fails to open the database for long enough for the backup to be successfully taken, SQL backup error 9001 happens. If the AutoClose property on the database is ON, the database will automatically close when there is no activity. As a result, this error may occur if the database closes abruptly during the backup.

sql server fatal error 9001

Corrupt databases or log files, a large SQL log file that requires a lot of storage space, and hardware problems are a few additional causes of this error. To get more details on the error, we can run the DBCC CHECKDB‘dbname’.

How To Fix SQL Server Fatal Error 9001?

Let’s discuss some of the following methods to fix the error.

  • Turn off Auto Close if it’s currently set to on. With no action throughout the backup process, this will stop the database from closing. 
    alter database [database_name] set AUTO_CLOSE OFF;
  • If there is a storage issue, use DBCC CHECKDB. 
    dbcc checkdb('database_name')
  • If the error occurs due to the corruption of the SQL database or log file, then launch Emergency Mode Repair. This will also help in the completion of the backup operation and the repair of the log file. It is not advisable to use this method because it can result in the deletion of some log file sections. 
    DBCC CHECKDB (N'database_name', REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS, NO_INFOMSGS;
  • Set SQL Server Database Offline and Online again. 
    alter database [database_name] set offline with rollback immediate;

    and

    alter database [database_name] set online;
  • For non-production instances, restarting the SQL Server is a good solution. Restarting SQL Configuration Manager through the Start menu, Windows Server’s Services, or Cmd via net start and net stop are all options.

[Need help with another issue? We’re happy to help 24/7.]

Conclusion

The SQL server fatal error 9001 occurs when the SQL server is unable to open the database for long enough for a backup to be successfully taken. In this article, we post some of the simple methods from our Tech team to fix the error easily.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Источник

Permalink

Cannot retrieve contributors at this time

description title ms.custom ms.date ms.service ms.reviewer ms.subservice ms.topic helpviewer_keywords ms.assetid author ms.author

MSSQLSERVER_9001

MSSQLSERVER_9001 | Microsoft Docs

04/04/2017

sql

supportability

reference

9001 (Database Engine error)

a54de936-90c6-4845-aa96-29d32f154601

MashaMSFT

mathoma

MSSQLSERVER_9001

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 9001
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name LOG_NOT_AVAIL
Message Text The log for database ‘%.*ls’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Explanation

The database log was taken offline. Usually this signifies a catastrophic failure that requires the database to restart.

User Action

Diagnose other errors and restart the instance of SQL Server if it has not already restarted itself.

Источник

Permalink

Cannot retrieve contributors at this time

description title ms.custom ms.date ms.service ms.reviewer ms.subservice ms.topic helpviewer_keywords ms.assetid author ms.author

MSSQLSERVER_9001

MSSQLSERVER_9001 | Microsoft Docs

04/04/2017

sql

supportability

reference

9001 (Database Engine error)

a54de936-90c6-4845-aa96-29d32f154601

MashaMSFT

mathoma

MSSQLSERVER_9001

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 9001
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name LOG_NOT_AVAIL
Message Text The log for database ‘%.*ls’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Explanation

The database log was taken offline. Usually this signifies a catastrophic failure that requires the database to restart.

User Action

Diagnose other errors and restart the instance of SQL Server if it has not already restarted itself.

Источник
  • Remove From My Forums

  • Question

  • I have SQL 2012 database on availability group environment

    Due to lack of space on SQL log partition. I have added to new hard drive configures on RAID1

    Moved the ldf files from active partition to newly created partition.

    SMS change the path for log drive to new drive

    Restart SQL server services

    I cannot connect to databases anymore and I have also lost all setting of Availability group

    Error message

     

    Event logs for Application

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          16/07/2015 8:32:22 a.m.
    Event ID:      5123
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ***.Local
    Description:
    CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file ‘D:SQL Logstemplog.ldf’.
    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»MSSQLSERVER» />
        <EventID Qualifiers=»49152″>5123</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2015-07-15T20:32:22.000000000Z» />
        <EventRecordID>368973</EventRecordID>
        <Channel>Application</Channel>
        <Computer>****.Local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3(The system cannot find the path specified.)</Data>
        <Data>D:SQL Logstemplog.ldf</Data>
        <Binary>03140000100000000B0000004E005A00490054005300530051004C0030003400000000000000</Binary>
      </EventData>
    </Event>

    New location for D:SQL Logstemplog.ldf is into L:SQL Logstemplog.ldf

    Muhammad Mehdi

    • Edited by

      Wednesday, July 15, 2015 8:50 PM
      More information

Answers

  • looks like you forgot to alter the database files for tempdb and it is looking for the file in the old location..

    heres what you can to fix it

    1. start sql server in minimal configuration mode — i.s in the configuration manager — go to advanced start up parameters and add -f to it

    2. start the sql server and in the ssms — ALter database tempdb MODIFY FILE ( NAME = templog, FILENAME = ‘L:SQL
    Logstemplog.ld    f’ )

    3. remove the paraameter added in step 1 and restart . it shoulf work.

    or follow this article..

    https://www.xtivia.com/start-sql-server-lost-tempdb-data-files/

    Hope it Helps!!

    • Marked as answer by
      MM from AUS
      Thursday, July 16, 2015 8:54 PM

Источник
  • Remove From My Forums

  • Question

  • I have SQL 2012 database on availability group environment

    Due to lack of space on SQL log partition. I have added to new hard drive configures on RAID1

    Moved the ldf files from active partition to newly created partition.

    SMS change the path for log drive to new drive

    Restart SQL server services

    I cannot connect to databases anymore and I have also lost all setting of Availability group

    Error message

     

    Event logs for Application

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          16/07/2015 8:32:22 a.m.
    Event ID:      5123
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ***.Local
    Description:
    CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file ‘D:SQL Logstemplog.ldf’.
    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»MSSQLSERVER» />
        <EventID Qualifiers=»49152″>5123</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2015-07-15T20:32:22.000000000Z» />
        <EventRecordID>368973</EventRecordID>
        <Channel>Application</Channel>
        <Computer>****.Local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3(The system cannot find the path specified.)</Data>
        <Data>D:SQL Logstemplog.ldf</Data>
        <Binary>03140000100000000B0000004E005A00490054005300530051004C0030003400000000000000</Binary>
      </EventData>
    </Event>

    New location for D:SQL Logstemplog.ldf is into L:SQL Logstemplog.ldf

    Muhammad Mehdi

    • Edited by

      Wednesday, July 15, 2015 8:50 PM
      More information

Answers

  • looks like you forgot to alter the database files for tempdb and it is looking for the file in the old location..

    heres what you can to fix it

    1. start sql server in minimal configuration mode — i.s in the configuration manager — go to advanced start up parameters and add -f to it

    2. start the sql server and in the ssms — ALter database tempdb MODIFY FILE ( NAME = templog, FILENAME = ‘L:SQL
    Logstemplog.ld    f’ )

    3. remove the paraameter added in step 1 and restart . it shoulf work.

    or follow this article..

    https://www.xtivia.com/start-sql-server-lost-tempdb-data-files/

    Hope it Helps!!

    • Marked as answer by
      MM from AUS
      Thursday, July 16, 2015 8:54 PM

Источник

Проблема

При попытке выполнить резервное копирование в Autodesk Data Management (ADMS) Console может произойти сбой в файлах журнала. 

 Ошибка: соединение с базой данных было нарушено. Повторный запуск операции. Исключение: Предупреждение: Неустранимая ошибка 9001 в период по месяцам. Обратите внимание на ошибку и время и обратитесь к системному администратору. Stacktrace: at Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e) at Connectivity.Core.Database.SqlAccess.ExecuteNonQueryInternal(SqlCommand cmd) at Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String commandText, Int32TimecommandTimecommandPost Parameter[] commandParameters) at Connectivity.Core.DataAccess.DatabaseLocking.RevokeSiteAccess(String databasename, IEnumerable sites, ICollection`1 permissions) at Connectivity.Core.Services.KnowledgeMasterService.RevokeSiteAccess(ArrayListDatabases, ArrayList sites) at Connectivity.Core.Services.MasterServices.Master KnowledgeVaultMaster(OnProgressDelegate onProgress) в System.Runtime.Remoting.Messaging.Message.Dispatch(Object target) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Причины

Сбой при создании резервной копии: ошибка базы данных в SQL.
 

Решение

Если Microsoft SQL Server Management Studio (SMSS) не установлен, установите его с установочного носителя Microsoft или скачайте с веб-сайта Microsoft.

Войдите в экземпляр AutodeskVault SQL Server с помощью SSMS —

1. Автономная работа со всеми базами данных Vault.
2. Отключите все базы данных, связанные с Vault.
3. Войдите в консоль ADMS Console.

Удалите базы данных из списка в Vault или Libraries.

Подключите их повторно с помощью ADMS Console.

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ятрогенная патология врачебные ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Microsoft sql server ошибка 7399

    • ➤