Błąd "Serwer ... nie mógł przeprowadzić dearchiwizacji"

[Bitoslaw - DiamondBytom 1]

Witam

Jak w temacie zrobiłem archiwizację na komputerze1 i chce przenieść tą bazę na komputer2. Ale na komputerze2 wyskakuje na sam koniec taki błąd. Od 2 dni już próbuje na różne sposoby i nic...

[HotKey . 249]

hmmm "odmowa dostępu"

 

czy autentykacja windows jest odznaczona?

 

Weź autentykację SQL login:

sa

hasło - puste.

 

Daj znać, czy pomogło.

[Bitoslaw - DiamondBytom 1]

Cały czas robię na autentykacji SQL login i taki błąd jest.

[Bartosz Rosa 1 778]

Komputer o nazwie MATEUSZ nie może uzyskać dostępu do folderu roboczego utworzonego na komputerze DIAMOND. Czy na komputerze2 jest zainstalowany serwer SQL i to na nim jest wykonywana dearchiwizacja?

[Bitoslaw - DiamondBytom 1]

Sytacja wygląda tak, na komputerze1 (DIAMOND) zrobiłem archiwizację i teraz na komputerze2 (MATEUSZ) staram się zrobić dearchiwizację aby przenieść bazę sello z komputera1 na komputer2.

I tak jest SQL bo archiwizacje i dearchiwizacje SubiektaGT przebiegły pomyślnie.

[Bitoslaw - DiamondBytom 1]

Problem rozwiązany, po zmianie nazwy podmiotu na całkiem inną oraz wybranie temp komputera2 zamiast komputera1 zadziałało

 

A pomoże mi ktoś z tym? Bo tu już nie mam pomysłu...

https://forum.sello.pl/index.php?topic=9965.0

 

 

[HotKey . 249]

Może łączność z tym drugim komputerem ?

Może firewall?

Czy komputer da się pingować ?

[Bitoslaw - DiamondBytom 1]

Może łączność z tym drugim komputerem ?

Może firewall?

Czy komputer da się pingować ?

Rozwiązałem już problem wyżej

[Adam Wrobel 0]

mam podobny problem podczas przenoszenia bazy z jednego komputera na drugi. Co może być tego przyczyną?

 

15.01.2024 17:33:26  Server  Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) 
    Jun 17 2011 00:54:03 
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

15.01.2024 17:33:26  Server  (c) Microsoft Corporation.
15.01.2024 17:33:26  Server  All rights reserved.
15.01.2024 17:33:26  Server  Server process ID is 6304.
15.01.2024 17:33:26  Server  System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'X399 AORUS Gaming 7'.
15.01.2024 17:33:26  Server  Authentication mode is MIXED.
15.01.2024 17:33:26  Server  Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
15.01.2024 17:33:26  Server  This instance of SQL Server last reported using a process ID of 12580 at 15.01.2024 17:32:30 (local) 15.01.2024 16:32:30 (UTC). This is an informational message only; no user action is required.
15.01.2024 17:33:26  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
15.01.2024 17:33:26  Server  SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
15.01.2024 17:33:26  Server  Detected 24 CPUs. This is an informational message; no user action is required.
15.01.2024 17:33:27  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.
15.01.2024 17:33:27  Server  Lock partitioning is enabled.  This is an informational message only. No user action is required.
15.01.2024 17:33:27  Server  Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
15.01.2024 17:33:27  Server  Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid8s  Starting up database 'master'.
15.01.2024 17:33:27  spid8s  2 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid8s  0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid8s  Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid8s  FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'INSERTGT'.
15.01.2024 17:33:27  spid8s  SQL Trace ID 1 was started by login "sa".
15.01.2024 17:33:27  spid8s  Starting up database 'mssqlsystemresource'.
15.01.2024 17:33:27  spid8s  The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid12s  Starting up database 'model'.
15.01.2024 17:33:27  spid8s  Server name is 'DESKTOP-9RK2DCM\INSERTGT'. This is an informational message only. No user action is required.
15.01.2024 17:33:27  spid8s  Informational: No full-text supported languages found.
15.01.2024 17:33:27  spid8s  Starting up database 'msdb'.
15.01.2024 17:33:27  spid12s  Clearing tempdb database.
15.01.2024 17:33:27  Server  A self-generated certificate was successfully loaded for encryption.
15.01.2024 17:33:27  Server  Server is listening on [ 'any' <ipv6> 59665].
15.01.2024 17:33:27  Server  Server is listening on [ 'any' <ipv4> 59665].
15.01.2024 17:33:27  Server  Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
15.01.2024 17:33:27  Server  Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
15.01.2024 17:33:27  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.
15.01.2024 17:33:27  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.
15.01.2024 17:33:27  Server  SQL Server is now ready for client connections. This is an informational message; no user action is required.
15.01.2024 17:33:27  spid12s  Starting up database 'tempdb'.
15.01.2024 17:33:27  spid15s  The Service Broker protocol transport is disabled or not configured.
15.01.2024 17:33:27  spid15s  The Database Mirroring protocol transport is disabled or not configured.
15.01.2024 17:33:27  spid15s  Service Broker manager has started.
15.01.2024 17:33:27  spid8s  Recovery is complete. This is an informational message only. No user action is required.
15.01.2024 17:34:06  spid51  Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
15.01.2024 17:34:06  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.
15.01.2024 17:34:06  spid51  Starting up database 'qwe'.
15.01.2024 17:34:06  spid51  Starting up database 'qwe_kopia'.
15.01.2024 17:34:06  spid51  Starting up database '_1'.

 

[Bartosz Rosa 1 778]

To jest log serwera SQL, a jaki jest problem w programie?