MS SQL Optima

0

Dzień dobry,

Zwracam się do Was z gorącą prośbą o pomoc.
Być może i ten temat był już tu poruszany gdzieś na forum, ale jeżeli chodzi o mnie jestem totalnym laikiem i nie znam się na informatyce :)

Zainstalowałam program Comarch optima. Dwa tygodnie temu program działał normalnie, mogłam wystawiać faktury itp.
Przedwczoraj wyskoczył mi komunikat, który chciał dokonać konfiguracji i połączyć się z serverem.
Woła on nazwę użytkownika i hasło - czego w ogóle nie zakładałam.
Zadzwoniłam na infolinie Optimy i Pan, który mi pomógł powiedział, ze jest gdzieś wina systemu, a nie programu bo pomimo uruchomienia funkcji w Usługach po odświeżeniu komputer sam go wyłącza.

Poniżej znajduje się treść jednego z plików errorlog

2017-01-28 08:58:35.30 Server Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (Intel X86)
Oct 20 2015 15:41:49
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.3 <x64> (Build 14393: ) (WOW64)

2017-01-28 08:58:35.31 Server (c) Microsoft Corporation.
2017-01-28 08:58:35.31 Server All rights reserved.
2017-01-28 08:58:35.31 Server Server process ID is 7640.
2017-01-28 08:58:35.31 Server System Manufacturer: 'Acer', System Model: 'Aspire ES1-311'.
2017-01-28 08:58:35.31 Server Authentication mode is MIXED.
2017-01-28 08:58:35.31 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.OPTIMA\MSSQL\Log\ERRORLOG'.
2017-01-28 08:58:35.31 Server The service account is 'WORKGROUP\PAOLITA$'. This is an informational message; no user action is required.
2017-01-28 08:58:35.31 Server Registry startup parameters:
-d C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.OPTIMA\MSSQL\DATA\master.mdf
-e C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.OPTIMA\MSSQL\Log\ERRORLOG
-l C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.OPTIMA\MSSQL\DATA\mastlog.ldf
2017-01-28 08:58:35.31 Server Command Line Startup Parameters:
-s "OPTIMA"
2017-01-28 08:58:35.66 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.
2017-01-28 08:58:35.66 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-01-28 08:58:35.66 Server Detected 3977 MB of RAM. This is an informational message; no user action is required.
2017-01-28 08:58:35.66 Server Using conventional memory in the memory manager.
2017-01-28 08:58:36.10 Server This instance of SQL Server last reported using a process ID of 2224 at 2017-01-27 18:56:36 (local) 2017-01-27 17:56:36 (UTC). This is an informational message only; no user action is required.
2017-01-28 08:58:36.10 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.
2017-01-28 08:58:36.11 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-28 08:58:36.12 Server Software Usage Metrics is disabled.
2017-01-28 08:58:36.13 spid5s Starting up database 'master'.
2017-01-28 08:58:36.20 spid5s 14 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2017-01-28 08:58:36.21 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2017-01-28 08:58:36.26 Server CLR version v4.0.30319 loaded.
2017-01-28 08:58:36.35 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319.
2017-01-28 08:58:36.49 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-01-28 08:58:36.49 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-01-28 08:58:36.52 spid5s SQL Trace ID 1 was started by login "sa".
2017-01-28 08:58:36.53 spid5s Server name is 'PAOLITA\OPTIMA'. This is an informational message only. No user action is required.
2017-01-28 08:58:36.54 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.OPTIMA\MSSQL\Binn\ftimport.dll'.
2017-01-28 08:58:36.54 spid5s Starting up database 'msdb'.
2017-01-28 08:58:36.54 spid9s Starting up database 'mssqlsystemresource'.
2017-01-28 08:58:36.61 spid9s The resource database build version is 11.00.6020. This is an informational message only. No user action is required.
2017-01-28 08:58:36.68 spid12s A self-generated certificate was successfully loaded for encryption.
2017-01-28 08:58:36.68 spid12s Server is listening on [ 'any' <ipv6> 63851].
2017-01-28 08:58:36.69 spid12s Server is listening on [ 'any' <ipv4> 63851].
2017-01-28 08:58:36.69 spid12s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\OPTIMA ].
2017-01-28 08:58:36.69 spid12s Server local connection provider is ready to accept connection on [ \.\pipe\MSSQL$OPTIMA\sql\query ].
2017-01-28 08:58:36.69 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.
2017-01-28 08:58:36.69 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-01-28 08:58:36.69 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-28 08:58:36.70 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/paolita:OPTIMA ] 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-28 08:58:36.70 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/paolita:63851 ] 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-28 08:58:37.13 spid9s Starting up database 'model'.
2017-01-28 08:58:37.34 spid5s 1 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2017-01-28 08:58:37.46 spid9s Error: 9003, Severity: 20, State: 1.
2017-01-28 08:58:37.46 spid9s The log scan number (32:448:1) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2017-01-28 08:58:37.46 spid9s SQL Server shutdown has been initiated
2017-01-28 08:58:37.46 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2017-01-28 08:58:37.47 spid5s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.

Bardzo proszę, pomóżcie mi to jakoś rozwiązać. Będę wdzięczna za waszą pomoc.
Dziękuję.

0

Z loga wynika, ze poleciała Ci baza model, jedna z systemowych i dlatego sql nie chce wstac, rozwiazanie:
https://blog.sqlauthority.com[...]d-model-database-from-backup/

https://msdn.microsoft.com/en[...]rary/dd207003(v=sql.110).aspx

1 użytkowników online, w tym zalogowanych: 0, gości: 1, botów: 0