February 13, 2012 at 12:04 am
Hi Experts,
Scenario: Iam using sql server 2008 sp1 enterprise edition on windows 7 os.For practice purpose i was moving the model db to another place which is in same drive(C:).
after restart the services i am facing the connection issues.using configuration manager to start the service of that instance.its showing "the request failed or the service didn't respond in a timely fashion.consult the eventlog or the other applicable error logs for details."
in the event viewer showing "FCB::Open failed: Could not open file C:\Srikanth\System Databases\modeldb\modeldev.mdf for file number 1. OS error: 2(The system cannot find the file specified.)."
Now what can i do to solve this issue?
Thank you,
sk
February 13, 2012 at 1:44 am
Hi sqldba,
Can you explain me what is your aim to do this...???
paste your all errors here...
did you check ldf and mdf files?
February 13, 2012 at 1:53 am
Iam learning the sql server administration.For practice purpose i was moving the model db to other place.
Here are the steps i was followed
1)using the alter database command changed the file paths to another location
2)stopped the services
3)copied the files to that new location
4)restart the services
in this step4 it was not restarted.
by using configuration manager to restart the service of that instance .its showing "the request failed or the service didn't respond in a timely fashion.consult the eventlog or the other applicable error logs for details."
now how to connect to that instance?
Thank you,
February 13, 2012 at 1:58 am
I'm guessing the instance isn't running.
Are you sure that the path you set for the model DB matches the one that the files are in?
What's the contents of the error log.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 13, 2012 at 2:02 am
Hi Gila Sir,
2012-02-13 14:27:38.76 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2012-02-13 14:27:38.76 Server (c) 2005 Microsoft Corporation.
2012-02-13 14:27:38.76 Server All rights reserved.
2012-02-13 14:27:38.76 Server Server process ID is 2752.
2012-02-13 14:27:38.76 Server System Manufacturer: 'Dell Inc.', System Model: 'Dell System XPS L502X'.
2012-02-13 14:27:38.76 Server Authentication mode is WINDOWS-ONLY.
2012-02-13 14:27:38.76 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.PROD\MSSQL\Log\ERRORLOG'.
2012-02-13 14:27:38.76 Server This instance of SQL Server last reported using a process ID of 7536 at 2/13/2012 2:27:33 PM (local) 2/13/2012 8:57:33 AM (UTC). This is an informational message only; no user action is required.
2012-02-13 14:27:38.76 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.PROD\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.PROD\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.PROD\MSSQL\DATA\mastlog.ldf
2012-02-13 14:27:38.80 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-02-13 14:27:38.80 Server Detected 4 CPUs. This is an informational message; no user action is required.
2012-02-13 14:27:38.82 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.
2012-02-13 14:27:38.83 Server Node configuration: node 0: CPU mask: 0x000000000000000f Active CPU mask: 0x000000000000000f. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2012-02-13 14:27:38.84 spid6s Starting up database 'master'.
2012-02-13 14:27:38.97 spid6s Resource governor reconfiguration succeeded.
2012-02-13 14:27:38.97 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2012-02-13 14:27:38.97 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2012-02-13 14:27:38.97 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'PROD'.
2012-02-13 14:27:38.99 spid6s SQL Trace ID 1 was started by login "sa".
2012-02-13 14:27:38.99 spid6s Starting up database 'mssqlsystemresource'.
2012-02-13 14:27:39.08 spid6s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2012-02-13 14:27:39.42 spid10s Starting up database 'model'.
2012-02-13 14:27:39.42 spid6s Server name is 'MADDUKURI-PC\PROD'. This is an informational message only. No user action is required.
2012-02-13 14:27:39.45 spid10s Error: 17204, Severity: 16, State: 1.
2012-02-13 14:27:39.45 spid10s FCB::Open failed: Could not open file C:\Srikanth\System Databases\modeldb\modeldev.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2012-02-13 14:27:39.45 spid10s Error: 5120, Severity: 16, State: 101.
2012-02-13 14:27:39.45 spid10s Unable to open the physical file "C:\Srikanth\System Databases\modeldb\modeldev.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2012-02-13 14:27:39.46 spid10s Error: 945, Severity: 14, State: 2.
2012-02-13 14:27:39.46 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2012-02-13 14:27:39.46 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.
2012-02-13 14:27:39.46 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
February 13, 2012 at 2:05 am
check and provide the log file error.
February 13, 2012 at 2:08 am
here are the errors
2012-02-13 14:27:39.42 spid10s Starting up database 'model'.
2012-02-13 14:27:39.42 spid6s Server name is 'MADDUKURI-PC\PROD'. This is an informational message only. No user action is required.
2012-02-13 14:27:39.45 spid10s Error: 17204, Severity: 16, State: 1.
2012-02-13 14:27:39.45 spid10s FCB::Open failed: Could not open file C:\Srikanth\System Databases\modeldb\modeldev.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2012-02-13 14:27:39.45 spid10s Error: 5120, Severity: 16, State: 101.
2012-02-13 14:27:39.45 spid10s Unable to open the physical file "C:\Srikanth\System Databases\modeldb\modeldev.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2012-02-13 14:27:39.46 spid10s Error: 945, Severity: 14, State: 2.
2012-02-13 14:27:39.46 spid10s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
February 13, 2012 at 2:10 am
Dear,
There is no space in drive,add another drive or delete some data as per the size of the db's you are adding in that drive.
February 13, 2012 at 2:14 am
Dear,
In my laptop only one drive is there i.e C:
still it has 120 gb free space in that drive.
Thank you,
February 13, 2012 at 2:22 am
Try this..
STEP1: identify the db status:
use master
select databaseproperty(‘db_name’,'isShutdown’)
Most of them it would return 1 in this situation
STEP2: Clear up the internal db status:
use master
alter database db_name set offline
it would return with no error in most cases
STEP3: Get detail error message:
use master
alter database db_name set online
After step3, sql server will first verify the log file, if the log file is okay, it will verify the rest of the data file(s). Most of time it is because of the file location or file properties setting. For example if it is file location issue:
alter database db_name
modify (file=’logical name’, filename=’physical name’)
go
February 13, 2012 at 2:26 am
Thank you gila sir,
file names are different that is the problem.
now its working fine.
February 13, 2012 at 1:43 pm
Always check what the error tells you first 🙂 Saves a lot of time.
Jared
CE - Microsoft
February 22, 2012 at 3:32 am
I would suggest you to move the data file of model db to another location(drive), and then start the SQL Services and then try attaching the database. Also check event viewer for any errors.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply