When creating your stored procedures be sure to “SET NOCOUNT ON;”
On my SQL Server, the default setting is OFF so if explicit initialization is excluded the default behavior will create an error on the Qlik side (load script).
![usp_withTmpTbl_QlikSenseExample_01.png](/legacyfs/online/188969_usp_withTmpTbl_QlikSenseExample_01.png)
If you didn’t set up your stored procedure correctly you will likely see something like the example below:
![usp_withTmpTbl_QlikSenseExample_02.png](/legacyfs/online/188970_usp_withTmpTbl_QlikSenseExample_02.png)
![usp_withTmpTbl_QlikSenseExample_03.png](/legacyfs/online/188971_usp_withTmpTbl_QlikSenseExample_03.png)
** I would like to thank Gareth Wilson for teaching me how to correct this error! **
https://community.qlik.com/message/1411505#1411505