Can't connect to SQL Server anymore.. Please help.

Karim El Kadri 0 Reputation points
2025-01-23T22:54:45.59+00:00

I used SQL last year for sometime just fine, then recently this month tried getting back to it & suddenly it doesn't work. I might have deleted some files by accident so I uninstalled everything SQL related & installed again. Still not connecting to the server. And now even the SQL configuration manager doesn't show the statuses, showing "couldn't create snap-in" error.

When I'm trying to connect to the server it takes a while then says cannot connect to SQL Server due to network-related or instance-specific issue & that the system couldn't find the file specified, even though the reinstallation was 100% succesfully completed & I just used all default options with no customization.

I have attached 2 screenshots of the errors showing on each tool.sql error

sql error 2

I would really appreciate help possible as I need this for my job. Thank you so much!

I have also attached an error log below as further reference:

2025-01-23 11:50:36.82 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)

Sep 24 2019 13:48:23 

Copyright (C) 2019 Microsoft Corporation

Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 18363: )

2025-01-23 11:50:36.83 Server UTC adjustment: -5:00

2025-01-23 11:50:36.83 Server (c) Microsoft Corporation.

2025-01-23 11:50:36.83 Server All rights reserved.

2025-01-23 11:50:36.83 Server Server process ID is 6252.

2025-01-23 11:50:36.83 Server System Manufacturer: 'HUAWEI', System Model: 'MACHR-WX9'.

2025-01-23 11:50:36.83 Server Authentication mode is WINDOWS-ONLY.

2025-01-23 11:50:36.83 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Log\ERRORLOG'.

2025-01-23 11:50:36.83 Server The service account is 'NT Service\MSSQL$SQLEXPRESS03'. This is an informational message; no user action is required.

2025-01-23 11:50:36.83 Server Registry startup parameters:

 -d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\DATA\master.mdf

 -e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\Log\ERRORLOG

 -l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS03\MSSQL\DATA\mastlog.ldf

2025-01-23 11:50:36.83 Server Command Line Startup Parameters:

 -s "SQLEXPRESS03"

2025-01-23 11:50:36.90 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2025-01-23 11:50:36.90 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2025-01-23 11:50:36.90 Server Detected 8037 MB of RAM. This is an informational message; no user action is required.

2025-01-23 11:50:36.91 Server Using conventional memory in the memory manager.

2025-01-23 11:50:36.91 Server Page exclusion bitmap is enabled.

2025-01-23 11:50:37.45 Server Buffer Pool: Allocating 2097152 bytes for 1269760 hashPages.

2025-01-23 11:50:37.80 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2025-01-23 11:50:38.96 Server Buffer pool extension is already disabled. No action is necessary.

2025-01-23 11:50:39.38 Server Query Store settings initialized with enabled = 1,

2025-01-23 11:50:39.43 Server The maximum number of dedicated administrator connections for this instance is '1'

2025-01-23 11:50:39.43 Server This instance of SQL Server last reported using a process ID of 16920 at 2025/1/23 11:50:01 (local) 2025/1/23 16:50:01 (UTC). This is an informational message only; no user action is required.

2025-01-23 11:50:39.44 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-01-23 11:50:39.46 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.

2025-01-23 11:50:39.47 Server In-Memory OLTP initialized on lowend machine.

2025-01-23 11:50:39.55 Server [INFO] Created Extended Events session 'hkenginexesession'

2025-01-23 11:50:39.55 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.

2025-01-23 11:50:39.57 Server Total Log Writer threads: 2. This is an informational message; no user action is required.

2025-01-23 11:50:39.60 Server CLR version v4.0.30319 loaded.

2025-01-23 11:50:39.60 Server clflushopt is selected for pmem flush operation.

2025-01-23 11:50:39.60 Server Software Usage Metrics is disabled.

2025-01-23 11:50:39.64 spid10s Starting up database 'master'.

2025-01-23 11:50:39.73 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2025-01-23 11:50:39.96 spid10s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2025-01-23 11:50:39.96 spid10s SQL Server Audit has started the audits. This is an informational message. No user action is required.

2025-01-23 11:50:40.04 spid10s SQL Trace ID 1 was started by login "sa".

2025-01-23 11:50:40.04 spid10s Server name is 'KARIM\SQLEXPRESS03'. This is an informational message only. No user action is required.

2025-01-23 11:50:40.06 spid10s Starting up database 'msdb'.

2025-01-23 11:50:40.07 spid14s Starting up database 'mssqlsystemresource'.

2025-01-23 11:50:40.09 spid14s The resource database build version is 15.00.2000. This is an informational message only. No user action is required.

2025-01-23 11:50:40.15 spid14s Starting up database 'model'.

2025-01-23 11:50:40.20 spid14s Clearing tempdb database.

2025-01-23 11:50:40.28 spid26s A self-generated certificate was successfully loaded for encryption.

2025-01-23 11:50:40.29 spid26s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\SQLEXPRESS03 ].

2025-01-23 11:50:40.29 spid26s Server local connection provider is ready to accept connection on [ \.\pipe\MSSQL$SQLEXPRESS03\sql\query ].

2025-01-23 11:50:40.29 spid26s 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.

2025-01-23 11:50:40.31 spid26s SQL Server is now ready for client connections. This is an informational message; no user action is required.

2025-01-23 11:50:40.31 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.

2025-01-23 11:50:40.31 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Karim:SQLEXPRESS03 ] 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.

2025-01-23 11:50:40.31 spid14s Starting up database 'tempdb'.

2025-01-23 11:50:40.46 spid29s The Service Broker endpoint is in disabled or stopped state.

2025-01-23 11:50:40.46 spid29s The Database Mirroring endpoint is in disabled or stopped state.

2025-01-23 11:50:40.47 spid29s Service Broker manager has started.

2025-01-23 11:50:40.47 spid10s Recovery is complete. This is an informational message only. No user action is required.

2025-01-23 11:56:21.75 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.

2025-01-23 11:56:21.76 spid51 Using 'xplog70.dll' version '2019.150.2000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,377 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. LiHongMSFT-4306 30,361 Reputation points
    2025-01-26T01:15:42.4666667+00:00

    Hi @Karim El Kadri

    cannot connect to SQL Server due to network-related or instance-specific issue & that the system couldn't find the file specified

    Regarding this connect issue, it is suggested to troubleshoot follow by this tech doc: Network-related or instance-specific error.

    Best regards,

    Cosmog


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.