InsERT GT => Subiekt GT => Wątek zaczęty przez: Napoleon321 w Lipiec 21, 2016, 19:33:13
-
Witam, otóż ustawiłem sobie harmonogram w programie archiwizator aby robił kopie bezpieczeństwa raz dziennie. Niestety zamiast kopi jest log z kodem błędu, który podaje poniżej. Bardzo proszę o pomoc w rozwiązaniu tego problemu.
"2016-07-21 17:00:00: Podmiot 'EKA' nie został zarchiwizowany!
Błąd: 80040c81
(null)"
-
Podpowiedz trochę i zamieść log serwera SQL.
-
Podpowiedz trochę i zamieść log serwera SQL.
Robiłem to na standardowym programie inserta archiwizator, nie wiem co mógłbym jeszcze podpowiedzieć, odnośnie loga serwera to gdzie mam go szukać, bo jestem całkowitym laikiem w tym temacie.
-
Podpowiedz trochę i zamieść log serwera SQL.
Robiłem to na standardowym programie inserta archiwizator, nie wiem co mógłbym jeszcze podpowiedzieć,
Przecież napisałem - mógłbyś zamieścić log serwera SQL.
odnośnie loga serwera to gdzie mam go szukać,
Program serwisowy->główne menu->Serwer->Log.
bo jestem całkowitym laikiem w tym temacie.
W takim razie masz bardzo duże szanse, aby podobnie jak wiele innych osób na forum zrobić sobie krzywdę.
-
Jak nie wiesz jak znaleźć log to chociaż napisz ile masz wolnego miejsca na dysku i jaki jest rozmiar bazy lub jednego z ostatnich plików archiwizacyjnych?
-
Oto log z mojego laptopa
2016-07-21 13:25:04 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (Intel X86)
Jun 17 2011 00:57:23
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.2 <X86> (Build 9200: )
2016-07-21 13:25:05 Server (c) Microsoft Corporation.
2016-07-21 13:25:05 Server All rights reserved.
2016-07-21 13:25:05 Server Server process ID is 2336.
2016-07-21 13:25:05 Server System Manufacturer: 'Hewlett-Packard', System Model: 'HP ProBook 6570b'.
2016-07-21 13:25:05 Server Authentication mode is MIXED.
2016-07-21 13:25:05 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-07-21 13:25:05 Server This instance of SQL Server last reported using a process ID of 2476 at 19.07.2016 14:05:07 (local) 19.07.2016 12:05:07 (UTC). This is an informational message only; no user action is required.
2016-07-21 13:25:05 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-07-21 13:25:05 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-07-21 13:25:05 Server Detected 4 CPUs. This is an informational message; no user action is required.
2016-07-21 13:25:05 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.
2016-07-21 13:25:05 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid7s Starting up database 'master'.
2016-07-21 13:25:05 spid7s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid7s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'INSERTGT'.
2016-07-21 13:25:05 spid7s SQL Trace ID 1 was started by login "sa".
2016-07-21 13:25:05 spid7s Starting up database 'mssqlsystemresource'.
2016-07-21 13:25:05 spid7s The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid10s Starting up database 'model'.
2016-07-21 13:25:05 spid7s Server name is 'HP\INSERTGT'. This is an informational message only. No user action is required.
2016-07-21 13:25:05 spid7s Informational: No full-text supported languages found.
2016-07-21 13:25:05 spid7s Starting up database 'msdb'.
2016-07-21 13:25:05 spid10s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 17408 in file C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\modellog.ldf will be written.
2016-07-21 13:25:05 spid10s Clearing tempdb database.
2016-07-21 13:25:06 Server A self-generated certificate was successfully loaded for encryption.
2016-07-21 13:25:06 Server Server is listening on [ 'any' <ipv6> 49290].
2016-07-21 13:25:06 Server Server is listening on [ 'any' <ipv4> 49290].
2016-07-21 13:25:06 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-07-21 13:25:06 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-07-21 13:25:06 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.
2016-07-21 13:25:06 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.
2016-07-21 13:25:06 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-07-21 13:25:06 spid10s Starting up database 'tempdb'.
2016-07-21 13:25:06 spid13s The Service Broker protocol transport is disabled or not configured.
2016-07-21 13:25:06 spid13s The Database Mirroring protocol transport is disabled or not configured.
2016-07-21 13:25:06 spid13s Service Broker manager has started.
2016-07-21 13:25:06 spid7s Recovery is complete. This is an informational message only. No user action is required.
2016-07-21 15:25:59 Server Server resumed execution after being idle 3377 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2016-07-21 15:25:59 spid51 Starting up database 'EKA'.
2016-07-21 15:25:59 spid51 17 transactions rolled forward in database 'EKA' (5). This is an informational message only. No user action is required.
2016-07-21 15:25:59 spid51 0 transactions rolled back in database 'EKA' (5). This is an informational message only. No user action is required.
2016-07-21 15:25:59 spid51 Recovery is writing a checkpoint in database 'EKA' (5). This is an informational message only. No user action is required.
2016-07-21 15:26:13 Backup Database backed up. Database: EKA, creation date(time): 2016/06/26(19:02:57), pages dumped: 27746, first LSN: 24588:16:60, last LSN: 24588:40:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\ProgramData\InsERT\Temp\{79F245B6-0A01-4D35-B9E7-26E1AF4D9713}\EKA_201607211526.bak'}). This is an informational message only. No user action is required.
2016-07-21 16:44:45 Server Server resumed execution after being idle 58 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2016-07-21 16:44:47 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-07-21 16:44:47 spid51 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.
2016-07-21 16:44:48 spid51 Starting up database 'EKA_kopia'.
2016-07-21 17:00:01 spid51 Error: 18204, Severity: 16, State: 1.
2016-07-21 17:00:01 spid51 BackupDiskFile::CreateMedia: Backup device 'C:\Users\hp\Dysk Google\EKA\Archiwum Rachmistrza\Roboczy\{1F674DEE-5AC5-4EB7-B25F-CB2856C99BB9}\EKA_20160721170000.bak' failed to create. Operating system error 5(Odmowa dostępu.).
2016-07-21 17:00:01 Backup Error: 3041, Severity: 16, State: 1.
2016-07-21 17:00:01 Backup BACKUP failed to complete the command BACKUP DATABASE EKA. Check the backup application log for detailed messages.
2016-07-21 21:18:21 Backup Database backed up. Database: EKA, creation date(time): 2016/06/26(19:02:57), pages dumped: 27786, first LSN: 24612:391:49, last LSN: 24612:412:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\ProgramData\InsERT\Temp\{01D91290-15D9-4B77-9A87-BBE55A23E7BE}\EKA_201607212118.bak'}). This is an informational message only. No user action is required.
2016-07-21 22:45:45 Server Server resumed execution after being idle 323 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2016-07-21 22:47:13 Backup Database backed up. Database: EKA, creation date(time): 2016/06/26(19:02:57), pages dumped: 27786, first LSN: 24613:415:90, last LSN: 24613:450:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\ProgramData\InsERT\Temp\{D6ED35DF-BDED-4481-B5A8-1C2EFAEDDC4E}\EKA_201607212247.bak'}). This is an informational message only. No user action is required.
2016-07-21 22:48:09 spid53 Starting up database 'EKA_kopia'.
2016-07-21 22:48:13 Backup Database backed up. Database: EKA, creation date(time): 2016/06/26(19:02:57), pages dumped: 27786, first LSN: 24613:463:67, last LSN: 24613:490:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\ProgramData\InsERT\Temp\{BBE7D2C3-7C63-4097-8305-68E2E0390702}\EKA.bak'}). This is an informational message only. No user action is required.
2016-07-21 22:48:15 spid53 Starting up database 'EKA_kopia_1'.
2016-07-21 22:48:15 spid53 The database 'EKA_kopia_1' is marked RESTORING and is in a state that does not allow recovery to be run.
2016-07-21 22:48:15 spid53 Starting up database 'EKA_kopia_1'.
2016-07-21 22:48:15 Backup Restore is complete on database 'EKA_kopia_1'. The database is now available.
2016-07-21 22:48:16 Backup Database was restored: Database: EKA_kopia_1, creation date(time): 2016/06/26(19:02:57), first LSN: 24613:463:67, last LSN: 24613:490:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'C:\ProgramData\InsERT\Temp\{BBE7D2C3-7C63-4097-8305-68E2E0390702}\EKA.bak'}). Informational message. No user action required.
2016-07-21 22:49:59 spid52 Setting database option AUTO_CLOSE to OFF for database EKA.
2016-07-22 00:04:06 spid59 Starting up database 'EKA_kopia'.
-
2016-07-21 17:00:01 spid51 BackupDiskFile::CreateMedia: Backup device 'C:\Users\hp\Dysk Google\EKA\Archiwum Rachmistrza\Roboczy\{1F674DEE-5AC5-4EB7-B25F-CB2856C99BB9}\EKA_20160721170000.bak' failed to create. Operating system error 5(Odmowa dostępu.).
Rozumiem, że wkleiłeś log nawet bez zajrzenia do niego w celu poszukania przyczyny problemu ? Jak widać wyraźnie pisze, że wskazałeś w parametrach archiwizacji katalog roboczy, do którego serwer SQL nie ma uprawnień, zmień katalog lub nadaj uprawnienia, polecam to pierwsze, gdyż bez sensu jest wrzucanie plików tymczasowych do chmury.
-
Masz wyraźnie napisane w logu odmowie dostępu. Tuż przed tym zwrotem jest podana lokalizacja w której program próbuje utworzyć tymczasowy folder. Na pierwszy rzut oka albo nie ma uprawnień albo miejsca.
PS dlaczego Tapatalk nie informuje że ktoś w międzyczasie napisał odpowiedź? Eh...
-
2016-07-21 17:00:01 spid51 BackupDiskFile::CreateMedia: Backup device 'C:\Users\hp\Dysk Google\EKA\Archiwum Rachmistrza\Roboczy\{1F674DEE-5AC5-4EB7-B25F-CB2856C99BB9}\EKA_20160721170000.bak' failed to create. Operating system error 5(Odmowa dostępu.).
Rozumiem, że wkleiłeś log nawet bez zajrzenia do niego w celu poszukania przyczyny problemu ?
Owszem, wkleiłem, bo jak napisałem, jestem laikiem i nie znam angielskiego. Sorry, ale w zalewie tych wszystkich komunikatów, tego nie zobaczyłem. Program pytał się o hasło chyba admina i mu podałem, ale albo ja się pomyliłem.