December 20, 2009 at 9:36 am
Hello,
I am trying to run Sql Server Express on a local machine.
Please take note that I have enough space and memory.
I got the following error:
Starting up database 'model'.
2009-12-20 15:30:27.70 spid7s Informational: No full-text supported languages found.
2009-12-20 15:30:27.70 spid7s Starting up database 'msdb'.
2009-12-20 15:30:27.70 spid10s Error: 17204, Severity: 16, State: 1.
2009-12-20 15:30:27.70 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(path not found).
2009-12-20 15:30:27.71 spid10s Error: 5120, Severity: 16, State: 101.
2009-12-20 15:30:27.71 spid10s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(path not found)".
2009-12-20 15:30:27.70 Server A self-generated certificate was successfully loaded for encryption.
2009-12-20 15:30:27.74 spid7s Error: 17204, Severity: 16, State: 1.
2009-12-20 15:30:27.74 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(Impossibile trovare il percorso specificato.).
2009-12-20 15:30:27.74 spid7s Error: 5120, Severity: 16, State: 101.
2009-12-20 15:30:27.74 spid7s Unable to open the physical file "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(path not found)".
2009-12-20 15:30:27.74 spid10s Error: 17207, Severity: 16, State: 1.
2009-12-20 15:30:27.74 spid10s FileMgr::StartLogFiles: Operating system error 2(path 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.
2009-12-20 15:30:27.74 spid10s File activation failure. The physical file name "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2009-12-20 15:30:27.74 spid10s Error: 945, Severity: 14, State: 2.
2009-12-20 15:30:27.74 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-20 15:30:27.74 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-20 15:30:27.74 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2009-12-20 15:30:27.76 Server Server is listening on [ 'any' <ipv6> 1145].
2009-12-20 15:30:27.77 Server Server is listening on [ 'any' <ipv4> 1145].
2009-12-20 15:30:27.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2009-12-20 15:30:27.77 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
Thank you in advance for helping me.
Ellie
December 20, 2009 at 11:53 am
the database files for the model and msdb database are not where SQL expects them to be. As model cannot be found, tempdb cannot be created (tempdb is created from model).
So you are correct, this is not a memory or space issue but 'inaccessible files'.
If you have these database files available but in a different location, move them to where SQL expects them to be (as listed in the errorlog you posted)
---------------------------------------------------------------------
December 20, 2009 at 12:05 pm
Thank you for your answer.
I cannot understand why it looks for files on the partition e: as e is a partition to recover the system.
and I cannot touch it.
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(path not found).
December 20, 2009 at 12:16 pm
can you see the drive? do you have access to it, are the files there?
whats happened to this server recently? Has SQL ever started? Has someone tried to move the system databases?
---------------------------------------------------------------------
December 21, 2009 at 12:26 am
Hello,
I can see the drive but I have no access.
I tried several time to install Sql Server Express.
I tried to install it in Italian and in English.
There were always problems.
During the installation my pc does not reboot itself so if I have some errors I have to recover the system.
At the very beginning it worked.. only once then because of a problem I had to install it again.
After that it never worked.
It is really a mess.
Thank you very much.
Ellie
December 21, 2009 at 3:47 am
then unless you can contact someone who can help you and has access to that drive this sounds like an uninstall via add\remove programs and a reinstall. ensure when you reinstall it that you go into advanced options and specify where you want the database files and.exes to be placed and SQL runs under an account that has access to those drives
---------------------------------------------------------------------
December 22, 2009 at 4:44 pm
Hi,
I have a similar issue and think this is a Microsoft bug.
See http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/ba2ebe4b-6aca-4fe8-9157-cd9956d5b0fa
This is 100% reproducible here.
This appears to be 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.
regards
February 23, 2010 at 5:13 am
hello..... anyone there that has any idea of this issue?
Its as if when this combination is used, it loops through a piece of developers "debug" code that may be in the SQL Express 2008 installer that was hard coded to his local path of "e:\sql10_main_t\sql\mkmastr\databases\objfre\i386\"
April 3, 2010 at 4:58 pm
Last year I have installed sqlServer2008 Express at leeast 10 times, on a XP sp2 and sp3, Vista and Windows7 and every time all was going smoothly, until I've decided to reinstall SqlExpress 2008 on my home machine (Win XP Sp3, Automatic updates on), two days ago. I have experience problem you have described, with mysterious path E:\....". I'm pretty sure that it is a some windows update issue, altought I've found that problem exist since sqlserver2005. After unsuccessfully trying to solve issue by myself (repair, reinstal * x, allowing network service account full access to sql folders, I've decided looking for a solution here on the sqlcentral. Please, do not hesitate to mail me on Alisterthedog@yahoo.com if you have right solution for this issue.
April 5, 2010 at 1:32 am
I am focusing on following error.
Operating system error 3: "3(path not found)".
As I am having experience of above error and suggest you that you should change time zone then try.
April 5, 2011 at 5:40 am
Would you try the following:
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=domain\myname /SAPWD=StrongPassword
Cheers,
AL
April 5, 2011 at 6:04 am
your SQL Setup is correct use the Correct one !!!!
Vimal Kumar
9999797952
April 5, 2011 at 7:16 am
this thread is a year old people...............
---------------------------------------------------------------------
April 5, 2011 at 11:17 pm
http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx
This comes either because path of mdf ldf is not correct or user doesn't have permission.
Thanks
June 3, 2011 at 9:55 pm
Hi Folks,
I know this post is a year old, but this is the exact problem I'm having and I haven't found any other thread addressing it anywhere.
As you have pointed out, the problem is that the path is not correct. Here's what's in my log file:
spid10s 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: 3(The system cannot find the path specified.).
--------------------
Now, on this computer the E: drive is the CD drive... This would have been the 2008 R2 installation disc.
Why is the file path being specified to the E: drive?
Should I try to reinstall or is there a way to specify the correct location?
I am trying to get 2008 R2 Developer to work on my local machine... I have never gotten SQL Server to start due to this error.
I have searched my C: drive and not found model.mdf.
Where should it be?
I appreciate any help.
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply