SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Error 17058 when trying to start MSSQLSERVER service


Error 17058 when trying to start MSSQLSERVER service

Author
Message
luissantos
luissantos
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6051 Visits: 1016
Hello comunity

After running the setup of sql server 2008 on my HP server with OS Windows server 2008 R2 standard 64 bits,
the setup return errors failed on theses services:
-Database engine services
-Sql Server Replication
-Full text search
-Reporting Services
When i try to start MSSQLSERVER, i receive the following error :

event ID 17058
initerrlog: Could not open error log file ''. Operating system error = 3(failed to retrieve text for this error. Reason: 15105).

Curiously, the installation on : C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\
have only create theses folders : binn, install and upgrade
and also these files:
-sql_engine_core_inst_keyfile.dll
-sql_fulltext_keyfile.dll

Could someone give me some help , because is the first time that i have this problem and i don´t know how to solve them.

Many thanks and best regards
Luis Santos



luissantos
luissantos
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6051 Visits: 1016
Hello comunity

I solve this problem and for those person that have the same one would should install sql server 2008 not by the autorun option, but you must with right click select : Open and Run setup as administrator.

Also, if you open SSMS and you try to browse server name and nothing appears, you need just to write
the correct server name or instance\servername.

I hope this conclusion help other users with this kind of situation.

Best regards.
Luis Santosw00t



julian.hatwell
julian.hatwell
SSC Veteran
SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)

Group: General Forum Members
Points: 237 Visits: 21
Hello folks - I have a similar problem with my box. This was working fine before the weekend.

The server is a VM, sharing a drive with a number of other VM's. We had a major windows update pack applied on Saturday. 100's of patches that had not been applied for a few months. This filled up the physical disc where the servers were running and they all shut down unexpectedly.

We freed up some disc space and restarted the OS, but SQL server services did not start up. Trying to restart them manually gives me this message in the even log:

A file activation error occurred. The physical file name 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\mssqlsystemresource.ldf' may be incorrect. Diagnose and correct additional errors, and retry the operation.

Trying to start SQL server from cmd: sqlservr -T3608 gives the following message multiple times:

Error: 17058, Severty: 16, State: 1.
initerrlog Could not open error log file ''.
Operating system error = 3(failed to retrieve text for this error. Reason 15105).

I have checked and the file exists at: 'E:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\mssqlsystemresource.ldf' so not sure what I can do about that.

Can anyone help?
julian.hatwell
julian.hatwell
SSC Veteran
SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)SSC Veteran (237 reputation)

Group: General Forum Members
Points: 237 Visits: 21
If anyone should follow this up - I found a clue in my trusty Wrox Press SQL Server Admin book "The resource database is only written to during installation or applying a service pack."

Given my issue happened right after a service pack was applied and we had an unexpected shutdown, I thought the best thing was to re-apply the service pack. This fixed the problem.
jpipia
jpipia
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 13
I am getting the exact same error. It seems out of the blue though since I didn't apply any service packs. The only thing I can think of that changed was a bunch of Windows updates a while ago.
The .ldf file is there. Anyone know how I can get it fixed?
Thanks
Judy McNeil
Bipsy
Bipsy
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1945 Visits: 467
Your installation is not fully completed.

try repairing your installation or remove all sql components , reboot your machine and try to install it again.
jpipia
jpipia
SSC-Enthusiastic
SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)SSC-Enthusiastic (150 reputation)

Group: General Forum Members
Points: 150 Visits: 13
Thanks. I will try to repair with the CD. The thing is, the installation has been completed and working for over a year.
It is just a development instalation and no one is counting on it at the moment. I just get nervous when things seem to break for no reason. I like to know the reason.
michael_gm
michael_gm
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 42
this is a permission problem!... you must try access the log with the user is running sql server.... orrrr.....only for testing... try adding the user is running sqlserver as admin and you'll notice that you may start the service....

Michael Guerra.
mxhxr
mxhxr
Old Hand
Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)Old Hand (399 reputation)

Group: General Forum Members
Points: 399 Visits: 311
It's a permissions problem.

To verify that's the case in your scenario, give the user that you are running the SQL Server service under administrative rights on the SQL Server machine. Then try to start the service. If it succeeds, you can then start to chip away at the rights to an acceptable point. But try this prior to reinstalling SQL Server or any of the other drastic measures mentioned prior.



j.noruzi
j.noruzi
SSC-Enthusiastic
SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)SSC-Enthusiastic (105 reputation)

Group: General Forum Members
Points: 105 Visits: 1
Hello guys.
I had the same problem.
my problem occurred when i change start-up parameters for sql server 2008r2 service. i had a mistake when changed that parameters.
Mistake => i forgotten putting ";" (semicolon) between each parameter. i corrected this mistake so problem solved.

this is Correct Start-up Parameters :

-dC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG;-lC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search