LocalReport.Render does not return

Sorry for the cross-post, but I'm not sure what the best place to post this
is, and I'm getting a bit desparate.
Part of our product uses the SQL Server Reporting engine to create reports
in Excel and PDF format. To do this I am using the LocalReport object the
Microsoft.ReportViewer.WinForms namespace. This is all running in a
web-based service running in IIS.
In development and UAT this has worked flawlessly and had been very powerful
and convenient. Having just put some of our systems live, we are suddenly
running into problems that I am unable to work out how to resolve.
Everything works fine at first, but after the service has been running for
between 20 and 40 minutes, suddenly the report generation stops working.
I've added debug logging to the application, and can see that the last
statement that gets executed is a call to the LocalReport.Render method.
This never returns.
If we recycle the application pool, the reports start working again -- for
another 20 to 40 minutes. Then they stop, just as before.
Setting the application pools to automatically recycle every 20 minutes
seems like a very bad solution to this. I would really like to understand
why it is that the system is locking up. But without being able to step into
the source code for the LocalReport object, I'm completely at a loss as to
how I can resolve this.
Does anyone have any suggestions as to what I could try?
We're using VS2005 and ASP.NET v2.0, running in IIS6 on Windows Server 2003.
My thanks in advance,
--
(O)enoneHave you tried using the WebForms version? Usually when there are a WinForms
and WebForms versions of the same item it's due to the fact that the
WinForms version will not run in the ASP.Net threading model, or uses
services that are not applicable in that environment.
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199...2006
"Oenone" <oenone@.nowhere.com> wrote in message
news:eLhRw6PVHHA.4756@.TK2MSFTNGP06.phx.gbl...
> Sorry for the cross-post, but I'm not sure what the best place to post
> this is, and I'm getting a bit desparate.
> Part of our product uses the SQL Server Reporting engine to create reports
> in Excel and PDF format. To do this I am using the LocalReport object the
> Microsoft.ReportViewer.WinForms namespace. This is all running in a
> web-based service running in IIS.
> In development and UAT this has worked flawlessly and had been very
> powerful and convenient. Having just put some of our systems live, we are
> suddenly running into problems that I am unable to work out how to
> resolve.
> Everything works fine at first, but after the service has been running for
> between 20 and 40 minutes, suddenly the report generation stops working.
> I've added debug logging to the application, and can see that the last
> statement that gets executed is a call to the LocalReport.Render method.
> This never returns.
> If we recycle the application pool, the reports start working again -- for
> another 20 to 40 minutes. Then they stop, just as before.
> Setting the application pools to automatically recycle every 20 minutes
> seems like a very bad solution to this. I would really like to understand
> why it is that the system is locking up. But without being able to step
> into the source code for the LocalReport object, I'm completely at a loss
> as to how I can resolve this.
> Does anyone have any suggestions as to what I could try?
> We're using VS2005 and ASP.NET v2.0, running in IIS6 on Windows Server
> 2003.
> My thanks in advance,
> --
> (O)enone
>|||Mark Fitzpatrick wrote:
> Have you tried using the WebForms version?
Hmm, interesting, no I haven't.
The application in question can potentially be driven from both a web
service and also a Windows Forms application (it's implemented in a separate
DLL that can be used in either environment). I initially wrote it all in the
WinForms environment, and hence by the time I got to running it from the web
I'd forgotten all about the existence of the WebForms version.
As we're only using it to programmatically generate the report content
(we're not using the report viewer control at all), I just assumed that the
WinForms version would work correctly in both environments.
Anyway, I've rebuilt the application using the WebForms version of the DLL
(which was nice and easy), and have deployed that to our productions server,
now I just need to wait and see if it makes a difference. I'll post back
with the results.
Thanks for giving me something else to try! :)
--
(O)enone|||Oenone wrote:
>> Have you tried using the WebForms version?
> Hmm, interesting, no I haven't.
Sadly this has exactly the same problem as the WinForms version. After
working fine for a little while, it ultimately stops returning each time it
is called.
Any other suggestions?
--
(O)enone

Localizing cube elements

We're an ISV that builds a product which includes a predefined set of SSAS2005 cubes, dimensions, and measures. We want to support the localization of the various cube elements. The ideal way would be to use translations - however, we need to support Standard Edition, and my understanding is that translations are only supported under Enterprise Edition. :( So the question is, what's the best way to accomplish this and still support SE?

Right now we're looking at using AMO to programmatically translate the various OLAP elements (we also looked at directly modifying the XML/A deployment script, but aren't pursuing that option for process reasons). There are some concerns about this approach, however. There doesn't seem to be a language-independent way to identify specific OLAP objects from an OLAP client (there is an ID property on some objects, but as far as I can tell it isn't usable from ADOMD.NET, and it isn't present on all objects anyway). In other words, in our admin tools if we want to query a specific cube, there's no language independent way to reference it.

Also, if we change the names of, for example, a measure, we also need to change the expression for any calculations that reference that measure.

Is there some more elegant solution that we're missing here?

Thanks,
Kevin

Kevin.

You can argue back and fourth but looks like the answer for your case is to use translations :).
And that is the feature desinged specifically for the case you describe.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Oh, I agree - which is why I was extremely disappointed when translations was announced as an enterprise edition feature only. That decision really complicated the lives of ISVs. A nice compromise might have been to support a single translation on SE, so that ISVs could localize to one foreign language without having to rename all of their cube elements.

Anyway, it sounds like you're saying that isn't much of a good alternative here that supports SE.

local sql to server sql

I am working on a project that requires pc's on a production line to run a
product testing application. On each pc I would like to have a local sql
database that will have three simple tables. One for product testing
information, one for test results and one for error descriptions. I would
like to link these tables to a server based sql server. In the past, I have
accomplished the same function using Microsoft Access, by creating link
tables to the main sql server, and it has worked quite well. Can I do this
using a local sql server? I've been reading about Sql Server Compact and Sql
Server Express, but I'm not sure which would be better, or if either has the
capability to perform as I need them to. I'd appreciate any help or advice
on this.
Thanks.Install SQL Server Express on the selected Client computers. And create
Linked Server in the Primary SQL Server to each, computer.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"jfmoyn" wrote:
> I am working on a project that requires pc's on a production line to run a
> product testing application. On each pc I would like to have a local sql
> database that will have three simple tables. One for product testing
> information, one for test results and one for error descriptions. I would
> like to link these tables to a server based sql server. In the past, I have
> accomplished the same function using Microsoft Access, by creating link
> tables to the main sql server, and it has worked quite well. Can I do this
> using a local sql server? I've been reading about Sql Server Compact and Sql
> Server Express, but I'm not sure which would be better, or if either has the
> capability to perform as I need them to. I'd appreciate any help or advice
> on this.
> Thanks.|||Thanks. I appreciate your help.
"Mohit K. Gupta" wrote:
> Install SQL Server Express on the selected Client computers. And create
> Linked Server in the Primary SQL Server to each, computer.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
>
> "jfmoyn" wrote:
> > I am working on a project that requires pc's on a production line to run a
> > product testing application. On each pc I would like to have a local sql
> > database that will have three simple tables. One for product testing
> > information, one for test results and one for error descriptions. I would
> > like to link these tables to a server based sql server. In the past, I have
> > accomplished the same function using Microsoft Access, by creating link
> > tables to the main sql server, and it has worked quite well. Can I do this
> > using a local sql server? I've been reading about Sql Server Compact and Sql
> > Server Express, but I'm not sure which would be better, or if either has the
> > capability to perform as I need them to. I'd appreciate any help or advice
> > on this.
> > Thanks.