Меню

Ошибка sql server 17058

  • Remove From My Forums

  • Вопрос

  • Прооблема с запуском службы SQL Server 2008. Служба не запускается и в журнале ошибок выдается сообщение:
    Источник: MSSQLSERVER
    Категория: Сервер
    ID: 17058

    initerrlog: не удалось открыть файл журнала ошибок «». Ошибка операционной системы = 3(Системе не удается найти указанный путь.).

    Может кто-нибудь помочь в решении проблемы?

    Михаил

Ответы

  • Похоже, наилучее решение в этой ситуации, оставить сервер работать под системной учетной записью. Может я не прав?

    Михаил

    не совсем…

    стартовать сервер под системной записью совсем нехорошо… и небезопасно.

    созданную отдельную учетку надо  добавить в группы
    SQLServer2005MSFTEUser$ИМЯ_СЕРВЕРА$MSSQLSERVER
    SQLServer2005MSSQLUser$ИМЯ_СЕРВЕРА$MSSQLSERVER

    blog.wadmin.ru

    • Помечено в качестве ответа

      17 ноября 2009 г. 9:18

Источник

I’m working with virtual machine on the windows 8. There is a SQL Server 2008 on the virtual machine. And in the services; when I try to start the SQL Server service getting an error like this:

enter image description here

Can anyone help me?

Thanks.

Edit:

The OS of virtual machine is windows server 2008.

asked Dec 23, 2013 at 9:08

bdkhsn's user avatar

bdkhsnbdkhsn

331 gold badge1 silver badge4 bronze badges

4

CHeck for another error in the event log that is time-correlated to this one. Basically — this one is from the service manager. The SQL Server service should have written another error (either into th event log or the errorlog) that contains the internal error that happened. THis error is generic from the serivce manager and as such totally irrelevant to debugging. It also is well known — google for «Sql server 17058» finds tons of references.

It seems to be a permission error:

http://www.it-sideways.com/2012/11/mssql-startup-error-code-17058.html

points to

«Could not open error log file ». Operating system error = 3 (The system cannot find the path specified.).»

which would be an operating system level configuration or insallation issue.

answered Dec 23, 2013 at 11:27

TomTom's user avatar

TomTomTomTom

4,6141 gold badge15 silver badges19 bronze badges

1

Yes. You could check that you have all paths configured correctly in this service properties in SQL Server Configuration Manager or Services. This is tab called Startup parameters.

answered Dec 23, 2013 at 13:13

Kuba Miazek's user avatar

Источник

I’m working with virtual machine on the windows 8. There is a SQL Server 2008 on the virtual machine. And in the services; when I try to start the SQL Server service getting an error like this:

enter image description here

Can anyone help me?

Thanks.

Edit:

The OS of virtual machine is windows server 2008.

asked Dec 23, 2013 at 9:08

bdkhsn's user avatar

bdkhsnbdkhsn

331 gold badge1 silver badge4 bronze badges

4

CHeck for another error in the event log that is time-correlated to this one. Basically — this one is from the service manager. The SQL Server service should have written another error (either into th event log or the errorlog) that contains the internal error that happened. THis error is generic from the serivce manager and as such totally irrelevant to debugging. It also is well known — google for «Sql server 17058» finds tons of references.

It seems to be a permission error:

http://www.it-sideways.com/2012/11/mssql-startup-error-code-17058.html

points to

«Could not open error log file ». Operating system error = 3 (The system cannot find the path specified.).»

which would be an operating system level configuration or insallation issue.

answered Dec 23, 2013 at 11:27

TomTom's user avatar

TomTomTomTom

4,6141 gold badge15 silver badges19 bronze badges

1

Yes. You could check that you have all paths configured correctly in this service properties in SQL Server Configuration Manager or Services. This is tab called Startup parameters.

answered Dec 23, 2013 at 13:13

Kuba Miazek's user avatar

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

  • Question

  • hi

    I am intalling SQL 2008 standard with SP1 on a Windows Server 2003 R2 SP2.

    I installed as  «local service account» for MSSQLServer (SQL database engine) and SQL agent.

    But I want to change to «service account» as [domainsvc_XXX] for MSSQLserver and SQL agent.

    I add the [domainsvc_XXX]  in local security policy — «Log as a service»

    and also add in SSMS — Security — New Login (windows authentication.

    When I started the MSSQLserver and SQL agent using the [domainsvc_XXX], I got an error 17058.  Initerrlog: could not open error log file.»  Operating system error=3 (The system cannot find the path specified).

    I don’t know where else to look at..

    Also, how do I find the cumulative service pack for SQL server 2008 standard?

    thanks

    Irene

Источник

SQL error 17058 occurs due to various reasons that include insufficient privileges, corrupted log files, an issue with network policies, and permission issues.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and see how to fix it.

Different causes and fixes for the SQL error 17058

Let us take a look at the different reasons for this error to occur. Also, we shall see its respective fixes.

1. Cause: Insufficient privilege of SQL Server Service Account in the Log directory

Solution:

  • First, start the SQL Server Configuration Manager.
  • From the left menu options, click to select ‘SQL Server Services’.
  • Then from the right panel, right-click on ‘SQL Server (MSSQLSERVER)’ and click ‘Properties’. Here, choose the correct service.
  • Click on the ‘Startup Parameters’ tab and note the location after -e parameter.
  • Browse for the Log location.
  • Now right-click on the “Log” folder and click Properties and then access the “Security” tab.
  • Now, verify the SQL Server service account permission of this folder and give proper access to this folder.
  • Finally, restart the SQL Server service.
  • In case, if you face the same error again, then try to change highly privileged service account like “Local System”.

2. Cause: Corrupted log file

Solution:

In order to fix the corrupted log file, rename the existing log file. Renaming will generate a new log file.

3. Cause: Issue with network policies which restrict access to the server

Solution:

Add a correct network policy. Here are the steps for doing the same:

First, open the NPS console, and double-click on Policies.

Right-click Network Policies, and click New in the console tree. Now a new Network Policy wizard opens.

You can now use the New Network Policy wizard to create a policy.

4. Cause: Permission problem for the logon account

Solution:

In order to fix this error, we need to fix the permission issue. Here are the steps to change the permissions.

Access Admin Tools >> Services

Now click on each SQL Service and change the Log On as credentials. change them to Local System Account and Allow service to interact with Desktop.

[Need any assistance in fixing SQL errors? – We’ll help you]

Conclusion

In short, this error occurs due to various reasons that include insufficient privileges, corrupted log files, the issue with network policies, and permission issues. Today, we saw the different causes and their fixes to this error.

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

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

Не удалось запустить службу SQL Server на Локальный компьютер. Подробности содержатся в журнале системных событий. Если эта служба разработана не в Майкрософт, обратитесь к разработчику службы, и сообщите специфический для этой службы код ошибки…:

Код ошибки 13

Решение:

При появлении данной ошибки необходимо зайти в Пуск → Microsoft SQL Server → Средства настройки → Диспетчер конфигурации SQL Server / SQL ServerConfiguration Manager → Конфигурация сети SQL Server → Протоколы для SQLEXPRESS и проверить, включены ли протоколы (все протоколы должны быть включены).

Код ошибки 1814

Вариант ошибки на английском:
Windows could not start the SQL Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code — 1814.

Причина: Ошибка возникает, когда по какой-то причине путь к файлам базы по умолчанию не соответствует действительному.

Решение:
Возможно в папке C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLDATA нет необходимых файлов. Необходимо добавить с заменой файлы из папки C:Program FilesMicrosoft SQL ServerMSSQL10_50.SQLEXPRESSMSSQLTemplateData.

Код ошибки 3417

Решение:

Перед заменой файлов рекомендуется сохранить копию папки Data в отдельной директории.

Cкопировать данные из C:Program FilesMicrosoft SQL ServerMSSQLXXXMSSQLTemplate Data в C:Program FilesMicrosoft SQL ServerMSSQLXXXMSSQLDATA

Для 64-разрядных систем — C:Program Files (x86)Microsoft SQL ServerMSSQLXXXMSSQLTemplate Data в C:Program Files (x86)Microsoft SQL ServerMSSQLXXXMSSQLDATA

Если замена файлов не помогла, необходимо дать права на папку Microsoft SQL Server.

Код ошибки 17058

Решение:

Необходимо дать полные права на папки C:Program FilesMicrosoft SQL Server и C:Program Files (x86)Microsoft SQL Server. Если данное решение не поможет — в свойствах службы на вкладке Вход в систему поставьте флаг С системной учетной записью.

Код ошибки 17113

Решение:

Перед заменой файлов рекомендуется сохранить копию папки Data в отдельной директории.

Cкопировать данные из C:Program FilesMicrosoft SQL ServerMSSQLXXXMSSQLTemplate Data в C:Program FilesMicrosoft SQL ServerMSSQLXXXMSSQLDATA

Источник

I got an error when I try to start the SQL Server service and the error message suggest me to analyze event log for further details, after I have analyzed found the following details in the event 17058.

Log Name:      Application
Source:        MSSQLSERVER
Event ID:      17058
Task Category: Server
Level:         Error
Description:
initerrlog: Could not open error log file ''. Operating system error = 3(The system cannot find the path specified.).

Cause:

This error occurs due to the insufficient privilege of SQL Service Service Account in the Log directory : C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLog

Troubleshooting and Fix:

1. Start SQL Server Configuration manager.

2. Click to select ‘SQL Server Services’ from the left menu options.

3. On the right panel, right click on ‘SQL Server (MSSQLSERVER)’ and click ‘Properties’.

4. Click ‘Advanced’ tab.

5. Scroll down and copy the value stored in ‘Startup Parameters’ and paste it on textfile. It will be something like this :

-dC:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATAmaster.mdf;-eC:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG;-lC:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATAmastlog.ldf

Event 17058 - initerrlog: Could not open error log file (SQL Server)

6. Browse the Log location “C:Program FilesMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLLog”.

7. Right click on the folder “Log” and click Properties and then to visit to “Security” tab. Now, check SQL Server service account permission on this folder and give proper access to this folder.

8. Now, Restart the SQL Server service. if you face the same error again, try to change highly privileged service account like “Local System”.

Thanks,

Morgan
Software Developer

Источник

[Solved-2 Solutions] Event 17058 — initerrlog: Could not Open Error Log File

Error Description:

  • There is no ERRORLOG file and SQL is not getting started.
Log Name: Application
Source: MSSQLSERVER
Event ID: 17058
Task Category: Server
Level: Error
Description:
initerrlog: Could not open error log file ”. Operating system error = 3(The system cannot find the path specified.).
click below button to copy the code. By — sql tutorial — team

Solution 1:

  • Check the -e startup parameter for your SQL Server error log. Verify that the path mentioned for the -e parameter exists. Also check if the SQL Service account has read/write-rights on this path.

Solution 2:

  • Start SQL Server Configuration manager.
  • Click to select ‘SQL Server Services’ from the left menu options.
  • On the right panel, right click on ‘SQL Server (MSSQLSERVER)’ and click ‘Properties’. You may want to choose correct service.

initer

Learn sql — sql tutorial — initer — sql examples — sql programs

  • Note the location after -e parameter.
  • Browse the Log location ” E:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVER MSSQLLog”.
  • Right click on the folder “Log” and click Properties and then to visit to “Security” tab. Now, check SQL Server service account permission on this folder and give proper access to this folder.
  • Now, Restart the SQL Server service. If you face the same error again, try to change highly privileged service account like “Local System”.

Источник

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

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

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

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Ошибка ssl альфа банк что это
  • Ошибка spi на котле аристон

    • ➤