Databases
StackOverflow2013
Postsdbo
POWrong Date Format (locale) in SQL Server Reporting Services Report
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWrong Date Format (locale) in SQL Server Reporting Services Report
    primarykey
    data
    text
    <p>I am unable to solve an issue with a report on SSRS.</p> <p>The scenario is : a link in a Silverlight application loads a new web page containing a Microsoft.Reporting.WebForms.ReportViewer control. The parameters for the control are passed in the QueryString to the new page.</p> <p>If the date is passed as 01/08/2011, when the report is loaded, the date control on the report viewer has the value 08/01/2011 (i.e. it has been converted to American format and my locale is United Kingdom, en-GB).</p> <p>This only happens in the deployed solution, it works correctly in Visual Studio on my local PC. My IE settings are correct.</p> <p>I made the following checks on the deployed IIS Server (IIS 6.0):-</p> <p>The security account for the relevant Application Pool = Network Service.</p> <p>In the Registry the SID for this user is S-1-5-20 so I checked the registry settings under HKEY_USERS > S-1-5-20 > Control Panel > International . These were all correctly set for United Kingdom. Although theoretically they should not have an effect I also checked the same settings for Local System (S-1-5-18) and NT-Authority (S-1-5-19) which were identical.</p> <p>I next checked the Culture and UI Culture on the web site. These were as follows: -</p> <p>Right-click website - Properties > ASP.NET. Click the 'Edit Global Configuration' button to check the server config settings. Select the Application tab and view the values for Culture and UI Culture.</p> <p>Both values are set as en-GB. So OK.</p> <p>Did the same in the 'Edit Configuration' button which is for viewing/editing the specific application's config file.The websites' config file values will supercede the server config file values. These are also OK.</p> <p>Next I checked the SSRS Server.</p> <p>Service runs under 'Local System' account. Registry settings for this account are correct HKEY_USERS > S-1-5-18 > Control Panel > International. S-1-5-19 and S-1-5-20 also correct</p> <p>ReportServer.aspx page directive includes Culture="en-GB" (e.g. &lt;%@ Page Language="C#" AutoEventWireup="true" Inherits="Microsoft.ReportingServices.WebServer.ReportViewerPage" Culture="en-GB"%>)</p> <p>In code the parameter values are set using Microsoft.Reporting.WebForms.ReportViewer.SetParameters(ms.ReportParameter []) and ms.ReportParameter(name, value, visible) and the parameters are definitely the correct value when they are received at this point by the web app (when I step through in code).</p> <p>I don't know where to turn next. The one difference I have but I can't imagine it is the problem is that the querystring is URLEncoded on the deployed version but not in the design on my local PC i.e</p> <p>[server version] ...%26END_DATE%3d31%2f07%2f2012+00%3a00%3a00%26START_DATE%3d01%2f08%2f2011+00%3a00%3a00</p> <p>[local version]</p> <p>...&amp;END_DATE=31/07/2012+00:00:00&amp;START_DATE=01/08/2011+00:00:00</p> <p>I would be extremely GRATEFUL for any suggestions that anyone has.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEzaBlade
    1. USEzaBlade
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload