Hey Alex,
the exception you see is that ReportServer is trying to load a key store to send in order to sign the email and potentially encrypt it. This can be safely ignored unless, of course, you do want to use S/MIME.
About the configuration issue. We have now introduced an automatic mechanism that installs the most important configuration files on first startup. This will come with the next (minor bugfix) version which should be out this or next week.
As for the main question. The date parameter currently does not offer a different date format. I’ve created a ticket for this. The format displayed by the date picker, however, is not the format in which the result gets passed on to the query. That is, the result is passed on as a date object and the jdbc driver ensures that the transformation is done correctly when it is used in conjunction with a column of type date. For example, in the following query I have a column of type TIMESTAMP (in mysql).
SELECT * FROM T_AGG_ORDER WHERE
OR_ORDERDATE > ${P_DATE_FROM} AND OR_ORDERDATE < ${P_DATE_TO}
Here I can simply use the parameter as is, and the jdbc driver will ensure that the date object passed on by ReportServer is correctly transformed. In case I have the date stored as character date, let’s say, in format dd/MM/yyyy, the easiest is to use
SELECT * FROM TABLE WHERE
MYDATE = ${_P_DATE_FROM.format(‘dd/MM/yyyy’)}
Note the underscore before the the parameter’s key. Regrettably, I’ve just found a minor bug concerning this feature, that is, this will in the current version only work if the date parameter was changed from its default setting. The bug is already fixed in the SVN and the fix will be part of the upcoming release. To work around this you might do something like
SELECT * FROM TABLE WHERE
MYDATE = ${null == _P_DATE_FROM.value ? '26/11/2010' : _P_DATE_FROM.format('dd/MM/yyyy')}
I’ve also added a ticket to allow to specify the output format of date parameters directly, when configuring the date parameter.
Cheers
Arno