Forum Użytkownikow Subiekt GT
InsERT GT => Subiekt GT => Wątek zaczęty przez: kmwwa w Lipiec 06, 2016, 03:30:33
-
Sytuacja jest taka że zaszła potrzeba zmigrowania systemu InsertGT (Subiekt, Rewizor, Gratyfikant) na nową maszynę bo stara z racji parametrów (kilkuletnie HP na i3 z 2GB ram, 1 dyskiem i Windows7 zaktualizowanym do Win10) po prostu puchnie.
Nowa maszyna to już dedykowany serwer FS Primergy z RAID1, dyskiem SSD na baze i 8GB pamięci. System to Server 2012R2.
Instaluje się na nim każdy SQL Express (już przećwiczyłem 2014, 2012, 2008) i na każdym działa generowanie firmy w trybie Demo ale za nic nie działa dearchiwizacja podmiotu ze starej maszyny.
Tzn następuje odczyt pliku BAK, rozpakowaywanie, potem ten kolejny etap i na końcu komunikat o niemożności wykonania operacji i pełniejszej informacji w LOG serwera. Raz o niezgodności usera "sa" a raz nawet bez tego.
jest szansa że brakuje BC2005 ale on sie na tej architekturze nie pozwala zainstalować.
Próbowałem już robić na "sa" bez hasła i z hasłem które wg dokumentacji jest na aktualnie używanym SQL na serwerze. Autentykacji przez windows - zawsze działa i zawsze działa tak samo.
Poniżej logi serwera z 3 prób na 2008, 2012, 2014 (ta mnie interesuje najbardziej, pozostałe robiłem żeby mieć porównanie).
SQLE 2014
2016-07-06 02:39:47 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
2016-07-06 02:39:47 Server UTC adjustment: 2:00
2016-07-06 02:39:47 Server (c) Microsoft Corporation.
2016-07-06 02:39:47 Server All rights reserved.
2016-07-06 02:39:47 Server Server process ID is 1152.
2016-07-06 02:39:47 Server System Manufacturer: 'FUJITSU', System Model: 'PRIMERGY TX1310 M1'.
2016-07-06 02:39:47 Server Authentication mode is MIXED.
2016-07-06 02:39:47 Server Logging SQL Server messages in file 'E:\SQL_DATA\MSSQL12.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-07-06 02:39:47 Server The service account is 'NT Service\MSSQL$INSERTGT'. This is an informational message; no user action is required.
2016-07-06 02:39:47 Server Registry startup parameters:
-d E:\SQL_DATA\MSSQL12.INSERTGT\MSSQL\DATA\master.mdf
-e E:\SQL_DATA\MSSQL12.INSERTGT\MSSQL\Log\ERRORLOG
-l E:\SQL_DATA\MSSQL12.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-07-06 02:39:47 Server Command Line Startup Parameters:
-s "INSERTGT"
2016-07-06 02:39:51 Server SQL Server detected 1 sockets with 4 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.
2016-07-06 02:39:51 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-07-06 02:39:51 Server Detected 8109 MB of RAM. This is an informational message; no user action is required.
2016-07-06 02:39:51 Server Using conventional memory in the memory manager.
2016-07-06 02:39:51 Server Default collation: Polish_CI_AS (us_english 1033)
2016-07-06 02:39:52 Server Query Store settings initialized with enabled = 1,
2016-07-06 02:39:52 Server This instance of SQL Server last reported using a process ID of 2244 at 2016-07-06 02:38:07 (local) 2016-07-06 00:38:07 (UTC). This is an informational message only; no user action is required.
2016-07-06 02:39:52 Server The maximum number of dedicated administrator connections for this instance is '1'
2016-07-06 02:39:52 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.
2016-07-06 02:39:52 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-06 02:39:52 Server Software Usage Metrics is disabled.
2016-07-06 02:39:52 spid8s Starting up database 'master'.
2016-07-06 02:39:53 Server CLR version v4.0.30319 loaded.
2016-07-06 02:39:53 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-07-06 02:39:53 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-07-06 02:39:53 spid8s SQL Trace ID 1 was started by login "sa".
2016-07-06 02:39:53 spid8s Server name is 'GTSERWER\INSERTGT'. This is an informational message only. No user action is required.
2016-07-06 02:39:53 spid15s A self-generated certificate was successfully loaded for encryption.
2016-07-06 02:39:53 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-07-06 02:39:53 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-07-06 02:39:53 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.
2016-07-06 02:39:53 spid8s Starting up database 'msdb'.
2016-07-06 02:39:53 spid12s Starting up database 'mssqlsystemresource'.
2016-07-06 02:39:53 spid12s The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2016-07-06 02:39:54 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-07-06 02:39:54 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.
2016-07-06 02:39:54 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/GTSERWER:INSERTGT ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. 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.
2016-07-06 02:39:54 spid12s Starting up database 'model'.
2016-07-06 02:39:55 spid12s Clearing tempdb database.
2016-07-06 02:39:55 spid12s Starting up database 'tempdb'.
2016-07-06 02:39:56 spid18s The Service Broker endpoint is in disabled or stopped state.
2016-07-06 02:39:56 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2016-07-06 02:39:56 spid18s Service Broker manager has started.
2016-07-06 02:39:56 spid8s Recovery is complete. This is an informational message only. No user action is required.
2016-07-06 02:39:58 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-07-06 02:48:56 Logon Error: 18456, Severity: 14, State: 8.
2016-07-06 02:48:56 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <named pipe>]
2016-07-06 02:49:04 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-07-06 02:49:04 spid51 Using 'xpstar.dll' version '2014.120.2000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
SQLE 2012
2016-07-06 01:08:26 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2016-07-06 01:08:26 Server (c) Microsoft Corporation.
2016-07-06 01:08:26 Server All rights reserved.
2016-07-06 01:08:26 Server Server process ID is 1316.
2016-07-06 01:08:26 Server System Manufacturer: 'FUJITSU', System Model: 'PRIMERGY TX1310 M1'.
2016-07-06 01:08:26 Server Authentication mode is MIXED.
2016-07-06 01:08:26 Server Logging SQL Server messages in file 'E:\SQL_DATA\MSSQL11.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-07-06 01:08:26 Server The service account is 'NT Service\MSSQL$INSERTGT'. This is an informational message; no user action is required.
2016-07-06 01:08:26 Server Registry startup parameters:
-d E:\SQL_DATA\MSSQL11.INSERTGT\MSSQL\DATA\master.mdf
-e E:\SQL_DATA\MSSQL11.INSERTGT\MSSQL\Log\ERRORLOG
-l E:\SQL_DATA\MSSQL11.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-07-06 01:08:26 Server Command Line Startup Parameters:
-s "INSERTGT"
2016-07-06 01:08:27 Server SQL Server detected 1 sockets with 4 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.
2016-07-06 01:08:27 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-07-06 01:08:27 Server Detected 8109 MB of RAM. This is an informational message; no user action is required.
2016-07-06 01:08:27 Server Using conventional memory in the memory manager.
2016-07-06 01:08:27 Server This instance of SQL Server last reported using a process ID of 3044 at 2016-07-06 01:08:23 (local) 2016-07-05 23:08:23 (UTC). This is an informational message only; no user action is required.
2016-07-06 01:08:27 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.
2016-07-06 01:08: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.
2016-07-06 01:08:27 Server Software Usage Metrics is disabled.
2016-07-06 01:08:27 spid5s Starting up database 'master'.
2016-07-06 01:08:27 Server CLR version v4.0.30319 loaded.
2016-07-06 01:08:27 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-07-06 01:08:27 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-07-06 01:08:27 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-07-06 01:08:27 spid5s SQL Trace ID 1 was started by login "sa".
2016-07-06 01:08:27 spid5s Server name is 'GTSERWER\INSERTGT'. This is an informational message only. No user action is required.
2016-07-06 01:08:27 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.INSERTGT\MSSQL\Binn\ftimport.dll'.
2016-07-06 01:08:27 spid5s Starting up database 'msdb'.
2016-07-06 01:08:27 spid9s Starting up database 'mssqlsystemresource'.
2016-07-06 01:08:27 spid9s The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2016-07-06 01:08:27 spid12s A self-generated certificate was successfully loaded for encryption.
2016-07-06 01:08:27 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-07-06 01:08:27 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-07-06 01:08:27 spid12s 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-06 01:08:27 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-07-06 01:08:27 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.
2016-07-06 01:08:27 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/GTSERWER:INSERTGT ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. 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.
2016-07-06 01:08:27 spid9s Starting up database 'model'.
2016-07-06 01:08:27 spid9s Clearing tempdb database.
2016-07-06 01:08:27 spid9s Starting up database 'tempdb'.
2016-07-06 01:08:27 spid15s The Service Broker endpoint is in disabled or stopped state.
2016-07-06 01:08:27 spid15s The Database Mirroring endpoint is in disabled or stopped state.
2016-07-06 01:08:27 spid15s Service Broker manager has started.
2016-07-06 01:08:27 spid5s Recovery is complete. This is an informational message only. No user action is required.
2016-07-06 01:10:01 spid52 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-07-06 01:10:01 spid52 Using 'xpstar.dll' version '2011.110.2100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
SQLE 2008
2016-07-06 02:00:14 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Express Edition with Advanced Services (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2016-07-06 02:00:14 Server (c) Microsoft Corporation.
2016-07-06 02:00:14 Server All rights reserved.
2016-07-06 02:00:14 Server Server process ID is 2740.
2016-07-06 02:00:14 Server System Manufacturer: 'FUJITSU', System Model: 'PRIMERGY TX1310 M1'.
2016-07-06 02:00:14 Server Authentication mode is MIXED.
2016-07-06 02:00:14 Server Logging SQL Server messages in file 'E:\SQL_DATA\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-07-06 02:00:14 Server This instance of SQL Server last reported using a process ID of 2228 at 2016-07-06 02:00:13 (local) 2016-07-06 00:00:13 (UTC). This is an informational message only; no user action is required.
2016-07-06 02:00:14 Server Registry startup parameters:
-d E:\SQL_DATA\MSSQL10_50.INSERTGT\MSSQL\DATA\master.mdf
-e E:\SQL_DATA\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG
-l E:\SQL_DATA\MSSQL10_50.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-07-06 02:00:14 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-07-06 02:00:14 Server Detected 4 CPUs. This is an informational message; no user action is required.
2016-07-06 02:00:15 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-06 02:00:15 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.
2016-07-06 02:00:15 spid7s Starting up database 'master'.
2016-07-06 02:00:15 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-07-06 02:00:15 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'INSERTGT'.
2016-07-06 02:00:15 spid7s SQL Trace ID 1 was started by login "sa".
2016-07-06 02:00:15 spid7s Starting up database 'mssqlsystemresource'.
2016-07-06 02:00:15 spid7s The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2016-07-06 02:00:15 spid7s Server name is 'GTSERWER\INSERTGT'. This is an informational message only. No user action is required.
2016-07-06 02:00:15 spid10s Starting up database 'model'.
2016-07-06 02:00:15 spid7s Informational: No full-text supported languages found.
2016-07-06 02:00:15 spid7s Starting up database 'msdb'.
2016-07-06 02:00:15 spid10s Clearing tempdb database.
2016-07-06 02:00:15 spid10s Starting up database 'tempdb'.
2016-07-06 02:00:15 spid13s The Service Broker protocol transport is disabled or not configured.
2016-07-06 02:00:15 spid13s The Database Mirroring protocol transport is disabled or not configured.
2016-07-06 02:00:15 spid13s Service Broker manager has started.
2016-07-06 02:00:15 spid7s Recovery is complete. This is an informational message only. No user action is required.
2016-07-06 02:00:15 Server A self-generated certificate was successfully loaded for encryption.
2016-07-06 02:00:15 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-07-06 02:00:15 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-07-06 02:00:15 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-06 02:00:15 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-06 02:00:15 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-07-06 02:00:59 Logon Error: 18456, Severity: 14, State: 8.
2016-07-06 02:00:59 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <named pipe>]
2016-07-06 02:01:10 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-07-06 02:01:10 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.
Niestety teraz na próby mam tylko Archiwum robione Archiwizatorem z InsertGT. A jedyne co mi przychodzi do głowy to zbackupowac baze wprost na bieżącym SQL Expr. i podpinać w nowym środowisku na SQLE 2014 a backupy robić potem na SQL - bo czytałem że nawet jak się to odpali to Archiwizacja i Dearchiwizacja zawodzi mocno.
jakieś pomysły/sugestie jak to gryźć?
-
Przepraszam że posta pod postem ale w żadnej przeglądarce nie działa mi "Modyfikuj"
Jeszcze ew. mogę na obecnym serwerze zmienić hasło dla "sa", wykonać archiwizację i na nowej maszynie ze 100% tym samym hasłem dla "sa" zrobić Dearchiwizację.
Tylko wolał bym wiedzieć niż działać na czuja. Problemem jest na pewno to że baza była utworzona zapewne jeszcze w SQLE 2005, podnoszona do 2008 (ale zawsze było BC2005) a SQLE2014 ma z tym problem.
Nie wiem czy jednak tylko mechanizm Insert ma z tym problem czy nawet samej bazy za pomocą SSMS 2014 się nie da przeszczepić.
-
Przepraszam że generuje kolejnego posta ale "Modyfikuj" wciąż mi nie działa.
Jestem krok dalej. Tzn:
Podczas wypakowywania przez Dearchiwizacje pliku IAR w podfolderze tymczasowym utworzonym we wskazanym folderze roboczym powstaje plik *.BAK taki czysto SQLowy.
Nie wolno klikać OK w oknie z komunikatem błędu Insertu bo zamknie okno i plik usunie.
Ale jak już tam jest to można go skopiować w inne miejsce.
Z tego miejsca normalnie SSMS 2014 można odtworzyć i podłączyć baze danych przez Restore (i skopiować podczas tego procesu pliki we właściwą lokalizację).
Insert to widzi i uruchamia się oraz pracuje poprawnie - wiec zapewne patent z backupem za pomocą SSMS na jednej maszynie i o odtworzeniem na drugiej też przejdzie.
Natomiast Archiwizator Insert w moim przypadku i tak nie umie zarchiwizować tej bazy ponownie choć na niej pracuje.
-
Wygląda na problemy z prawami dostępu do folderu roboczego przez SQL Serwer
jest szansa że brakuje BC2005 ale on sie na tej architekturze nie pozwala zainstalować.
Co to znaczy, że się nie pozwala zainstalować?
Jakiś komunikat błędu?
-
jest szansa że brakuje BC2005 ale on sie na tej architekturze nie pozwala zainstalować.
Dziwne, bo ja mam identyczną architekturę (WS 2012R2 + SQL Server 2014) i miałem podobny problem jak ty, opisany pod tym linkiem również z logami w załączniku: http://www.forumsubiekta.pl/subiekt/problem-z-dearchiwizacja-12283/msg70194/#msg70194
Jednak bez problemu mogłem zainstalować BC2005 i problem ustał, także musi się dać doinstalować ten dodatek na tej architekturze. Link, z którego ja instalowałem: https://www.microsoft.com/en-us/download/details.aspx?id=24793
-
Powyższy opis wskazuje na to, że nie wiesz co robisz... Programy Insertu (podobnie jak większość innych) wymagają BC2005 do wykonywania operacji na bazie danych... Nie ma konieczności wykonywać archiwum za pomocą SSMS, aby uzyskać nieskompresowany backup bazy danych - wystarczy w parametrach archiwizacji wyłączyć kompresję... Jak najbardziej można odtworzyć archiwum baz danych narzędzi od Insertu, to jest "tylko" backup bazy danych Microsoftu, nic więcej, ale trzeba wiedzieć jak to poprawnie zrobić (opisywane nawet kilka razy na forum)... Nie mniej należałoby wyjaśnić dlaczego nie chce się zainstalować BC2005...
Zamieszczone przez Ciebie logi wskazują też, że nie znasz hasła na sa do własnego serwera SQL. Napisze też/zamieść zrzut ekranu jak dokładnie logujesz się do serwera SQL.
...a backupy robić potem na SQL - bo czytałem że nawet jak się to odpali to Archiwizacja i Dearchiwizacja zawodzi mocno.
Kto i gdzie pisze takie bzdury ?
jakieś pomysły/sugestie jak to gryźć?
Patrząc na to czym próbujesz się na co dzień zajmować raczej Ci się nie spodobają, więc przemilczę.
-
Mam podobny problem. Chciałem na domowym wgrać sobie kopię. Na win 7 nie było problemu. Po postawieniu Win 10 Pro x64 i ponownej instalacji Subiekta nie mogę odtworzyć backupu. Backup robiony tez z pod win 10 Home x64.
Logowanie na serwer z autentykacją bo bez nie loguje. Żadnego hasła na "sa" nie zakładałem.
Log jest taki:
2016-07-10 11:54:03 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2016-07-10 11:54:03 Server (c) Microsoft Corporation.
2016-07-10 11:54:03 Server All rights reserved.
2016-07-10 11:54:03 Server Server process ID is 2708.
2016-07-10 11:54:03 Server System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model: 'EX38-DS5'.
2016-07-10 11:54:03 Server Authentication mode is WINDOWS-ONLY.
2016-07-10 11:54:03 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-07-10 11:54:03 Server This instance of SQL Server last reported using a process ID of 2680 at 10.07.2016 10:23:27 (local) 10.07.2016 08:23:27 (UTC). This is an informational message only; no user action is required.
2016-07-10 11:54:03 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-10 11:54:04 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-07-10 11:54:04 Server Detected 4 CPUs. This is an informational message; no user action is required.
2016-07-10 11:54: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-10 11:54:06 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.
2016-07-10 11:54:09 spid7s Starting up database 'master'.
2016-07-10 11:54:10 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-07-10 11:54:11 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'INSERTGT'.
2016-07-10 11:54:12 spid7s SQL Trace ID 1 was started by login "sa".
2016-07-10 11:54:12 spid7s Starting up database 'mssqlsystemresource'.
2016-07-10 11:54:12 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2016-07-10 11:54:14 spid10s Starting up database 'model'.
2016-07-10 11:54:14 spid7s Server name is 'PC-DOM\INSERTGT'. This is an informational message only. No user action is required.
2016-07-10 11:54:14 spid7s Informational: No full-text supported languages found.
2016-07-10 11:54:14 spid7s Starting up database 'msdb'.
2016-07-10 11:54:16 Server A self-generated certificate was successfully loaded for encryption.
2016-07-10 11:54:16 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-07-10 11:54:16 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-07-10 11:54:16 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-10 11:54:17 spid10s Clearing tempdb database.
2016-07-10 11:54:17 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-10 11:54:17 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-07-10 11:54:23 spid10s Starting up database 'tempdb'.
2016-07-10 11:54:25 spid13s The Service Broker protocol transport is disabled or not configured.
2016-07-10 11:54:25 spid13s The Database Mirroring protocol transport is disabled or not configured.
2016-07-10 11:54:25 spid13s Service Broker manager has started.
2016-07-10 11:54:26 spid7s Recovery is complete. This is an informational message only. No user action is required.
2016-07-10 12:48:08 Logon Error: 18456, Severity: 14, State: 58.
2016-07-10 12:48:08 Logon Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <named pipe>]
2016-07-10 12:48:20 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-07-10 12:48:20 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-10 12:48:23 spid51 Starting up database 'DeTeMoto'.
2016-07-10 13:03:41 Logon Error: 18456, Severity: 14, State: 58.
2016-07-10 13:03:41 Logon Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <named pipe>]
2016-07-10 13:04:09 Logon Error: 18456, Severity: 14, State: 58.
2016-07-10 13:04:09 Logon Login failed for user 'sa'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <named pipe>]
Nie działa archiwum ani z kompresja ani bez.
SQL 2008 na obu,
-
Mam podobny problem. Chciałem na domowym wgrać sobie kopię. Na win 7 nie było problemu. Po postawieniu Win 10 Pro x64 i ponownej instalacji Subiekta nie mogę odtworzyć backupu. Backup robiony tez z pod win 10 Home x64.
System operacyjny NIE ma znaczenia.
Logowanie na serwer z autentykacją bo bez nie loguje. Żadnego hasła na "sa" nie zakładałem.
Wszystko zrobiłeś Ty, jak wynika z logów został niepoprawnie zainstalowany serwer SQL z autentykację Windows, należy zmienić na MIXED (opisane na tym i innych forach) lub zainstalować raz jeszcze.
SQL 2008 na obu,
Również nie prawda, w zamieszczonym logu wyraźnie pisze, że jest to wersja 2008 R2 SP1, więc nie ma pewności jaka wersja była wcześniej.
--
Nie napisałeś ani słowa o instalacji BC2005.