Reporting Services :: SSRS Report Parameters Getting Reset After Hitting Apply (Sharepoint Integrated Mode)
Mar 6, 2015
We have SSRS reports (pointing to SQL 2012) containing cascading parameters that we have deployed on SharePoint 2013 and once a user makes a selection to the parent parameter, child parameters are getting refreshed based on the selection in the parent parameter and then we see this:
Once we hit Apply, the Loading image comes up and approximately10 seconds later, The whole webpage gets refreshed and the parameter selections get reset to default parameters.Â
This is getting frustrating because there are about 10 parameters in the report and once a user makes selections and hit apply if the page gets reset, the user has to make all the selections again.
We are working with Microsoft support on this who suggested us to increase the timeout setting of DistributedCache service on all our SharePoint servers which did seem to work initially but I do see this issue happening occasionally.
i have created an report which retrieve data from table which contains a datetime field. The data of that particular field is stored in UTC time. when i navigating the report from sharepoint site i wish the datetime field will be converted into local time based on the selected timezone of the user.
issue where SSRS reports being executed from a report library in SharePoint intermittently are reloaded after hitting the apply button to run. Â We are using SSRS 2010 and SharePoint 2013 in integrated mode. So a user clicks on the report, fills in the parameters and hits apply. Maybe 70% of the time the report runs fine. Â The other 30% the report just reloads and wipes out any parameter selections. We do have a load balancer in front of the web servers.
I've ran fiddler to capture some of the error logging.
Things we have tried. Multiple versions of IE 8,9,10,11, Firefox, Chrome. Â All browsers seem to exhibit the behavior.
We ran so more traffic monitoring and it doesn't appear on these refreshes that report actually connects to the data context so it seems to be failing prior to that. (Possibly at the SharePoint server. Logging from the server apparently didn't show much in terms of when this occurred) It doesn't seem to matter if the report has 1 or 10 parameters.Â
We did notice that when we took the load balancer out of the equation and just hit the web server directly, the refreshes "appeared" to decrease in regularity but still occur.Also, the reports do not exhibit the refresh issue when running locally within Visual Studio 2013.
We have a Report Server integrated with SharePoint. A month ago we deployed a report (rdl file) in SharePoint, but the person who deployed it was no longer connected with us. So we decided to deactivate it in our Active Directory. Yesterday, our users returned issues regarding they are unable to access their report. I believe the issue was "object reference not set to an instance of an object".
So I tried to download the rdl file and redeployed it but i am getting error upon deploying to SharePoint. My workaround is to delete the rdl file in SharePoint, redeploy the shared datasource and shared datasets and the rdl file. It went and was now able to run the report in SharePoint.
Is there something relation/happened when deactivating the account in AD that users unable to access the report in SharePoint?
I am trying to follow the instructions on: http://technet.microsoft.com/en-us/library/bb677365.aspx they contain many "if"s and links to other sites and I got totally confused and stuck. The idea is - I need to have one machine with SQL for reporting services and SharePoint databases and the reporting services and the other machine for a complete SharePoint installation (the main server of the farm)
Now I have done the following: two servers (lets call them SQL and MOSS)
The domain contains the following users: sqlservices: for running all the SQL services and reporting services moss: for administering MOSS databases moss-services: for running all the MOSS services Machine SQL - installed Windows Server 2003 Standard Edition SP1, joined to the domain as SQL The following is done from a local Administrator account: IIS 6 with ASP.NET installed SQL Server 2005 with SP2, Reporting services installed but not configured all the services are running as domainsqlservices .NET 3.0 installed http://support.microsoft.com/kb/918642 fix installed done WINDOWSMicrosoft.NETFrameworkv2.0.50727aspnet_regiis €“i MOSS as Web Front installed, not configured
Machine MOSS - installed Windows Server 2003 Standard Edition SP1, joined to the domain as MOSS The following is done from a local Administrator account: IIS 6 with ASP.NET installed .NET 3.0 installed http://support.microsoft.com/kb/918642 fix installed done WINDOWSMicrosoft.NETFrameworkv2.0.50727aspnet_regiis €“i Computers->My computer->DCOM Config->IIS WAMREG admin Service->PropertiesSecurity->Customize->Edit, added domainmoss-services and domainMOSS users with rights Local launch, Local activate MOSS Complete installed, configured for: New server farm Database server: SQL Username: domainMOSS Port: Default Auth: NTLM SharePointRS.msi installed to enable RS in SharePoint Admin page Then temporarily gave to the user domainMOSS sysadmin rights in the SQL server on the SQL machine to avoid errors with creating databases while configuring SharePoint from the Admin Portal. From the Admin Portal configured Office SharePoint Server Search with domainmoss-services account Shared Services Administration €“ New SSP created with 2 separate web apps for SSP and MySites, both app pools run as domainmoss-services and SSP itself runs as domainmoss-services Windows SharePoint Services Search configured, Service Account - domainmoss-services, Content Access Account - domainmoss-services
Everything went OK.
Now came back to the machine SQL: run Reporting Services Configuration and: Report Server Virtual Directory €“ created new, called it ReportServer. When hit Apply, the applicatin suddenly quit, but I checked €“ the Virtual Directory was registered on the IIS and working. Checked if Windows service identity is domainsqlservices, OK. Web service identity: Application Pool: New Name: ReportServer Windows Account: domainsqlservices Apply, everything went fine.
Database setup: choose server SQL, Connect Database name: New name: ReportServer, checked Create the report server database in SharePoint Integrated Mode OK Credeantials Type - Service credentials (I guess it means previously set domainsqlservices will be used) Apply,OK, everything went fine.
Launch SharePoint Products and Technologies Configuration Wizard, Connect to an existing farm, Database server: SQL, Retrieve datbase names: selected SharePoint_Config, Username: domainMOSS, Next, everything fine here.
Now as far as I understand I need to give reporting services an access to SharePoint databases? Went to the machine MOSS, launched SharePoint 3.0 Central Administration:
Application Management-> Reporting Services-> Manage integration settings, URL: http://SQL/reportserver, Windows Authentification, OK then back, Grant database access-> Server Name: SQL, OK, now it is asking for credentials. And now the problem: no matter what I enter (domainsqlservices, domainMOSS) I get a message: €žA connection to the computer cannot be established€?. Why, why, why? I can ping the server, SharePoint services are running fine and they are using the SQL server on the SQL machine and there are no errors in the event viewer (they should be if there were any problems to connect the SQL databases). If I enter wrong credentials, I receive "Unable to log on with the given username and password.", so I guess there IS a connection to the computer (or how else could SharePoint determne that login is wrong?).
Also, if I open http://SQL/reportserver, I get €žThe report server has encountered a configuration error€? and the log in C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesLogFiles says €žSharePoint content service is null. Report Server may not have joined the SharePoint farm, or Report Server service account may not have been granted access to farm.€? I guess it is OK while I have not granted access to the SharePoint databases? Please, show me, what did I do so wrong that €žA connection to the computer cannot be established€?? How can I grant the access and finalize configuring Reporting Services? Thanks.
I am receiving the following error when I run the report builder query. I am able to successfully select the dimensions and measures that I am intrested in but when I run the report I get the error message.
The 'PerspectiveID' custom property for the 'query' perspective is either not set or is not set to the string data type. ---------------------------- Semantic query execution failed. ---------------------------- Query execution failed for data set 'dataSet'. ---------------------------- An error has occurred during report processing.
I am testing this against both Adventureworks standard and enterprise cubes. Additionality I saw a post in this forum http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=368962&SiteID=1 that seemed related but I am using reporting services in sharepoint integrated mode so I am having a hard time trying to troubleshoot this.
Well, I have SQL Server 2005 SP2 Reporting Services installed and configured in sharepoint integrated mode, so I am deploying reports in sharepoint libraries. Also I configured sharepoint to use forms authentication with builtin AspNetSqlMembership provider, but after this action I couldnot open reports through sharepoint library, instead of this, error was displayed mentioned below. I searched and found hotfix Cumulative Update 3 build 3186 for this issue, request it from microsoft support and applied it, but nothing has changed!
Error I have been experiencing is following:
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> The request failed with the error message: -- <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/_layouts/login.aspx?ReturnUrl= %2f_vti_bin %2fReportServer%2fReportService2006.asmx">here</a>.</h2> </body></html>
I continued to dig and find out that this hotfix should update Microsoft.ReportingServices.SharePoint.UI.WebParts.dll from version 9.0.3042.0 to new version 9.0.3180.0, but when I checked file version after applying hotfix, it remained the same as was before i.e. 9.0.3042.0. Apparently this cumulative update does not fix this issue. anyone has any idea how to solve it? Thanks in advance.
We have reports in SharePoint integrated mode which are really slow when compared to native mode. I have been asked to research and give info on what exactly causes the delays.
Any articles which give me information as to what happens when a report is run from SharePoint server and where does it log.
I have recently installed Reporting Services Integrated mode with minor issues and at the end I was able to execute reports as well as add the content types.
I am now working on doing the same exact thing except I do not see Report Server Content types. I am able to upload a report and execute it but cannot add the Content Types. When I login into Central Administrator I see the content type in there. Is there something I am missing to add it to "My Site"
I'm running MOSS 2007 in Integrated Mode, and I have a number of reports that are deployed to the Reports Library, and are working just fine when you go there and run them interactively.
Now however, I need to address the report via a URL, and pass it a parameter. Just to add a bit more pain, the report is in mdx, and expects an mdx parameter.
Here is the parameter "prm_cost_centre":
[DIM LEARNER AIM].[COST CENTRE DESC].&[Business]
Here is the URL of the report:
http://vmmoss:88/ReportsLibrary/Report1.rdl
(If you hit that URL as is, it runs fine, using the default parameter)
Now, I know that we have to escape the ampersand, so I'm thinking that this URL should do it.
http://vmmoss:88/ReportsLibrary/Report1.rdl&rs:Command=Render&prm_cost_centre=[DIM LEARNER AIM].[COST CENTRE DESC].%26[Business]
But it doesn't - It throws a 400 Bad Request error.
I know I must be very close, but I just can't work out what URL I need to pass in order to get the damn thing to run.
I'm deploying a performance point site which includes several parameterized SSRS reports. Reporting services is configured to run in Sharepoint integrated mode.
I'd like to pass the parms to certain reports via URL posts when a user clicks on certain fields in a scorecard.
I can setup the basic URL to open a report, as follows:
When this URL is executed, the sharepoint site redirects with the following URL, which opens the report and prompts for a text date paramater (DatePrompt) in the format dd-mmm-yy (i.e. 01-Sep-07)
I am setting up sharepoint and sql server integration environment. I am considering the following topology: PowerPivot for SharePoint 2013 and Reporting Services in SharePoint mode Two Server Deployment
[URL]
I am looking to follow the topology example by the letter, which involves installing PowerPivot for SharePoint (aka SSAS in SharePoint mode) in the same server as my SQL, and installing SSRS in SharePoint (SP) integrated mode in the same server as SharePoint.
I understand, however, that if I wanted to install SSRS in SP mode in the same server as SQL, I could but only if the server contains the SP Object Model.
My first question is, what would involve having the SP Object Model in the SQL Server?
Would only installing SP binaries be enough; or Do I need to do a minimal install of SP in the SQL server enough for it to joing the SP farm? And most importantly, what would be the licensing implications for SP in case I want proceed down this route and have SSRS in SharePoint mode installed in the same server as the SQL?
I encounter this error when user try to subscribe using email delivery to one of the report. I have configured the Reporting Services to use Sharepoint integrated mode. This user is a regular user that has read access to the report item.
Below is the message detail:
A subscription delivery error has occurred. (rsDeliveryError) A subscription delivery error has occurred. (rsDeliveryError) One of the extension parameters is not valid for the following reason: The account you are using does not have administrator privileges. A subscription cannot be created for [emailaddress]. (rsInvalidExtensionParameter)
Is it true that user needs to have administrator privilege in order to subscribe for report? I don't think so, right?
I got the following exception from the code listed below:
System.Web.Services.Protocols.SoapException occurred Message="The operation is not supported on a report server that is configured to run in SharePoint integrated mode. ---> The operation is not supported on a report server that is configured to run in SharePoint integrated mode." Source="System.Web.Services" Actor="http://haileizws32b:8080/ReportServer/ReportService2005.asmx" Lang="" Node="http://haileizws32b:8080/ReportServer/ReportService2005.asmx" Role="" StackTrace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.PerformancePoint.Planning.Client.Common.ReportServer.ReportingServices2005.ListChildren(String Item, Boolean Recursive) in c:Officedev14ppsplanningclientCommonReportingServices2005.cs:line 1001 at Microsoft.PerformancePoint.Planning.Client.Common.DataAgent.RetrieveDirectoryStructureFromReportingServices(Object caller, Object parameters) in c:Officedev14ppsplanningclientCommonAgentsDataAgent.cs:line 2027 InnerException:
The code is like:
ReportingServices2005 reportingServices = new ReportingServices2005();
Works fine in Visual Studio. Once deployed to SharePoint though, the drill through returns an error that says report can't be found. So I added the .rdl to the conditional statement in the report Design.
I have a set of SSRS reports published on the server. It can be accessed through a web application or through SharePoint. Most of the reports work fine through both - web app and SharePoint. However, one of the report, which returns large amount of data has some problem:
1. It generates fine from web app 2. It generates fine from SharePoint; only if one or two values selected from Filter dropdown 3. However, if all items (about 20 items) selected from Filter dropdown... and click on View Report, it processes for a while and then shows nothing. The page remains blank.
Did some research and felt the problem is with Distributed Cache Service.
I have created a ssrs report using ssrs-2012 that contains 2 tables 2 pie charts and 1 line chart. But I am unable to see 2 pie charts and and 1 line chart after deploying the rdl in sharepoint server.
Why I am not able to see those charts, or sharepoint server will not support charts at all.
I have configured Reporting services to use MOSS integrated mode. I have two servers, one for MOSS and the other for SQL database and reporting server.
Since I am using NTLM for IIS authentication, I can only use "Trusted Account" for Reporting Service Integration.
Then I created a report in SQL Server BI development studio and deployed to a MOSS document library. The deployment was successful. However, when I tried to open the report, I got the following error message:
An error has occurred during report processing. This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode.
I have tried to switch to "Windows Authentication" for Reporting Service Integration, but this will give error for "Set Server Defaults" screen. Also the deployment from BI studio to MOSS will fail with authentication error. So I think I have to stay with "Trusted Account" option there.
What should I do to make the report accessible while using "Trusted Account"? Is there any configuration which has to be done for this purpose? Any input is appreciated.
Is there any way to get SSRS 2014 report viewer to run in standards mode? We currently host SSRS report viewer in a standards mode IFrame. Â Seems to work fine for all browsers but IE8. In IE8, the report detail is missing.
I'm guessing that SSRS Viewer on IE 8 requires Quirks mode.
I noticed this article which states that SSRS 2014 Viewer only works in quirks mode.
Rendering issues with SQL Server Reporting Services reports in Internet Explorer
How do you get the SSRS viewer to run on IE8 in standards mode?
I am trying to develop a report from cube,and it has one drill through report.when i click on sales amount field on main report,then it open the drill through report with details.Here i passed the **(category,subcat,product)parameters(Cascaded)** to drill through report in action part of main report.In my main report i have two columns .
columns are **Level**  and        **Salesamount**. Â
Values are like Â
**[-]category** Â Â Â Â Â Â Â **100** Â Â **[-]subcat** Â Â Â Â Â Â **50** Â Â Â Â Â **product** Â Â Â Â Â **30**
when i click on 100, parameters are passed & it open the detail report correctly, but when i click on 50,the values for subcat parameter is not getting values in detail report and same as the product also.
Is there a way to subscribe SSRS report using dynamic parameters for email and trigger the report from autosys job so that report should generate the exact time the job is triggered.Let me describe, my SSRS report should be triggered on success of one autosys job. i need to send email parameter and time of report schedule from this autosys job.
We have started to use reporting services in integrated mode with windows sharepoint. Since this installation the drillthrough reports have stopped working. We get the following error when a hyperlink is cllicked:-
The item 'http://vtrends/reports/IslandRegionCountryState' cannot be found. (rsItemNotFound)
In the textbox properties we have set the 'Jump to Report' hyperlink option to use a condition. Based on the link clicked, one of two reports will be displayed. If i remove this condition and manually select the report to run then there are no problems. This however is not the functionality that is needed. Any help will be appreciated.
hello good afternoon, I am having this issue, I need to move reporting services from one server to another, but I need that credentials, roles and reports stay the same. But as the reporting services is integrated with sharepoint, dont know if I can move both at the same or it has to be done one at a time. this is just data migration, but still I will like to Know how it can be done having the same structure with the roles and credentials. or it is prefered to do a ghost?? but the issue will be that we have the reporting services in one place and the data in another... don´t know how this will affect. thanks in advanced for the help.
Sorry for the long post, but I'm trying to include as much info as possible.
I'm having trouble getting SQL Server 2005 Reporting Services and MOSS 2007 working together in integrated mode. Everything seems to be ok, but we get a 'HTTP 401 Unauthorized' error when using the 'Set server defaults' link from MOSS 2007 Central Administration. None of the other links give this error, but I'm not sure whether MOSS just eats the error message...
Here's the background: Sql Server 2005 is installed on a separate box, let's call it SERVER1. This Sql Server hosts both the MOSS content database as well as the reporting services database.MOSS 2007 is installed on a different box, let's call it SERVER2I've installed all the required components for both boxes with no installation errorsSSRS seems to be running fine on SERVER1. Report Manager can be used directly with a browser in native mode.SSRS also *seems* to be running fine in Integrated mode, i.e. I can create a reporting database for integrated mode: The url http://host/ReportService/ReportService2006.asmx responds normally when I access it through browser using my domain credentialsThe url http://host/Reports/ returns a message saying that I can't access it in integrated mode, which, I take, is normal MOSS is running ok on SERVER2 I can see that SERVER1 is in the same farm after I've installed WSS3.0 on SERVER1Also I can see the "Reporting Services" section in Central Administration So all in all, everything seems to be ok. However, when I try to use the 'Set server defaults' link from MOSS Central Administration I get an 'HTTP 401 Unauthorized' error. I'm assuming clicking this link will result in MOSS calling the Reporting Services' SOAP endpoint ReportService2006.asmx which now seems to be the culprit. Here's why I think so:
Whenever this occurs, the IIS logs on SERVER2 show that someone from SERVER1 is indeed trying to connect to ReportService2006.asmx, but I'm not seeing any user credentials being passed (whenever I access the asmx through my web browser, the credentials I entered in the browser are recorded in the log). Furthermore, the Event Viewer on SERVER2 shows Audit Failure (code 529) events occurring every time I get the HTTP 401 error.
The Event viewer's message is as follows:
Logon Failure: Reason: Unknown user name or bad password User Name: Domain: Logon Type: 3 Logon Process: Kerberos Authentication Package: Kerberos Workstation Name: - Caller User Name: - Caller Domain: - Caller Logon ID: - Caller Process ID: - Transited Services: - Source Network Address: <SERVER1 IP> Source Port: <PORT> From the Event Viewer message and the IIS log it would seem like my MOSS is trying anonymous access whenever it tries to access the SSRS SOAP endpoint, which of course results in a 401, since anonymous access is not allowed. Please note that if I enable anonymous access in the Reporting Services' virtual directories (just for testing), I get a different error. This indicates that the HTTP 401 indeed originates from this particular web service call.
I've heard that SPS2003 and Reporting Services don't like each other on the same box, but this is hearsay. Does anyone know if this is a confirmed fact? This box does have SPS2003 and SSRS2005 installed. I tried to uninstall the SPS2003 but that didn't help anymore.
I noticed someone having similar issues in another thread, but I didn't see resolutions. I'm pretty baffled as to whether this is a problem with the MOSS Add-in or the Reporting Services installation.
Any input on this issue is very much appreciated. I'll try to also include a follow-up if we're able to get this working ourselves.
I have a third party app that passes parameters (main dataset query) from the app to SSRS. Â Unfortunately, when the parameters are passed from the app they will contain equal signs ("=") in front of each parameter. Â For example, the parameters that may be passed to the main dataset query should be:
"HYDRO, OKO, ONEPL, TECHNI"
However, the parameters that are passed from the app, get to SSRS as:
"=HYDRO, =OKO, =ONEPL, =TECHNI"
Again, this is for the main dataset query and there may be one parameter or there may be any number of them.
Basically, I need to strip the "=" signs from the parameters. whether there is one parameter or ten.
I believe that I will need a custom function to strip the equal signs?
I wonder where in Reporting Services Configuration i can change the mode to Share Point Integrated? Do i need to create a new database, or can i change the mode for the one i use?
We have an Office SharePoint 2007 site, we developed a couple of web parts and added them to our site. We used SQL Server Reporting services 2005 as our reporting solution. The reports are hosted on the report center and when we need a report, we open it by sending a URL requesting the report, passing the report parameters in the URL query string. So the report is filtered based on the parameters passed from the web parts.
But since best practices say that you should host reports directly under SharePoint, by configuring the reporting services to run in the SharePoint integrated mode. We followed the steps and installed SharePointRS and we finally succeeded to publish the reports to a SharePoint folder, but we had a limitation: we are unable to pass the report parameters internally to the report hosted in SharePoint. If we passed them in the query string as the report center case, SharePoint neglects them totally. So the question is: how can I pass parameters internally between a SharePoint web part and a SQL server 2005 reporting services report hosted in SharePoint?
Up until an hour ago, I was using the Sql Server Reporting Services Report Viewer webpart in Sharepoint with forms authentication, and was not having an issue. The only thing that I did (or remember doing) before things went sour was upload a new report to the document list and since then whenever I try to access a report, manage the data source on a report, change the report URL in the webpart, I get the following message:
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> The request failed with the error message: -- <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/_layouts/login.aspx?ReturnUrl=%2f_vti_bin%2fReportServer%2fReportService2006.asmx">here</a>.</h2> </body></html>
--.
I found some related posts and have tried the following, but none have helped:
Removed all reports and reuploaded only the one that was definitely working. I changed the application pool for the report server to be the same app pool as Sharepoint (runs under domain admin account). I changed the application pool for the report server back to it's original (which the Reporting Services Configuration prefers - was running under Network Service acct before the problem started, now running under domain admin acct) I can browse to http://server/reportserver. I'm running under forms authentication, which had been working. I can access the three configs for Reporting Services under Application Management in Central Admin - I've tried changing the settings. I can access http://server/_vti_bin/reportserver/reportservice2006.asmx as well as http://server/_vti_bin/reportserver/reportserviceauthentication.asmx (that was suggested in one post) I've restarted IIS numerous times, and also finally rebooted the server. I've created a new document list and set it for report content, just like the other list.
I also just noticed that even though I've set up my admin account as a site collection administrator, I now no longer see my report options under the New button in the document library (both the old and new). I don't know if this is related.
I'm sure that this is a case of something minor that I did that I forgot about. Any suggestions or other troubleshooting that I can do?
I am trying to run a Reporting services report and pass a parameter using url access and SP Integrated mode.
I have managed to come up with the following: http://DashBrdRptSite/reportserver?http://npvmdashbrd1:2764/Reports/dashbrdrptstore/real%20time%20running/test.rdl&rs:Command=Render&Year=2006&Year=2007&Month=1
This works perfect as long as I run it from the actual server that has Sharepoint and reporting services installed.
If I try to run it from my desktop, I get prompted for a user name and password. And now matter how many times I enter my user/pass... it does not work.
If I just run the sharepoint link that appears on the report when I run it from within sharepoint... such as
That runs no problem no matter where I run it from (my desktop or the Sharepoint Server), but it looks like I cannot pass it parameters. I guess becuase it is useing RSViewerPage.aspx.
I made one report in SSRS 2008 in which getting data from one SharePoint List.
three parameters in report :
Country StartDate EndDate
I am using query which I created with CAML.
query is running well and data is coming correctly if I run this on Query designer.and date format must be YYYY-MM-DD.but when I try to run through on run time then the date control is showing format dd/mm/yyyy.
I change the regional settings of windows and SharePoint site to English(United States). and when I select date control it is also putting date in format like "YYYY-MM-DD'. and in that format report is working well in Query designer view.But on run time still it is not working.
