Forum Użytkownikow Subiekt GT
InsERT GT => Subiekt GT => Wątek zaczęty przez: kedar1989 w Lipiec 12, 2012, 09:46:48
-
Witam,
Mam problem, Subiekt GT nie chce połączyć się z bazą danych przy logowaniu. W SQL server 2005 jest przy SQL server (INSERTGT) status "stopped" gdy klikam start pojawia się błąd. Sprawdziłem folder logi i jest tam kilka plików ERRORLOG z dzisiejszą datą. Bardzo proszę o szybką pomoc. Dodatkowo wysyłam treść pliku errorlog:
2012-07-12 09:35:53.04 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6002: Service Pack 2)
2012-07-12 09:35:53.04 Server (c) 2005 Microsoft Corporation.
2012-07-12 09:35:53.04 Server All rights reserved.
2012-07-12 09:35:53.04 Server Server process ID is 5648.
2012-07-12 09:35:53.04 Server Authentication mode is MIXED.
2012-07-12 09:35:53.04 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2012-07-12 09:35:53.04 Server This instance of SQL Server last reported using a process ID of 4932 at 2012-07-12 09:24:49 (local) 2012-07-12 07:24:49 (UTC). This is an informational message only; no user action is required.
2012-07-12 09:35:53.04 Server Registry startup parameters:
2012-07-12 09:35:53.04 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2012-07-12 09:35:53.04 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2012-07-12 09:35:53.04 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2012-07-12 09:35:53.07 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-07-12 09:35:53.07 Server Detected 2 CPUs. This is an informational message; no user action is required.
2012-07-12 09:35:53.20 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.
2012-07-12 09:35:53.27 Server Database mirroring has been enabled on this instance of SQL Server.
2012-07-12 09:35:53.27 spid5s Starting up database 'master'.
2012-07-12 09:35:53.33 spid5s Error: 9003, Severity: 20, State: 1.
2012-07-12 09:35:53.33 spid5s The log scan number (529:264: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.
2012-07-12 09:35:53.33 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.
Pozdrawiam
kedar1989
-
Oj, znowu niezabezpieczona baza danych lub wadliwy sprzęt - według opisu błędu uszkodzony jest log transakcyjny bazy master - odtwórz bazę z archiwum lub przeinstaluj serwer.
-
Dziękuje za odpowiedź. Dkozlowki mógłbyś mi napisać jak to zrobić aby nie utracić danych?
-
Masz w ogóle jakieś archiwum ? Aby nie utracić danych trzeba o tym myśleć wcześniej ! Na razie serwer krzyzczy o bazę master, ale nie wiadomo co zostało z bazy programu.
Najprościej będzie zainstalować na nowo SQL'a, potem podłącz bazę lub odtwórz z archiwum.
No i zadbaj o serwer i archiwa, aby sytuacja się nie powtórzyła.
-
Subiekt był codziennie archiwizowany. Rozumiem że mam odinstalować Microsoft SQL server 2005 i zainstalować od nowa?
W opcjach odinstalowania mam wybrać Remove SQL Server 2005 instance components> INSERTGT:Database Engine?
-
Tak.
-
Zainstalowałem od nowa teraz jak mam podłączyć nową bazę dla subkietka? w sql mam tylko SQL server (SQLEXPRESS)
-
Skorzystaj z po prostu z programu serwisowego Insertu - bazy w formacie mdf ( czyli gdy już wykonasz restore z backupu ) można podłączać / odlączać .
-
Udało się :D właściwie bez utraty żadnych danych. Dziękuje bardzo za pomoc !
-
Witam. Dzisiaj też spotkałem się z podobnym problemem :
Nie potrafię uruchomić serwera SQL
2018-02-07 00:15:56.00 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2018-02-07 00:15:56.00 Server (c) 2005 Microsoft Corporation.
2018-02-07 00:15:56.00 Server All rights reserved.
2018-02-07 00:15:56.00 Server Server process ID is 2076.
2018-02-07 00:15:56.00 Server System Manufacturer: 'FUJITSU SIEMENS', System Model: 'ESPRIMO C5730'.
2018-02-07 00:15:56.00 Server Authentication mode is WINDOWS-ONLY.
2018-02-07 00:15:56.00 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2018-02-07 00:15:56.00 Server This instance of SQL Server last reported using a process ID of 1984 at 2018-02-07 00:15:54 (local) 2018-02-06 23:15:54 (UTC). This is an informational message only; no user action is required.
2018-02-07 00:15:56.00 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2018-02-07 00:15:56.01 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-02-07 00:15:56.01 Server Detected 2 CPUs. This is an informational message; no user action is required.
2018-02-07 00:15:56.03 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.
2018-02-07 00:15:56.06 Server Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-02-07 00:15:56.08 spid6s Starting up database 'master'.
2018-02-07 00:15:56.14 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2018-02-07 00:15:56.24 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2018-02-07 00:15:56.25 spid6s SQL Trace ID 1 was started by login "sa".
2018-02-07 00:15:56.25 spid6s Starting up database 'mssqlsystemresource'.
2018-02-07 00:15:56.28 spid6s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2018-02-07 00:15:56.43 spid10s Starting up database 'model'.
2018-02-07 00:15:56.43 spid6s Server name is 'MICHAL-ZDALNY\SQLEXPRESS'. This is an informational message only. No user action is required.
2018-02-07 00:15:56.43 spid6s Informational: No full-text supported languages found.
2018-02-07 00:15:56.43 spid6s Starting up database 'msdb'.
2018-02-07 00:15:56.56 Server A self-generated certificate was successfully loaded for encryption.
2018-02-07 00:15:56.56 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2018-02-07 00:15:56.56 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2018-02-07 00:15:56.56 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2018-02-07 00:15:56.57 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.
2018-02-07 00:15:56.57 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-02-07 00:15:57.07 spid10s Clearing tempdb database.
2018-02-07 00:15:58.73 spid10s Starting up database 'tempdb'.
2018-02-07 00:15:58.82 spid13s The Service Broker protocol transport is disabled or not configured.
2018-02-07 00:15:58.82 spid13s The Database Mirroring protocol transport is disabled or not configured.
2018-02-07 00:15:58.83 spid13s Service Broker manager has started.
2018-02-07 00:15:58.83 spid6s Recovery is complete. This is an informational message only. No user action is required.
Proszę o pomoc
-
Może niedowidzę, ale to
SQL Server is now ready for client connections.
mówi że serwer jest gotowy do połączenia, więc skąd twierdzenie że nie możesz uruchomić serwera SQL?
-
Może dlatego, że przy instalacji zwykłej została utworzona instacja SQLEXPRESS, a nie InsertGT. Co wyraźnie jst napisane w logu.
W zwiazku z tym należy się podłączyć do instancji SQLEXPRESS.
-
witam. nie za bardzo wiem co mogę z tym zrobić, próbowałem przeinstalować sql. Czy ktoś może mi pomóc ?
-
serwisant
-
Bardzo pomocne jest to gdy pokazujesz LOG z serwera SQLEXPRESS a komunikat z serwera INSERTGT :)