Message failed at endpointQueue.Timeouts queue

[ramonsmits]

It’s clear that NOCOUNT is still ON. Did you really set it to OFF at the Server?

Alternatively, you can use a custom connection factory as mentioned here:

NHibernate.StaleStateException: Batch update returned unexpected row count from update; actual row count: -1; expected: 1

Can you check if you have NOCOUNT on or off on the SQL server instance? NHibernate requires this to be OFF so that it gets the row count returned. If this is not possible then you can customize the connection factory used by NHibernate to disable this. The code for this can be found at the following issue: Make usage of NHibernate compatible with `SET NOCOUNT ON` DB-wide setting · Issue #112 · Particular/NServiceBus.NHibernate · GitHub Code: public class CustomDriverConnectionProvider : NHi…