Reporting services 2005 - rezising the legend size

Hi all,I have a report with a chart.the chart has a legend.The problem is that the number of categoried the legend contains grows in time.

How to i do i make the legend rezing dynamicly so that the text doesnt go over the other?

You could consider a "table" legend layout which may be able to better accomodate the legend items.

Other than that, you could look into building a custom legend by using a table data region instead of using the built-in legend (see this article for more details: http://blogs.msdn.com/bwelcker/archive/2005/05/20/420349.aspx)

-- Robert

Reporting Services 2005

What is the best option to monitor user accesses to published reports? IT department wants to have an idea about the need (value and time) of produced reports.

Regards,

Vitor Mota

I will not comment on what the "best option" is, but this is an option I use frequently for debugging.

If you use stored procedures to generate the data for your reports, you can have them update a stats table to indicate that a given report has been run. You would have to have stored procedures unique to a given report for this to work, but I suppose if you wanted to be fancy, you could write stored procedures just for this purpose.

Otherwise, there are lots of IIS log analyzers out there.

|||

Thanks for your answer.

I'm reading data to reports using MDX queries without using sps and analyzing the IIS logs are hard to do.

I was looking for an "almost" ready solution to use. Any other idea?

Best regards,

Vitor Mota

reporting services 2000 installation problem

Hi all, I recently installed Reporting Services 2000 on my server for the
first time and it caused my existing web apps to stop functioning. I have a
few custom dlls in the GAC and I had to end up re-registering them in the
GAC and restart iis services. That fixed my apps not working. But now, for
some reason Report Manager will not work. Here is what I get:-
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Required permissions cannot be acquired.
Source Error:
Line 256: <add assembly="System.EnterpriseServices,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 257: <add assembly="System.Web.Mobile,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 258: <add assembly="Appone.Data.Services,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=1949095674c58f09" />
Line 259: <add assembly="Appone.Web.Security,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=7b58630078eb0f75" />
Line 260: <add assembly="Appone.Web.Config, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=01a8235a19f330a7" />
Source File:
c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line:
258
----
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032
Any ideas? What can I do to fix this?
TIA,
ParamOK just came in this morning and everything was down. Had to re-register
dlls into GAC and restart again and now seems to be back up. Except Report
Manager still does not work.
thanks
"Param R." <pr@.nospam.com> wrote in message
news:uENazG6BFHA.2012@.TK2MSFTNGP15.phx.gbl...
> Hi all, I recently installed Reporting Services 2000 on my server for the
> first time and it caused my existing web apps to stop functioning. I have
> a few custom dlls in the GAC and I had to end up re-registering them in
> the GAC and restart iis services. That fixed my apps not working. But now,
> for some reason Report Manager will not work. Here is what I get:-
> Configuration Error
> Description: An error occurred during the processing of a configuration
> file required to service this request. Please review the specific error
> details below and modify your configuration file appropriately.
> Parser Error Message: Required permissions cannot be acquired.
> Source Error:
>
> Line 256: <add assembly="System.EnterpriseServices,
> Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> Line 257: <add assembly="System.Web.Mobile,
> Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
> Line 258: <add assembly="Appone.Data.Services,
> Version=2.0.0.0, Culture=neutral, PublicKeyToken=1949095674c58f09" />
> Line 259: <add assembly="Appone.Web.Security,
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=7b58630078eb0f75" />
> Line 260: <add assembly="Appone.Web.Config,
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=01a8235a19f330a7" />
>
> Source File:
> c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config
> Line: 258
>
> ----
> Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
> ASP.NET Version:1.1.4322.2032
> Any ideas? What can I do to fix this?
> TIA,
> Param
>sql

Reporting Services - use of temp tables

Hello all,

I need to create a report based on a stored procedure. This stored procedure contains temp tables. At the time of creating the report, I receive a message mentioning - There is an error in the query. Invalid object name '<temp table name'>

Doesn't Reporting Services support temp tables?

Thanks all,
SauravYou can use temporary tables. I tend to do it like...

-- Create temporary tables
declare @.MyTempTable table
(
field1 int,
field2 smalldatetime,
field3 int,
field4 smallint
)

You can then use @.MyTempTable for your SP.

Hope that helps.sql

Reporting Services - Installation Question

Hi,
Can I set up RS and then install VB.NET 2003 at a later time to add the
Report Designer functionality?
Thanks
Jerryyes. After you install the IDE just re-run the RS installer and select the
development tools.
--
Floyd
"Jerry Spivey" <jspivey@.vestas-awt.com> wrote in message
news:OMWSV$wuFHA.2556@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Can I set up RS and then install VB.NET 2003 at a later time to add the
> Report Designer functionality?
> Thanks
> Jerry
>

Reporting Services

Hi there

Have been using the "vanilla" SQL Express for some time now and feel that I kind of know what I'm doing.

However, I have no idea what can be acheived with the Reporting Services that come with the "advanced" SQL Express.

Can someone please explain what I can do with Reporting Services?

Reporting Services is a web server that allows you to provide a reporting exerience for your database that can be accessed on a web site rather than requring people to open up a specific application. Think about things like summary or rollup reports; there is no need to have everyone install a specialized application, you just create reports and Deploy them to RS and then folks can look at them.

Like any access to SQL, you can use either Windows or SQL Auth, depending on how your SQL Server is configured, and then use that to control access to the data.

RS Express provides some limited Export capability (PDF & XLS) and can only access local, relational data. There is more information in BOL and a whole series of webcasts you can view to learn more at http://msdn.microsoft.com/sql/bi/reporting/default.aspx.

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

Reporting Services

We have SQL 2000 as our database platform. I can't see any large scale
migration any time soon. However we would like to start using Reporting
Services. What are the options of using 2005 Reporting services and point
them at a 2000 server through e.g. linked servers etc. Is something like
this possible or am I going in the wrong direction."Chris" <nospam@.nospam.com> wrote in message
news:esUzl4RTHHA.1000@.TK2MSFTNGP05.phx.gbl...
> We have SQL 2000 as our database platform. I can't see any large scale
> migration any time soon. However we would like to start using Reporting
> Services. What are the options of using 2005 Reporting services and point
> them at a 2000 server through e.g. linked servers etc. Is something like
> this possible or am I going in the wrong direction.
>
You don't even need linked servers. Just install Reporting Services 2005,
and you can build reports that pull data from SQL 2000 databases.
David|||Additional Info:
Besides the database where data for the reports is stored, RS itself also
needs SQL Server to host its meta database, which may or may not be in the
same computer where RS runs. For RS2005, yes, you can use SQL Server2000 to
host RS2005 meta database. However, where the RS meta-database is in the
same computer as the RS or not, you need SQL Server2005 license to use
RS2005 (That is, if the SQL Server is in different computer as RS, you need
two licenses: one for RS (SQL Server2005, in your case); and one for the SQL
Server2000 (SQL Server2005 or 2000 license).
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ucaOUjSTHHA.1200@.TK2MSFTNGP04.phx.gbl...
>
> "Chris" <nospam@.nospam.com> wrote in message
> news:esUzl4RTHHA.1000@.TK2MSFTNGP05.phx.gbl...
> You don't even need linked servers. Just install Reporting Services 2005,
> and you can build reports that pull data from SQL 2000 databases.
> David

Reporting Services

We have SQL 2000 as our database platform. I can't see any large scale
migration any time soon. However we would like to start using Reporting
Services. What are the options of using 2005 Reporting services and point
them at a 2000 server through e.g. linked servers etc. Is something like
this possible or am I going in the wrong direction."Chris" <nospam@.nospam.com> wrote in message
news:esUzl4RTHHA.1000@.TK2MSFTNGP05.phx.gbl...
> We have SQL 2000 as our database platform. I can't see any large scale
> migration any time soon. However we would like to start using Reporting
> Services. What are the options of using 2005 Reporting services and point
> them at a 2000 server through e.g. linked servers etc. Is something like
> this possible or am I going in the wrong direction.
>
You don't even need linked servers. Just install Reporting Services 2005,
and you can build reports that pull data from SQL 2000 databases.
David|||Additional Info:
Besides the database where data for the reports is stored, RS itself also
needs SQL Server to host its meta database, which may or may not be in the
same computer where RS runs. For RS2005, yes, you can use SQL Server2000 to
host RS2005 meta database. However, where the RS meta-database is in the
same computer as the RS or not, you need SQL Server2005 license to use
RS2005 (That is, if the SQL Server is in different computer as RS, you need
two licenses: one for RS (SQL Server2005, in your case); and one for the SQL
Server2000 (SQL Server2005 or 2000 license).
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ucaOUjSTHHA.1200@.TK2MSFTNGP04.phx.gbl...
>
> "Chris" <nospam@.nospam.com> wrote in message
> news:esUzl4RTHHA.1000@.TK2MSFTNGP05.phx.gbl...
>> We have SQL 2000 as our database platform. I can't see any large scale
>> migration any time soon. However we would like to start using Reporting
>> Services. What are the options of using 2005 Reporting services and point
>> them at a 2000 server through e.g. linked servers etc. Is something like
>> this possible or am I going in the wrong direction.
> You don't even need linked servers. Just install Reporting Services 2005,
> and you can build reports that pull data from SQL 2000 databases.
> David

Reporting Services

I have a hard time figuring out how the web service part is being
used. Has anyone done this? We are looking for a web service kind of
feature.
ThanksWhat are you trying to do? RS has very very strong support for web services.
Indeed, Report Manager in RS 2005 does everything it does using web
services. Books online has a whole ton on web services.
But, to back up, unless you are doing something fancy you are better off to
use the webform or winform that ships with VS 2005. Or in other cases look
at the URL integration. But, I would recommend using the controls from VS
2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ross" <ross_smith@.csaa.com> wrote in message
news:e7450aef-4d07-43df-8c87-1675739e884c@.s13g2000prd.googlegroups.com...
>I have a hard time figuring out how the web service part is being
> used. Has anyone done this? We are looking for a web service kind of
> feature.
> Thanks|||On Feb 21, 7:41=A0am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> What are you trying to do? RS has very very strong support for web service=s.
> Indeed, Report Manager in RS 2005 does everything it does using web
> services. Books online has a whole ton on web services.
> But, to back up, unless you are doing something fancy you are better off t=o
> use the webform or winform that ships with VS 2005. Or in other cases look=
> at the URL integration. But, I would recommend using the controls from VS
> 2005.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ross" <ross_sm...@.csaa.com> wrote in message
> news:e7450aef-4d07-43df-8c87-1675739e884c@.s13g2000prd.googlegroups.com...
>
> >I have a hard time figuring out how the web service part is being
> > used. Has anyone done this? We are looking for a web service kind of
> > feature.
> > Thanks- Hide quoted text -
> - Show quoted text -
What we were trying to do is have a client (via a browser app) get the
data from a data server, then pass a report name and the data to a
report server. I want to do this via a web service from report server
and then call a url but that requires passing data across applications
in IIS. I was hoping that the web services in the reporting servcies
could somehow help me. I don't know the right questions to ask to
resolve this.
Thanks.|||RS is designed as a SOA (Service Oriented Architecture). The pattern it is
designed to follow is that you give RS the parameters and the report name
and it does the rest. It queries the data and then renders it in whatever
format you desire. There is no direct way to do what you are asking for. If
you absolutely must do this you have several options:
1. Use the control that ships with VS 2005. It has a local and a remote
mode. In local mode you give the control the report and the tableset and it
does the rest. No server is used at all. However, there is a lot more work
to do with this method. You have to write code responding to events (for
instance with subreports). Designing a report is more complicated and takes
longer. And you lose the benefits of having a server (caching, performance
under load, subscriptions, etc).
2. If your goal is to interact with your own object model and the object
model retrieves the data then you might consider a Data Processing Extension
(search on that term in Books Online).
3. RS does have the ability to have a report be based on data returned by a
web service. So if the data you want to report off of is only available as a
web service this is a possibility for you.
http://technet.microsoft.com/en-us/library/ms345334.aspx
Finally, my guess is you have not created any reports in RS at all. That
would be a good place to start. Make sure you understand how to create
regular simple reports first and then go from there.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ross" <ross_smith@.csaa.com> wrote in message
news:5228a703-5767-4940-a3bc-b06e38f2c7ca@.i29g2000prf.googlegroups.com...
Snip
What we were trying to do is have a client (via a browser app) get the
data from a data server, then pass a report name and the data to a
report server. I want to do this via a web service from report server
and then call a url but that requires passing data across applications
in IIS. I was hoping that the web services in the reporting servcies
could somehow help me. I don't know the right questions to ask to
resolve this.
Thanks.

Reporting Service will not start

SQL Server 2005 SP1 (Express) will not start
Reporting Services Configuration Manager reports:
System.ServiceProcess.TimeoutException: Time out has expired and the
operation has not been completed.
at
System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
desiredStatus, TimeSpan timeout)
at
ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
Windows Event Application log contains:
Service cannot be started. System.TypeInitializationException: The type
initializer for 'Microsoft.ReportingServices.Library.Global' threw an
exception. --> System.Configuration.ConfigurationErrorsException: An error
occurred creating the configuration section handler for RStrace: That
assembly does not allow partially trusted callers. (c:\Program
Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
System.Security.SecurityException: That assembly does not allow partially
trusted callers.
at
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
SecurityAction action, Object demand, IPermission permThatFailed)
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
fillCache)
...
Thanks for the helpI have the exact same problem on my machine - did you ever find a solution to
this?
"Automate" wrote:
> SQL Server 2005 SP1 (Express) will not start
> Reporting Services Configuration Manager reports:
> System.ServiceProcess.TimeoutException: Time out has expired and the
> operation has not been completed.
> at
> System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> desiredStatus, TimeSpan timeout)
> at
> ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
>
> Windows Event Application log contains:
> Service cannot be started. System.TypeInitializationException: The type
> initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> exception. --> System.Configuration.ConfigurationErrorsException: An error
> occurred creating the configuration section handler for RStrace: That
> assembly does not allow partially trusted callers. (c:\Program
> Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> System.Security.SecurityException: That assembly does not allow partially
> trusted callers.
> at
> System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> SecurityAction action, Object demand, IPermission permThatFailed)
> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> Boolean& bNeedSecurityCheck)
> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> fillCache)
> ...
>
> Thanks for the help|||The problem was occuring on a large companies computers that used their own
standardized secure Windows install images. They told me they had to open up
the security of DCOM but I don't know exactly what they changed.
"Flayto" wrote:
> I have the exact same problem on my machine - did you ever find a solution to
> this?
> "Automate" wrote:
> > SQL Server 2005 SP1 (Express) will not start
> >
> > Reporting Services Configuration Manager reports:
> >
> > System.ServiceProcess.TimeoutException: Time out has expired and the
> > operation has not been completed.
> > at
> > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > desiredStatus, TimeSpan timeout)
> > at
> > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> >
> >
> > Windows Event Application log contains:
> >
> > Service cannot be started. System.TypeInitializationException: The type
> > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > occurred creating the configuration section handler for RStrace: That
> > assembly does not allow partially trusted callers. (c:\Program
> > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > System.Security.SecurityException: That assembly does not allow partially
> > trusted callers.
> > at
> > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > SecurityAction action, Object demand, IPermission permThatFailed)
> > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > Boolean& bNeedSecurityCheck)
> > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > fillCache)
> > ...
> >
> >
> > Thanks for the help|||Well, I managed to fix the problem after a bit of research. In the end, all I
needed to do was re-install .Net 2.0 framework. I'm not sure if it got
damaged because of the order I installed applications on my computer, but
repairing Framework 2.0 seems to have done the trick.
"Automate" wrote:
> The problem was occuring on a large companies computers that used their own
> standardized secure Windows install images. They told me they had to open up
> the security of DCOM but I don't know exactly what they changed.
> "Flayto" wrote:
> > I have the exact same problem on my machine - did you ever find a solution to
> > this?
> >
> > "Automate" wrote:
> >
> > > SQL Server 2005 SP1 (Express) will not start
> > >
> > > Reporting Services Configuration Manager reports:
> > >
> > > System.ServiceProcess.TimeoutException: Time out has expired and the
> > > operation has not been completed.
> > > at
> > > System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
> > > desiredStatus, TimeSpan timeout)
> > > at
> > > ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
> > >
> > >
> > > Windows Event Application log contains:
> > >
> > > Service cannot be started. System.TypeInitializationException: The type
> > > initializer for 'Microsoft.ReportingServices.Library.Global' threw an
> > > exception. --> System.Configuration.ConfigurationErrorsException: An error
> > > occurred creating the configuration section handler for RStrace: That
> > > assembly does not allow partially trusted callers. (c:\Program
> > > Files\Microsoft SQL Server\MSSQL.3\Reporting
> > > Services\ReportServer\bin\ReportingServicesService.exe.config line 3) -->
> > > System.Security.SecurityException: That assembly does not allow partially
> > > trusted callers.
> > > at
> > > System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm,
> > > PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh,
> > > SecurityAction action, Object demand, IPermission permThatFailed)
> > > at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
> > > publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor,
> > > Boolean& bNeedSecurityCheck)
> > > at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
> > > fillCache)
> > > ...
> > >
> > >
> > > Thanks for the help

Reporting Service seems to "go to sleep" after a while...

My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?

Is there an error generated? What tells you that the report has gone to "sleep"?|||

No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.

I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.

Any other suggestions beside these?

|||

>> any other suggestions

Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)

Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?

>L<

|||

I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.

I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.

|||

OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?

>L<

|||

I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.

I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?

|||

To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)

As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?

Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?

>L<

|||

One of the forum posts suggested to create a snapshot.

Reporting Services is running on Windows Server 2003 on IIS 6.

There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?

Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).

In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).

Everytime the report server wakes up, an entry in the Event Log is created with the text:

The ReportServer service has been activated.

The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?

|||

I suppose you could change the values for the default web site/app pool also but you shouldn't need to.

Try unchecking the Recycle worker process option altogether. **

Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...

** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.

... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?

>L<

|||

I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".

Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.

In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.

We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.

|||

Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.

>L<

|||

I'm going to refer the problem to Microsoft Support and see if I can get any further with this

|||

I think that's a good idea. I hope you get further than this...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1

... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.

Good luck,

>L<

Reporting Service seems to "go to sleep" after a while...

My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?

Is there an error generated? What tells you that the report has gone to "sleep"?|||

No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.

I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.

Any other suggestions beside these?

|||

>> any other suggestions

Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)

Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?

>L<

|||

I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.

I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.

|||

OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?

>L<

|||

I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.

I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?

|||

To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)

As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?

Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?

>L<

|||

One of the forum posts suggested to create a snapshot.

Reporting Services is running on Windows Server 2003 on IIS 6.

There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?

Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).

In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).

Everytime the report server wakes up, an entry in the Event Log is created with the text:

The ReportServer service has been activated.

The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?

|||

I suppose you could change the values for the default web site/app pool also but you shouldn't need to.

Try unchecking the Recycle worker process option altogether. **

Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...

** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.

... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?

>L<

|||

I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".

Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.

In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.

We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.

|||

Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.

>L<

|||

I'm going to refer the problem to Microsoft Support and see if I can get any further with this

|||

I think that's a good idea. I hope you get further than this...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1

... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.

Good luck,

>L<

Reporting Service seems to "go to sleep" after a while...

My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?

Is there an error generated? What tells you that the report has gone to "sleep"?|||

No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.

I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.

Any other suggestions beside these?

|||

>> any other suggestions

Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)

Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?

>L<

|||

I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.

I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.

|||

OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?

>L<

|||

I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.

I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?

|||

To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)

As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?

Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?

>L<

|||

One of the forum posts suggested to create a snapshot.

Reporting Services is running on Windows Server 2003 on IIS 6.

There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?

Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).

In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).

Everytime the report server wakes up, an entry in the Event Log is created with the text:

The ReportServer service has been activated.

The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?

|||

I suppose you could change the values for the default web site/app pool also but you shouldn't need to.

Try unchecking the Recycle worker process option altogether. **

Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...

** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.

... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?

>L<

|||

I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".

Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.

In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.

We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.

|||

Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.

>L<

|||

I'm going to refer the problem to Microsoft Support and see if I can get any further with this

|||

I think that's a good idea. I hope you get further than this...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1

... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.

Good luck,

>L<

Reporting Service seems to "go to sleep" after a while...

My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?

Is there an error generated? What tells you that the report has gone to "sleep"?|||

No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.

I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.

Any other suggestions beside these?

|||

>> any other suggestions

Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)

Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?

>L<

|||

I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.

I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.

|||

OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?

>L<

|||

I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.

I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?

|||

To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)

As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?

Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?

>L<

|||

One of the forum posts suggested to create a snapshot.

Reporting Services is running on Windows Server 2003 on IIS 6.

There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?

Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).

In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).

Everytime the report server wakes up, an entry in the Event Log is created with the text:

The ReportServer service has been activated.

The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?

|||

I suppose you could change the values for the default web site/app pool also but you shouldn't need to.

Try unchecking the Recycle worker process option altogether. **

Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...

** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.

... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?

>L<

|||

I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".

Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.

In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.

We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.

|||

Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.

>L<

|||

I'm going to refer the problem to Microsoft Support and see if I can get any further with this

|||

I think that's a good idea. I hope you get further than this...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1

... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.

Good luck,

>L<

Reporting Service seems to "go to sleep" after a while...

My reporting server seems to go to sleep after some time of non-use. This is affecting the users who create reports at the start of the day. A report that takes 1 second to generate takes 11 seconds on first hit in the morning. After the initial "wake up" call, the report server generates the reports normally without any delay. Can I keep it awake the whole time? Is there a setting somewhere?

Is there an error generated? What tells you that the report has gone to "sleep"?|||

No error. Just the delay. It's not the report that goes to sleep, its the reporting service. As I said, a report that takes 1 second to generate takes 11 seconds on first hit if the reporting server hasn't been used for a while.

I searched this forum and found other posts similar to mine. It seems that you need to change the shutdown timeout of the App Pool of the reporting service and/or create a snapshot of a dummy report each hour or so.

Any other suggestions beside these?

|||

>> any other suggestions

Those *are* the right answers, usually. ( examples: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056458&SiteID=1 or http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=703914&SiteID=1)

Are you saying you already tried this advice and it did not work for you, or that you don't want to follow those instructions for some reason <s>?

>L<

|||

I tried both and they aren't working. When I run a report in the morning, it still takes a long time to "wake up". I then look at Event Log of the reporting server to discover that an entry has just been made saying that reporting services has been activated. It should already be activated according to those other posts.

I've got reporting services creating a snapshot of a dummy report every hour and I've set the background thread in IIS to shutdown after 2 days, so I'm doing everything those other posts suggest. Still no go.

|||

OK. This might be a stupid question but... could overnight patching or maintenance procedures of any type that might require a reboot, or even just a shut down of ASP.NET, be involved here?

>L<

|||

I don't think the web server / reporting server shuts down each night. I believe it is constantly turned on.

I had a look at how the snapshot works. It seems to create an SQL job, which runs on a schedule. This would mean the snapshot has nothing to do with ASP.NET and the IIS worker process, which I think it is the culprit. Maybe I need something to constantly download a dummy report on the web server to keep the web service alive? How could I do that?

|||

To tell you the truth, I didn't even understand why you were creating a snapshot on the hour (did you find that part in the instructions somewhere? ) I ws sure the worker thread thing was what you needed to do. (I know you said you set the background thread -- are you sure you did the right thing for the application pool that reporting services is using?)

As far as how you can download a dummy report, sure you can do that various kludgey ways with a bunch of work -- but that seems like a depressing idea, doesn't it <s>?

Can you describe exactly what you did re " I've set the background thread in IIS to shutdown after 2 days" and under what OS/version of IIS ?

>L<

|||

One of the forum posts suggested to create a snapshot.

Reporting Services is running on Windows Server 2003 on IIS 6.

There are two virtual directories under "Default Website": Reports and ReportServer. The application pool for each is "ReportServer". But the application pool for "Default Website" is "DefaultAppPool". Maybe that's a problem?

Going to the properties window of the "ReportServer" app pool, in the Performance tab, there is an option "Shut down worker process after being idle for (time in minutes)". This was 20 minutes and I changed it to 2880 minutes (2 days).

In the "Recycling" tab (the first tab) there is a "Recycle worker process (in minutes)" option which is set to 1740 (if that helps).

Everytime the report server wakes up, an entry in the Event Log is created with the text:

The ReportServer service has been activated.

The report server seems to deactivate a lot during the day, not just in the mornings. Maybe it's something to do with the fact that Default Web Site has a different app pool than the two reporting services virtual directories that sit under it?

|||

I suppose you could change the values for the default web site/app pool also but you shouldn't need to.

Try unchecking the Recycle worker process option altogether. **

Are you absolutely sure that the event log says "has been activated" rather than "started" or "started successfully" each time? Are you *sure* <g>? because this message shouldn't be happening multiple times... and doesn't mean what you are interpreting it to mean...

** Look: I'm pretty sure that, in spite of the fact that you think it's the "reportserver service" and are seeing that message, that what you are seeing is due to recompiling of the app instance for the web application.

... but, just in case, if it is really the service, I assume you have also checked to make sure that the service startup type is Automatic?

>L<

|||

I had copied and pasted the Event Log message into my post, and it happens multiple times a day. I checked the Service and it's set to "Automatic".

Before I set it to 2 days, I had originally tried unchecking the Recycle worker process altogether, but the same thing.

In the meantime, I've set up a little console application that runs on the server via Windows Scheduler every 15 minutes. It uses the Reporting Services Web Service to download one of the AdventureWorks sample reports before closing. This seems to be a good interim solution, albeit not ideal.

We are eventually going to upgrade to Reporting Services 2005, so maybe that will help.

|||

Oh!!! I am terribly sorry for having wasted your time on the event log message. I had no idea that you were in RS 2000. I am sure that the messages might be different there.

>L<

|||

I'm going to refer the problem to Microsoft Support and see if I can get any further with this

|||

I think that's a good idea. I hope you get further than this...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203521&SiteID=1

... I believe the solution posted there is specific to RS 2005 but at least it is a cogent explanation of the IIS component of the issue <s>.

Good luck,

>L<

Reporting parameters alignment

Hello All,
First time post question here :)
Is it possible to have 3 or more parameters in one row in RS2000 ? by
default only 2 are alowed to display in one row in reporting parameters
header, and it seems no setting in VS.net 2003 can handle it. or is it
possbile to directly write some xml code to achieve it?
Anyone can help me out ?
Thanks!
Regards,
--ChrisNo, It is handled by SSRS only. if you want to be shown as per your
requirement then you need to create your own forms using asp.net
Amarnath
"neogump" wrote:
> Hello All,
> First time post question here :)
> Is it possible to have 3 or more parameters in one row in RS2000 ? by
> default only 2 are alowed to display in one row in reporting parameters
> header, and it seems no setting in VS.net 2003 can handle it. or is it
> possbile to directly write some xml code to achieve it?
> Anyone can help me out ?
> Thanks!
> Regards,
> --Chris
>|||Amarnath,
Thanks for your information!|||So we cannot customize the report parameter area with our own controls added
to it or changing aligment ? and we cannot add a button on the report
parameter area.
Thanks,
Ravi Manda
"neogump" wrote:
> Amarnath,
> Thanks for your information!
>|||Correct.
"Ravi Manda" <RaviManda@.discussions.microsoft.com> wrote in message
news:32A91524-5F6A-4295-B3B7-E47155E451E1@.microsoft.com...
> So we cannot customize the report parameter area with our own controls
> added
> to it or changing aligment ? and we cannot add a button on the report
> parameter area.
> Thanks,
> Ravi Manda
>
> "neogump" wrote:
>> Amarnath,
>> Thanks for your information!
>>

Reporting on a Cube -- Time Dimension Issue

Hello,

I have an Analysis Services Cube that I would like to report on. However, the Time Dimension currently only has four columns, Day of Month, Month(name) , Year, and DateKey (DateTime representation at midnight for every day). Thus when I drag the month attribute onto the report, it is sorted April - August - December - etc. instead of Jan - Feb - Mar. How do I fix this? I remember reading something in the MSDN Library about it but I can't find it again now.

ThomasJust remove sorting for Time group in Report. It's well known problem.|||Hmm, I haven't added any sorting, this is just drag-and-drop from the list of dimensions in the "Report Builder" tool for Reporting Services and in Visual Studio. So I haven't added any sorting, however in VS I can modify the User Sort - Value property. Unfortunately if I remove it or set it to another field (my date key field) VS crashes when I try to preview. Any other suggestions?|||The Month attribute KeyColumns should be defined as a composite key consisting of the Year and Month column. This should get sorting right because if no Sort attribute is specified UDM will sort by the key. Take a look at how the Month attribute is defined in the AW sample cube.|||Thanks a bunch, but here's a funny story. I actually figured that out and was coming here to post the answer in case any one else needed it. Seems like you beat me to the punch. Thanks again anyways!