MSSQL Keeps restarting after upgrading to 2026.3.0

[nickjossy]

Steps To Reproduce

I have a self hosted instance that auto-updates each week using the Updateself & update scripts.

After updating last night the MSSQL server attempted to update the database using script repl_upgrade.sql but eventually crashed. It restarts and does the whole thing again.

errorlog.txt

crash.txt

crash.json

Expected Result

Database update should complete and allow logon.

Actual Result

MSSQL keeps restarting itself.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.3.0

Environment

Self-Hosted

Environment Details

Hosted on Synology RS820+ running DSM 7.3.2

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-33961
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-33961

[aughur]

Got exactly the same problem on Synology DS1621+ DSM 7.3.2.

[bglf83]

I have the same issue as well, running a Synology DS1621+ with fully updated DSM 7.3.2.

It's also being tracked on the Bitwarden Community forums Bitwarden 2026.03.0 MSSQL Container Problem.

[e42sh]

Same ... on DS720+ on DSM 7.3.2

[SergeantConfused]

Hello @nickjossy,

Thank you for your report. This is already being tracked and investigated internally, and I'll keep this GitHub report open for now for external visibility; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

By the way, could you all list the exact version of Docker Engine you are using? Also, if you can, please try updating it and also updating the operating system (if needed) and report back if that changes anything. Please remember to mirror/image the server so that you'd be able to roll back, in case anything goes awry.

Thank you again,

[nickjossy]

I've got the latest versions of Synology and Container Manager (their name for Docker). This reports as:

Docker version 24.0.2, build 610b8d0

Synology DSM 7.3.2-86009 Update 3

Linux 4.4.302+ #86009 SMP Wed Nov 26 18:45:09 CST 2025 x86_64 GNU/Linux synology_denverton_rs820+

[danieled-it]

Docker version 24.0.2, build 610b8d0
Synology DSM 7.3.2-86009 Update 3
Linux DiskStation 4.4.302+ #86009 SMP Wed Nov 26 18:45:32 CST 2025 x86_64 GNU/Linux synology_apollolake_218+

[BodoHuberPhy]

All are most recent versions for my DS1819+:

Docker version 24.0.2, build 610b8d0
Synology DSM 7.3.2-86009 Update 3
Linux DiskStation2 4.4.302+ #86009 SMP Wed Nov 26 18:45:09 CST 2025 x86_64 GNU/Linux synology_denverton_1819+

I had to restore to bitwarden 2026.2.1 to have a running system.

[aughur]

DS1621+
Docker version 24.0.2, build 610b8d0
Synology DSM 7.3.2-86009 Update 3
Linux drops 4.4.302+ #86009 SMP Wed Nov 26 18:19:20 CST 2025 x86_64 GNU/Linux synology_v1000_1621

[teaboyteaboy]

Unfortunately didn't catch this before I tried to update :)

Synology DS923+
Docker version 24.0.2, build 610b8d0
Synology DSM 7.3.2-86009 Update 3
Linux 4.4.302+ #86009 SMP Wed Nov 26 18:29:22 CST 2025 x86_64 GNU/Linux synology_r1000_923+

Errors seen after dbupdate timeout:

Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=73; handshake=112; [Login] initialization=2; authentication=8; [Post-Login] complete=29012;
---> System.ComponentModel.Win32Exception (258): No error information
at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, SqlCommand command, Boolean callerHasConnectionLock, Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock, Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, TimeoutTimer timeout, Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool, Func3 accessTokenCallback)
at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open()
at Bit.Migrator.DbMigrator.PrepareDatabase(CancellationToken cancellationToken) in /source/util/Migrator/DbMigrator.cs:line 89
at Bit.Migrator.DbMigrator.MigrateMsSqlDatabaseWithRetries(Boolean enableLogging, Boolean repeatable, String folderName, Boolean dryRun, CancellationToken cancellationToken) in /source/util/Migrator/DbMigrator.cs:line 45
at Bit.Setup.Program.PrepareAndMigrateDatabase() in /source/util/Setup/Program.cs:line 197
at Bit.Setup.Program.Update() in /source/util/Setup/Program.cs:line 161
at Bit.Setup.Program.Main(String[] args) in /source/util/Setup/Program.cs:line 59
ClientConnectionId:1509ab95-47e8-4a36-a525-87de7c1115b8
Error Number:-2,State:0,Class:11

[e42sh]

Unfortunately didn't catch this before I tried to update :)

Same, but a downgrade of mssql to 2026.2.1 in compose yaml helped me.

[DimebagCFH]

Dears,
Does the new bitwarden update fix the current issue ?

[Acrobutt]

Dears, Does the new bitwarden update fix the current issue ?

not in 2026.3.1, had to back to 2026.2.1 once again

[andrevanduin]

Right around the same time that the .claude folder is added to the repo everything starts to break. Another victim of AI slop. Time to look for a different password manager sigh...