Temat: WF-Mag problem z dearchiwizacją

Witam,

przenoszę WF-Mag na nowy komputer. NIestety kiedy chcę wgrać kopię bazy z archiwum mam "wyszarzone" opcje wyboru Archiwizacja i Dearchiwizacja - zaznaczona jest Archiwizacja i nie mogę tego zmienić.

Pls o poradę.

Pozdrawiam
Jacek

Temat: WF-Mag problem z dearchiwizacją

Proszę spróbować uruchomić archiwizatora jako administrator - nie spotkałem się z takim problemem ale czasami brak uprawnień objawia się w bardzo dziwny sposób.

Temat: WF-Mag problem z dearchiwizacją

Chyba loguje się jako administrator. Cały czas loguje się loginem "sa".

Temat: WF-Mag problem z dearchiwizacją

chodzi o uruchomienie programu w trybie jako admnistrator a nie samo logowanie.
Prawy klawisz myszy na archiwizator i opcja Uruchom jako administrator

Temat: WF-Mag problem z dearchiwizacją

uruchomienie jako administrator nie rozwiazuje problemu.
mam dokladnie to samo.

zaplacilem dzis za aktualizacje, ktora zainstalowalem na nowym komputerze, poprzez administratora baz danych, utworzylem nowa baze, nastepnie chcialem przywrocic archiwum z dotychczasowego serwera - niestety na etapie ekranu logowanie do SQL server, opcje archiwizuj oraz dearchiwizuj sa niedostepne.Ten post został edytowany przez Autora dnia 09.01.17 o godzinie 16:40

Temat: WF-Mag problem z dearchiwizacją

To niestety trochę za mało informacji. Nie wiadomo ani jaki system ani jaka konfiguracja.
Może Pan spróbować uruchomić archiwizatora bezpośrednio z katalogu (program files (x86)\common files\wa-pro

Temat: WF-Mag problem z dearchiwizacją

Windows 7/MS sql express 2014.
Uruchomilem bezposrednio z katalogu WA-PRO, bez roznicy, wciaz opcje wyboru archiwizuj / dearchiwizuj - sa niedostepne.

Temat: WF-Mag problem z dearchiwizacją

na szybkosci, moge jeszcze podrzucic errorlog.
kilkukrotnie pojawia bledne logowanie ale to pomylka.
haslo oczywiscie pamietam i loguje sie dalej do kolejnego okna ustawien archiwizacji.

2017-01-09 21:26:32.11 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.1 <X64> (Build 7601: Service Pack 1)

2017-01-09 21:26:32.88 Server UTC adjustment: 1:00
2017-01-09 21:26:32.92 Server (c) Microsoft Corporation.
2017-01-09 21:26:32.93 Server All rights reserved.
2017-01-09 21:26:32.93 Server Server process ID is 7620.
2017-01-09 21:26:32.93 Server System Manufacturer: 'Dell Inc.', System Model: 'Inspiron One 2205'.
2017-01-09 21:26:33.15 Server Authentication mode is MIXED.
2017-01-09 21:26:33.18 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2017-01-09 21:26:33.18 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2017-01-09 21:26:33.18 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2017-01-09 21:26:33.18 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2017-01-09 21:27:29.17 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-01-09 21:27:29.17 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-01-09 21:27:29.17 Server Detected 3835 MB of RAM. This is an informational message; no user action is required.
2017-01-09 21:27:29.23 Server Using conventional memory in the memory manager.
2017-01-09 21:27:31.14 Server Default collation: Polish_CI_AS (us_english 1033)
2017-01-09 21:27:57.52 Server Query Store settings initialized with enabled = 1,
2017-01-09 21:27:59.49 Server This instance of SQL Server last reported using a process ID of 13900 at 2017-01-09 21:13:14 (local) 2017-01-09 20:13:14 (UTC). This is an informational message only; no user action is required.
2017-01-09 21:27:59.58 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-01-09 21:27:59.59 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.
2017-01-09 21:27:59.60 Server Software Usage Metrics is disabled.
2017-01-09 21:27:59.57 Server The maximum number of dedicated administrator connections for this instance is '1'
2017-01-09 21:28:01.04 spid7s Starting up database 'master'.
2017-01-09 21:28:02.64 Server CLR version v4.0.30319 loaded.
2017-01-09 21:28:05.57 spid7s Recovery completed for database master (database ID 1) in 2 second(s) (analysis 26 ms, redo 773 ms, undo 0 ms.) This is an informational message only. No user action is required.
2017-01-09 21:28:08.54 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-01-09 21:28:13.19 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-01-09 21:28:14.72 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-01-09 21:28:24.75 spid7s SQL Trace ID 1 was started by login "sa".
2017-01-09 21:28:27.09 spid7s Server name is 'EV24'. This is an informational message only. No user action is required.
2017-01-09 21:28:28.23 spid10s Starting up database 'mssqlsystemresource'.
2017-01-09 21:28:28.23 spid7s Starting up database 'msdb'.
2017-01-09 21:28:28.56 spid10s The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2017-01-09 21:28:31.04 spid10s Starting up database 'model'.
2017-01-09 21:28:32.22 spid15s A self-generated certificate was successfully loaded for encryption.
2017-01-09 21:28:32.51 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2017-01-09 21:28:32.51 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2017-01-09 21:28:32.51 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.
2017-01-09 21:28:32.90 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-01-09 21:28:32.90 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.
2017-01-09 21:28:33.11 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/EV24 ] 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.
2017-01-09 21:28:33.58 spid10s Clearing tempdb database.
2017-01-09 21:28:38.87 spid10s Starting up database 'tempdb'.
2017-01-09 21:28:39.86 spid18s The Service Broker endpoint is in disabled or stopped state.
2017-01-09 21:28:39.99 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2017-01-09 21:28:40.54 spid18s Service Broker manager has started.
2017-01-09 21:28:40.54 spid7s Recovery is complete. This is an informational message only. No user action is required.
2017-01-09 21:28:44.53 Logon Error: 18456, Severity: 14, State: 8.
2017-01-09 21:28:44.53 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <named pipe>]
2017-01-09 21:33:21.24 Logon Error: 18456, Severity: 14, State: 5.
2017-01-09 21:33:21.24 Logon Login failed for user 'waproking'. Reason: Could not find a login matching the name provided. [CLIENT: <named pipe>]
2017-01-09 21:33:23.63 Logon Error: 18456, Severity: 14, State: 8.
2017-01-09 21:33:23.63 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <named pipe>]
2017-01-09 21:33:29.97 spid51 SQL Server blocked access to procedure 'sys.xp_cmdshell' of component 'xp_cmdshell' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'xp_cmdshell' by using sp_configure. For more information about enabling 'xp_cmdshell', search for 'xp_cmdshell' in SQL Server Books Online.
2017-01-09 21:33:30.62 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2017-01-09 21:33:30.70 spid51 Configuration option 'xp_cmdshell' changed from 0 to 1. Run the RECONFIGURE statement to install.
2017-01-09 21:33:30.72 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2017-01-09 21:36:57.36 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2017-01-09 21:36:57.44 spid51 Using 'xplog70.dll' version '2014.120.2000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2017-01-09 21:37:22.41 spid51 Configuration option 'default language' changed from 0 to 14. Run the RECONFIGURE statement to install.
2017-01-09 21:37:23.87 spid51 Starting up database 'WAPRO'.
2017-01-09 21:37:24.36 spid51 Setting database option RECOVERY to SIMPLE for database 'WAPRO'.
2017-01-09 21:37:24.38 spid51 Setting database option AUTO_SHRINK to OFF for database 'WAPRO'.
2017-01-09 21:37:24.38 spid51 Setting database option AUTO_CLOSE to ON for database 'WAPRO'.
2017-01-09 21:37:24.38 spid51 Setting database option AUTO_CREATE_STATISTICS to ON for database 'WAPRO'.
2017-01-09 21:37:24.38 spid51 Setting database option AUTO_UPDATE_STATISTICS to ON for database 'WAPRO'.
2017-01-09 21:37:25.00 spid51 Starting up database 'WAPRO'.
2017-01-09 21:37:25.20 spid51 Setting database option AUTO_CLOSE to OFF for database 'WAPRO'.
2017-01-09 21:37:25.23 spid51 Setting database option PAGE_VERIFY to CHECKSUM for database 'WAPRO'.
2017-01-09 21:37:25.23 spid51 Setting database option RECURSIVE_TRIGGERS to OFF for database 'WAPRO'.
2017-01-09 21:37:25.26 spid51 Configuration option 'clr enabled' changed from 0 to 1. Run the RECONFIGURE statement to install.
2017-01-09 21:37:25.30 spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2017-01-09 21:37:25.56 spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2017-01-09 21:37:25.56 spid51 SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2017-01-09 21:37:25.64 spid51 Setting database option TRUSTWORTHY to ON for database 'WAPRO'.
2017-01-09 21:37:26.23 spid51 Setting database option AUTO_CLOSE to OFF for database 'WAPRO'.
2017-01-09 21:37:26.23 spid51 Setting database option PAGE_VERIFY to CHECKSUM for database 'WAPRO'.
2017-01-09 21:37:51.52 spid51 AppDomain 2 (WAPRO.dbo[runtime].1) created.
2017-01-09 21:44:01.97 spid51 Setting database option AUTO_CLOSE to OFF for database 'WAPRO'.
2017-01-09 21:44:01.97 spid51 Setting database option PAGE_VERIFY to CHECKSUM for database 'WAPRO'.
2017-01-09 21:44:11.30 spid51 Setting database option RECURSIVE_TRIGGERS to OFF for database 'WAPRO'.
2017-01-09 21:48:52.03 Logon Błąd: 18456; ważność: 14; stan: 8.
2017-01-09 21:48:52.03 Logon Login failed for user 'sa'. Przyczyna: hasło jest niezgodne z podaną nazwą logowania. [KLIENT: <named pipe>]Ten post został edytowany przez Autora dnia 09.01.17 o godzinie 22:01

Temat: WF-Mag problem z dearchiwizacją

To nie jest problem logowania bo jak sam Pan pisze - nie są aktywne żadne opcje na ekranie logowania więc proces logowania nie ma jeszcze miejsca.