Friday, March 30, 2012
ReportBuider and cascading parameters
filters?
KamelOn Aug 23, 10:21 am, kamel <kwic...@.gmail.com> wrote:
> Is it possible to implement cascading parametrs via Report Builder
> filters?
> Kamel
Hi,
Haven't found out about Report Builder, but i do know the via BI
studio you can.
In order to work with cascading params, you must have more then one
dataset and
i don't see how that's possible with ReportBuilder.
if you need more info how to do it via Business Intelligence Studio,
just tell me.
Greetings
Vinnie|||I know it's possible in Designer;
I'd like to implement it in ReportBuider...
Thank you for your response.
Wednesday, March 28, 2012
Report Viewer/Default Parameters
Thanks.
accessed
acceded
accused
accedes
accursed
Edit...
Ignore all
Add to dictionary(No suggestions)
Edit...
Ignore all
Add to dictionary
accessed
acceded
accused
accedes
accursed
Edit...
Revert to "accesed"
Assuming you are asking for viewing report through report server: default values can be (1) constant, (2) expression-based, or (3) dataset based.
Regarding (2): you could determine the default value based on the current userid, e.g =iif(User!UserId="abc", "Default1", "Default2")
Regarding (3): you could use the current user information in the query commandtext or as parameter into a stored procedure to dynamically determine the default value.
-- Robert
|||If you are using the ReportViewer control in ASP.NET, you can set the value of the parameter programatically based on the current user identity:
this.ReportViewer1.ServerReport.ReportPath = "/SampleReports/Employee Sales Summary";
ReportParameter p = new ReportParameter("EmpID", "20");
this.ReportViewer1.ServerReport.SetParameters(new ReportParameter[] { p });
Wednesday, March 21, 2012
report via url with parameters: strange issue....
I'm testing my report via a url, with report parameters.
But i have a strange issue:
If I open a new browser, and I do:
"http://localhost/reportserver?/r1/Report_R1&rs:Command=Render&rc:Toolbar=False" (thus without parameters)
Then it takes the default values that are configured in the report.
This returns 3 records, which is OK
If I open a new browser, and I do:
"http://localhost/reportserver?/r1/Report_R1&rs:Command=Render&rc:Toolbar=False&STAmonth=6"
This returns 5 records, which is OK
If I open a new browser, and I do:
"http://localhost/reportserver?/r1/Report_R1&rs:Command=Render&rc:Toolbar=False&STAmonth=5"
This returns 0 records, which is OK
BUT HERE COMES THE STRANGE THING:
If i try to go to two url's after eachother in the same browser, it gives bad result....
thus:
"http://localhost/reportserver?/r1/Report_R1&rs:Command=Render&rc:Toolbar=False&STAmonth=5"
this returns 0 records, this is OK
but if I do hereafter (in the same browser)
"http://localhost/reportserver?/r1/Report_R1&rs:Command=Render&rc:Toolbar=False" (thus without parameters)
it still returns 0 records, while it should return 3 records.
Anyone experienced this also?
What can I do or what am I doing wrong?
Thanks
Hi sttke,
This looks to be a by-product of keeping the session open and caching information. You can add rs:ClearSession=true to the url and it should clear the parameters.
|||that does the job !!!thanks a lot, Brad !!!
Report Timeout
directly to PDF via a web services call to the Reporting Services web
service. For this particular report, at exactly 3 minutes, the report always
aborts processing and redirects to a "Page Cannot Be Displayed". The Report
Server log file at this time shows IsClientConnected...Orphan Request
detected or something like that. When I run the report via Report Manager,
everything works fine. I do specify a timeout value of 2400000 in my Asp.Net
where I'm consuming the web service. I've looked at almost every other
timeout but since it works fine in Report Manager, I am inclined to believe
the problem is in my Asp.Net code. Any ideas?Open your Reporing service's web service reference file and in the
constructor
add: "this.Timeout=......"
Works for web service access method.
"AdamB" <AdamB@.discussions.microsoft.com> wrote in message
news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
>I have a report I execute from an Asp.Net front-end. The report is
>rendered
> directly to PDF via a web services call to the Reporting Services web
> service. For this particular report, at exactly 3 minutes, the report
> always
> aborts processing and redirects to a "Page Cannot Be Displayed". The
> Report
> Server log file at this time shows IsClientConnected...Orphan Request
> detected or something like that. When I run the report via Report
> Manager,
> everything works fine. I do specify a timeout value of 2400000 in my
> Asp.Net
> where I'm consuming the web service. I've looked at almost every other
> timeout but since it works fine in Report Manager, I am inclined to
> believe
> the problem is in my Asp.Net code. Any ideas?|||I'm not sure where this file is that you are referring to. Also, in my
Asp.Net where I am consuming the web service, I am doing the following:
Dim rs As New WebService (where WebService is the name of my reference to
the Reporting Service ws)
rs.Timeout = 2400000
"Oleg Yevteyev" wrote:
> Open your Reporing service's web service reference file and in the
> constructor
> add: "this.Timeout=......"
> Works for web service access method.
> "AdamB" <AdamB@.discussions.microsoft.com> wrote in message
> news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
> >I have a report I execute from an Asp.Net front-end. The report is
> >rendered
> > directly to PDF via a web services call to the Reporting Services web
> > service. For this particular report, at exactly 3 minutes, the report
> > always
> > aborts processing and redirects to a "Page Cannot Be Displayed". The
> > Report
> > Server log file at this time shows IsClientConnected...Orphan Request
> > detected or something like that. When I run the report via Report
> > Manager,
> > everything works fine. I do specify a timeout value of 2400000 in my
> > Asp.Net
> > where I'm consuming the web service. I've looked at almost every other
> > timeout but since it works fine in Report Manager, I am inclined to
> > believe
> > the problem is in my Asp.Net code. Any ideas?
>
>|||Ok, I think you're talking about the Reference.vb file but I have no idea
where this timeout setting is supposed to go.
Adam
"Oleg Yevteyev" wrote:
> Open your Reporing service's web service reference file and in the
> constructor
> add: "this.Timeout=......"
> Works for web service access method.
> "AdamB" <AdamB@.discussions.microsoft.com> wrote in message
> news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
> >I have a report I execute from an Asp.Net front-end. The report is
> >rendered
> > directly to PDF via a web services call to the Reporting Services web
> > service. For this particular report, at exactly 3 minutes, the report
> > always
> > aborts processing and redirects to a "Page Cannot Be Displayed". The
> > Report
> > Server log file at this time shows IsClientConnected...Orphan Request
> > detected or something like that. When I run the report via Report
> > Manager,
> > everything works fine. I do specify a timeout value of 2400000 in my
> > Asp.Net
> > where I'm consuming the web service. I've looked at almost every other
> > timeout but since it works fine in Report Manager, I am inclined to
> > believe
> > the problem is in my Asp.Net code. Any ideas?
>
>|||"AdamB" <AdamB@.discussions.microsoft.com> wrote in message
news:D19C1C10-7F24-4834-9EAC-7A20650CE348@.microsoft.com...
> I'm not sure where this file is that you are referring to. Also, in my
> Asp.Net where I am consuming the web service, I am doing the following:
> Dim rs As New WebService (where WebService is the name of my reference to
> the Reporting Service ws)
> rs.Timeout = 2400000
Ok - seems like it is correct - just be sure to set that Timeout property on
every instance of "ws" you are creating.
More simple way is to open the reference file you correctly identified in
another post and place "rs.Timeout = 2400000"
in the constructor. In that case you wouldn't have to set that property on
every instance of "ws" you're creating.
I hope, you know what the constructor is.
There are a couple more places to check.
1. You can set in Page_Load method of your page
Server.ScriptTimeout=2400
2. Do it globally in machine.config or web.config
<configuration>
<system.web>
<httpRuntime executionTimeout="2400"
................................/>
in addtion of what you have already done.
Tuesday, March 20, 2012
Report subscription and Failure sending mail:
report via email. I used Report Manager to setup the report subscriptions,
but I get the following status message:
"Failure sending mail: The Report Server has encountered a configuration
error; more details in the log files"
The log file contains the following:
ERROR: Throwing
Microsoft.ReportingServices
Any ideas?
I am also getting the error on SQL Server 2005 with SP1 and am currently trying to get the email working.
The only bit of extra information I can give is that when I do
net helpmsg 110
I get: The system cannot open the device of file specified.
As yet, I have no idea what device or file report server is trying to open.
I'll update this message if I figure this out.
Report subscription and Failure sending mail:
report via email. I used Report Manager to setup the report subscriptions,
but I get the following status message:
"Failure sending mail: The Report Server has encountered a configuration
error; more details in the log files"
The log file contains the following:
ERROR: Throwing
Microsoft.ReportingServices
Any ideas?
I am also getting the error on SQL Server 2005 with SP1 and am currently trying to get the email working.
The only bit of extra information I can give is that when I do
net helpmsg 110
I get: The system cannot open the device of file specified.
As yet, I have no idea what device or file report server is trying to open.
I'll update this message if I figure this out.
Report snapshot generation failed on MDX script
Hi,
I am running RS 2005 and Analysis Services 2005. I was able to get RS to connect to the OLAP database (via stored credential) when generating snapshot. However, it failed when processing MDX script in the report dataset. The same report works fine in browser and VStudio, but only failed during snapshot or cache generation. Below is the error message and the affected MDX script. Any help would be appreciated!
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Get Online Help
Incorrect syntax near '{'. Incorrect syntax near 'Business Type'. Incorrect syntax near 'Facility'. Incorrect syntax near 'Production Units Reporting UOM'.
WITH SET [UOM] AS
' ([Raw Materials Source UOM].[Source UOM].ALLMEMBERS - [Raw Materials Source UOM].[Source UOM].[All]) *
([Raw Materials Reporting UOM].[Reporting UOM].ALLMEMBERS - [Raw Materials Reporting UOM].[Reporting UOM].[All]) *
([Production Units Source UOM].[PU Source UOM].ALLMEMBERS - [Production Units Source UOM].[PU Source UOM].[All]) *
([Production Units Reporting UOM].[PU Reporting UOM].ALLMEMBERS - [Production Units Reporting UOM].[PU Reporting UOM].[All])'
SELECT NON EMPTY
{
[Measures].[Weight], [Measures].[Weight per Production Unit Converted]
} ON COLUMNS,
NON EMPTY
{
(([Time].[Year].ALLMEMBERS - [Time].[Year].[All]) *
([Raw Materials].[Category Type].ALLMEMBERS - [Raw Materials].[Category Type].[All]) *
([Raw Materials].[Category].ALLMEMBERS - [Raw Materials].[Category].[All]) *
[UOM])
}
having not IsEmpty([Measures].[Weight]) And ([Measures].[All Facilities Production Unit Converted], [Production Units].[UOM]) > 0
DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS
FROM
(
SELECT ( { [Business Type].[Business Type].&[{11116DDD-FD7B-46AA-A4D8-73492E220001}]}) ON COLUMNS
FROM
(
SELECT ({[Raw Materials Reporting UOM].[Reporting UOM].&[Lb]}) ON COLUMNS
FROM
(
SELECT ({[Production Units Reporting UOM].[PU Reporting UOM].&[Yd2]}) ON COLUMNS FROM [Pinnacle]
)
)
)
WHERE
(
[Facility].[LocationType].&[1],
[Facility].[Initiative - InitiativeFacility].[Initiative].&[{11136DDD-FD7B-46AA-A4D8-73492E220002}]
)
CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
It was a mistake on my part. The data source was set to MS SQL Server, instead it should be MS SQL Analysis Services.
Thanks.
SouBee
Friday, March 9, 2012
Report service and automatically creating a PDF report.
via a report button.
Currently when users click the report button the users web interface opens
(would like to not the the web interface just create the PDF without any
interaction) then the user is prompted to open/saved/cancel.
Is it possible to click on the so called report button and automatically
create the PDF? no dialog boxes appering just create the PDF?
Is this a workstation issue with internet exploier?
Running the 2000 version of SQL & it's counter part of reporting services.
All workstations all XP Pro Sp2
MikeHi Mike,
Well I'm using RS 2005 and all the latest stuff here, so I'm not sure
if it'll work but here goes. From a website, my users click a button
and I then do this in C# my code :
//*******************************
string url;
int idStage =3D Convert.ToInt32(lblIdStage.Text);
int annee =3D Convert.ToInt32(lblAnnee.Text);
int idTrimestreAdmission =3D
Convert.ToInt32(lblIdTrimestreAdmission.Text);
url =3D
"http://xxxxx.xxxxx.ca/ReportServer?/Rapport_xxxx/Etxxxge";
url +=3D "&rs:Format=3DPDF";
url +=3D "&idStage=3D" + idStage;
url +=3D "&annee=3D" + annee;
url +=3D "&idTrimestreAdmission=3D" + idTrimestreAdmission;
url +=3D "&idDomaineFormation=3D" +
Convert.ToInt32(Session["IdDomaineFormation"]);
Response.Redirect(url);
//*******************************
This basically pop up a acrobat reader with my report in it.
Hope it helps, cheers.
Mike a =E9crit :
> woundering if there's a way for the user to automatically create a PDF re=port
> via a report button.
> Currently when users click the report button the users web interface opens
> (would like to not the the web interface just create the PDF without any
> interaction) then the user is prompted to open/saved/cancel.
> Is it possible to click on the so called report button and automatically
> create the PDF? no dialog boxes appering just create the PDF?
> Is this a workstation issue with internet exploier?
> Running the 2000 version of SQL & it's counter part of reporting services.
> All workstations all XP Pro Sp2 > > Mike
Wednesday, March 7, 2012
Report Server renders incorrect URL for [Export] button
We have a Report Server 2000 on a client site. The server is accessible
via server name (NetBIOS name) from the local LAN, but only via a DNS name
from outer regions of the WAN (these users are on a different but trusted
domain in the bigger forest). The reports render successfully when accessed
via either the NetBIOS or DNS name, but the URL rendered for the â'Exportâ'
functionality always refers to the NetBIOS (server) name. As a result users
on the WAN cannot use the â'Exportâ' functionality since the URL is not found
from that network location (without us adding a local host entry which is
against company policy).
The page source shows a number of variables, including dmRepUrl,
touchSessionUrl, printUrl, renderingUrl, exportUrl and docMapUrl â' these are
all incorrectly mapping to the server name.
I cannot find any matching entry in the Report Server configuration and it
seems as-if this code is output by a compiled assembly on the Report Server.
Are these URLs configurable at all?
Thank you,
James Avenant
GijimaAst ConsultantHi James,
Thank you for your posting!
From your description, my understanding of this issue is: You want to
deploy your report server on a WAN environment. If I misunderstood your
concern, please feel free to let me know.
Based on my experience, you need to specify a fully qualified domain name
instead of the Netbios name in the config file.
The first step is to change the following two registry values under this
key to the appropriate new values:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Reporting
Services\
RSVirtualDir = http://server.company.com/ReportServer (Old Value was
http://server/ReportServer)
WAVirtualDir = http://server.company.com/Reports (Old Value was
http://server/Reports)
The final piece is to make a change in the following to config files on
your reporting server:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\RSWebApplication.config
Each file will contain one instance of the server referenced by name
(http://server/ReportServer). Replace it with the fully qualified domain
name, keeping the trailing directory
(http://server.company.com/ReportServer)
Now just restart the service and you should be able to access the reports
inside or out using a fully qualified domain name.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Saturday, February 25, 2012
Report Server access via WebClient / HttpWebRequest
This is a follow-up question I have to a previous post about accessing the
Reporting Services server without exposing a URL to the user that can be
tampered with.
I am using WebClient / HttpWebRequest to screen scrape a server-side
initiated request to the Reporting Service and writing the output into an
ASPX page. This works to a certain extent.
Unfortunately, when the ASPX page initiates the call, all relative URLs are
not correctly processed. For example, the usual address of the report server
might be http://brensydsql/ReportServer however, using a WebClient /
HttpWebRequest will use the hostname of the machine it's on, so relative URLs
will be relative to the local hostname instead of the report server's
hostname.
ie /images/blah.jpg would resolve as http://hostname/images/blah.jpg instead
of http://brensydsql/images/blah.jpg
Adding a <base href='http://brensydsql'> doesn't work either because Sql
Reporting services resources are only accessible during the request
processing and cannot be directly linked after the request has finished. The
Reporting Server needs to be fooled into thinking the root server is
brensydsql when the request is first initiated.
For some reason, after the report has been processed, the fully qualified
url to the image / whatever resource is no longer valid - seems like it is
only valid for the duration of the request?
I've tried to set the BaseAddress property of the WebClient object but this
has no effect.I have been looking at the same problem. I can't believe Microsoft
decided to pass the parameters unencrypted. Surely they must have
realised developers would need to have hidden and secured params.
Anyway, I digress.
Try using regular expressions to alter all of the links in the report.
The basics of this is here:
http://www.junto.co.uk/Diary/2005/10/6363e490-89a1-4f22-b811-d8d82c98acc9.aspx
Hope this helped.
Philip York wrote:
> Hi,
> This is a follow-up question I have to a previous post about accessing the
> Reporting Services server without exposing a URL to the user that can be
> tampered with.
> I am using WebClient / HttpWebRequest to screen scrape a server-side
> initiated request to the Reporting Service and writing the output into an
> ASPX page. This works to a certain extent.
> Unfortunately, when the ASPX page initiates the call, all relative URLs are
> not correctly processed. For example, the usual address of the report server
> might be http://brensydsql/ReportServer however, using a WebClient /
> HttpWebRequest will use the hostname of the machine it's on, so relative URLs
> will be relative to the local hostname instead of the report server's
> hostname.
> ie /images/blah.jpg would resolve as http://hostname/images/blah.jpg instead
> of http://brensydsql/images/blah.jpg
> Adding a <base href='http://brensydsql'> doesn't work either because Sql
> Reporting services resources are only accessible during the request
> processing and cannot be directly linked after the request has finished. The
> Reporting Server needs to be fooled into thinking the root server is
> brensydsql when the request is first initiated.
> For some reason, after the report has been processed, the fully qualified
> url to the image / whatever resource is no longer valid - seems like it is
> only valid for the duration of the request?
> I've tried to set the BaseAddress property of the WebClient object but this
> has no effect.
Monday, February 20, 2012
Report request orphaned after 60 seconds?
report is calling a stored procedure via ADO.Net. The stored procedure is
slow, but acceptable.
Iâ've set the report timeout settings to 300 in all the relevant config files
and the report itself but this had no effect.
The RunningJobs record for this request in the ReportServer database shows
the report having a timeout of 1800.
My questions are:
1. These time values consistently represent the time in seconds, right?
2. I realise orphaned and expired requests are cancelled after 60 seconds by
default, but why does is this request orphaned?
Section of the ReportServer log:
>>
aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
'/Reports/NumberOneReport' )
aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
SqlStreamingBufferSize to default value of '65536' Bytes because it was not
specified in Server system properties.
aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
jobs to the database
aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., Error doing timer action for Running Requests Scavenger;
<<
Any help or suggestions appreciated.Roberto,
FYI: The ADO connection probably has its own Timeout setting. I know SQL
Server itself does. Have you checked these two properties yet? I'm not sure
where the ADO timeout setting is, but I know the SQL Server one is in the
Server Properties window.
Hope that helps.
Catadmin
--
MCDBA, MCSA
Random Thoughts: If a person is Microsoft Certified, does that mean that
Microsoft pays the bills for the funny white jackets that tie in the back?
@.=)
"Roberto" wrote:
> I am trying to debug a problem where a report times out after 60 seconds; the
> report is calling a stored procedure via ADO.Net. The stored procedure is
> slow, but acceptable.
> Iâ've set the report timeout settings to 300 in all the relevant config files
> and the report itself but this had no effect.
> The RunningJobs record for this request in the ReportServer database shows
> the report having a timeout of 1800.
> My questions are:
> 1. These time values consistently represent the time in seconds, right?
> 2. I realise orphaned and expired requests are cancelled after 60 seconds by
> default, but why does is this request orphaned?
> Section of the ReportServer log:
> >>
> aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
> '/Reports/NumberOneReport' )
> aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
> SqlStreamingBufferSize to default value of '65536' Bytes because it was not
> specified in Server system properties.
> aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
> jobs to the database
> aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for more
> details., Error doing timer action for Running Requests Scavenger;
> <<
> Any help or suggestions appreciated.|||The ADO timeout is set in my component.config to 300 (debugged this and the
call is using this value), the SQL server timeout to 600.
I hadn't thought of the SQL Server timeout so thanks for the post.
Still having the same problem though.
"Catadmin" wrote:
> Roberto,
> FYI: The ADO connection probably has its own Timeout setting. I know SQL
> Server itself does. Have you checked these two properties yet? I'm not sure
> where the ADO timeout setting is, but I know the SQL Server one is in the
> Server Properties window.
> Hope that helps.
> Catadmin
> --
> MCDBA, MCSA
> Random Thoughts: If a person is Microsoft Certified, does that mean that
> Microsoft pays the bills for the funny white jackets that tie in the back?
> @.=)
>
> "Roberto" wrote:
> > I am trying to debug a problem where a report times out after 60 seconds; the
> > report is calling a stored procedure via ADO.Net. The stored procedure is
> > slow, but acceptable.
> >
> > Iâ've set the report timeout settings to 300 in all the relevant config files
> > and the report itself but this had no effect.
> >
> > The RunningJobs record for this request in the ReportServer database shows
> > the report having a timeout of 1800.
> >
> > My questions are:
> >
> > 1. These time values consistently represent the time in seconds, right?
> >
> > 2. I realise orphaned and expired requests are cancelled after 60 seconds by
> > default, but why does is this request orphaned?
> >
> > Section of the ReportServer log:
> >
> > >>
> >
> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to RenderFirst(
> > '/Reports/NumberOneReport' )
> >
> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
> > SqlStreamingBufferSize to default value of '65536' Bytes because it was not
> > specified in Server system properties.
> >
> > aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1 running
> > jobs to the database
> >
> > aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
> > RunningJobContext.IsClientConnected; found orphaned request
> >
> > aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for more
> > details., Error doing timer action for Running Requests Scavenger;
> > <<
> >
> > Any help or suggestions appreciated.|||Is your report server running on Windows 2003 with IIS 6? Check if
increasing the IIS timeout (120 seconds on IIS6) on the default web site
helps.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roberto" <Roberto@.discussions.microsoft.com> wrote in message
news:C5C7D412-819E-46AD-86D6-53E782A09368@.microsoft.com...
> The ADO timeout is set in my component.config to 300 (debugged this and
> the
> call is using this value), the SQL server timeout to 600.
> I hadn't thought of the SQL Server timeout so thanks for the post.
> Still having the same problem though.
> "Catadmin" wrote:
>> Roberto,
>> FYI: The ADO connection probably has its own Timeout setting. I know SQL
>> Server itself does. Have you checked these two properties yet? I'm not
>> sure
>> where the ADO timeout setting is, but I know the SQL Server one is in the
>> Server Properties window.
>> Hope that helps.
>> Catadmin
>> --
>> MCDBA, MCSA
>> Random Thoughts: If a person is Microsoft Certified, does that mean that
>> Microsoft pays the bills for the funny white jackets that tie in the
>> back?
>> @.=)
>>
>> "Roberto" wrote:
>> > I am trying to debug a problem where a report times out after 60
>> > seconds; the
>> > report is calling a stored procedure via ADO.Net. The stored procedure
>> > is
>> > slow, but acceptable.
>> >
>> > I've set the report timeout settings to 300 in all the relevant config
>> > files
>> > and the report itself but this had no effect.
>> >
>> > The RunningJobs record for this request in the ReportServer database
>> > shows
>> > the report having a timeout of 1800.
>> >
>> > My questions are:
>> >
>> > 1. These time values consistently represent the time in seconds, right?
>> >
>> > 2. I realise orphaned and expired requests are cancelled after 60
>> > seconds by
>> > default, but why does is this request orphaned?
>> >
>> > Section of the ReportServer log:
>> >
>> > >>
>> >
>> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Call to
>> > RenderFirst(
>> > '/Reports/NumberOneReport' )
>> >
>> > aspnet_wp!library!e88!05/12/2005-12:34:52:: i INFO: Initializing
>> > SqlStreamingBufferSize to default value of '65536' Bytes because it was
>> > not
>> > specified in Server system properties.
>> >
>> > aspnet_wp!runningjobs!834!12/05/2005-12:35:49:: i INFO: Adding: 1
>> > running
>> > jobs to the database
>> >
>> > aspnet_wp!runningjobs!834!12/05/2005-12:36:49:: i INFO:
>> > RunningJobContext.IsClientConnected; found orphaned request
>> >
>> > aspnet_wp!library!834!12/05/2005-12:36:49:: e ERROR: Throwing
>> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details., Error doing timer action for Running Requests Scavenger;
>> > <<
>> >
>> > Any help or suggestions appreciated.|||I'm running locally on XP Pro, IIS 5.1
The IIS connection timeout is set to 900 seconds.
The report is executed via a web service which uses ADO.Net to call a stored
proc. I'll keep working on this and post more information when I get it. Keep
the ideas coming!
"Robert Bruckner [MSFT]" wrote:
> Is your report server running on Windows 2003 with IIS 6? Check if
> increasing the IIS timeout (120 seconds on IIS6) on the default web site
> helps.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Roberto" <Roberto@.discussions.microsoft.com> wrote in message
> news:C5C7D412-819E-46AD-86D6-53E782A09368@.microsoft.com...|||The report is executed via a web service which uses ADO.Net to call a stored
proc.
Web services have a default timeout of 100 seconds; that was the problem,
not the report server.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwebservicesprotocolswebclientprotocolclasstimeouttopic.asp
The code to resolve this issue was:
this.Timeout = System.Threading.Timeout.Infinite;
Where â'thisâ' is my web service class, which is inheriting from
System.Web.Services.Protocols.SoapHttpClientProtocol
Report rendered via webservice not executing from cache
the report on a Shared schedule'
I generate the report using the webservice function Render. All the
settings seem to be set properly, the cache options setting (using
GetCacheOptions) returns True, and the ExpirationDateTime is correct.
So how come when the report is run, it brings up a fresh rendition of
the report (according to the Globals!ExecutionTime variable)?
Could it be something I am not setting correctly when I render the
report? The only thing I am sending are the parameters (which by the
way I am forced to get directly from the database, since RS does not
retrieve second or third level parameters)
Please help!Hello Dear Hella
i need a feavour
i am Working on SQL Reporting Services since one month
i have a problem in generating report across the domains
My client database server is not configured to public domain
i am unable to access the report
So i thought of Using Web service to render the report
currently i am using Report viewer Control
You mentioned in your query that You are using web service
so can u help me in this regard
like what is the design to follow
and i need some code
waiting for your reply
have a good day
Anil Kumar
(anilkumarv@.infotechsw.com)
Hella wrote:
> I set a report to 'Cache a temporary copy of the report. Expire copy of
> the report on a Shared schedule'
> I generate the report using the webservice function Render. All the
> settings seem to be set properly, the cache options setting (using
> GetCacheOptions) returns True, and the ExpirationDateTime is correct.
> So how come when the report is run, it brings up a fresh rendition of
> the report (according to the Globals!ExecutionTime variable)?
> Could it be something I am not setting correctly when I render the
> report? The only thing I am sending are the parameters (which by the
> way I am forced to get directly from the database, since RS does not
> retrieve second or third level parameters)
> Please help!|||Anil,
Here is the code I am using:
Const REPORT_NAME = "/Reporting/Activity Types Detail"
Const FOLDER_PATH = "\\FileServer\Activity Types Detail\"
Dim strConn As String = "Integrated
Security=SSPI;server=servername;database=dbname"
Dim oConn As SqlConnection = New SqlConnection(strConn)
Dim oDataRead As SqlDataReader
Dim forRendering As Boolean = True
Dim historyID As String = Nothing
Dim values As ReportService.ParameterValue() = Nothing
Dim credentials As ReportService.DataSourceCredentials() =Nothing
Dim parameters As ReportService.ReportParameter() = Nothing
Dim catItems As ReportService.CatalogItem() = Nothing
Dim rs As New ReportService.ReportingService
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
rs.Timeout = 36000000 '10 hours
catItems = rs.ListChildren(REPORT_NAME, True)
For Each cItem As ReportService.CatalogItem In catItems
If cItem.Type.ToString.ToLower = "report" Then
Dim report As String = cItem.Path.ToString
WriteLog("Processing report: " & report, True)
If Mid(cItem.Name.ToString, 1, 7) = "Monthly" Then
Try
'gets only 1st parameter values
parameters = rs.GetReportParameters(report,
historyID, forRendering, values, credentials)
If Not (parameters Is Nothing) Then
For Each ParamValue As
ReportService.ValidValue In parameters(0).ValidValues
'txtProgressLog.Text =txtProgressLog.Text & vbCrLf & "Parameter 1: " & parameters(0).Name & "
- " & ParamValue.Value
WriteLog("Parameter 1: " &
parameters(0).Name & " - " & ParamValue.Value, False)
'get second level parameters
Dim strCommand As String = "SELECT
DISTINCT T0.objid AS EmpObjid, T0.first_name + ' ' + T0.last_name AS
EmpName FROM dbo.table_employee T0 INNER JOIN dbo.table_act_entry T1 ON
T0.objid = T1.act_entry2user WHERE (DATEPART(yy, T1.entry_time) = 2005)
AND (T1.entry_time < LTRIM(STR(DATEPART(mm, GETDATE()))) + '/1/' +
LTRIM(STR(DATEPART(yy, GETDATE())))) AND T0.x_department = '" &
ParamValue.Value & "'"
Dim oComm As SqlCommand = New
SqlCommand(strCommand, oConn)
oConn.Open()
oDataRead = oComm.ExecuteReader
'Render reports using parameter
combination
Do Until oDataRead.Read = False
'txtProgressLog.Text =txtProgressLog.Text & vbCrLf & "Parameter 2: " & parameters(1).Name & "
- " & oDataRead(0).ToString
WriteLog("Parameter 2: " &
parameters(1).Name & " - " & oDataRead(0).ToString & " - " &
parameters(2).Name & " - " & oDataRead(1).ToString, False)
'build parameter names and
values
Dim param(2) As
ReportService.ParameterValue
param(0) = New
ReportService.ParameterValue
param(1) = New
ReportService.ParameterValue
param(2) = New
ReportService.ParameterValue
param(0).Name =parameters(0).Name
param(0).Value =ParamValue.Value
param(1).Name =parameters(1).Name
param(1).Value = oDataRead(0)
param(2).Name =parameters(2).Name
param(2).Value = oDataRead(1)
Dim result As Byte() = Nothing
Dim iColon As Int16 = 0
Dim sFileName As String =cItem.Name.ToString & " - " & ParamValue.Value & " - " &
oDataRead(1).ToString & " - " & oDataRead(0).ToString
'remove colon from department name
iColon = InStr(sFileName, ":")
If iColon > 0 Then
sFileName = Mid(sFileName,
1, iColon - 1) & Mid(sFileName, iColon + 1)
End If
rs.SessionHeaderValue = New
ReportService.SessionHeader
result = rs.Render(report,
"HTML4.0", Nothing, Nothing, param, Nothing, Nothing, Nothing, Nothing,
Nothing, Nothing, Nothing)
WriteLog("Execution date and
time: " & rs.SessionHeaderValue.ExecutionDateTime & vbTab & "Is new
execution: " & rs.SessionHeaderValue.IsNewExecution.ToString, False)
Console.WriteLine(("Expiration
date and time: " & rs.SessionHeaderValue.ExpirationDateTime.ToString))
Dim ExpDef As
ReportService.ExpirationDefinition
Console.WriteLine(("Cache
Options: " & rs.GetCacheOptions(report, ExpDef).ToString))
If
rs.SessionHeaderValue.IsNewExecution = True Then
Dim stream As FileStream =File.Create(FOLDER_PATH & sFileName & ".html", result.Length)
stream.Write(result, 0,
result.Length)
stream.Close()
End If
'Process.Start(FOLDER_PATH &
sFileName & ".html")
Loop
oComm = Nothing
oConn.Close()
Next ParamValue
End If
Catch exc As SoapException
Console.WriteLine(exc.Detail.InnerXml.ToString())
WriteLog(exc.Detail.InnerXml.ToString(),
False)
Exit Sub
End Try
End If
End If
Next
Hope it helps.