Showing posts with label calling. Show all posts
Showing posts with label calling. Show all posts

Saturday, February 25, 2012

Application of HTMLviewer.css to reports called through Report Man

We are customizing Report Manager and have been able to get the
reportingservices.css style sheet working well.
As we will be calling reports from within Report Manager, we would like to
apply the HTMLviewer.css file to every report called through Report Manger.
This would enable us to get the same look and feel in the Report Manager as
well as the parameter area / HTML viewer.
Does anyone know if it is possible to implement this?
Thanks
DarrenHi!
Really, you have to snag the report call inside the report manager and to
replace it with your url (a call to report server which differs from the one
generated by report manager only in that it the name of css file as a
parameter - rs:StylSheet it seems to me). It's not very difficult, but
requires concentration. I can recommend a book - Hitchiker's guide to
Reporting Services by Peter Blackburn. It can be very helpful.
Regards, Ailil
"Darren" wrote:
> We are customizing Report Manager and have been able to get the
> reportingservices.css style sheet working well.
> As we will be calling reports from within Report Manager, we would like to
> apply the HTMLviewer.css file to every report called through Report Manger.
> This would enable us to get the same look and feel in the Report Manager as
> well as the parameter area / HTML viewer.
> Does anyone know if it is possible to implement this?
> Thanks
> Darren
>|||Great,
Thanks Ailil - so it can be done! I've actually got that book, but not
knowing Java, got a bit lost. I'll get our Java person to have a look at it
- hopefully it will be possible to pass the report string as a variable and
simply add the stylesheet command to the end.
Darren
"Ailil" wrote:
> Hi!
> Really, you have to snag the report call inside the report manager and to
> replace it with your url (a call to report server which differs from the one
> generated by report manager only in that it the name of css file as a
> parameter - rs:StylSheet it seems to me). It's not very difficult, but
> requires concentration. I can recommend a book - Hitchiker's guide to
> Reporting Services by Peter Blackburn. It can be very helpful.
> Regards, Ailil
> "Darren" wrote:
> > We are customizing Report Manager and have been able to get the
> > reportingservices.css style sheet working well.
> >
> > As we will be calling reports from within Report Manager, we would like to
> > apply the HTMLviewer.css file to every report called through Report Manger.
> > This would enable us to get the same look and feel in the Report Manager as
> > well as the parameter area / HTML viewer.
> >
> > Does anyone know if it is possible to implement this?
> >
> > Thanks
> > Darren
> >
> >|||Hello!
Now I'm a bit lost ;). Why Java? Where are you going to use Java in the
Report Manager? It can be quite ok without java :), particularly if you
already have the book.
Regards, Ailil
"Darren" wrote:
> Great,
> Thanks Ailil - so it can be done! I've actually got that book, but not
> knowing Java, got a bit lost. I'll get our Java person to have a look at it
> - hopefully it will be possible to pass the report string as a variable and
> simply add the stylesheet command to the end.
> Darren
> "Ailil" wrote:
> > Hi!
> >
> > Really, you have to snag the report call inside the report manager and to
> > replace it with your url (a call to report server which differs from the one
> > generated by report manager only in that it the name of css file as a
> > parameter - rs:StylSheet it seems to me). It's not very difficult, but
> > requires concentration. I can recommend a book - Hitchiker's guide to
> > Reporting Services by Peter Blackburn. It can be very helpful.
> >
> > Regards, Ailil
> >
> > "Darren" wrote:
> >
> > > We are customizing Report Manager and have been able to get the
> > > reportingservices.css style sheet working well.
> > >
> > > As we will be calling reports from within Report Manager, we would like to
> > > apply the HTMLviewer.css file to every report called through Report Manger.
> > > This would enable us to get the same look and feel in the Report Manager as
> > > well as the parameter area / HTML viewer.
> > >
> > > Does anyone know if it is possible to implement this?
> > >
> > > Thanks
> > > Darren
> > >
> > >|||Hi Ailil,
I figured that we would have to intercept the call to the Report Server as
shown on page 533, to replace the standard URL call generated by Report
Manager, with a URL where the parameter 'rc:Stylesheet = htmlviewer' is added
to the end.
Thanks
Darren
"Ailil" wrote:
> Hello!
> Now I'm a bit lost ;). Why Java? Where are you going to use Java in the
> Report Manager? It can be quite ok without java :), particularly if you
> already have the book.
> Regards, Ailil
> "Darren" wrote:
> > Great,
> >
> > Thanks Ailil - so it can be done! I've actually got that book, but not
> > knowing Java, got a bit lost. I'll get our Java person to have a look at it
> > - hopefully it will be possible to pass the report string as a variable and
> > simply add the stylesheet command to the end.
> >
> > Darren
> >
> > "Ailil" wrote:
> >
> > > Hi!
> > >
> > > Really, you have to snag the report call inside the report manager and to
> > > replace it with your url (a call to report server which differs from the one
> > > generated by report manager only in that it the name of css file as a
> > > parameter - rs:StylSheet it seems to me). It's not very difficult, but
> > > requires concentration. I can recommend a book - Hitchiker's guide to
> > > Reporting Services by Peter Blackburn. It can be very helpful.
> > >
> > > Regards, Ailil
> > >
> > > "Darren" wrote:
> > >
> > > > We are customizing Report Manager and have been able to get the
> > > > reportingservices.css style sheet working well.
> > > >
> > > > As we will be calling reports from within Report Manager, we would like to
> > > > apply the HTMLviewer.css file to every report called through Report Manger.
> > > > This would enable us to get the same look and feel in the Report Manager as
> > > > well as the parameter area / HTML viewer.
> > > >
> > > > Does anyone know if it is possible to implement this?
> > > >
> > > > Thanks
> > > > Darren
> > > >
> > > >|||Hi!
Hey :). You mean JavaScript :). It's a bit different thing )
Regards, Ailil
"Darren" wrote:
> Hi Ailil,
> I figured that we would have to intercept the call to the Report Server as
> shown on page 533, to replace the standard URL call generated by Report
> Manager, with a URL where the parameter 'rc:Stylesheet = htmlviewer' is added
> to the end.
> Thanks
> Darren
> "Ailil" wrote:
> > Hello!
> > Now I'm a bit lost ;). Why Java? Where are you going to use Java in the
> > Report Manager? It can be quite ok without java :), particularly if you
> > already have the book.
> >
> > Regards, Ailil
> >
> > "Darren" wrote:
> >
> > > Great,
> > >
> > > Thanks Ailil - so it can be done! I've actually got that book, but not
> > > knowing Java, got a bit lost. I'll get our Java person to have a look at it
> > > - hopefully it will be possible to pass the report string as a variable and
> > > simply add the stylesheet command to the end.
> > >
> > > Darren
> > >
> > > "Ailil" wrote:
> > >
> > > > Hi!
> > > >
> > > > Really, you have to snag the report call inside the report manager and to
> > > > replace it with your url (a call to report server which differs from the one
> > > > generated by report manager only in that it the name of css file as a
> > > > parameter - rs:StylSheet it seems to me). It's not very difficult, but
> > > > requires concentration. I can recommend a book - Hitchiker's guide to
> > > > Reporting Services by Peter Blackburn. It can be very helpful.
> > > >
> > > > Regards, Ailil
> > > >
> > > > "Darren" wrote:
> > > >
> > > > > We are customizing Report Manager and have been able to get the
> > > > > reportingservices.css style sheet working well.
> > > > >
> > > > > As we will be calling reports from within Report Manager, we would like to
> > > > > apply the HTMLviewer.css file to every report called through Report Manger.
> > > > > This would enable us to get the same look and feel in the Report Manager as
> > > > > well as the parameter area / HTML viewer.
> > > > >
> > > > > Does anyone know if it is possible to implement this?
> > > > >
> > > > > Thanks
> > > > > Darren
> > > > >
> > > > >|||Yeah - meant JavaScript not Java.
I've posted another message re changing the default htmlviewer style sheet
as the SP2 readme file says that there is a config setting where you can
change the default style sheet.
Thanks for your help.
Darren
"Ailil" wrote:
> Hi!
> Hey :). You mean JavaScript :). It's a bit different thing )
> Regards, Ailil
> "Darren" wrote:
> > Hi Ailil,
> >
> > I figured that we would have to intercept the call to the Report Server as
> > shown on page 533, to replace the standard URL call generated by Report
> > Manager, with a URL where the parameter 'rc:Stylesheet = htmlviewer' is added
> > to the end.
> >
> > Thanks
> > Darren
> >
> > "Ailil" wrote:
> >
> > > Hello!
> > > Now I'm a bit lost ;). Why Java? Where are you going to use Java in the
> > > Report Manager? It can be quite ok without java :), particularly if you
> > > already have the book.
> > >
> > > Regards, Ailil
> > >
> > > "Darren" wrote:
> > >
> > > > Great,
> > > >
> > > > Thanks Ailil - so it can be done! I've actually got that book, but not
> > > > knowing Java, got a bit lost. I'll get our Java person to have a look at it
> > > > - hopefully it will be possible to pass the report string as a variable and
> > > > simply add the stylesheet command to the end.
> > > >
> > > > Darren
> > > >
> > > > "Ailil" wrote:
> > > >
> > > > > Hi!
> > > > >
> > > > > Really, you have to snag the report call inside the report manager and to
> > > > > replace it with your url (a call to report server which differs from the one
> > > > > generated by report manager only in that it the name of css file as a
> > > > > parameter - rs:StylSheet it seems to me). It's not very difficult, but
> > > > > requires concentration. I can recommend a book - Hitchiker's guide to
> > > > > Reporting Services by Peter Blackburn. It can be very helpful.
> > > > >
> > > > > Regards, Ailil
> > > > >
> > > > > "Darren" wrote:
> > > > >
> > > > > > We are customizing Report Manager and have been able to get the
> > > > > > reportingservices.css style sheet working well.
> > > > > >
> > > > > > As we will be calling reports from within Report Manager, we would like to
> > > > > > apply the HTMLviewer.css file to every report called through Report Manger.
> > > > > > This would enable us to get the same look and feel in the Report Manager as
> > > > > > well as the parameter area / HTML viewer.
> > > > > >
> > > > > > Does anyone know if it is possible to implement this?
> > > > > >
> > > > > > Thanks
> > > > > > Darren
> > > > > >
> > > > > >

Application is hung

Hello Friends,
A user is calling stating that their application is hung - sitting with an hour glass or with the browser not responding. Assume you know the server and the instance and that the server supports multiple instances.

You need to determine if the database could be contributing to the problem or could be the cause of the problem. Describe at a high level what process you would follow to rule the database out or in as the problem.

Any idea!

Thanks,
FrankHello Friends,
A user is calling stating that their application is hung

I'll leave that alone....|||Hello Friends,
A user is calling stating that their application is hung - sitting with an hour glass or with the browser not responding. Assume you know the server and the instance and that the server supports multiple instances.

You need to determine if the database could be contributing to the problem or could be the cause of the problem. Describe at a high level what process you would follow to rule the database out or in as the problem.

Any idea!

Thanks,
FrankAsk your instructor or TA which help desk you should call for that kind of problem on these servers?

-PatP|||I'll leave that alone....Now pay attention! They are claiming that their application is hung. That is a different kind of issue, not bragging!

-PatP|||Didn't your sweetie in high school used to call you her applicator?

..damn this is more corral stuff...

Any good question lately?

Oh, and btw, it's never the database...|||High level ... hmmm ... do a hard reset on the application server! If the problem goes away it's the application. If that fails, do a hard reset on the database server. If the problem goes away, the application caused the problem to appear on the database server. If the problem still exists, press the red button in the server room and switch over to the generators.

;)|||Now pay attention! They are claiming that their application is hung. That is a different kind of issue, not bragging!

-PatP
No brag ... just fact!

Monday, February 13, 2012

app.config for DLL

I am calling a C# method/DLL from Reporting Services. In the DLL, I am
referencing ConfigurationSettings.AppSettings["DBConnectionString"].
This should go in app.config in the caller's folder. This is fine when
the caller is a regular .NET application, but I don't know where to put
the app.config for Reporting Services.1. During runtime the report is generated under the Report Server host
process so the <appSetting> section in web.config file should work. Try
rendering a report from the Report which has a textbox with the following
expression:
= System.Configuration.Configuration.AppSettings(<your config value>)
Please note that the web.config file already has a configuration section
so you need to add only the <appSettings> element. You should have the same
result when calling this from your DLL since it will be loaded in the RS
application domain.
2. During design time it is a bit trickier. Unfortunately, the current
configuration handler of the Report Designer doesn't seem to recognize
<appSettings>. However, you can render the report in debug mode by hitting
F5. This renders the report under ReportHost.exe. To get the config settings
working, create a ReportHost.exe.config in C:\Program Files\Microsoft SQL
Server\80\Tools\Report Designer and place your configuration section there
(the <configuration> element should be spelled with small "c"), e.g.:
<?xml version="1.0" encoding="utf-8" ?><configuration>
<appSettings>
<add key="serverUrl" value="http://localhost/reportserver" />
</appSettings>
</configuration>
b) To get the Preview tab working you could either check for Nothing and
replace that with a default value, or wrap the ConfigSettings.AppSettings
call to default to some default constant values. Once again, this is only
needed during design time. Your runtime report generation shouldn't need
this hack.
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Bucky" <uw_badgers@.mail.com> wrote in message
news:1103320212.226556.252030@.f14g2000cwb.googlegroups.com...
>I am calling a C# method/DLL from Reporting Services. In the DLL, I am
> referencing ConfigurationSettings.AppSettings["DBConnectionString"].
> This should go in app.config in the caller's folder. This is fine when
> the caller is a regular .NET application, but I don't know where to put
> the app.config for Reporting Services.
>|||Just to clarify...by web.config I meant the Report Server web.config file
located in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer if default setup settings have been accepted.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Teo Lachev [MVP]" <teo.lachev@.nospam.prologika.com> wrote in message
news:%23wqOlKK5EHA.3728@.TK2MSFTNGP12.phx.gbl...
> 1. During runtime the report is generated under the Report Server host
> process so the <appSetting> section in web.config file should work. Try
> rendering a report from the Report which has a textbox with the following
> expression:
> = System.Configuration.Configuration.AppSettings(<your config value>)
> Please note that the web.config file already has a configuration section
> so you need to add only the <appSettings> element. You should have the
> same result when calling this from your DLL since it will be loaded in the
> RS application domain.
> 2. During design time it is a bit trickier. Unfortunately, the current
> configuration handler of the Report Designer doesn't seem to recognize
> <appSettings>. However, you can render the report in debug mode by hitting
> F5. This renders the report under ReportHost.exe. To get the config
> settings
> working, create a ReportHost.exe.config in C:\Program Files\Microsoft SQL
> Server\80\Tools\Report Designer and place your configuration section there
> (the <configuration> element should be spelled with small "c"), e.g.:
>
> <?xml version="1.0" encoding="utf-8" ?><configuration>
> <appSettings>
> <add key="serverUrl" value="http://localhost/reportserver" />
> </appSettings>
> </configuration>
> b) To get the Preview tab working you could either check for Nothing and
> replace that with a default value, or wrap the ConfigSettings.AppSettings
> call to default to some default constant values. Once again, this is only
> needed during design time. Your runtime report generation shouldn't need
> this hack.
>
> --
> Hope this helps.
> ---
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website: http://www.manning.com/lachev
> Buy it from Amazon.com: http://shrinkster.com/eq
> Home page and blog: http://www.prologika.com/
> ---
> "Bucky" <uw_badgers@.mail.com> wrote in message
> news:1103320212.226556.252030@.f14g2000cwb.googlegroups.com...
>>I am calling a C# method/DLL from Reporting Services. In the DLL, I am
>> referencing ConfigurationSettings.AppSettings["DBConnectionString"].
>> This should go in app.config in the caller's folder. This is fine when
>> the caller is a regular .NET application, but I don't know where to put
>> the app.config for Reporting Services.
>