November 24, 2009 at 1:35 pm
Starting up database 'model'.
2009-11-24 15:32:09.22 Server Dedicated admin connection support was established for listening locally on port 1554.
2009-11-24 15:32:09.22 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 15:32:09.22 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 15:32:09.22 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 15:32:09.22 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 1. OS error: 5(Access is denied.).
2009-11-24 15:32:09.22 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 15:32:09.22 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 15:32:09.22 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 15:32:09.22 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'E:\MSSQL\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 15:32:09.22 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 15:32:09.22 spid9s FCB::Open failed: Could not open file E:\MSSQL\MSSQL.4\MSSQL\Data for file number 2. OS error: 5(Access is denied.).
2009-11-24 15:32:09.24 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 15:32:09.24 spid9s Unable to open the physical file "E:\MSSQL\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 15:32:09.24 spid9s File activation failure. The physical file name "E:\MSSQL\MSSQL.4\MSSQL\Data" may be incorrect.
2009-11-24 15:32:09.24 spid9s Error: 945, Severity: 14, State: 2.
2009-11-24 15:32:09.24 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2009-11-24 15:32:09.24 spid9s 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-11-24 15:32:09.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
November 24, 2009 at 1:43 pm
Krasavita (11/24/2009)
I need my sql server to run asap. Now I just want to be the way it was before for now. I removed everything from e drive and want to stay the way it was on c drive, error log is showing the following:
How did you move everything back to c: Drive,
Are you doing the steps mentioned in this link http://msdn.microsoft.com/en-us/library/ms345408(SQL.90).aspx
or are you doing it differently?
ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME = 'new_path\os_file_name' )
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 1:48 pm
Raghavender (11/24/2009)
Try the below url:
That was the same link provided by me initially..
in the above article he mentioned about a trace flag like –c –m T3608.
Here we need to just enable the –T3608 only, not whole –c –m T3608
I know what the command switches (- c -m) do when SQL starts from command mode..
Can you explain any particular reason why to avoid - c -m ?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 2:39 pm
I can't do anything even in these mode we have windows authentication
November 24, 2009 at 2:53 pm
Krasavita (11/24/2009)
I can't do anything even in these mode we have windows authentication
I am sorry, I did not understand. Can you explain what do you mean?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 3:32 pm
I switched everything back to c drive and still can't run instanse,here is error log:
2009-11-24 17:25:12.60 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 17:25:12.60 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 17:25:12.60 spid9s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data for file number 1. OS error: 5(Access is denied.).
2009-11-24 17:25:12.60 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 17:25:12.60 spid9s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 17:25:12.60 spid9s Error: 17207, Severity: 16, State: 1.
2009-11-24 17:25:12.60 spid9s FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data'. Diagnose and correct the operating system error, and retry the operation.
2009-11-24 17:25:12.60 spid9s Error: 17204, Severity: 16, State: 1.
2009-11-24 17:25:12.60 spid9s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data for file number 2. OS error: 5(Access is denied.).
2009-11-24 17:25:12.60 spid9s Error: 5120, Severity: 16, State: 101.
2009-11-24 17:25:12.60 spid9s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data". Operating system error 5: "5(Access is denied.)".
2009-11-24 17:25:12.60 spid9s File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Data" may be incorrect.
2009-11-24 17:25:12.60 spid9s Error: 945, Severity: 14, State: 2.
2009-11-24 17:25:12.60 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2009-11-24 17:25:12.60 spid9s 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-11-24 17:25:12.60 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
November 24, 2009 at 3:44 pm
Any security settings have been changed?
SQL Server is unable to access the directories that are mentioned in the error log.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 3:49 pm
No,nothing was changed, I am in a lot of trouble, I don't know what to do
November 24, 2009 at 4:29 pm
I have been asking the same question.. Are you following the steps mentioned in the link given.
What errors are you getting when Altering the system databases?
Are you able to start the SQL Server in single user mode?
Did you change the SQL Startup parameters as described in the article
http://support.microsoft.com/kb/224071
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 24, 2009 at 11:24 pm
try manually giving full access to the folder where sql file are there to id which the sql services are using to start. hope this may help.
i faced same issue when i was installing sp3 on sql server 2005 my installation failed due to access issue even though i had full rights...
November 25, 2009 at 4:35 am
removed post.
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply