“Error 17058” starting SQL Server (MSSQLSRVER) service on SharePoint Server

Asked By 20 points N/A Posted on -
qa-featured

Hi,

We are upgrading from MOSS 2007 to SharePoint 2010. I have made a SharePoint 2010 development server. All SharePoint elements are available on this server. As like SharePoint 2010, MSSQL Enterprise is also installed here. I have added “attach database”, copy of a database, from our MOSS 2007 environment.

All was functioning well. It was as a template used in an ESXVM ware environment for a series of developer SharePoint. The server was exactly the type that we want, so we made a template of the original server and for future use we made a new virtual server from the template along with a different server name. But it didn’t respond. I work with STSADM-o re-name server and worked fine. Now what is happening is that SQL Server (MSSQLSERVER) services will not respond. The error message in the event log is like the following:

The SQL Server (MSSQLSERVER) service terminated with service-specific error %%17058.

I have made a tour at c:/ProgramFiles/Microsoft SQL via command prompt.

Servermssql10_50.mssqlservermssqlbinn.

I also try the command "sqlserver.exe/c".  Then I found the following error:

2011-11-07 09:52:14.49 Server      Error: 17058, Severity: 16, State: 1.

2011-11-07 09:52:14.49 Server      initerrlog: Could not open error log file 'E:MSSQL10_50.MSSQLSERVERMSSQLLogERRORLOG'. Operating system error = 5(Access is denied.).

I am using a local administrator account. Can anyone give me an idea where I can start from? For the need of upgrading to SharePoint 2010, we need to make this individual SharePoint environment. May be we have to change some of our web parts?

Thanks in advance.

SHARE
Best Answer by Tony clever
Best Answer
Best Answer
Answered By 20 points N/A #96426

“Error 17058” starting SQL Server (MSSQLSRVER) service on SharePoint Server

qa-featured

Hi friend,

The SQL Server (MSSQLSERVER) service terminated with service-specific error” this error happens for me many times. I solved this problem by this ways.

1. First I installed SQL server 2008 manually not from autoplay. For this right click on setup file and click run as administrator.

2. If you open browser it will show nothing for the first time. Then I opened SSMS but it was also blank. Then I wrote instanceservername manually.

3. This time I got access. Then I created new database.By doing this I got access MSSQL Enterprise.

If this process is successful then you can also include attach database” as a copy of current database. You can also find some tutorial for this on here msdn.microsoft.com/en-us/library/ms170208.aspx

Answered By 10 points N/A #96427

“Error 17058” starting SQL Server (MSSQLSRVER) service on SharePoint Server

qa-featured

Hello Emi,

You will need to ensure that your app pool account has got access to the SQL server as well as the databases. What you are getting could be a permission issue, and therefore you can go ahead and change it into one of domain administrators to do a test.

It will be better if you attach database migration or move all databases way to do it for when you change server name a lot of potential issues will be caused.

Also, you can check out the SQL server error log file to get more details about the cause of the error. You can look in to C:Program FilesMicrosoft SQL ServerMSSQL10.MSSQLSERVERMSSQLLogerrorlog.

Regards,

Carl

 

Related Questions