Re: unable to start SQL Service ... error code 3417
- From: Tom R <TomR@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Aug 2009 10:47:01 -0700
How about just create a new instance and restore databases to the new instance?
--
TR
"Tibor Karaszi" wrote:
Yes, judging from that error message, your master isn't healthy. I would first do root cause.
analysis, trying to determine what caused this in the first place.
I wouldn't go with restoring master from another instance. You have to be careful with collations,
and whatnot (I haven't done that myself, so I can't comment on whatever things need to be taken care
of).
The supported route is to rebuild your master database, start SQL Server in single user mode,
restore a backup from this master database, and then restore msdn and if needed model (since you did
a rebuild). Search and you will find plenty of instructions on this. If you don't have a backup of
your master (etc) then you are in for more work after the rebuild (re-creating whatever got lost
from the rebuild).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tom R" <TomR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DEE6C344-80BF-4D56-BE75-642E795D52B0@xxxxxxxxxxxxxxxx
If the Master database is corrupt, how would you advise I maybe replace with
another Master? ... I do have another Master as I have another instance of
SQL running for the Outlook Business Conact Manager ... suppose I can back
this up and then restore? ... will try.
--
TR
"Tibor Karaszi" wrote:
File system compressed. Check in Windows explorer (can be configured
to show compressed files in blue). Here's the error text for 3417:
"SQL Server cannot start the master database. If the master or tempdb
cannot be brought online, SQL Server cannot run. This error is usually
preceded by other errors. Review error logs to find the root cause."
I suggest you check the SQL Server errorlog file and from that try to
determine what is the root cause.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tom R" <TomR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1A5E2C84-6666-4445-8958-393024A3FC3C@xxxxxxxxxxxxxxxx
I am not sure I follow when you say compressed. Do you mean zipped?
If not,
how do I determine if they are compressed? I have not compressed
any sql
folders ... that I know of.
--
TR
"Sylvain Lafontaine" wrote:
I like it when a technician makes changes to your system without
telling you
what he's doing. In your case, the first thing to do would
probably be to
make a backup of the MDF and LDF files for the databases.
The sql service won't start if either the Sql-Server folder or the
data file
folders is compressed. If you have (or the technician have) done
so then
uncompress them. For other possible solutions, see
http://decoding.wordpress.com/2008/08/25/sql-server-2005-expess-how-to-fix-error-3417/ .
If nothing work, you might have to remove/reinstall SQL-Server.
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam
please)
Independent consultant and remote programming for Access and
SQL-Server
(French)
"Tom R" <TomR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B62998FC-DAC6-4C13-8312-A226BBCEFF76@xxxxxxxxxxxxxxxx
I recently had an issue with being able to log into my Windows XPS
Vista
Ultimate notebook. I contacted Dell Support who helped me
rectify the
problem. The technician then asked if he could log into my pc to
fix this
problem ... I allowed him to do this via Dell Remote Assistant
(uninstalled
software after service call). When he logged in, He deleted
files in an
area
that looked like they might be somewhere in the Windows
directory. It
could
be just a coincidence, but now I am unable to get my MSSQLSERVER
service
started. I think it is possibly a coincidence because as I
research the
error message below, I see this has happened to others, where the
service
suddenly would not start. I have done a system retore fyi.
Regardless, I
desperately need a solution to this problem ... the error message
I
receive
when I attempt to start the service is
Windows could not start the SQL Server (MSSQLSERVER) on local
Computer.
For
more information, review the System Event Log. If this is a
non-Microsoft
service, contact the sservice vendor, and refer to
service-specific error
code 3417.
Any assistance and/or advice would be much appreciated.
--
TR
- Follow-Ups:
- Re: unable to start SQL Service ... error code 3417
- From: Tibor Karaszi
- Re: unable to start SQL Service ... error code 3417
- References:
- unable to start SQL Service ... error code 3417
- From: Tom R
- Re: unable to start SQL Service ... error code 3417
- From: Sylvain Lafontaine
- Re: unable to start SQL Service ... error code 3417
- From: Tom R
- Re: unable to start SQL Service ... error code 3417
- From: Tibor Karaszi
- Re: unable to start SQL Service ... error code 3417
- From: Tom R
- Re: unable to start SQL Service ... error code 3417
- From: Tibor Karaszi
- unable to start SQL Service ... error code 3417
- Prev by Date: Re: Recovery from Missing Tempdb Log File/Drive
- Next by Date: Installing Adventure Works sample databases - need help
- Previous by thread: Re: unable to start SQL Service ... error code 3417
- Next by thread: Re: unable to start SQL Service ... error code 3417
- Index(es):
Relevant Pages
|
Loading