[URGENT] MSSQL DB no more accessible (Timeout Expired) after upgrade to 2025.3

Hi Pico,

I sent you a private message with a link to book an emergency meeting.

We'll troubleshoot this in live and I'll share our findings in this public thread.

Best regards,

Hi Pico,

I sent you a private message with a link to book an emergency meeting.

We'll troubleshoot this in live and I'll share our findings in this public thread.

Best regards,

@Marc-Antoine Dubois

I have rollback to 2025.2.30 .

I will be available at 15.00 cest.

We can repeat the upgrade process together.

P

Hi Pico,

Sounds good to me!

I've scheduled on your behalf at 3 PM CEST. You'll receive an email confirmation.

We'll talk soon.

Best regards,

Hi,

The solution was to increase the connection timeout from 5 seconds to 10 seconds. We found this solution from another thread: https://forum.devolutions.net/topics/43457/rdm-connecting-to-windows-sql-server-always-throws-error-when-connection-first-time-after-starting-rdm