August 1, 2008 at 8:38 am
Hello,
Previous, sry for my bad english. and i would mention that im novice in 2005 sql server technologies.
So, on my small business server, i meet a problem with the services sharepoint and sbsmonitoring after the update kb948110. I have reinstalled sharepoint, sbsmonitoring and reboot. Now, sharepoint and sbsmonitoring are running, but sql server and wsus are stopped and don't want start.
In my mssql errorlog, we can see :
SQL Server is now ready for client connections. This is an informational message; no user action is required.
The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
Erreur : 927, Gravité : 14, État : 2.
La base de données 'model' ne peut pas être ouverte. Elle est en cours de restauration.
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.
Thinking it could be a problem of rights of the folder, i have renamed the mssql tempdb files (in the folder tempdata and data)and restart the server but no effect.
I don't know if its a real problem of tempdb size? if yes, how change the limit of this size? I beleived that i could do this with the software sql server management studio express, so, i install it, but it can't connect to the server sql.
I also don't know where write any sql requete to do this. So i don't know anything about how to correct this problem. :crying:
Thank you for your help.
August 1, 2008 at 8:57 am
I'd be more concerned right now with the message in the log
The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
What's the message right below that? My french isn't up to spec.
TempDB is created based off the model database. If model can't be found or opened, tempDB can't be created. Are there any other error messages in the log (earlier) relating to model?
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
August 1, 2008 at 9:06 am
thank you for your help
This his my complete errorlog
2008-08-01 16:54:13.42 Server (c) 2005 Microsoft Corporation.
2008-08-01 16:54:13.44 Server All rights reserved.
2008-08-01 16:54:13.44 Server Server process ID is 7488.
2008-08-01 16:54:13.44 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-08-01 16:54:13.45 Server This instance of SQL Server last reported using a process ID of 1008 at 01/08/2008 14:53:46 (local) 01/08/2008 12:53:46 (UTC). This is an informational message only; no user action is required.
2008-08-01 16:54:13.45 Server Registry startup parameters:
2008-08-01 16:54:13.48 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-08-01 16:54:13.48 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-08-01 16:54:13.48 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-08-01 16:54:13.53 Serveur SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-08-01 16:54:13.55 Serveur Detected 2 CPUs. This is an informational message; no user action is required.
2008-08-01 16:54:14.62 Serveur 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.
2008-08-01 16:54:15.23 Serveur Database mirroring has been enabled on this instance of SQL Server.
2008-08-01 16:54:15.40 spid4s Starting up database 'master'.
2008-08-01 16:54:18.78 spid4s SQL Trace ID 1 was started by login "sa".
2008-08-01 16:54:19.14 spid4s Starting up database 'mssqlsystemresource'.
2008-08-01 16:54:19.20 spid4s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2008-08-01 16:54:20.84 spid8s Starting up database 'model'.
2008-08-01 16:54:20.97 spid8s The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2008-08-01 16:54:20.94 spid4s Server name is 'BWSRV\BKUPEXEC'. This is an informational message only. No user action is required.
2008-08-01 16:54:21.00 spid4s Starting up database 'msdb'.
2008-08-01 16:54:21.03 spid8s Erreur : 927, Gravité : 14, État : 2.
2008-08-01 16:54:21.03 spid8s The database 'model' could not be opened. She is in restoration.
2008-08-01 16:54:21.17 spid4s The database 'msdb' is marked RESTORING and is in a state that does not allow recovery to be run.
2008-08-01 16:54:21.44 spid8s 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-08-01 16:54:21.44 spid8s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2008-08-01 16:54:21.76 Serveur The certificate was successfully loaded for encryption.
Thx for your help
August 1, 2008 at 9:11 am
It looks like you are out of space on the drive that Temp DB is running from,
Do you have some space free? or do you have another drive to run Temp Db from?
August 1, 2008 at 9:15 am
Yes, on this partition i have just 5 go free. I ve got another partition with more 150 go free. How can i do this transfert ou move ?
Thx
August 1, 2008 at 9:17 am
The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
The database 'model' could not be opened. She is in restoration.
The database 'msdb' is marked RESTORING and is in a state that does not allow recovery to be run.
Looks like there's some problem with the model and msdb databases. Can't see what though.
Do you know where the model and msdb databases are supposed to be? Are they in the same folder as the master database? Could you check and make sure that the files are there.
TempDB isn't been created because there's a problem with the model database. If model can't be brought online, tempDB can't be recreated.
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
August 1, 2008 at 9:27 am
Hum, i m a novice, but i can already say that i found the files following :
in the folder MSSQL1/MSSQL/data, with the files master, we can find :
model$4IDR
modellog$4IDR
model.mdf
modellog.ldf
msdb$4IDR
msdblog$4IDR
msdb.mdf
msdblog.ldf
msdbdata.mdf
tempdb.mdf
templog.ldf
in the folder MSSQL1/MSSQL/template data, with the files master, we can find :
msdbdata.mdf
msdblog.ldf
model.mdf
modellog.ldf
tempdb.mdf
templog.ldf
in the folder MSSQL1/MSSQL/install, with the files master, we can find :
instmsdb.sql
Thx for your help
August 1, 2008 at 9:33 am
Dunno if it'll help, but worth a try before we resort to more drastic measures
Can you move the files
model$4IDR
modellog$4IDR
msdb$4IDR
msdblog$4IDR
somewhere else? Don't delete them, just move them out of the data folder, maybe to My Documents. Then see if you can start SQL.
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
August 1, 2008 at 9:38 am
Ok, i do it, but no effect apparently :S
thx for help
August 1, 2008 at 10:00 am
Don't know for sure. I'm just guessing here.
Is there another instance of SQL on that box? (check in the services screen)
Are the files marked as read-only (right-click, properties)
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
August 1, 2008 at 10:11 am
ok, i move them,
in my processus i find twice time sqlservr.exe running, i don't know if it help you.
The service sbsmonitoring and sql browser is running too.
In the folder mssql/data, we can find also the files following :
mssqlsystemressources.ldf
mssqlsystemressource.mdf
and the files of the master database like mastlog$4IDR, mastlog.mdf ect.
and the problematic tempdb :S
what kind of information could i give you ?
thx
August 1, 2008 at 10:25 am
Then there's a second SQL instance on the box, and we may be messing with its files, instead of the broken instance's files. Don't touch anything in the mssql/data folder.
Does the other SQL instance start correctly? Does the broken SQL instance start now? Any different errors? If not, there are a couple of more drastic things to try, but I have a class to attend now. I'm sure someone else will drop in with suggestions in the mean time
Do you have a support contract with Microsoft? It might be time to call their customer support people for this.
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
August 1, 2008 at 10:33 am
hum, when you talk about instance sql, you talk about services like sharepoint or about another thing?
I sry again, but i haven't got knowledge about some sql terms.
May be is there a link with sbsmonitoring, which we have no correctly reinstall the first time, and after the second seems to run correctly?
Or a link with backup exec.
What do you need?
August 1, 2008 at 10:36 am
So when i use the sql services manager, i could see two server,
-myserver/bkupexec
-myserver
if it can help
August 1, 2008 at 10:43 am
This means that you have two instances of SQL server running on the same server, it is like having two seperate sql servers running.
So you need to be careful that any changes that you are making do not affect the other instance.
Are you having the same issues with your second instance of SQL server?
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply