While working with Entity Framework (EF), sometimes the EF doesn’t recognize the columns returned by the Stored Procedure.
1) If the db procedure is using temporary table (e.g. #tempTable), EF don’t recognize the MetaData from the procedure.
2) If multiple select … statements exists in db procedure.
Before executing procedure or beginning of db procedure set the FMTONLY to ON like below line:
SET FMTONLY ON
This will force EF to read the metadata from Temp tables
There would be performance issues with approach because the way EF read the metadata from temp tables is to execute them multiple times.
Instead of using the temp tables, create table variables and use them to store data temporarily. While using this option you don’t need to set the FMTONLY setting.
Using the table variables will be faster than FMTONLY option.
Find more detailed information at
I was getting this exception while working with the GDI images in asp.net.
My requirement was to upload the image from client then resize it and display.
The code was working fine on local development machine, but on production server it was throwing “Parameter is not valid” exception.
The general cause of this is that non-availability of resources required to generate a valid image file.
In my case the reason was that the destination folder was having read-only permissions, which was causing the code to hault while saving the processed image back to server.
For the resources I read during this issue, I found out some more reasons, these can be following:
1) Invalid source image path passed to the Drawing/Image/Bitmap object.
2) Invalid destination image path passed to the Drawing/Image/Bitmap object.
3) Corrupted/incomplete byte array.
4) Disposing of Source object before completing generation of new Image.
5) Folder write permissions while saving the new file.