Tuesday, February 14, 2012

Cant connect to my SQLExpress Instance

Hello guys,

I've got some troubles , by attempting to connect the SQL Server database to my server.

I've got this error message on the SQL Configuration Manager (when i tried to start SQL Server which was stopped) " The request failed or the service did not respond in a timely fashion.Consult the event log or the other applicable error logs for details "

I found that error log :


2007-12-18 19:36:12.20 Server Server process ID is 5080.
2007-12-18 19:36:12.20 Server Logging SQL Server messages in file'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-18 19:36:12.20 Server This instance of SQL Server last reportedusing a process ID of 1180 at 18/12/2007 19:12:20 (local) 18/12/200719:12:20 (UTC). This is an informational message only; no user actionis required.
2007-12-18 19:36:12.20 Server Registry startup parameters:
2007-12-18 19:36:12.20 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-18 19:36:12.20 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-18 19:36:12.20 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-18 19:36:12.20 Server SQL Server is starting at normal prioritybase (=7). This is an informational message only. No user action isrequired.
2007-12-18 19:36:12.20 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-12-18 19:36:12.40 Server Using dynamic lock allocation. Initialallocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.This is an informational message only. No user action is required.
2007-12-18 19:36:12.42 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-12-18 19:36:12.43 spid4s Starting up database 'master'.
2007-12-18 19:36:12.50 spid4s Error: 9003, Severity: 20, State: 1.
2007-12-18 19:36:12.50 spid4s The log scan number (228:88:1) passed tolog scan in database 'master' is not valid. This error may indicatedata corruption or that the log file (.ldf) does not match the datafile (.mdf). If this error occurred during replication, re-create thepublication. Otherwise, restore from backup if the problem results in afailure during startup.
2007-12-18 19:36:12.50 spid4s Cannot recover the master database. SQLServer is unable to run. Restore master from a full backup, repair it,or rebuild it. For more information about how to rebuild the masterdatabase, see SQL Server Books Online.

I'm on it since this morning and i haven't been able to fix it , none of the web ressources helped me you're my last chance of sleeping tightly :'(

Thank you so much.

Amokrane CHENTIR


welcome to the forums,

after reading the logfile, i think the Master database is damaged , note that SQL server can't work wothout this database .

you need to re-install the Sqlserver , or repair the installation , go to add/remove programs from control panel ,

and repair the SQl server Express Installation.

|||

Thank you very much , i've just tried it and it worked :)


No comments:

Post a Comment