Fehler nach WIN7 Upd.

[MarkusT]

hallöchen zusammen

nach irgend einem win7 update lässt sich die wawi nicht mehr öffnen bzw. die datenbank: siehe bild im anhang.

auch der serverdienst startet nicht automatisch und lässt sich nicht per hand starten. bin am verzweifeln. kann doch net sein

 

[MarkusT]

AW: Fehler nach WIN7 Upd.

ups.. falsches forum erwischt. bitte verschieben!

 

[MarkusT]

AW: Fehler nach WIN7 Upd.

Und as ist die ERRORLOG:

2010-04-06 20:03:41.63 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 6.1 (Build 7600: )

2010-04-06 20:03:41.69 Server (c) 2005 Microsoft Corporation.
2010-04-06 20:03:41.69 Server All rights reserved.
2010-04-06 20:03:41.69 Server Server process ID is 4992.
2010-04-06 20:03:41.69 Server Authentication mode is MIXED.
2010-04-06 20:03:41.69 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ LOG\ERRORLOG'.
2010-04-06 20:03:41.69 Server This instance of SQL Server last reported using a process ID of 536 at 05.04.2010 13:06:17 (local) 05.04.2010 11:06:17 (UTC). This is an informational message only; no user action is required.
2010-04-06 20:03:41.69 Server Registry startup parameters:
2010-04-06 20:03:41.69 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2010-04-06 20:03:41.69 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2010-04-06 20:03:41.69 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2010-04-06 20:03:41.75 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-04-06 20:03:41.75 Server Detected 4 CPUs. This is an informational message; no user action is required.
2010-04-06 20:03:43.19 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-04-06 20:03:43.31 Server Database mirroring has been enabled on this instance of SQL Server.
2010-04-06 20:03:43.33 spid3s Starting up database 'master'.
2010-04-06 20:03:43.50 spid3s Fehler: 9003, Schweregrad: 20, Status: 1.
2010-04-06 20:03:43.50 spid3s The log scan number (219:496: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.
2010-04-06 20:03:43.51 spid3s 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.

 

[MarkusT]

AW: Fehler nach WIN7 Upd.

ich hab schon alles versucht aber es klappt nicht. will aber nicht alles neu installieren

 

[MarkusT]

AW: Fehler nach WIN7 Upd.

Schade, kannmir neimand helfen?

 

[RC-Street]

AW: Fehler nach WIN7 Upd.

Ich grabe ungern so alte Threads aus, aber ich habe das gleiche Problem und kommen nicht weiter. Ich habe zwar ein Backup, dass zwei Montae alt ist.... jedoch würde ich die aktuellen Daten gerne noch retten.


2011-08-07 18:14:30.36 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

Jo, und nochmal Errorlog
2011-08-07 18:14:30.36 Server (c) 2005 Microsoft Corporation.
2011-08-07 18:14:30.36 Server All rights reserved.
2011-08-07 18:14:30.36 Server Server process ID is 1976.
2011-08-07 18:14:30.36 Server Authentication mode is MIXED.
2011-08-07 18:14:30.36 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\ LOG\ERRORLOG'.
2011-08-07 18:14:30.36 Server This instance of SQL Server last reported using a process ID of 1968 at 07.08.2011 13:54:57 (local) 07.08.2011 11:54:57 (UTC). This is an informational message only; no user action is required.
2011-08-07 18:14:30.36 Server Registry startup parameters:
2011-08-07 18:14:30.36 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-08-07 18:14:30.36 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-08-07 18:14:30.36 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-08-07 18:14:30.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-08-07 18:14:30.36 Server Detected 8 CPUs. This is an informational message; no user action is required.
2011-08-07 18:14:32.11 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.
2011-08-07 18:14:32.36 Server Database mirroring has been enabled on this instance of SQL Server.
2011-08-07 18:14:32.36 spid5s Starting up database 'master'.
2011-08-07 18:14:32.39 spid5s Fehler: 9003, Schweregrad: 20, Status: 1.
2011-08-07 18:14:32.39 spid5s The log scan number (258: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.
2011-08-07 18:14:32.48 spid5s 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.


Hat vielleicht jemand ein Tipp? Ich würde mich sehr freuen.
Ich schönes Wochenende noch.