go to post Alex Cashell · Apr 25, 2022 Solved it, using wireshark we can see MSSQL is responding that it can't find the stored procedure, the solution is to remove the ";1" from the stored procedure name and it works perfectly.