At least the error message suggests you run into the same issue. When I understand it right, that error pops up when some of the parameters provided to the report is used as an integer argument in the query. If that is your case, then the case also suggests a workaround… What I think is not quite clear though is why it works locally then.