After a power outage and re-boot, my sbs 2003 server is unable to start the SQLEXPRESS 2005 service. I am a total sql rookie and will try to provide all available details. We are running Blackberry Enterprise Server 4.1 which appears to be running on SQLEXPRESS 2005. Backup Exec 12 is successfully running on SQLSERVER 2005 without issue.
When launching the Blackberry Manager, I see - "Database login failed using trusted credentials, database connection lost. Please test connection again with a valid user ID and password."
Blackberry Server Configuration/Test Database Connection yields the following error message - "Test connection to database failed. Please verify that all database settings are correctly entered and that the specified SQL server is running."
When attempting to start the SQLEXPRESS service an application event 9003 is logged - "The log scan number (51:472:1) passed to log scan in database 'model' 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."
The SQL errorlog for for the failed service startup reads as follows:
2010-10-18 16:12:13.96 Server Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
May 26 2009 14:24:20
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2010-10-18 16:12:13.99 Server (c) 2005 Microsoft Corporation.
2010-10-18 16:12:13.99 Server All rights reserved.
2010-10-18 16:12:13.99 Server Server process ID is 7736.
2010-10-18 16:12:13.99 Server Authentication mode is WINDOWS-ONLY.
2010-10-18 16:12:13.99 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2010-10-18 16:12:13.99 Server This instance of SQL Server last reported using a process ID of 3296 at 10/18/2010 12:32:43 PM (local) 10/18/2010 6:32:43 PM (UTC). This is an informational message only; no user action is required.
2010-10-18 16:12:14.00 Server Registry startup parameters:
2010-10-18 16:12:14.01 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2010-10-18 16:12:14.01 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2010-10-18 16:12:14.01 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2010-10-18 16:12:14.06 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-10-18 16:12:14.06 Server Detected 4 CPUs. This is an informational message; no user action is required.
2010-10-18 16:12:14.65 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.
2010-10-18 16:12:15.66 Server Database mirroring has been enabled on this instance of SQL Server.
2010-10-18 16:12:15.78 spid4s Starting up database 'master'.
2010-10-18 16:12:16.54 spid4s SQL Trace ID 1 was started by login "sa".
2010-10-18 16:12:16.60 spid4s Starting up database 'mssqlsystemresource'.
2010-10-18 16:12:16.62 spid4s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2010-10-18 16:12:17.16 spid8s Starting up database 'model'.
2010-10-18 16:12:17.17 spid4s Server name is 'SERVERNAME\SQLEXPRESS'. This is an informational message only. No user action is required.
2010-10-18 16:12:17.17 spid4s Starting up database 'msdb'.
2010-10-18 16:12:17.28 spid8s Error: 9003, Severity: 20, State: 1.
2010-10-18 16:12:17.28 spid8s The log scan number (51:472:1) passed to log scan in database 'model' 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.
2010-10-18 16:12:17.32 spid8s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I have no idea how to resolve my SQLEXPRESS issue. It seems that the Blackberry Enterprise Server cannot function until I am able to successfully start SQLEXPRESS. I currently have 6 Blackberry users whose email is not working. Please help!!!