0x80004005 error when connecting to SQL Server 2019

Question

0x80004005 error when connecting to SQL Server 2019

Marcel Duboué 20

Hello

I have installed Windows 11 a month ago; everything works fine except for an application that I developed using Visual Studio and SQL Server Express.

I uninstalled everything that concerns SQL, deleted the directories and registry keys.

I reinstalled SQL server 2019 EXPRESS and I got an error when I want to open the base 'master': "Failed to create a user instance SQL Server due to a failure to start the process for the instance user".

The log file begins by

"2023-08-25 16:15:18.32 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)

Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-08-25 16:15:18.33 Server UTC adjustment: 2:00

2023-08-25 16:15:18.33 Server (c) Microsoft Corporation.

2023-08-25 16:15:18.33 Server Server process ID is 5172.

2023-08-25 16:15:18.33 Server System Manufacturer: 'GIGABYTE', System Model: 'BRi5(H)-10210E'.

2023-08-25 16:15:18.33 Server Authentication mode is WINDOWS-ONLY.

2023-08-25 16:15:18.33 Server Logging SQL Server messages in file 'C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.

2023-08-25 16:15:18.33 Server The service account is 'FIXE-MARCEL\Marcel'. This is an informational message; no user action is required.

2023-08-25 16:15:18.33 Server Command Line Startup Parameters:

-U "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data"

-d "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf"

-l "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf"

-e "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log"

c

-S "SQLEXPRESS"

-s "3BB31569-504D-4F"

2023-08-25 16:15:18.33 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.

2023-08-25 16:15:18.33 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2023-08-25 16:15:18.33 Server Detected 16221 MB of RAM. This is an informational message; no user action is required.

2023-08-25 16:15:18.33 Server Using conventional memory in the memory manager.

2023-08-25 16:15:18.33 Server Page exclusion bitmap is enabled.

2023-08-25 16:15:18.43 Server Buffer Pool: Allocating 2097152 bytes for 1253927 hashPages.

2023-08-25 16:15:18.44 Server Default collation: French_CI_AS (Français 1036)

2023-08-25 16:15:18.47 Server Buffer pool extension is already disabled. No action is necessary.

2023-08-25 16:15:18.50 Server InitializeLaunchpadUserSid failed with error code: 0x80004005

2023-08-25 16:15:18.50 Server InitializeLaunchpadUserSid failed. Implied authentication will be disabled. ErrorCode: 0x80004005.

2023-08-25 16:15:18.50 Server Implied authentication manager initialization failed. Implied authentication will be disabled, failure: 0x80004005

2023-08-25 16:15:18.50 Server Query Store settings initialized with enabled = 1,

2023-08-25 16:15:18.51 Server The maximum number of dedicated administrator connections for this instance is '1'

2023-08-25 16:15:18.51 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.

2023-08-25 16:15:18.51 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.

2023-08-25 16:15:18.51 spid1s Open of fault log C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS..\log\exception.log failed.

"

Thanks to explain me what is wrong, and the way of reparing it

5 answers

Your answer

Answer 1

Why are you using a user instance in the first place? This is an old feature which has been superceded by LocalDB. Then again, if you snuck in user instance in the connection string without any clear idea of why, just take it out.

"2023-08-25 16:15:18.32 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)

So this is the original version of SQL 2019. You should download and install the most recent Cumulative Update to get access to many bug fixes and enhancements. https://www.microsoft.com/en-US/download/details.aspx?id=100809

Answer 2

Not necessarily an answer, but this might narrow it down a bit.

First of all, I would Google on the first bit and not concentrate on that error number. x8004005 is a broad catch-all for "can't connect". Generally it means you're trying to get from A to Z and something between B and Y broke. Then this occurs with an ODBC connection, there is an entire checklist of all the thigs that can go wrong.

Instead, I'd focus on this part:
2023-08-25 16:15:18.50 Server Implied authentication manager initialization failed. Implied authentication will be disabled,

If you're installing through the command shield, I'd make authentication mode mixed (not necessarily needed, but it can provide an extra access method should there be a problem with Windows/Domain authentication), and check Add Current User during setup (if you Google examples of installation, it will show you the exact screen). You may have already done the latter part, since I see the following:

2023-08-25 16:15:18.33 Server The service account is 'FIXE-MARCEL\Marcel'. This is an informational message; no user action is required.

I also see:

2023-08-25 16:15:18.51 Server The maximum number of dedicated administrator connections for this instance is '1'

Presuming the instance is running under your account (and not a default account associated with the installation), this shouldn't be a problem. It indicates, however, that you're essentially running in single user mode (at least as far as administrators are concerned). I'm not sure there would be a reason to have that setting turned on an Express instance you're just standing up. I believe setting this to 0 during installation would remove this limit, which would at least eliminate that possibility from the list of possible issues.

You can also use notepad to look at the error log files in this folder:

2023-08-25 16:15:18.33 Server Logging SQL Server messages in file 'C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.

though it will probably just show the messages you included in the message.

I'm presuming you're trying to open master via SSMS. If it's through an application connecting with ODBC, there's a host of other issues which might be causing this (though I'm guessing that's not the case, based on the error messages presented).

Erland Sommarskog 120.2K Reputation points MVP

2023-08-25T21:08:03.0466667+00:00

2023-08-25 16:15:18.51 Server The maximum number of dedicated administrator connections for this instance is '1' Presuming the instance is running under your account (and not a default account associated with the installation), this shouldn't be a problem. It indicates, however, that you're essentially running in single user mode (at least as far as administrators are concerned). I'm not sure there would be a reason to have that setting turned on an Express instance you're just standing up. I believe setting this to 0 during installation would remove this limit, which would at least eliminate that possibility from the list of possible issues.

Having exactly one DAC is the normal thing. Nothing to meddle with.

Answer 3

Hi, Erland and William

Thanks for your help.

1- I have run the Cumulative Update; same result

2- the log file begins by (with a different error description, but using my Visual Studio application, the same message)

2023-08-26 09:15:34.75 Server      Microsoft SQL Server 2019 (RTM-CU22) (KB5027702) - 15.0.4322.2 (X64) 
	Jul 27 2023 18:11:00 
	Copyright (C) 2019 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-08-26 09:15:34.75 Server      UTC adjustment: 2:00
2023-08-26 09:15:34.75 Server      (c) Microsoft Corporation.
2023-08-26 09:15:34.76 Server      All rights reserved.
2023-08-26 09:15:34.76 Server      Server process ID is 2936.
2023-08-26 09:15:34.76 Server      System Manufacturer: 'GIGABYTE', System Model: 'BRi5(H)-10210E'.
2023-08-26 09:15:34.76 Server      Authentication mode is WINDOWS-ONLY.
2023-08-26 09:15:34.76 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2023-08-26 09:15:34.76 Server      The service account is 'WORKGROUP\FIXE-MARCEL$'. This is an informational message; no user action is required.
2023-08-26 09:15:34.76 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2023-08-26 09:15:34.76 Server      Command Line Startup Parameters:
	 -s "SQLEXPRESS"
2023-08-26 09:15:34.77 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.
2023-08-26 09:15:34.77 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-08-26 09:15:34.77 Server      Detected 16221 MB of RAM. This is an informational message; no user action is required.
2023-08-26 09:15:34.77 Server      Using conventional memory in the memory manager.
2023-08-26 09:15:34.77 Server      Page exclusion bitmap is enabled.
2023-08-26 09:15:34.90 Server      Buffer Pool: Allocating 2097152 bytes for 2057780 hashPages.
2023-08-26 09:15:34.91 Server      Default collation: French_CI_AS (Français 1036)
2023-08-26 09:15:34.93 Server      Buffer pool extension is already disabled. No action is necessary.
2023-08-26 09:15:34.96 Server      Query Store settings initialized with enabled = 1, 
2023-08-26 09:15:34.97 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-08-26 09:15:34.97 Server      This instance of SQL Server last reported using a process ID of 21508 at 26/08/2023 09:15:26 (local) 26/08/2023 07:15:26 (UTC). This is an informational message only; no user action is required.
2023-08-26 09:15:34.97 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.
2023-08-26 09:15:34.98 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.
2023-08-26 09:15:34.98 Server      In-Memory OLTP initialized on standard machine.
2023-08-26 09:15:35.00 Server      [INFO] Created Extended Events session 'hkenginexesession'
2023-08-26 09:15:35.00 Server      Database Instant File Initialization: activé. 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.
2023-08-26 09:15:35.02 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2023-08-26 09:15:35.03 Server      clflushopt is selected for pmem flush operation.
2023-08-26 09:15:35.03 Server      Software Usage Metrics is disabled.
2023-08-26 09:15:35.04 spid9s      Starting up database 'master'.
2023-08-26 09:15:35.07 Server      CLR version v4.0.30319 loaded.
2023-08-26 09:15:35.12 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2023-08-26 09:15:35.15 spid9s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2023-08-26 09:15:35.15 spid9s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2023-08-26 09:15:35.16 spid9s      SQL Trace ID 1 was started by login "sa".
2023-08-26 09:15:35.16 spid9s      Server name is 'Fixe-Marcel\SQLEXPRESS'. This is an informational message only. No user action is required.
2023-08-26 09:15:35.25 spid21s     A self-generated certificate was successfully loaded for encryption.
2023-08-26 09:15:35.25 spid21s     Server is listening on [ 'any' <ipv6> 53075].
2023-08-26 09:15:35.25 spid21s     Server is listening on [ 'any' <ipv4> 53075].
2023-08-26 09:15:35.25 spid21s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2023-08-26 09:15:35.25 spid21s     Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2023-08-26 09:15:35.25 spid21s     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.
2023-08-26 09:15:35.25 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.
2023-08-26 09:15:35.25 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Fixe-Marcel:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. 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.
2023-08-26 09:15:35.25 spid21s     Server is listening on [ ::1 <ipv6> 60600].
2023-08-26 09:15:35.25 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Fixe-Marcel:53075 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. 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.
2023-08-26 09:15:35.25 spid21s     Server is listening on [ 127.0.0.1 <ipv4> 60600].
2023-08-26 09:15:35.25 spid21s     Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunchSQLEXPRESS ].
2023-08-26 09:15:35.25 spid21s     Resource governor reconfiguration encountered an issue (HRESULT code : 0x80040002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure.
2023-08-26 09:15:35.25 spid21s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2023-08-26 09:15:35.30 spid22s     A new instance of the full-text filter daemon host process has been successfully started.
2023-08-26 09:15:35.34 spid24s     Starting up database 'msdb'.
2023-08-26 09:15:35.34 spid26s     Starting up database 'DWQueue'.
2023-08-26 09:15:35.34 spid14s     Starting up database 'mssqlsystemresource'.
2023-08-26 09:15:35.35 spid14s     The resource database build version is 15.00.4322. This is an informational message only. No user action is required.
2023-08-26 09:15:35.36 spid14s     Synchronize Database 'master' (1) with Resource Database.
2023-08-26 09:15:35.36 spid26s     Parallel redo is started for database 'DWQueue' with worker pool size [4].
2023-08-26 09:15:35.37 spid26s     Parallel redo is shutdown for database 'DWQueue' with worker pool size [4].
2023-08-26 09:15:35.37 spid14s     Starting up database 'model'.
2023-08-26 09:15:35.39 spid14s     Synchronize Database 'model' (3) with Resource Database.
2023-08-26 09:15:35.50 spid14s     Clearing tempdb database.
2023-08-26 09:15:35.50 spid26s     Synchronize Database 'DWQueue' (7) with Resource Database.
2023-08-26 09:15:35.50 spid24s     Synchronize Database 'msdb' (4) with Resource Database.
2023-08-26 09:15:35.55 spid14s     Starting up database 'tempdb'.
2023-08-26 09:15:35.66 spid24s     The Service Broker endpoint is in disabled or stopped state.
2023-08-26 09:15:35.66 spid24s     The Database Mirroring endpoint is in disabled or stopped state.
2023-08-26 09:15:35.67 spid24s     Service Broker manager has started.
2023-08-26 09:15:35.68 spid9s      TEMPDB configuration for Polybase completed successfully.
2023-08-26 09:15:35.68 spid9s      Recovery is complete. This is an informational message only. No user action is required.
2023-08-26 09:18:06.75 Logon       Erreur : 15372, Gravité : 16, État : 1.
2023-08-26 09:18:06.75 Logon       Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. [CLIENT : <local machine>]
2023-08-26 09:18:08.95 Logon       Erreur : 15372, Gravité : 16, État : 1.
2023-08-26 09:18:08.95 Logon       Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. [CLIENT : <local machine>]
2023-08-26 09:18:34.83 Logon       Erreur : 15372, Gravité : 16, État : 1.
2023-08-26 09:18:34.83 Logon       Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. [CLIENT : <local machine>]
2023-08-26 09:18:36.98 Logon       Erreur : 15372, Gravité : 16, État : 1.
2023-08-26 09:18:36.98 Logon       Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. [CLIENT : <local machine>]

3- The concerned application was developped many years ago by two men in order to constitute a genealogic data base of acts for their area (now more than 500K acts are registered). We were not developpers but genealogists.
The application resisted unchanged jumping from Widows 8 to Windows 10. And the last jump to Windows 11 failed.
This history explains archaic features of the application; I cannot modify my myself these features; I have to continue.

Have you simple solutions?

The instance runs on my PC, I am the only user (my friend is no more there)

The other log file (in AppData / Local ..) says

2023-08-26 09:18:35.08 Server      Microsoft SQL Server 2019 (RTM-CU22) (KB5027702) - 15.0.4322.2 (X64) 
	Jul 27 2023 18:11:00 
	Copyright (C) 2019 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-08-26 09:18:35.08 Server      UTC adjustment: 2:00
2023-08-26 09:18:35.08 Server      (c) Microsoft Corporation.
2023-08-26 09:18:35.08 Server      All rights reserved.
2023-08-26 09:18:35.08 Server      Server process ID is 15876.
2023-08-26 09:18:35.08 Server      System Manufacturer: 'GIGABYTE', System Model: 'BRi5(H)-10210E'.
2023-08-26 09:18:35.08 Server      Authentication mode is WINDOWS-ONLY.
2023-08-26 09:18:35.08 Server      Logging SQL Server messages in file 'C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2023-08-26 09:18:35.08 Server      The service account is 'FIXE-MARCEL\Marcel'. This is an informational message; no user action is required.
2023-08-26 09:18:35.08 Server      Command Line Startup Parameters:
	 -U "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Template Data"
	 -d "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf"
	 -l "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf"
	 -e "C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log"
	 -c
	 -S "SQLEXPRESS"
	 -s "F17DB520-379F-44"
2023-08-26 09:18:35.08 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.
2023-08-26 09:18:35.08 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-08-26 09:18:35.09 Server      Detected 16221 MB of RAM. This is an informational message; no user action is required.
2023-08-26 09:18:35.09 Server      Using conventional memory in the memory manager.
2023-08-26 09:18:35.09 Server      Page exclusion bitmap is enabled.
2023-08-26 09:18:35.21 Server      Buffer Pool: Allocating 2097152 bytes for 1971373 hashPages.
2023-08-26 09:18:35.21 Server      Default collation: French_CI_AS (Français 1036)
2023-08-26 09:18:35.24 Server      Buffer pool extension is already disabled. No action is necessary.
2023-08-26 09:18:35.27 Server      InitializeLaunchpadUserSid failed with error code: 0x80004005
2023-08-26 09:18:35.27 Server      InitializeLaunchpadUserSid failed. Implied authentication will be disabled. ErrorCode: 0x80004005.
2023-08-26 09:18:35.27 Server      Implied authentication manager initialization failed. Implied authentication will be disabled, failure: 0x80004005
2023-08-26 09:18:35.27 Server      Query Store settings initialized with enabled = 1, 
2023-08-26 09:18:35.28 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-08-26 09:18:35.28 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.
2023-08-26 09:18:35.28 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.
2023-08-26 09:18:35.28 spid1s      Open of fault log C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\..\log\exception.log failed.
2023-08-26 09:18:35.28 spid1s      Open of fault log C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\..\log\exception.log failed.

etc ..

Thank you

Answer 4

Erland Sommarskog 120.2K MVP

Sorry, I took your post to read that you had written a new application. It if it is an old application, I can understand why user instance is there (although, I never like them).

There is a known issue with Windows 11 and SQL Server, where Windows 11 for cretain disk drives reports a disk sector size that SQL Server cannot cope with. So that certainly sounds like a possible explanation. However, I don't see the normal error messages I'm used to see in that situation.

In any case, Microsoft has published an article with workarounds for that situtaion, and I think you should try that first. But since and old and dusty feature is involved may be something else.

Marcel Duboué 20 Reputation points

2023-08-26T15:19:51.19+00:00
Hi Erland

I saw arguments about sectors size, but I don't think that it is the reason, for:

3 weeks ago this application was running fine, under Windows 10

my disk, a Samsung SSD 980 500GB has sectors of 512K (at least as I cqn remember, for, now, when I want to execute fsutil fsinfo sectorInfo C:, I get an errors "access denied...)

It seems that the identification goes wrong; though I am the only administrator on my PC

Thanks for help
Erland Sommarskog 120.2K Reputation points MVP

2023-08-26T21:15:58.3366667+00:00

3 weeks ago this application was running fine, under Windows 10

This is issue does exist on Windows 10. It is new for Windows 11, so the fact you upgraded makes this a prime suspect.

I don't recall the exact model, but the specific model that has been causing a problem is a Samsung 9-something SSD.

You should absolutely try the workarounds in that article.
Marcel Duboué 20 Reputation points

2023-08-27T09:51:56.0966667+00:00

I want to be sure that I am correctly identified, both by Windows and SQL Server
For Microsoft, I am

working on

For SQL Server Management Studio, I am

with properties (notice Windows 10 Home !! in place of Windows 11)

Do you think that all is consistent ?

Thank you
Erland Sommarskog 120.2K Reputation points MVP

2023-08-27T09:59:43.85+00:00

I'm not sure what this question has to do with your other problem. Windows 11 appears to have some identity problem, and I also see that SSMS says Windows 10, despite that my laptop is running Windows 11 (but was upgraded to Windows 10).

Then again, the image kind of suggests that you Express instance is running normally. Did you apply the steps in the article about troubleshooting the disk sector size?
Marcel Duboué 20 Reputation points

2023-08-27T15:24:08.2066667+00:00

Thanks Erland,

I saw this entry, but I did'nt saw messages like that.
I tried to see the sectorinfo

and specifying C:, I got an access denied

which, I suppose is the proof that somerthing is wrong in my identification, or at least the identification of my rights. What is your opinion ?

Thanks
Erland Sommarskog 120.2K Reputation points MVP

2023-08-27T19:05:49.21+00:00

You need to open the Command Prompt with Run as Administrator (select that from the context menu).
Marcel Duboué 20 Reputation points

2023-08-27T20:03:35.23+00:00

Hi Erland

I don't understand what you mean.

Can you explain with more details the procedure ? (I am from the old school...)

Thank you
Erland Sommarskog 120.2K Reputation points MVP

2023-08-27T20:11:39.2866667+00:00

See attached screenshot. It happens to be in Spanish, but it should give you an idea.

(The Spanish machine is the only one I had around with a standard Windows 11 interface.)
Marcel Duboué 20 Reputation points

2023-08-28T08:41:54.77+00:00

Thanks, I've done otherwise but it works

so, my problem seems not to be there ....

Thanks for help
Erland Sommarskog 120.2K Reputation points MVP

2023-08-28T20:47:59.01+00:00

OK. So in the log file for the user instance there is:

Open of fault log C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS..\log\exception.log failed.

This is not the errorlog, that is the one you posted. Rather the message sounds like there was an exception, and for some reason this log file cannot be created/written to. But when this happens, something else have already gone wrong. You could check the Windows eventlog to see if there is something related.

But better is probably to see if you can find the database files and connect them to the actual SQL Express instance. Because if the files are damaged, it is game over unless you have a backup.
Marcel Duboué 20 Reputation points

2023-08-29T12:28:55.25+00:00

Hi Thanks Erland

The line you have mentionned are the 37th and 38 th :

Previously was a first error, lines 30 to 32

You probably understand what it means, not me (my first experience of computer was in 1963 (yes, and I'm not completly out ....). I am retired since 2003, so my knowledge is fixed to that date....

It is why my intellectual activity depends on that Visual Studio application.

So if you guide me, I'm able to do all the necessary tests

1- Where can I find the Windows eventlog ?

2- Is the master.mdf file (in /Users/Marcel/AddData/Mocal/Microsoft/Microsoft SQL Server Date/SQLEXPRESS) the one I have to connect to my instance ?

3- How ? With SMSM ?

Thanks
Marcel Duboué 20 Reputation points

2023-08-29T12:35:25.08+00:00

Hi, I have forgot a crucial point

My application is a multibase one; the only action it does at the beginning is to open 'master'; then I can choose one other .mdf file; for I can manage with several databases, depending of the places
Erland Sommarskog 120.2K Reputation points MVP

2023-08-29T21:23:04.21+00:00
I'm afraid that I don't understand those three lines. The Launchpad process has nothing to with user instances, to my knowing. But maybe this is another launchpad. Anyway, that's why I glossed over them.

The Windows EventLog has been around a long time. It was there already in the nineties, before you retired. :-) One way to reach it is to right-click My Computer and select Manage.

I would guess your database is somewhere in C:\Users\Marcel\AppData\Local\Microsoft\Microsoft SQL Server Data\SQLEXPRESS. I say guess, because I have little experience with user instances. It's not really the master database you are interested, but the real database, whatever the names of those files may be.

Copy these files into C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA, and tem from SSMS say:

CREATE DATABASE SomeDBName ON (FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\Filename.mdf', FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\DATA\Filename.ldf' ) FOR ATTACH
Marcel Duboué 20 Reputation points

2023-08-30T09:03:40.23+00:00

Hi Erland

1- I've found the journal (my problem is that, depending on the Windows versions since 1990 and Windows 3... it is in different places). All the SQL Server errors are writen

Nothing new, it is exactly the message I got.

2- relatively to databases : I tried to Create and Attach a DB as you said, result

Two questions :

2.1 Is you syntax correct ?

2.2 On my french system, the directories have different names;

I have already notices that english syntax is better, do you agree ?

Thanks

Tomorrow I'll got 80 !!!
Erland Sommarskog 120.2K Reputation points MVP

2023-08-30T21:46:03.2666667+00:00
2.1 Is you syntax correct ?

To be honest, I wrote it with some guesswork and did not test, so your error message made me a little nervous. However, I ran this successfully:

CREATE DATABASE Northwind ON (FILENAME = 'S:\MSSQL\DIXNEUF\northwnd.mdf'), (FILENAME = 'S:\MSSQL\DIXNEUF\northwnd.ldf') FOR ATTACH

Looking closer at your screenshot, I see the error. You have .mdf for both files. One of them should be .ldf.

As for Programmes vs Program Files, that is little of a mystery with some language overlay over the English names in Windows, so I think both will work.
Marcel Duboué 20 Reputation points

2023-08-31T08:11:37.11+00:00

Hi, thank you for you enormous help.

1- First try

2- Second try (with english repertory )

So, the path is good, but I can't create that DB

3- third try : with an existing DB

=> It seems a matter of rigths ? Do'nt you think so ?

4- If it can help you : I have the same application running under Windows 10 on an old portable (it's an ancien habit, to keep a version before changing the environment); I can't easily work with that version but it works, so I can make on measures, experiments that are usefull. It is exactly the same configuration that was previously on my PC (now unfortunately with Windows 11)

Thatks for all
Erland Sommarskog 120.2K Reputation points MVP

2023-08-31T20:57:57+00:00

If you have the database and application on other machine, that may be the best solution. I am not really optimistic that we can get your user instance to work (because I have very little idea what is wrong with it.)

The error in the second attempt suggests that there is no file Essai.mdf in that folder at all. If there had been a permissions issue - which would not surprise me - the error number would be 5, Access is denied.
Marcel Duboué 20 Reputation points

2023-09-01T07:26:43.6+00:00

Hi,

1- Obviously there was no file Essai.mdf in the 2d attempt, for the reason that I think that the aim was to create it !!!
2- It is why, for the third attempt I used an existing file. Same result.

3- So, what do you suggest, using my old PC ? Tell you where was the files ? Give you copy of the initial code ?

I precise that all was running normally for several years, when, 3 weeks ago I upgraded (Up ? or down ?) to Windows 11...

Thanks to follow me
Erland Sommarskog 120.2K Reputation points MVP

2023-09-01T21:15:26.4433333+00:00

The purpose of FOR ATTACH is to attach existing database files to a different instance that they origined from, both the .mdf and the .ldf file. Make sure that you have both in place. You say "same results" - check the error message carefully, maybe the part from the OS at the end has changed?

3- So, what do you suggest, using my old PC ?

If that is an option for you, yes. We may be able to attach the files directly to the Express instance, but then you need to change the connection string, which may mean change the code of the application.

Tell you where was the files ? Give you copy of the initial code ?

Not sure what you mean here. I have no interest in your files.

I precise that all was running normally for several years, when, 3 weeks ago I upgraded (Up ? or down ?) to Windows 11...

But now something broke. New versions of OSs does not only mean new features. It may also mean that old features, less secure, may be removed.
Marcel Duboué 20 Reputation points

2023-09-02T08:22:17.55+00:00

Hi Erland

1- I reentered the 3d attempt with 2 existing files (created by the ancien instance of course) and it seems to work

2- But my application still aborts immediatly

attemting to open that DB, see the code below:

I first show images and titles then try to open the known DB

as mentionned in the code, the two files for the called DB were in the same directory of the executable (startuppath) : CharneGroupe.exe

3- For it does'nt succeed, I try to start in the initial Catalog : 'master' and that, too, fails, and gives my message

In the code there are old traces, as comments now, of other attempts, should I unmask they ? In order to see the delivered messages ?

Thanks to follow me

The process stops here with the message I gave you upper.
Erland Sommarskog 120.2K Reputation points MVP

2023-09-02T08:32:20.43+00:00

Of course the application still fails, because it still tries in the same place. But since you have the source code for the application, remove everything with User Instance=true. Move this Catalogue database to the DATA folder like the other database and attach it. The remove everything with AttachDBFilename (another option I've never been able to understand the point of), and just say Database=Catalogue.

Marcel Duboué 20

Hi

It's not so simple for me, for at least 2 reasons:

1- There is e verry long time that I hav'nt touch this code

2- When I jumped from Window 8 to Windows 10, I automaticaly upgraded Visual Studio too, anf plenty of lines were added, that I hardly understand

Nevertheless, I want to recover my application (which, I recall, was perfectly running before "upgrading?" to Windows 11). To do so, I am ready to do modifications.

3- You say "remove everything with "User Instance=true" : done, about 10 occurrences

4- move and attach Catalog DB, done till yesterday

5- remove everything with AttachDBFilename : Oups !!

5.1 Two occurences; both refers to a place that no more exists :

SettingsFile xmlns="http://schemas.microsoft.com/VisualStudio/2004/01/settings" CurrentProfile="(Default)" GeneratedClassNamespace="My" GeneratedClassName="MySettings" UseMySettingsClassName="true">
  <Profiles />
  <Settings>
    <Setting Name="RelevésChGrConnectionString" Type="(Connection string)" Scope="Application">
      <DesignTimeValue Profile="(Default)">&lt;?xml version="1.0" encoding="utf-16"?&gt;
&lt;SerializableConnectionString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
  &lt;ConnectionString&gt;Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Users\Marcel\Documents\Développements\Visual Basic 2005\Evolution relevés\RelevésChGr.mdf";Integrated Security=True;Connect Timeout=30&lt;/ConnectionString&gt;
  &lt;ProviderName&gt;System.Data.SqlClient&lt;/ProviderName&gt;
&lt;/SerializableConnectionString&gt;</DesignTimeValue>
      <Value Profile="(Default)">Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Users\Marcel\Documents\Développements\Visual Basic 2005\Evolution relevés\RelevésChGr.mdf";Integrated Security=True;Connect Timeout=30</Value>
    </Setting>
  </Settings>
</SettingsFile>

=> What must I delete ?

I hav'nt delete, I'm waiting for you ....

Thanks

Marcel Duboué 20 Reputation points

2023-09-02T13:13:26.04+00:00

Hi (second this day)

Here is all the concerned paragraph
Erland Sommarskog 120.2K Reputation points MVP

2023-09-02T14:30:37.1533333+00:00

I would say that if you want help with the Visual Studio stuff, that is a question for a different tag. From an SQL Server perspective, the answer is that user instances is a feature that "smells funny", and chances to get your user instance to work is slim. At least I don't know what's wrong with it, and I don't know how to repair it. Or if it is repairable. On the other hand, changing the source code of the application to use the regular SQLEXPRESS instance should be straightforward from my perspective. If it feels like an unsurmountable obstacle, that may be because you waited too long with fixing the code.
Marcel Duboué 20 Reputation points

2023-09-02T17:23:24.5866667+00:00

Hi Erland

So, you seem to consider that, if I want to keep Windows 11, I'll probably be obliged to reconstruc my application ....

The choice of User Instance was not mine. How can I be convinced that it is linked with Visual Studio ?

Otherwise the only solution I have is to turn back to Windows 10. Do'nt you think so ?

Is it alway possible (I migrated to Windows 11 on auguste the 8th, appromatively)
Erland Sommarskog 120.2K Reputation points MVP

2023-09-02T17:35:21.95+00:00

Reverting to Windows 10 may or may not resolve the problem. If the issue is that Windows 11 has security features or something else that breaks user instances in general, yes, going back to Windows 10 will help. But if the issue is that something fell apart in the upgrade, it may still be broken when you revert.

I've been asking myself "could this be a general problem with Windows 11 and user instances", but I'm leaning towards that this is unlikely. While user instances are a mouldy feature, it is likely that there are quite a few users like you who are running with a user instance. Thus, if this would be a general issue with Windows 11, I would have heard of it before.

But maybe more importantly, reverting back to Windows 10 is not really a serious option. I think Microsoft has said that it will be supported until 2025, but sooner or later, you would need to make the move anyway. Also, Windows 11 is a more secure operating system.

What you possibly could do is to install a virtual machine running Windows 10, and run this program in the VM. But from my point of view, while I'm not a .NET programmer, changing the program to use a regular instance is not a difficult task.

Answer 5

The error code 0x80004005 is a generic error that can occur due to various reasons. It is difficult to determine the exact cause of the error without more information. However, based on the log file you provided, it seems that the error occurred while creating a user instance of SQL Server. This could be due to a failure to start the process for the instance user.

I suggest you try the following steps:

Ensure that you have installed all the latest updates for Windows 11 and SQL Server 2019 Express.
Check if your SQL Server service is running. If not, start it.
Ensure that your SQL Server service account has sufficient permissions to access the necessary files and directories.
Try running SQL Server Management Studio as an administrator and see if it resolves the issue.
Check if there are any antivirus or firewall settings that might be blocking SQL Server from running properly.

If none of these steps work, I recommend you post your question on a relevant forum or community where experts can help you with your issue.

I hope this helps!

Erland Sommarskog 120.2K Reputation points MVP

2023-08-27T20:01:41.7733333+00:00

If none of these steps work, I recommend you post your question on a relevant forum or community where experts can help you with your issue.

Why would this not be a relevant forum? Or did you forget to delete that paragraph when you copied and pasted from Chat GPT? If you indeed use chat GPT for your answer, you are violating the usage policy for AI in Microsoft Q&Ahttps://learn.microsoft.com/en-us/answers/support/ai-usage-policy.

Share via

0x80004005 error when connecting to SQL Server 2019

5 answers

Your answer