HTTP 200 response code showing as error in Blazemeter

I am executing a jmeter script which has a response message as HTTP 200, the same works fine on local machine. But when doing the same in Blazemeter, it marks the HTTP 200 response as an error and does not sample with the error as "The response was null", thus increasing the overall% error.

Note. Even "Recover all embedded resources" is not checked in the script.

Any help is appreciated!