[Risolto] SQL-Impossibile eseguire la richiesta o il servizio non...

di il
2 risposte

[Risolto] SQL-Impossibile eseguire la richiesta o il servizio non...

Salve a tutti, nel mentre cercavo di risolvere un problema eccone subito un altro con il server…

stavo provando a trovare una soluzione in merito a questo mio post

https://www.iprogrammatori.it/forum-programmazione/access/problema-linkaggio-be-sql-express-fe-access-tramite-funzione-t53048.html

dopo aver settato tcp/ip e riavviato il servizio, mentre provavo a collegare il FE con il server, mi è crashato e non vi è modo di avviarlo…stò cercando in rete ma nessun risultato…il log riporta quanto segue ma al momento non riesco ad individuare il problema…come posso risolvere?

2024-02-01 15:08:10.64 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 19045: )
2024-02-01 15:08:10.64 Server      UTC adjustment: 1:00
2024-02-01 15:08:10.64 Server      (c) Microsoft Corporation.
2024-02-01 15:08:10.64 Server      All rights reserved.
2024-02-01 15:08:10.69 Server      Server process ID is 6260.
2024-02-01 15:08:10.69 Server      System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 7040'.
2024-02-01 15:08:10.69 Server      Authentication mode is MIXED.
2024-02-01 15:08:10.69 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2024-02-01 15:08:10.69 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2024-02-01 15:08:10.69 Server      Registry startup parameters: 
     -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2024-02-01 15:08:10.69 Server      Command Line Startup Parameters:
     -s "SQLEXPRESS"
2024-02-01 15:08:10.94 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.
2024-02-01 15:08:10.94 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-02-01 15:08:10.94 Server      Detected 8076 MB of RAM. This is an informational message; no user action is required.
2024-02-01 15:08:10.95 Server      Using conventional memory in the memory manager.
2024-02-01 15:08:11.04 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (Italiano 1040)
2024-02-01 15:08:11.08 Server      Query Store settings initialized with enabled = 1, 
2024-02-01 15:08:11.09 Server      The maximum number of dedicated administrator connections for this instance is '1'
2024-02-01 15:08:11.09 Server      This instance of SQL Server last reported using a process ID of 12428 at 2/1/2024 3:04:05 PM (local) 2/1/2024 2:04:05 PM (UTC). This is an informational message only; no user action is required.
2024-02-01 15:08:11.09 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.
2024-02-01 15:08:11.09 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.
2024-02-01 15:08:11.12 Server      Software Usage Metrics is disabled.
2024-02-01 15:08:11.13 spid7s      Starting up database 'master'.
2024-02-01 15:08:11.16 spid7s      14 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2024-02-01 15:08:11.16 spid7s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2024-02-01 15:08:11.20 Server      CLR version v4.0.30319 loaded.
2024-02-01 15:08:11.23 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2024-02-01 15:08:11.23 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2024-02-01 15:08:11.26 spid7s      SQL Trace ID 1 was started by login "sa".
2024-02-01 15:08:11.26 spid7s      Server name is 'DESKTOP-4RC72H8\SQLEXPRESS'. This is an informational message only. No user action is required.
2024-02-01 15:08:11.26 spid15s     Error: 17182, Severity: 16, State: 1.
2024-02-01 15:08:11.26 spid15s     TDSSNIClient initialization failed with error 0xd, status code 0x10. Reason: Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. The data is invalid. 
2024-02-01 15:08:11.26 spid15s     Error: 17182, Severity: 16, State: 1.
2024-02-01 15:08:11.26 spid15s     TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid. 
2024-02-01 15:08:11.26 spid15s     Error: 17826, Severity: 18, State: 3.
2024-02-01 15:08:11.26 spid15s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2024-02-01 15:08:11.26 spid15s     Error: 17120, Severity: 16, State: 1.
2024-02-01 15:08:11.26 spid15s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2 Risposte

Devi accedere o registrarti per scrivere nel forum
2 risposte