hello guys,

I am having the same problem and sql server 2005 is not starting , every solution on the web requires sql server service to be running , or require to connect to SSMS , but to connect to sql server management studio sql server service must be running, i am in terrible condition, please if you guys have any solution.. I have already treid rebuilding master database but even after that nothing is working........... please help.

This is the log file

009-07-13 17:05:43.43 Server Detected 2 CPUs. This is an informational message; no user action is required.

2009-07-13 17:05:43.56 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-07-13 17:05:43.57 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

2009-07-13 17:05:44.59 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

2009-07-13 17:05:44.59 Server Database Mirroring Transport is disabled in the endpoint configuration.

2009-07-13 17:05:44.59 spid4s Warning ******************

2009-07-13 17:05:44.60 spid4s SQL Server started in single-user mode. This an informational message only. No user action is required.

2009-07-13 17:05:44.60 spid4s Starting up database 'master'.

2009-07-13 17:05:44.70 spid4s Error: 9003, Severity: 20, State: 1.

2009-07-13 17:05:44.70 spid4s The log scan number (239:200:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

2009-07-13 17:05:44.70 spid4s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.