Top-Themen

Aktuelle Themen (A bis Z)

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

MSSQL Server Agent startet nicht mehr

Mitglied: dimo11

dimo11 (Level 1) - Jetzt verbinden

02.08.2011, aktualisiert 08:16 Uhr, 12348 Aufrufe, 4 Kommentare

Hallo,
ich bräuchte dringend eure Hilfe ich weis nicht mehr was ich machen kann damit der Agent wieder läuft.

Nach einen Neustart des Servers startet der Server Agent auf einmal nicht mehr.

System Windows Server 2008, MSSQL 2008 R2.

Fehler beim einlochen mit Management Studio : "Die msdb-Datenbank kann nicht geöffnet werden. Sie wurde bei der Wiederherstellung als SUSPECT gekennzeichnet. Weitere Informationen finden Sie im SQL Server-Fehlerprotokoll. (Microsoft SQL Server, Fehler: 926)"

Leider lässt sich der Server-Agent auch nicht mehr manuell über die Dienste Starten.

Im SQLAGENT.OUT steht folgendes :

2011-08-02 07:58:33 - ! [298] SQLServer Error: 18456, Fehler bei der Anmeldung für den Benutzer 'NT AUTHORITY\SYSTEM'. [SQLSTATE 28000]
2011-08-02 07:58:33 - ! [298] SQLServer Error: 4060, Die von der Anmeldung angeforderte msdb-Datenbank kann nicht geöffnet werden. Fehler bei der Anmeldung. [SQLSTATE 42000]
2011-08-02 07:58:33 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2011-08-02 07:58:33 - ! [298] SQLServer Error: 18456, Fehler bei der Anmeldung für den Benutzer 'NT AUTHORITY\SYSTEM'. [SQLSTATE 28000]
2011-08-02 07:58:33 - ! [298] SQLServer Error: 4060, Die von der Anmeldung angeforderte msdb-Datenbank kann nicht geöffnet werden. Fehler bei der Anmeldung. [SQLSTATE 42000]
2011-08-02 07:58:33 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2011-08-02 07:58:33 - ? [098] SQLServerAgent terminated (normally)


Im ERRORLOG :

2011-08-02 07:58:13.36 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2011-08-02 07:58:13.36 Server (c) Microsoft Corporation.
2011-08-02 07:58:13.36 Server All rights reserved.
2011-08-02 07:58:13.36 Server Server process ID is 4104.
2011-08-02 07:58:13.36 Server System Manufacturer: 'FUJITSU', System Model: 'D2901-H1'.
2011-08-02 07:58:13.36 Server Authentication mode is MIXED.
2011-08-02 07:58:13.36 Server Logging SQL Server messages in file 'D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-08-02 07:58:13.36 Server This instance of SQL Server last reported using a process ID of 5588 at 02.08.2011 07:58:08 (local) 02.08.2011 05:58:08 (UTC). This is an informational message only; no user action is required.
2011-08-02 07:58:13.36 Server Registry startup parameters:
-d D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-08-02 07:58:13.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-08-02 07:58:13.36 Server Detected 4 CPUs. This is an informational message; no user action is required.
2011-08-02 07:58:13.41 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-02 07:58:13.45 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-08-02 07:58:13.50 spid7s Starting up database 'master'.
2011-08-02 07:58:13.57 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-08-02 07:58:13.58 spid7s CHECKDB for database 'master' finished without errors on 2011-08-01 10:30:50.713 (local time). This is an informational message only; no user action is required.
2011-08-02 07:58:13.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-08-02 07:58:13.62 spid7s SQL Trace ID 1 was started by login "sa".
2011-08-02 07:58:13.62 spid7s Starting up database 'mssqlsystemresource'.
2011-08-02 07:58:13.63 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-08-02 07:58:13.67 spid7s Server name is '...'. This is an informational message only. No user action is required.
2011-08-02 07:58:13.67 spid11s Starting up database 'model'.
2011-08-02 07:58:13.69 spid11s Clearing tempdb database.
2011-08-02 07:58:13.80 spid11s Starting up database 'tempdb'.
2011-08-02 07:58:13.83 spid14s The Service Broker protocol transport is disabled or not configured.
2011-08-02 07:58:13.83 spid14s The Database Mirroring protocol transport is disabled or not configured.
2011-08-02 07:58:13.84 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2011-08-02 07:58:13.84 spid14s Service Broker manager has started.
2011-08-02 07:58:13.87 spid21s Starting up database 'msdb'.
2011-08-02 07:58:13.88 spid13s Starting up database 'ReportServer'.
2011-08-02 07:58:13.88 spid23s Starting up database 'ReportServerTempDB'.
2011-08-02 07:58:13.91 spid21s Fehler: 9003, Schweregrad: 20, Status: 1.
2011-08-02 07:58:13.91 spid21s The log scan number (207:584:1) passed to log scan in database 'msdb' 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-02 07:58:13.91 spid21s Fehler: 3414, Schweregrad: 21, Status: 1.
2011-08-02 07:58:13.91 spid21s An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2011-08-02 07:58:13.97 spid7s Fehler: 8355, Schweregrad: 16, Status: 1.
2011-08-02 07:58:13.97 spid7s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
2011-08-02 07:58:13.98 spid7s Recovery is complete. This is an informational message only. No user action is required.
2011-08-02 07:58:14.10 Server A self-generated certificate was successfully loaded for encryption.
2011-08-02 07:58:14.10 Server Server is listening on [ 'any' <ipv6> 1433].
2011-08-02 07:58:14.10 Server Server is listening on [ 'any' <ipv4> 1433].
2011-08-02 07:58:14.10 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-08-02 07:58:14.10 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-08-02 07:58:14.10 Server Server is listening on [ ::1 <ipv6> 1434].
2011-08-02 07:58:14.10 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-08-02 07:58:14.10 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-08-02 07:58:14.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-08-02 07:58:14.11 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-08-02 07:58:33.40 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 07:58:33.40 Login failed for user 'NT AUTHORITY\SYSTEM'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 07:58:33.41 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 07:58:33.41 Login failed for user 'NT AUTHORITY\SYSTEM'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:03:49.42 spid56 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2011-08-02 08:03:49.43 spid56 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-08-02 08:06:16.13 spid56 Starting up database 'test'.
2011-08-02 08:06:16.19 spid56 Setting database option COMPATIBILITY_LEVEL to 100 for database test.
2011-08-02 08:06:16.22 spid56 Setting database option ANSI_NULL_DEFAULT to OFF for database test.
2011-08-02 08:06:16.23 spid56 Setting database option ANSI_NULLS to OFF for database test.
2011-08-02 08:06:16.24 spid56 Setting database option ANSI_PADDING to OFF for database test.
2011-08-02 08:06:16.26 spid56 Setting database option ANSI_WARNINGS to OFF for database test.
2011-08-02 08:06:16.27 spid56 Setting database option ARITHABORT to OFF for database test.
2011-08-02 08:06:16.28 spid56 Setting database option AUTO_CLOSE to OFF for database test.
2011-08-02 08:06:16.30 spid56 Setting database option AUTO_CREATE_STATISTICS to ON for database test.
2011-08-02 08:06:16.31 spid56 Setting database option AUTO_SHRINK to OFF for database test.
2011-08-02 08:06:16.32 spid56 Setting database option AUTO_UPDATE_STATISTICS to ON for database test.
2011-08-02 08:06:16.34 spid56 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database test.
2011-08-02 08:06:16.36 spid56 Setting database option CURSOR_DEFAULT to GLOBAL for database test.
2011-08-02 08:06:16.37 spid56 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database test.
2011-08-02 08:06:16.38 spid56 Setting database option NUMERIC_ROUNDABORT to OFF for database test.
2011-08-02 08:06:16.39 spid56 Setting database option QUOTED_IDENTIFIER to OFF for database test.
2011-08-02 08:06:16.41 spid56 Setting database option RECURSIVE_TRIGGERS to OFF for database test.
2011-08-02 08:06:16.42 spid56 Setting database option DISABLE_BROKER to ON for database test.
2011-08-02 08:06:16.43 spid56 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database test.
2011-08-02 08:06:16.44 spid56 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database test.
2011-08-02 08:06:16.45 spid56 Setting database option PARAMETERIZATION to SIMPLE for database test.
2011-08-02 08:06:16.47 spid56 Setting database option READ_WRITE to ON for database test.
2011-08-02 08:06:16.47 spid56 Setting database option RECOVERY to FULL for database test.
2011-08-02 08:06:16.48 spid56 Setting database option MULTI_USER to ON for database test.
2011-08-02 08:06:16.48 spid56 Setting database option PAGE_VERIFY to CHECKSUM for database test.
Mitglied: ackerdiesel
02.08.2011 um 08:47 Uhr
Hallo,

scheinbar hat der SQL-Agent keine Berechtigung. Ändere mal zum Test den Benutzer von "NT AUTHORITY\SYSTEM" auf einen Administrator und versuch dann mal den Agent zu starten.

Gruß
ackerdiesel
Bitte warten ..
Mitglied: dimo11
02.08.2011 um 08:56 Uhr
Hallo Danke für die Hilfe,

geht leider auch ned :

LOG :


2011-08-02 07:58:13.36 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2011-08-02 07:58:13.36 Server (c) Microsoft Corporation.
2011-08-02 07:58:13.36 Server All rights reserved.
2011-08-02 07:58:13.36 Server Server process ID is 4104.
2011-08-02 07:58:13.36 Server System Manufacturer: 'FUJITSU', System Model: 'D2901-H1'.
2011-08-02 07:58:13.36 Server Authentication mode is MIXED.
2011-08-02 07:58:13.36 Server Logging SQL Server messages in file 'D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-08-02 07:58:13.36 Server This instance of SQL Server last reported using a process ID of 5588 at 02.08.2011 07:58:08 (local) 02.08.2011 05:58:08 (UTC). This is an informational message only; no user action is required.
2011-08-02 07:58:13.36 Server Registry startup parameters:
-d D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-08-02 07:58:13.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-08-02 07:58:13.36 Server Detected 4 CPUs. This is an informational message; no user action is required.
2011-08-02 07:58:13.41 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-02 07:58:13.45 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-08-02 07:58:13.50 spid7s Starting up database 'master'.
2011-08-02 07:58:13.57 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-08-02 07:58:13.58 spid7s CHECKDB for database 'master' finished without errors on 2011-08-01 10:30:50.713 (local time). This is an informational message only; no user action is required.
2011-08-02 07:58:13.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-08-02 07:58:13.62 spid7s SQL Trace ID 1 was started by login "sa".
2011-08-02 07:58:13.62 spid7s Starting up database 'mssqlsystemresource'.
2011-08-02 07:58:13.63 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-08-02 07:58:13.67 spid7s Server name is 'S15445442'. This is an informational message only. No user action is required.
2011-08-02 07:58:13.67 spid11s Starting up database 'model'.
2011-08-02 07:58:13.69 spid11s Clearing tempdb database.
2011-08-02 07:58:13.80 spid11s Starting up database 'tempdb'.
2011-08-02 07:58:13.83 spid14s The Service Broker protocol transport is disabled or not configured.
2011-08-02 07:58:13.83 spid14s The Database Mirroring protocol transport is disabled or not configured.
2011-08-02 07:58:13.84 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2011-08-02 07:58:13.84 spid14s Service Broker manager has started.
2011-08-02 07:58:13.87 spid21s Starting up database 'msdb'.
2011-08-02 07:58:13.88 spid13s Starting up database 'ReportServer'.
2011-08-02 07:58:13.88 spid23s Starting up database 'ReportServerTempDB'.
2011-08-02 07:58:13.91 spid21s Fehler: 9003, Schweregrad: 20, Status: 1.
2011-08-02 07:58:13.91 spid21s The log scan number (207:584:1) passed to log scan in database 'msdb' 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-02 07:58:13.91 spid21s Fehler: 3414, Schweregrad: 21, Status: 1.
2011-08-02 07:58:13.91 spid21s An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2011-08-02 07:58:13.97 spid7s Fehler: 8355, Schweregrad: 16, Status: 1.
2011-08-02 07:58:13.97 spid7s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
2011-08-02 07:58:13.98 spid7s Recovery is complete. This is an informational message only. No user action is required.
2011-08-02 07:58:14.10 Server A self-generated certificate was successfully loaded for encryption.
2011-08-02 07:58:14.10 Server Server is listening on [ 'any' <ipv6> 1433].
2011-08-02 07:58:14.10 Server Server is listening on [ 'any' <ipv4> 1433].
2011-08-02 07:58:14.10 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-08-02 07:58:14.10 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-08-02 07:58:14.10 Server Server is listening on [ ::1 <ipv6> 1434].
2011-08-02 07:58:14.10 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2011-08-02 07:58:14.10 Server Dedicated admin connection support was established for listening locally on port 1434.
2011-08-02 07:58:14.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-08-02 07:58:14.11 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-08-02 07:58:33.40 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 07:58:33.40 Login failed for user 'NT AUTHORITY\SYSTEM'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 07:58:33.41 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 07:58:33.41 Login failed for user 'NT AUTHORITY\SYSTEM'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:03:49.42 spid56 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2011-08-02 08:03:49.43 spid56 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-08-02 08:06:16.13 spid56 Starting up database 'test'.
2011-08-02 08:06:16.19 spid56 Setting database option COMPATIBILITY_LEVEL to 100 for database test.
2011-08-02 08:06:16.22 spid56 Setting database option ANSI_NULL_DEFAULT to OFF for database test.
2011-08-02 08:06:16.23 spid56 Setting database option ANSI_NULLS to OFF for database test.
2011-08-02 08:06:16.24 spid56 Setting database option ANSI_PADDING to OFF for database test.
2011-08-02 08:06:16.26 spid56 Setting database option ANSI_WARNINGS to OFF for database test.
2011-08-02 08:06:16.27 spid56 Setting database option ARITHABORT to OFF for database test.
2011-08-02 08:06:16.28 spid56 Setting database option AUTO_CLOSE to OFF for database test.
2011-08-02 08:06:16.30 spid56 Setting database option AUTO_CREATE_STATISTICS to ON for database test.
2011-08-02 08:06:16.31 spid56 Setting database option AUTO_SHRINK to OFF for database test.
2011-08-02 08:06:16.32 spid56 Setting database option AUTO_UPDATE_STATISTICS to ON for database test.
2011-08-02 08:06:16.34 spid56 Setting database option CURSOR_CLOSE_ON_COMMIT to OFF for database test.
2011-08-02 08:06:16.36 spid56 Setting database option CURSOR_DEFAULT to GLOBAL for database test.
2011-08-02 08:06:16.37 spid56 Setting database option CONCAT_NULL_YIELDS_NULL to OFF for database test.
2011-08-02 08:06:16.38 spid56 Setting database option NUMERIC_ROUNDABORT to OFF for database test.
2011-08-02 08:06:16.39 spid56 Setting database option QUOTED_IDENTIFIER to OFF for database test.
2011-08-02 08:06:16.41 spid56 Setting database option RECURSIVE_TRIGGERS to OFF for database test.
2011-08-02 08:06:16.42 spid56 Setting database option DISABLE_BROKER to ON for database test.
2011-08-02 08:06:16.43 spid56 Setting database option AUTO_UPDATE_STATISTICS_ASYNC to OFF for database test.
2011-08-02 08:06:16.44 spid56 Setting database option DATE_CORRELATION_OPTIMIZATION to OFF for database test.
2011-08-02 08:06:16.45 spid56 Setting database option PARAMETERIZATION to SIMPLE for database test.
2011-08-02 08:06:16.47 spid56 Setting database option READ_WRITE to ON for database test.
2011-08-02 08:06:16.47 spid56 Setting database option RECOVERY to FULL for database test.
2011-08-02 08:06:16.48 spid56 Setting database option MULTI_USER to ON for database test.
2011-08-02 08:06:16.48 spid56 Setting database option PAGE_VERIFY to CHECKSUM for database test.
2011-08-02 08:50:55.69 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:50:55.69 Login failed for user 'NT AUTHORITY\LOCAL SERVICE'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:50:55.71 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:50:55.71 Login failed for user 'NT AUTHORITY\LOCAL SERVICE'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:51:04.58 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:51:04.58 Login failed for user 'NT AUTHORITY\LOCAL SERVICE'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:51:04.60 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:51:04.60 Login failed for user 'NT AUTHORITY\LOCAL SERVICE'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:02.86 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:02.86 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:02.88 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:02.88 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:13.89 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:13.89 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:13.90 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:13.90 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:39.36 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:39.36 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:53:39.37 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:53:39.37 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:54:33.94 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:54:33.94 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
2011-08-02 08:54:33.96 Fehler: 18456, Schweregrad: 14, Status: 38.
2011-08-02 08:54:33.96 Login failed for user 'S15445442\Administrator'. Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank. [CLIENT: <local machine>]
Bitte warten ..
Mitglied: 32067
02.08.2011 um 09:41 Uhr
Hallo,

eine der System-Datenbanken, die msdb, hat nen schweres Problem, so dass diese nicht online genommen werden kann. In der DB hat der Agent seine Daten gespeichert, deshalb kommt der nicht hoch.

2011-08-02 07:58:13.91 spid21s The log scan number (207:584:1) passed to log scan in database 'msdb' 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.

Da der SQL Server selber startet, würde ich einfach die msdb aus dem letzten Backup restoren und gut. Das musst du aber über RESTORE DATABASE machen, denn die GUI braucht auch die msdb, da steht drin, welche Backups wann gelaufen sind.
Bitte warten ..
Mitglied: dimo11
02.08.2011 um 10:15 Uhr
Vielen Dank !!!!
Das hat geklappt.
Bitte warten ..
Ähnliche Inhalte
Windows Server

MSSQL Server 2012 Datenbank startet nicht nach Restore

Frage von gechgerWindows Server8 Kommentare

Hallo Forum, wir haben versucht, eine gesicherte Datenbank eines produktiven MSSQL-Servers 2008 mittels Restore im Server Mnagement Studio in ...

Windows Server

Upgrade von MSSQL Server 2008 R2 auf MSSQL Server 2012 schlägt fehl

Frage von ArgoadminWindows Server4 Kommentare

Hallo, ich muss einen unserer SQL-Server upgraden. Das Upgrade bricht mit einer Fehlermeldung (siehe auch Foto) ab: Fehler bei ...

Datenbanken

MSSQL-Zugriffsproblem

Frage von petereDatenbanken3 Kommentare

Hallo, ich habe eine 32bit VB6-Anwendung, mit der ich auf MSSQL 2012 Server Instanzen zugreifen möchte, die einen Spielserver ...

Datenbanken

MsSQL 2005 zu MsSQL 2014 Servernamen ändern?

gelöst Frage von SPSmanDatenbanken21 Kommentare

Hallo, ich habe folgendes Problem: ein Kollege von mir ist mit meinem "alten System" mit MSSQL Server 2005 nach ...

Neue Wissensbeiträge
Sonstige Systeme
Es war einmal ein BeOS - Wer erinnert sich noch?
Information von BassFishFox vor 1 TagSonstige Systeme5 Kommentare

Hallo, Bin gerade ueber Haiku gestolpert, von dessen Existenz als "Nachfolger des BeOS" ich wusste nur mich nie wirklich ...

Datenschutz

Microsoft und DSGVO - ob das wohl jemals klappt (Probleme beim Datenabfluss für Office Pro Plus)?

Tipp von VGem-e vor 1 TagDatenschutz3 Kommentare

Servus Kollegen, siehe Aber wer setzt schon MS Office Pro Plus ein? Wie dann der Stand beim "normalen" MS ...

Windows 10

Macht Windows 10.1809 Probleme mit gemappten Netzlaufwerken (betrifft wohl insbes. AMD-Hardware und Trend Micro AV-Produkte)?

Tipp von VGem-e vor 1 TagWindows 103 Kommentare

Moin Kollegen, grad dazu gefunden und Hatten wir dies nicht bei früheren W10-Upgrades ebenfalls? Da bleibt nur, das Upgrade ...

Humor (lol)

Das neue Miniatur Wunderland OFFICIAL VIDEO - worlds largest model railway - railroad

Information von StefanKittel vor 2 TagenHumor (lol)2 Kommentare

Hallo, wer noch nie im Miniatur Wunderland war, sollte es dringend mal nachholen. Es gibt eine neues Video. Viele ...

Heiß diskutierte Inhalte
LAN, WAN, Wireless
Gäste-WLAN durch DD-WRT AP nach einem MikroTik Routerboard
Frage von NukolarLAN, WAN, Wireless16 Kommentare

Hallo, wie der Titel schon sagt möchte ich gerne ein Gäste-WLAN innerhalb eines bestehenden LANs einrichten. Dass die Gäste ...

DSL, VDSL
DSL Monitoring Tool - Quick and dirty?
Frage von george44DSL, VDSL15 Kommentare

Liebe Gemeinde, ich suche ein einfaches und vor allem schnell zu installierendes Monitoring-Tool zur kontinuierlichen Dokumentation (nur) der Internetanbindung. ...

Exchange Server
Outlook findet Postfach nicht
Frage von MaximaxExchange Server11 Kommentare

Hallo, und zwar haben wir auf der Arbeit ein kleines (großes) Exchange 2016 Problem. Exchange meldete gestern, dass die ...

Informationsdienste
Probleme auf dem Server
Frage von LangeLangeInformationsdienste9 Kommentare

Hallo zusammen, ich betreibe die Seite Keine Werbelinks. In der Analyse stellen wir fest, dass die Ladezeit in der ...