Forum Użytkownikow Subiekt GT
InsERT GT => Subiekt GT => Wątek zaczęty przez: MroczneWidmo w Czerwiec 09, 2020, 12:00:32
-
Dzień Dobry,
mam problem z archiwizacją subiekta. Przy próbuje archiwizacji jednej z dwóch baz (dla dwóch firm) wyskakuje od razu błąd, że nie mógł przeprowadzić archiwizacji i więcej info w logu serwera, niestety w nim jakoś nie odnajduje problemu. Możecie pomóc? Bardzo dziękuje
2020-06-06 03:34:45 Server Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0 (X64)
Jun 17 2016 19:14:09
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 18363: )
2020-06-06 03:34:45 Server UTC adjustment: 2:00
2020-06-06 03:34:45 Server (c) Microsoft Corporation.
2020-06-06 03:34:45 Server All rights reserved.
2020-06-06 03:34:45 Server Server process ID is 3728.
2020-06-06 03:34:45 Server System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'H81ND2H'.
2020-06-06 03:34:45 Server Authentication mode is MIXED.
2020-06-06 03:34:45 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Log\ERRORLOG'.
2020-06-06 03:34:45 Server The service account is 'WORKGROUP\SERV-PPENT$'. This is an informational message; no user action is required.
2020-06-06 03:34:45 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\DATA\mastlog.ldf
2020-06-06 03:34:45 Server Command Line Startup Parameters:
-s "INSERTGT"
2020-06-06 03:34:48 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-06-06 03:34:48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-06-06 03:34:48 Server Detected 16252 MB of RAM. This is an informational message; no user action is required.
2020-06-06 03:34:49 Server Using conventional memory in the memory manager.
2020-06-06 03:34:49 Server Default collation: Polish_CI_AS (us_english 1033)
2020-06-06 03:34:49 Server The maximum number of dedicated administrator connections for this instance is '1'
2020-06-06 03:34:49 Server This instance of SQL Server last reported using a process ID of 3768 at 06.06.2020 03:34:49 (local) 06.06.2020 01:34:49 (UTC). This is an informational message only; no user action is required.
2020-06-06 03:34:49 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.
2020-06-06 03:34:49 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.
2020-06-06 03:34:49 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2020-06-06 03:34:49 Server Software Usage Metrics is disabled.
2020-06-06 03:34:49 spid11s Starting up database 'master'.
2020-06-06 03:34:49 spid11s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2020-06-06 03:34:49 spid11s An error occurred during Service Master Key initialization. SQLErrorCode=x_cse_CannotDecryptSMK, State=8, LastWindowsError=-2146893813.
2020-06-06 03:34:49 Server CLR version v4.0.30319 loaded.
2020-06-06 03:34:49 spid11s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2020-06-06 03:34:49 spid11s SQL Server Audit has started the audits. This is an informational message. No user action is required.
<{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000001
2020-06-06 03:34:49 spid11s SQL Trace ID 1 was started by login "sa".
2020-06-06 03:34:49 spid11s Server name is 'SERV-PPENT\INSERTGT'. This is an informational message only. No user action is required.
2020-06-06 03:34:50 spid12s Starting up database 'mssqlsystemresource'.
2020-06-06 03:34:50 spid18s Starting up database 'msdb'.
2020-06-06 03:34:50 spid19s Starting up database 'ENTSPACE'.
2020-06-06 03:34:50 spid12s The resource database build version is 12.00.5000. This is an informational message only. No user action is required.
2020-06-06 03:34:50 spid15s A self-generated certificate was successfully loaded for encryption.
2020-06-06 03:34:50 spid15s Server is listening on [ 'any' <ipv6> 50416].
2020-06-06 03:34:50 spid15s Server is listening on [ 'any' <ipv4> 50416].
2020-06-06 03:34:50 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2020-06-06 03:34:50 spid15s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2020-06-06 03:34:50 spid15s 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.
2020-06-06 03:34:50 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2020-06-06 03:34:50 spid12s Starting up database 'model'.
2020-06-06 03:34:50 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2020-06-06 03:34:50 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SERV-PPENT:INSERTGT ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2020-06-06 03:34:50 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SERV-PPENT:50416 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2020-06-06 03:34:50 spid12s Clearing tempdb database.
2020-06-06 03:34:50 spid12s Starting up database 'tempdb'.
2020-06-06 03:34:50 spid20s The Service Broker endpoint is in disabled or stopped state.
2020-06-06 03:34:50 spid20s The Database Mirroring endpoint is in disabled or stopped state.
2020-06-06 03:34:50 spid20s Service Broker manager has started.
2020-06-06 03:34:50 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2020-06-06 03:34:50 spid11s Recovery is complete. This is an informational message only. No user action is required.
2020-06-06 04:00:18 spid51 AppDomain 2 (master.sys[runtime].1) created.
2020-06-06 08:34:24 spid52 Starting up database 'POWERPLAY'.
2020-06-06 09:14:52 spid53 Starting up database 'emos2s'.
2020-06-06 14:42:54 spid60 Starting up database 'POWERPLAY_kopia'.
2020-06-06 14:42:54 spid60 Error: 17204, Severity: 16, State: 1.
2020-06-06 14:42:54 spid60 FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Data\POWERPLAY_kopia.mdf for file number 1. OS error: 2(Nie można odnaleźć określonego pliku.).
2020-06-06 14:42:54 spid60 Error: 17207, Severity: 16, State: 1.
2020-06-06 14:42:54 spid60 FileMgr::StartLogFiles: Operating system error 2(Nie można odnaleźć określonego pliku.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Data\POWERPLAY_kopia_log.LDF'. Diagnose and correct the operating system error, and retry the operation.
2020-06-06 14:42:54 spid60 Starting up database 'ENTSPACE_kopia'.
2020-06-06 14:42:54 spid60 Error: 17204, Severity: 16, State: 1.
2020-06-06 14:42:54 spid60 FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Data\ENTSPACE_kopia.mdf for file number 1. OS error: 2(Nie można odnaleźć określonego pliku.).
2020-06-06 14:42:54 spid60 Error: 17207, Severity: 16, State: 1.
2020-06-06 14:42:54 spid60 FileMgr::StartLogFiles: Operating system error 2(Nie można odnaleźć określonego pliku.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL12.INSERTGT\MSSQL\Data\ENTSPACE_kopia_log.LDF'. Diagnose and correct the operating system error, and retry the operation.
2020-06-09 09:03:13 spid75 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2020-06-09 09:03:13 spid75 Using 'xpstar.dll' version '2014.120.5000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
-
Wykonaj backup za pomocą SSMS, może pojawi się jakiś czytelniejszy komunikat. Zalecam jednak kontakt z serwisantem, gdyż log serwera SQL wygląda niepokojące (nie wiadomo dlaczego brakuje logów transakcyjnych dla niektórych baz danych).
-
Gwoli ścisłości: z uprawnieniami, na których odpalasz ten program do kopii masz uprawnienia do katalogu bazami oraz logami i roboczego? Tzn. robisz to na tym kompie, na którym jest baza i masz np. uprawnienia administratora? I sprawdzałeś programem serwisowym InsERTa poprawność tych baz danych?
-
Program Serwisowy Insertu nie sprawdza stanu bazy danych a jedynie testuje niektóre dane pod kątem ich logicznej poprawności (bardzo "niektóre"