[Help] Problem on starting SQL Server

Question

Hi, i have installed SQL SERVER EXPRESS 2008 and when i try to start it, i get the following error:

 

Code Snippet

SQL Server Configuration Manager
The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details.

 

 

From Windows Event Log:

Code Snippet

FileMgr::StartLogFiles: Operating system error 2(File not found) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.

 

 

The path for the MSDBLog.ldf file is wrong because i don't have any E: drive in my Windows. [Where the *** it got this path from? (can u explain MS?)]

I have no idea on how to fix that path!

 

From log file:

Code Snippet

2008-09-21 04:17:51.93 spid10s     Starting up database 'model'.
2008-09-21 04:17:52.00 spid10s     Error: 17204, Severity: 16, State: 1.
2008-09-21 04:17:52.00 spid10s     FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(file not found.).
2008-09-21 04:17:52.03 spid10s     Error: 5120, Severity: 16, State: 101.
2008-09-21 04:17:52.03 spid10s     Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(file not found.)".
2008-09-21 04:17:52.14 spid10s     Error: 17207, Severity: 16, State: 1.
2008-09-21 04:17:52.14 spid10s     FileMgr::StartLogFiles: Operating system error 2(file not found.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2008-09-21 04:17:52.17 spid10s     File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2008-09-21 04:17:52.20 spid10s     Error: 945, Severity: 14, State: 2.
2008-09-21 04:17:52.20 spid10s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2008-09-21 04:17:52.20 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2008-09-21 04:17:52.26 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2008-09-21 04:17:52.26 spid7s      Server name is 'ADMIN\SQLEXPRESS'. This is an informational message only. No user action is required.

 

 

Seems to be the same problem. How to change that path to the correct one?

Answer 1

You can change the startup parameters (path\files) when you right click on the service in Configuration Manager.

 

However, uninstall and reinstall probably the way to go in your case.

 

Let us know if helpful.

---

---

Kalman Toth Database & OLAP Architect
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2016

Answer 2

 

I have reinstalled it as you said and now it's working fine. But, what is the explanation for the problem? Or we need to install SQL Server 2 times to get it working?

Thanks for your help!

Answer 3

There are many unresolved mysteries in Computer Science.

 

A good chunk of them can be fixed with reboot or reinstall.

 

 

Answer 4

I've got the same problem and reinstall doesn't solve it.  If you look at the error log, it is able to open the MASTER database but fails on MODEL and MSDB.  Since this mysterious E:\ drive is not in the Registry, I am guessing it is inside the MASTER database.

 

So how can I fix my MASTER to correctly point to the other databases?

Answer 5

This is not the solution to the problem. I encountered this exact problem on a clean install of SQL Server 2008 Enterprise. This error arose on both the model and tempdb paths. There is no option to change the path to either model or tempdb in Configuration Manager. You can't change the path to tempdb if the engine is not running and the engine won't start without a tempdb. I didn't delve into model as I got hooked up on tempdb.

 

The installer completely ignored the path that it was given for model (as part of the system databases path) and tempdb and chose the apparently hard coded path on the non-existent E: drive.

 

I have uninstalled and re-installed twice with the same result. I am going to take a more structured approach to detecting a way around this:

 

1. Install SQL Server 2008 with its default paths and change them later once the engine is running. This assumes that submitting non-default paths to the installer causes the problem.

 

2. Install SQL Server 2000 Enterprise and upgrade. This assumes that the upgrade will happily accept the existing paths to engine objects.

 

The installer has some bugs that are obviously going to take a while to sort out (if, in fact, any effort is being made in this direction). I did a cluster installation two days ago and the first node installed perfectly. The second node installation proceeded according to plan right up to the point at the very end where the installer detected that the Windows Server 2003 Hotfix had not been installed on the node. This was despite the fact that the installer had tried to install the hotfix up-front and this appeared to have succeeded (I'd had to restart the node for it). Very irritating and a monumental waste of time. I ended up downloading the hotfix and installing it separately. When I re-initiated the SQL installer, it bombed out because it did not like the product key, which it had quite happily accepted on the first run through. Fortunately, the workaround for this is documented elsewhere (delete the config file and manually enter the product key).

 

Now, it seems, the installer arbitrarily ignores path names given to it in non-clustered installations.

 

Gary

Answer 6

This was my 4th install attempt.  At least now that I have the 223MB install .exe on my machine it only takes 30-40 minutes of my life to try things.  I tried putting the data on my D:\ partition, but this didn't seem to help.  Good luck.  Let me know if this works for you.  If you're clustering, you're a bit more advanced than I am!

 

Since I really just want to play with SQL Server and .ASP/.NET, maybe I should try Express 2005?

Answer 7

Unfortunately, approach 1 failed. The engine still tries to access this:

e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf

 

I made no changes to the default installation settings.

 

Now I'm going to uninstall (yet again... how frustrating) and try upgrading a SQL Server 2000 or 2005 installation.

 

As for Express 2005, I have no experience of it. If you have the time (and have no other option), you could try an installation of Express 2005 and then, if it installs correctly, upgrade it to 2008 (but make sure it's a valid upgrade path... I haven't checked that). There are sufficient similarities between 2005 and 2008 that 2005 will give you a good platform to play with.

 

Gary

Answer 8

 

OK, here's a thing. I thought I would tool around a bit before I went down the nauseating path of uninstalling 2008, installing 2000 and upgrading. I created a folder E:\sql10_main_t\sql\mkmaster\databases\objfre\i386 and copied the MSDB and Model database files into it from C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA where the installer correctly put them (I was surprised to find). Tempdb was created in here too.

 

I rebooted the server and MSSQLSERVER service started correctly with no complaints. Now I have the issue of moving these system databases back to a sensible location, but at least the engine is running.

 

Gary

Answer 9

It never seems to end. The engine won't authenticate any logins (Windows or SQL). I have more probing to do.

Answer 10

So. I changed the startup parameters to point to this E: drive directory and copied the master DB data and log files into it. The engine started nicely... still could not log in. There is a discussion elsewhere in this forum where somebody asked about not being able to log in to a newly installed instance of SQL Server 2008, but it is unanswered. Brother, is this stuff broken or what?

 

Next, I promoted the server to a DC. SQL Server started OK... still unable to login (using either Windows or SQL Server authentication).

 

Now I'm going to try my method 2. I've uninstalled 2008 again (boooorrrriiinnngggg). I'll install SQL Server 2000 Ent and upgrade it. Wish me luck!

 

Gary

 

Answer 11

Well, I wiped it all out and installed 2005 Express and MSEE and it is up and running...even with my data on a different partition.  I am not sure I want to risk breaking it by upgrading to 2008 Express.  Maybe in a week or so when I have some free time.

Answer 12

Finally. Strategy 2 worked. Upgrade went without a hitch. Unfortunately I have to add the services not provided by 2000 separately, such as Reporting Services, but at least I can connect and log in to the server.

 

Gary

 

Answer 13

I've been getting the exact same problem.  I originally created a new DB instance on my D: drive but that failed and I took note of some of the above suggestions.  I have since uninstalled SQL 2008 Express and resinstalled using just the DEFAULT settings (ie. C: drive, SQLEXPRESS instance name, etc) and I still get the same exact error shown below:

2009-01-08 11:11:05.85 spid10s     Error: 17204, Severity: 16, State: 1.
2009-01-08 11:11:05.85 spid10s     FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 87(The parameter is incorrect.).
2009-01-08 11:11:05.89 spid10s     Error: 5120, Severity: 16, State: 101.
2009-01-08 11:11:05.89 spid10s     Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 87: "87(The parameter is incorrect.)".
2009-01-08 11:11:05.92 spid10s     Error: 17207, Severity: 16, State: 1.
2009-01-08 11:11:05.92 spid10s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2009-01-08 11:11:05.92 spid10s     File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2009-01-08 11:11:05.93 spid10s     Error: 945, Severity: 14, State: 2.
2009-01-08 11:11:05.93 spid10s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2009-01-08 11:11:05.93 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-01-08 11:11:05.96 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.


Time to check out what free offerings Oracle provides.  Microsoft really needs to fix this, as I'm a Visual Studio user and was counting on a tight integration between that and SQL Server. 

Answer 14

I encountered the same situation with the error message of not having the file at e:\sql10_main_t\sql\mkmastr\databases...........

and worst part is i DO NOT HAVE e drive on my server. :))). Microsoft rocks here now.

Now, i cannot even create the folders on my "E" drive which SQL Engine recognize during and after the installation and get it started and then move the files to the actual location.

Any clue on this problem is appreciated.  

 - Prashant Thakwani

 

 

Answer 15

I just wanted to bump this thread and say I am consistently seeing this problem as well.  I have three systems I am testing this on:
1. Fresh Windows XP
2. Server 2003 with a security lock down based on Federal Core Configuration Standards
3. Fresh Vista 32 Air Force Standard Desktop Configuration

I have no problems with the install on system #1, however #2 and #3 consistently fail after install when trying to start the SQL service.  Since the failing systems are the ones that have the tightest security, I am guessing this is a security issue.  However, I have tried giving full control to everyone on the SQL directory and added the local system account to a group with full control over the SQL directory.  For simplicity, I set up the SQL service to run as the local system account. 

My attempts at opening up the security haven't worked and it is frustrating that the only error information I get from SQL Server 2008 is an obvious developer path that provides me with no information to start from.  I am in no way a SQL expert, but I shouldn't have to be to install an Express version of SQL Server. 

SEE NEXT POST FOR FIX

Answer 16

So, it looks like this strange path occurs when the install doesn't complete successfully.  In my case, the cause was a group policy setting that was disabling debug.  I had to add the user that installs SQL Server 2008 Express to the group policy allowing Debug and that allowed the install to finish completely and successfully. 

The group policy item is:
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug

I found the fix in this thread:
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/ed4514fa-8d1d-4383-bbdf-fb06bfbad106/

Answer 17

For whatever reason (the debug permissions thing doesn't work) this is preventing me from installing on a 1and1 VPS.  Reinstalled 3+ times on two fresh images.  So, if you're on 1and1, don't bother reinstalling because this s*t isn't working.

Gonna try editing the master db.  I'm so frigging happy about this.

Answer 18

Warren,  I know its been a while but I just encountered this same exact problem.  I relocated the MSDB and Model databases as you did and the engine finally started.  I too was unable to login as the sa account I configured and any network account.  So, as a shot in the dark I just tried using a blank password for the sa account and voila, I'm in. 

Answer 19

Same problems as everybody else but nothing hear fixed the problem for me.    On another site I saw a link to an MSDN posting about rebuilding the system databases from the command line.    Once I did that I was able to start up the server.    The link is:

http://msdn.microsoft.com/en-us/library/dd207003.aspx

Basically I ran this command:

Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts /[ SAPWD= StrongPassword ]

from this directory:

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release

Good Luck!     btw, not too impressed with Microsoft at this point...   jeez!   

Answer 20

Same problems as everybody else but nothing hear fixed the problem for me.    On another site I saw a link to an MSDN posting about rebuilding the system databases from the command line.    Once I did that I was able to start up the server.    The link is:

http://msdn.microsoft.com/en-us/library/dd207003.aspx

Basically I ran this command:

Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts /[ SAPWD= StrongPassword ]

from this directory:

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release

Good Luck!     btw, not too impressed with Microsoft at this point...   jeez!   

Hi all,

I am getting the same issue. Its appears to be certainly an issue with the SQL 2008 installer. We install SQL 2008 SP1 as part of our product to XP - Windows 7, server 2003 - server 2008 without issues. (both x86 and x64)

No space issues, same hardware etc as all other successfull SQL 2008 Express SP1 installs ONLY difference is Server 2008 R2!!!!

Note: Our SQL 2005 Express SP3 installation is "successful" on the server 2008 R2 platform!

NOTE: this system does not have an e:\ drive!!!!!
"Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf"


This SAME installer when applied to a fresh Server 2008 R2 system on EXACTLY the same hardware as all other successful installs, fails with the following:

2009-12-22 10:12:05.11 Server      Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
    Mar 29 2009 10:11:52
    Copyright (c) 1988-2008 Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

2009-12-22 10:12:05.20 Server      (c) 2005 Microsoft Corporation.
2009-12-22 10:12:05.20 Server      All rights reserved.
2009-12-22 10:12:05.20 Server      Server process ID is 1080.
2009-12-22 10:12:05.25 Server      System Manufacturer: 'Dell Inc.', System Model: 'Vostro1510'.
2009-12-22 10:12:05.25 Server      Authentication mode is MIXED.
2009-12-22 10:12:05.26 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.MYINSTANCE\MSSQL\Log\ERRORLOG'.
2009-12-22 10:12:05.30 Server      This instance of SQL Server last reported using a process ID of 360 at 22/12/2009 10:08:11 AM (local) 21/12/2009 11:08:11 PM (UTC). This is an informational message only; no user action is required.
2009-12-22 10:12:05.30 Server      Registry startup parameters:
     -d c:\Program Files\Microsoft SQL Server\MSSQL10.MYINSTANCE\MSSQL\DATA\master.mdf
     -e c:\Program Files\Microsoft SQL Server\MSSQL10.MYINSTANCE\MSSQL\Log\ERRORLOG
     -l c:\Program Files\Microsoft SQL Server\MSSQL10.MYINSTANCE\MSSQL\DATA\mastlog.ldf
2009-12-22 10:12:05.50 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-12-22 10:12:05.50 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-12-22 10:12:07.39 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2009-12-22 10:12:09.25 Server      Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-12-22 10:12:10.32 spid7s      Starting up database 'master'.
2009-12-22 10:12:12.19 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MYINSTANCE'.
2009-12-22 10:12:13.27 spid7s      SQL Trace ID 1 was started by login "sa".
2009-12-22 10:12:13.52 spid7s      Starting up database 'mssqlsystemresource'.
2009-12-22 10:12:13.56 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2009-12-22 10:12:14.48 spid7s      Server name is 'WIN-869398VN1VJ\MYINSTANCE'. This is an informational message only. No user action is required.
2009-12-22 10:12:14.57 spid10s     Starting up database 'model'.
2009-12-22 10:12:14.59 spid7s      Informational: No full-text supported languages found.
2009-12-22 10:12:14.59 spid7s      Starting up database 'msdb'.
2009-12-22 10:12:15.42 spid10s     Error: 17204, Severity: 16, State: 1.
2009-12-22 10:12:15.42 spid10s     FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(failed to retrieve text for this error. Reason: 15100).
2009-12-22 10:12:15.82 spid7s      Error: 17204, Severity: 16, State: 1.
2009-12-22 10:12:15.82 spid7s      FCB::Open failed: Could not open file e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(failed to retrieve text for this error. Reason: 15105).
2009-12-22 10:12:15.90 spid10s     Error: 5120, Severity: 16, State: 101.
2009-12-22 10:12:15.90 spid10s     Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(failed to retrieve text for this error. Reason: 15105)".
2009-12-22 10:12:16.56 Server      A self-generated certificate was successfully loaded for encryption.
2009-12-22 10:12:16.76 Server      Server is listening on [ 'any' <ipv6> 49156].
2009-12-22 10:12:16.76 Server      Server is listening on [ 'any' <ipv4> 49156].
2009-12-22 10:12:16.84 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MYINSTANCE ].
2009-12-22 10:12:16.84 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$MYINSTANCE\sql\query ].
2009-12-22 10:12:16.88 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2009-12-22 10:12:16.95 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2009-12-22 10:12:16.95 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-12-22 10:12:17.26 spid7s      Error: 5120, Severity: 16, State: 101.
2009-12-22 10:12:17.26 spid7s      Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(failed to retrieve text for this error. Reason: 15105)".
2009-12-22 10:12:17.29 spid7s      Error: 17207, Severity: 16, State: 1.
2009-12-22 10:12:17.29 spid7s      FileMgr::StartLogFiles: Operating system error 2(failed to retrieve text for this error. Reason: 15105) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2009-12-22 10:12:17.30 spid10s     Error: 17207, Severity: 16, State: 1.
2009-12-22 10:12:17.30 spid10s     FileMgr::StartLogFiles: Operating system error 2(failed to retrieve text for this error. Reason: 15105) occurred while creating or opening file 'e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2009-12-22 10:12:17.36 spid7s      File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2009-12-22 10:12:17.50 spid10s     File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2009-12-22 10:12:17.51 spid10s     Error: 945, Severity: 14, State: 2.
2009-12-22 10:12:17.51 spid10s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2009-12-22 10:12:17.73 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-12-22 10:12:17.73 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.


Has anyone got any answers?
Hello Microsoft .....?????

---

Regards theVman

Answer 21

Thanks, Tommy, this worked perfectly for me!  From the directory you mentioned above:

Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=<myinstancename> /SQLSYSADMINACCOUNTS=<myusername>

I replaced <myinstancename> and <myusername> with real values for my system.  Didn't need the "[ SAPWD= StrongPassword ]" since I am using windows auth.  I also used the link you proposed to get more details.

Background:  I am running XP with latest service packs.  I used to have a working SQL Server 2000 install with a default and a named instance.  I installed 2008 Express to run side-by-side with the 2000 version.  But SSMS did not install and I could not figure out how to get it in there (followed lots of advice, to no avail).  So I uninstalled 2008 express and 2000 and re-installed 2008 Express which resulted in the e: drive problem discussed here.

After rebuilding the databases, I was able to start the service and connect to my instance thru SSMS.

Answer 22

This helped me a lot!!!

Thanks a lot

Answer 23

This worked for me too:

Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=domain\myname /SAPWD=StrongPassword

on windows 7 32 bit, and I am a member of domain and local admin

Prior to this i had:

1. installed with ALL defaults and plenty of space

2. Uninstalled, rebooted, reinstalled

3. re-booted

4. re-installed

5. un-installed and re-booted

6. prayed

7. animal sacrifice

8. etc

Thanks Tommy and Kevin

Answer 24

Hi, I also experienced this issue installing SQL 2008 EE 64-bit on Windows 2008 EE 64-bit. The only thing I was able to conclude, on my 4th un-install/re-install attempt, was that I had some permissions issues and the install took it's own course as a result (by attempting to install sytem db's in some 'hard-coded, non-existent' directory structure). I came upon this as I was looking for the system database files and couldn't access the folders without answering a prompt to 'Continue'. So before I attempted the 4th install I manually accessed each folder, answering the prompts to continue. After doing this the install worked. Colleen (great name, Warren T. Void)

---

DBA

Answer 25

I tried the solution suggested by TommyGrahn but could not get it to return successfully.  So I had to look further.  I kept receiving the following error:

Error result: -2068643838
Result facility code: 1203
Result error code: 2

And I was told to look in the summary.txt.  But none of this info actually helped me.  So I searched some more and found this link:

https://connect.microsoft.com/SQLServer/feedback/details/564905/rebuilding-system-databases-for-sql-server-2008-r2#

It suggests that you use the actual media setup rather than the bootstrap on your C: drive.  I changed the directory to my media (the SQL Server 2008 R2 Install Disc) and TommyGrahn's proposal worked.

Thanks Tommy and everyone else that submitted here.  I was this close to finding my cat.

Brent

---

B. Iverson Lead Engineer. We all live on this tiny blue marble...

Answer 26

This is issue happens after a failed installation. There is no single fix for this issue, because many problems can lead to a failed install, and this is the behavior of a partially installed SQL Server 2008.

To find the reason for the error, you must refer to your installation logs (C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log). Investigate the problem there, and reinstall SQL Server.

I had the same issue. I found that Summary.txt file says that my Installation failed. In error log file I found this:

'' is not a valid login, or you do not have permission.

And I knew that this happens when the computer name and the user name (user that is installing SQL Server) are the same. After changing the user name or the computer name and reinstalling the SQL Server, everything was fine.

Typically users will not encounter this problem because SQL Server setup program reports the error and will not complete successfully; and no one expects a failed install to work without error. In my case, SQL Server Express was installed with another application that was lazy to realize that the installation was not successful. It reported that everything installed correctly.

I hope that it helps other people to solve their problems.

Answer 27

This problem occurs when somehow the master and/or model and/or errorlog and/or tempdb files moved an other place than you installed them.

For example this could happen if you put a new physical drive instead of your damaged drive to your computer and the drive letter(s) not the same than before.

You can examine and change startup parameters from registry HKLM\SOFTWARE\[wow6432...]\Microsoft\MSSQLServer\MSSQLSEerver\Parameters or something like... and you can change the -d, -e and -l parameter values if it is necessary.

After you should start the SQL server from command prompt (sqlservr.exe -c) and you can see more detailed messages.

I can give you few solutions maybe you can use them:

1. The easy way if you create that drives where the SQL server looking for these files and you can create exactly the same folder structure what is needed for the SQL server and you can put these files to the right place. After it you can start the SQL server service and you can move these files in the official way (you can find it from KBs).

2. For example if you installed the SQL model and/or temp database to g: drive and now you don't have g: drive but your files are on the i: drive in the same folders you can use this command: "subst g: i:\". This will create a g: drive and link it to i:\ drive and path. After it you can start the SQL server and you can move databases in the official way :)

3. The tempdb path is written to every database. If you would like to change only the drive letter, maybe you can write a short C# code and you can change the drive letter directly in the master and other user database files (*.mdf). It works I just now did it and everything is fine :).

Just keep in your mind: these are NOT the official solutions so you can do it only on your responsibility!! Good luck! :)

---

Csaba Marosi

Answer 28

"Microsoft rocks here now."

Lol! These is why I hate Microsoft Products. I just need these products because of my work.

Answer 29

worked like a champ. You sir made my day (I was searching a solution like 5 hours)

Answer 30

It may be happened due to corrupt installation file.

Follow this steps to solve this issue:
1.Uninstall your SQL Server 2008 Express SP1
2.Download and install Microsoft .Net Framework 3.5 from:http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en
3.Download and install SQL Server 2008 Express SP1 from: http://www.microsoft.com/downloads/details.aspx?familyid=01AF61E6-2F63-4291-BCAD-FD500F6027FF&displaylang=en

For more information about how to uninstall an existing instance of SQL Server 2008: http://msdn.microsoft.com/en-us/library/ms143412.aspx

---

Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Answer 31

I needed a little bit more detailed information on how to solve this problem, however I am very Thankful to some others, namely the detailed input from: Pudge_DC (article below)
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4febbbb9-7cb4-4167-bfe7-194d60c7e5d7/database-service-will-not-start-because-it-is-using-the-wrong-path-to-find-the-resource-database?forum=sqlexpress

These are the errors from the Application Log in the Event Viewer for the following four files:

FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 21(The device is not ready.).
FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 21(The device is not ready.).

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.

I tried the 'Rebuild System Databases' (http://msdn.microsoft.com/en-us/library/dd207003.aspx), did not work.

I tried the steps in Pudge_DC post, but could not get them to work, However I had another working SQL Server 2008 R2 install, so I performed the following steps:

1. On the non-working SQL Server 2008 R2 install (The one generating the errors in the Application log) > I opened the ..\MSSQL\DATA folder > copied the master.mdf and mastlog.ldf files
2. On a working SQL Server install > I Stopped the SQL Server Service > opened the ..\MSSQL\DATA folder and moved the existing master.mdf and mastlog.ldf files into the ..\MSSQL\Backup folder.
3. Then I copied the master.mdf and mastlog.ldf files from the non-working SQL Server into ..\MSSQL\DATA folder on the working SQL Server.
4. Now I was able to follow the steps posted by Pudge_DC, which are:

=====
Started the Server via Command Line with: (Where SQLEXPRESS is the name of your SQL server)

NET START MSSQL$SQLEXPRESS /f /T3608

Logged into SQL with: (Where SQLEXPRESS is the name of your SQL server)

SQLCMD -S .\SQLEXPRESS

Checked my current settings with

SELECT database_id, name, physical_name FROM sys.master_files (NOTE: sure enough the four files named above were referencing the E:\ drive)

GO

Then updated all the file names with this: (where FULL FILEPATH is the file path for each file)

USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'modeldev'
 GO

 USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'modellog'
 GO

 USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'MSDBData'
 GO

 USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'MSDBLog'
 GO

 USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'tempdev'
 GO

 USE master
 GO
 UPDATE sys.master_files
 SET physical_name = 'FULL FILEPATH'
 WHERE name = 'templog'
 GO
=====

5. Stopped the SQL Server Service > copied the modified master.mdf and mastlog.ldf files back over into the ..\MSSQL\DATA folder on the non-working (Original) SQL Server.
6. Started the SQL Server Service normally and it started correctly.

On the working (Secondary) SQL Server, move your files back from the ..\MSSQL\Backup folder back to the ..\MSSQL\DATA folder and start the SQL Server Service back up, to wrap things up!

Thank God and thanks to all those that contributed to this solution, God Bless!

Answer 32

I have determined the absolute easiest answer.

To install MS SQL Express(most any recent version) on a domain controller, before installing your SQL instance (or after uninstalling the failed user instance), create a new domain account and password for you SQL instance to run under. When you get to the installation step where you set up services, make sure to specify that user account and password for the service name instead of the NT SERVICE account that is there.

Your installation will run successfully.

Answer 33

Hi all, I will now share my solution with you.

I did what TommyGrahn said but it did not work.

I uninstalled and deleted all files and folders the installation created and installed it, over and over again.

But always with same error result.

Finally I tried to start the sql service as Administrator instead of "NT Service\MSSQL$SQLEXPRESS" but also with no luck. But after that I ran TommyGrahn's solution and WOLA, it worked.

Good luck to you all!