July 5, 2005 at 1:46 pm
I have a report with 2 datetime parameters. When I preview the report in VS it appears to be working wonderfully. Yet, when I deploy and run it I always get rsReportParameterTypeMismatch error on the second datetime field. I have checked and double checked the way I am entering the date and it is the same as the field that appears to work.
Any ideas?
Thanks,
Eva
July 5, 2005 at 2:06 pm
I have had this problem as well I find if I explicity cast the datetime parameter into the format I wnat i.e. not US tehn it alwasy works fine.
I don't know why it does it but this has worked for me.
hth
Dave
July 5, 2005 at 2:12 pm
I am using US format though. Shouldn't that work then? Or am I missing something in what you are saying?
July 5, 2005 at 2:23 pm
No your not missing anything I'm in the UK and keep having problems with VS deciding to go all US on me for no reason.
Just assumed you might have had the same issue as I encountered.
We also get administrators setting up some databases as us english and some as english just to make our lives miserable.
Dave
July 6, 2005 at 6:50 am
Yeah, I can see why that would be annoying. I feel for you.
However, that is not my issue. Does anyone have any idea what could be causing one date to work fine but another to fail. And especially why would it work fine in preview but not after being deployed....
Thanks,
Eva
July 14, 2005 at 9:21 am
Hello evaleah,
i am facing with the same "rsReportParameterTypeMismatch" error,
i know that its because when the server executes the datetime report parameters, it turns the format from mm.dd.yy to dd.mm.yy, and i do not know how to avoid this, or why this happens.
if you find a solution to this problem, can you give it to me so i can use this reporting tool.
thank you
July 14, 2005 at 9:23 am
I ended up treating my datetime parameters as strings instead and now it works fine.
Annoying, but it works....
Eva
July 14, 2005 at 12:42 pm
I still haven't gotten this thing to work and I am frustrated beyond belief..... It works if I leave them as strings and I have NO other parameters. But if I add even one other parameter the whole thing busts again.
*sigh* I must admit I am getting to be less and less a fan of this product.
Can you tell me how you cast the parameter into the format you wanted? I can't seem to find a way to do that and am willing to try that at least!
Thanks,
Eva
September 21, 2006 at 5:09 pm
I'm having a similar, but not identical problem - and I have no solution either.
In my case I have the reports running on a PC (let's call it bob) under Reporting Services 2005. I have two reports, one that links to the other using a 'jump' to.
Working on the server (bob) itself, using it as both client & server, I can run the first report fine but when I click on the hyperlink to go to the second report, I get the type mismatch error.... BUT...
If I do exactly the same thing using the browser on my development PC (but still running the reports on bob as the server, using the same datasource and the same parameters for the initial report) then it works fine !
I suspected maybe it was a problem with different regions on the client and server end (even though I've found plenty of people stating the server should read the date format from the client), but I've checked and both the PC's are set to the same time zone, regional settings and input locale. Added to which, it doesn't make sense that it works from a PC other than the server, but not from the server where the formats should be the same on both ends.
I'm confused, and also liking this product less and less all the time.
January 18, 2007 at 2:32 am
I'm having the same problem but with a float... - and cant find any solution...
I'm confused, and also liking this product less and less all the time.
October 25, 2007 at 2:57 pm
I was experiencing the same problem with a date. In my case the report has been deployed for months with no problem.
Today someone in Canada was reporting a problem. To make a long story short, reporting server uses the "Language" parm in the browser (Internet Options-->General Tab-->Languages). When it posts back to the server, it pulls the locale from the Environment vars and validate the dates based on that. Setting U.S. to the first item in the language list, validated my date properly.
October 26, 2007 at 12:43 pm
people, the way to solve this problem is :-
Suppose RP_date is the parameter. let it be of type datetime only.
Create a new hidden parameter T_RP_date. let it be of string datatype and its value should always be date(RP_date)&'/'&month(RP_date)&'/'&year(RP_date).
Now the T_RP_date will always be of format dd/mm/yyyy format. now just convert T_RP_date to format 101.... hope u people got wat i meant...this is just the rough outline...
It worked for me and even better, i changed the language setting of the report to user!language, so it displays the date in local date format also in the report.(eg : dd/mm/yyyy in the US and mm/dd/yyyy in the UK)
if still u r not clear, ciontact me at jason143@gmail.com. i will be happy to share the exact way i have done.
October 27, 2007 at 1:51 am
Thanks for those two responses, when I next encounter the problem in RS I'll give them each a try.
December 21, 2008 at 10:22 pm
Hi frnds,
I was having the same problem...Viewing a report (created in SSRS 2005) in en-US , it works fine. But when I change language to German (de), my date time field gives the 'rsReportParameterTypeMismatch' error... I did a back-breaking search on this and found it's a MS bug and we require a hotfix for SSRS 2005. This issue has been taken care of in SSRS 2008.
Please see the following link for this -
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=271928
December 22, 2008 at 3:32 am
But u can still use the workaround i mentioned above to get ur code working.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply