OK - truck loads of folk have reported this problem - but I cannot solve it - so apologies for repeating the question...
My SQL Server 2005 Report is developed on the same server as it is run.
I have SQL Server 2005 SP2 installed. The report language is set as en-GB.
The browser language setting is en-NZ.
The report previews fine - I pick May 22 from the picker and it appears as 22/05/2007 in the report parameter text box - which since I am in NZ is exactly as I want it.
I deploy the report - If I run it from the report manager virtual directory the date picker performs as above i.e correctly.
I run the deployed report from the report server virtual directory and here is where the problem occurs - selecting May 22 from the date picker produces 05/22/2007 in the report parameter text box and produces the error
"The value provided for the report parameter 'StartScheduledDate' is not valid for its type. (rsReportParameterTypeMismatch)"
thanks for any help here - this problem has made this a ridiculously expensive report!
honestbob wrote:
I deploy the report - If I run it from the report manager virtual directory the date picker performs as above i.e correctly.
I run the deployed report from the report server virtual directory and here is where the problem occurs
Pardon me, what's the difference between the 2 sentenses? They both sound like you run from http://localhost/Reports?
I'd suggest looking at the Regional settings in your machine, and server, to make sure they're the same
e.g. Canada default is DD/MM/YYYY, while USA default is MM/DD/YYYY
|||bob,
what i have done with this in the past is always do a CDate() on the output of the calendar control before trying to use that output, then i can Format() it any way i like. I also found when trying to force it to a non-US date format i couldn't then use the Preview tab in the IDE to check my report, as that version of the control insists on rendering/outputting everything in US format, regardless of what culture you have your report/IE/server set to.
So in summary, i find the web version of that control works fine if you CDate everything before using it. And like the previous poster said, check the regional settings on your report server.
|||I was having the same problem but i managed to fix it.
edit the file "ReportViewer.aspx" on the reporting services machine.
it's in the "C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\Pages" by default,
and add the highlighted part with the desired culture value.
It solved the problem in my case.
<%@. Register TagPrefix="RS" Namespace="Microsoft.ReportingServices.WebServer" Assembly="ReportingServicesWebServer" %>
<%@. Page Language="C#" AutoEventWireup="true" Inherits="Microsoft.ReportingServices.WebServer.ReportViewerPage" Culture="pt-PT"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head id="headID" runat="server">
<title>Report Viewer</title>
</head>
<body style="margin: 0px; overflow: auto">
<form runat="server" ID="ReportViewerForm">
<RS:ReportViewerHost ID="ReportViewerControl" runat="server" />
</form>
</body>
</html>
Hope this will solve your problem too.
Tiago Certal
|||yes, that solved my problem too. I, too have tried fiddling with the regional settings on the database, the server, the local, the client computers etc. I would keep having the problem in IE, but not in Firefox. Firefox was fine.
so I tried to add the culture thing in, like Tiago suggested. only problem is that I think PT is portugese, so I had to use "en-CA" instead. Which then magically made the reports displayable in IE. Thank you Tiago!
problem is that now Firefox is having the same error. WHAT IS GOING ON?
No comments:
Post a Comment