> Hello Luther,
>
> Thank you your answer.
>
> When I first start the Outlook, it first tries to start the SQL server
> service. After a while it fails and gives two identical error messages
> "Cannot connect to local BCM database because teh SQL service (BCM servcie)
> is not running,,," Then opens a dialog box to create a new database or
> select an existing one on a computer (local) after awhile it caome swith
> another error message " Cannot access teh databse on Computer xxx..." I OK
> it, but then opens teh same doalog box, and repetas thios several times,
> then finallly lets Outlook to start.
>
> The BcmSqlStartupSVC is running. Since the MSSQL$MSSMLBIZ service fails
> on Outlook start up as I explained above, I manually force to start it
> using services I get the following errors in the event viewer:
> (Event ID :7024):
>
> The SQL Server (MSSMLBIZ) service terminated with service-specific error
> 3417 (0xD59).
>
> (Event ID: 9003):
>
> The log scan number (230:488: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.
>
> And the log file (ERRORLOG) in the C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\LOG directory says:
>
>
> 2008-10-14 23:50:09.81 Server Microsoft SQL Server 2005 - 9.00.3068.00
> (Intel X86)
> Feb 26 2008 18:15:01
> Copyright (c) 1988-2005 Microsoft Corporation
> Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)
>
> 2008-10-14 23:50:09.81 Server (c) 2005 Microsoft Corporation.
> 2008-10-14 23:50:09.81 Server All rights reserved.
> 2008-10-14 23:50:09.81 Server Server process ID is 8140.
> 2008-10-14 23:50:09.81 Server Authentication mode is WINDOWS-ONLY.
> 2008-10-14 23:50:09.81 Server Logging SQL Server messages in file
> 'c:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\LOG\ERRORLOG'.
> 2008-10-14 23:50:09.81 Server This instance of SQL Server last reported
> using a process ID of 6124 at 10/14/2008 11:27:36 PM (local) 10/15/2008
> 3:27:36 AM (UTC). This is an informational message only; no user action is
> required.
> 2008-10-14 23:50:09.81 Server Registry startup parameters:
> 2008-10-14 23:50:09.81 Server -d c:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\DATA\master.mdf
> 2008-10-14 23:50:09.81 Server -e c:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\LOG\ERRORLOG
> 2008-10-14 23:50:09.81 Server -l c:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\DATA\mastlog.ldf
> 2008-10-14 23:50:09.81 Server -T 840
> 2008-10-14 23:50:09.81 Server -T 2324
> 2008-10-14 23:50:09.82 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is
> required.
> 2008-10-14 23:50:09.82 Server Detected 2 CPUs. This is an informational
> message; no user action is required.
> 2008-10-14 23:50:09.98 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.
> 2008-10-14 23:50:10.04 Server The time stamp counter of CPU on
> scheduler id 1 is not synchronized with other CPUs.
> 2008-10-14 23:50:10.07 Server Database mirroring has been enabled on
> this instance of SQL Server.
> 2008-10-14 23:50:10.07 spid4s Starting up database 'master'.
> 2008-10-14 23:50:10.23 spid4s Error: 9003, Severity: 20, State: 1.
> 2008-10-14 23:50:10.23 spid4s The log scan number (230:488: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.
> 2008-10-14 23:50:10.23 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.
>
> .
>
>
>
> "Luther" <enowning@gmail.com> wrote in message
> news:01486163-5de9-408c-9644-93c77c25880b@n33g2000pri.googlegroups.com...
> On Oct 10, 8:54 pm, Athena <Ath...@discussions.microsoft.com> wrote:
>
> Is the MSSMLBIZ service running?
>