Originally posted by biz-engineer
The error message means what it says. If some input parameters are null (empty) or if such parameters inputs do not fit the proper format for the software to run properly, the internal software error checking detects that the values of input parameters are incorrect and reports a error. You need to fill the empty fields in page setup with some dummy data, and then the error messages will disappear. Does it makes sense to you now?
That's a good explanation, but actually, the error message is, itself, erroneous, but it's a mistake commonly made; what's really in error is an argument, not a parameter, but that's a software engineer's distinction. (An "argument" to a function is an actual value; a "parameter" can be thought of as a variable that can assume a range of values to be supplied in the form of arguments.)
On the other hand, one wonders why users should have to know stuff like that; it is, shall we say, unfortunate design. If the error message is not communicative, then I'd say the software is not really usable, and therefore defective.
"In the old days", we used to deal with error messages that looked sort of like this: "IEF54324 - Probable user error, please meditate and resubmit", but then there was a massive book in which every possible error message was listed in order of its identifier with a complete description of what it meant and what was necessary to correct it.