daniel.siljanovski wrote:Try to change the 'Connect Timeout=60' to let's say 180 or remove it completely (even if its not related to the command (query, transaction) execution timeout its worth trying because it might be related to some commit/rollback timeout issue (if any)).
I have set the timeout to 180 but I still get the same error. Here is the SQL log:
2022-05-25 16:54:42.06 spid18s Starting up database 'Nopcommerce'.
2022-05-25 16:54:42.06 spid17s Starting up database 'msdb'.
2022-05-25 16:54:42.07 spid6s Starting up database 'model'.
2022-05-25 16:54:42.09 spid6s Polybase feature disabled.
2022-05-25 16:54:42.09 spid6s Clearing tempdb database.
2022-05-25 16:54:42.11 spid18s 62 transactions rolled forward in database 'Nopcommerce' (16:0). This is an informational message only. No user action is required.
2022-05-25 16:54:42.13 spid18s 0 transactions rolled back in database 'Nopcommerce' (16:0). This is an informational message only. No user action is required.
2022-05-25 16:54:42.13 spid18s Recovery is writing a checkpoint in database 'Nopcommerce' (16). This is an informational message only. No user action is required.
2022-05-25 16:54:42.15 spid6s Starting up database 'tempdb'.
2022-05-25 16:54:42.23 spid16s The Service Broker endpoint is in disabled or stopped state.
2022-05-25 16:54:42.23 spid16s The Database Mirroring endpoint is in disabled or stopped state.
2022-05-25 16:54:42.24 spid16s Service Broker manager has started.
2022-05-25 16:54:42.34 spid4s Recovery is complete. This is an informational message only. No user action is required.