The value provided for the report parameter 'todt' is not valid for its type

Question

The value provided for the report parameter 'todt' is not valid for its type

it.development

Mr or Mrs. 500

Points: 599
More actions
September 1, 2010 at 7:25 am

#223294

Hello Forum,
I need little help from you. I m stuck due to this problem. I have developed report in SSRS. I m matching dates here if the date is >= and <= of input paramter's date. Here in Report developer its showing calender for choosing date.
When i select the date and press view report button, the data has been disappear from the date parameter and gives subject error.
"The value provided for the report parameter 'todt' is not valid for its type"
Can anybody have idea.
Best Regards,
Chintesh Soni

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Luke L SSC-Dedicated Points: 35547 More actions · Answer 1

I'm guessing this is gonna be about date formats... IE. by default SSRS/SQL etc expect dates to be dmy not mdy. More than likely your collation for SQL server and your regional settings for your computer, Report or SSRS setup are not consistent with each other. HEre's a link from MSDN talkign about how the regional settings affect SSRS... http://msdn.microsoft.com/en-us/library/ms156493.aspx

Also, you might just need to format the parameter value in the dataset not the parameter itself, just the mappign portion of the dataset where you specify @todt = todt.value Something along the lines of: =FORMAT(Parameters!todt.Value,"dd-MM-yyyy") may work.

-Luke.

To help us help you read this[/url]For better help with performance problems please read this[/url]

it.development Mr or Mrs. 500 Points: 599 More actions · Answer 2

Thanks for prompt response.

I am using SQL Server 2005 and SQL Server Business Intelligance Development Studio.

Version Details of SQL Server 2005 :

Microsoft SQL Server Management Studio9.00.1399.00

Microsoft Analysis Services Client Tools2005.090.1399.00

Microsoft Data Access Components (MDAC)2000.085.1132.00 (xpsp.080413-0852)

Microsoft MSXML2.6 3.0 5.0 6.0

Microsoft Internet Explorer7.0.5730.13

Microsoft .NET Framework2.0.50727.3053

Operating System5.1.2600

version details of SQL Server Business Intelligance Development Studio

Microsoft Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)

Microsoft .NET Framework Version 2.0.50727 SP2

Installed Edition: IDE Standard

SQL Server Reporting Services

Microsoft SQL Server Reporting Services Designers

Version 9.00.1399.00

when i have checked the lenguage in reports property it was showing english US however my machines lenguage is english UK. Does it makes some difference. I have changed but no result found.

We have updated SP 3 in SQL Server 2005. Can we update the SP 3 without updating SP 1. Because before SP 1 it was a bug in the SQL Server 2005 if u remember.

Pl guide for the same.

Thanks..

Chintesh Soni

Luke L SSC-Dedicated Points: 35547 More actions · Answer 3

Unfortunately, there are so many variables that I can't really offer good guidance for you. Additionally I'm in the US so it kinda just works for me, I've never personally had to go through finding a solution. Most of the places I've read about this issue in the past have talked about making sure things matched. Db collation, workstation, report server etc. They all have regional settings and the MS document I posted previously does a pretty good job of going through what is affected by which setting.

Most of the solutions I've seen where the workstation regional settings could change were done using the format string I previously posted. You use that in your data set properties where you assign the variable in your TSQL code to the parameter value from your report.

-Luke.

To help us help you read this[/url]For better help with performance problems please read this[/url]