We have faced this issue as well and including the “SET NOCOUNT ON” to custom triggers to resolve this issue. Hence, you need to check for “SET NOCOUNT ON” statement is available in custom triggers or stored procedures. If it is not available then alter that trigger / procedure to include the abovesaid statement. Hope it helps
↧