RS and HTTPS: service

Showing posts with label service. Show all posts

Wednesday, March 28, 2012

rsExecutionNotFound

We have just upgraded to SQL Server Reporting Service 2005 and our reports
were consistently generating 'rsExecutionNotFound' errors, like the one
shown below. The errors happen when a report was refreshed or a drilldown
'+' was clicked 90 seconds after the report was initially delivered.
We found the value for SessionTimeout was set to 60 instead of the default
value of 600. We had changed the value to 60 while attempting to decrease
the startup time for delivering a report. I'm not really sure how a 60
second setting got translated to a 90 second timeout but it was very
consistent.
When we changed the value to back to 600, the 90 second timeout ceased.
However, we have several users who like to keep the report up all day and
periodically hit 'Refresh' to see any updates. I suspect the current
SessionTimeout setting of 10 minutes will not be satisfactory.
How high can we set the value for SessionTimeout before causing problems
with Reporting Services or IIS?
Thanks,
TomHi Tom,
Welcome to MSDN newsgroup.
From your description, I learned that you're upgrading your SQLServer
Reporting services reports from 2000 to 2005 version. And you found that
since the default session timeout setting is changed to 60 in the report
server application, there will occur 'rsExecutionNotFound' error. Currently
you're wondering whether there is any means to enlarge the session timeout
to a large enough value to avoid such issue, correct?
Based on my understanding, SQL Server reporting service use ASP.NET web
application as its report server application, therefore the session timeout
you mentioned should be ASP.NET web application's session timeout setting.
And this timeout setting controls how long data stored in ASP.NET session
state can be persisted. Generally, we don't recommend that we set the
timeout to a too large value because session state consumes server's memory
resource and will hit server application's performance.
In addition, for the 90 seconds you mentioned, I'm thinking it could be the
ASP.NET http request's execution timeout setting since executionTimeout's
default value is 90 seconds(set in server's machine.config in .net
framework config dir). This timeout controls how long each ASP.NET request
can run on the server. For example, if our web page or web report page will
need to run a long task, we need to enlarge this timeout setting:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
ml/gngrfhttpruntimesection.asp
<system.web>
<httpRuntime
executionTimeout="45"
/>
Hope this helps.
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| From: "Tom Bean" <tbean@.newsgroup.nospam>
| Subject: rsExecutionNotFound
| Date: Wed, 25 Jan 2006 14:33:47 -0600
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67516
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| We have just upgraded to SQL Server Reporting Service 2005 and our
reports
| were consistently generating 'rsExecutionNotFound' errors, like the one
| shown below. The errors happen when a report was refreshed or a
drilldown
| '+' was clicked 90 seconds after the report was initially delivered.
|
| We found the value for SessionTimeout was set to 60 instead of the
default
| value of 600. We had changed the value to 60 while attempting to
decrease
| the startup time for delivering a report. I'm not really sure how a 60
| second setting got translated to a 90 second timeout but it was very
| consistent.
|
| When we changed the value to back to 600, the 90 second timeout ceased.
| However, we have several users who like to keep the report up all day and
| periodically hit 'Refresh' to see any updates. I suspect the current
| SessionTimeout setting of 10 minutes will not be satisfactory.
|
| How high can we set the value for SessionTimeout before causing problems
| with Reporting Services or IIS?
|
| Thanks,
| Tom
|
|
||||Steven,
We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
that could possibly cause the reports to timeout but the reports continued
to throw 'rsExecutionNotFound' after 90 seconds. The only change that
eliminated the error was increasing 'SessionTimeout' in the
ConfigurationInfo table.
Since sending my original message, I have recalled why we had lowered the
'SessionTimeout' setting to 60. We lowered the value to see new results in
a refreshed report sooner and under RS2000 there were no timeout problems.
We are noticing other problems with reports that worked perfectly in RS2000.
These problems appear to be the result of timeouts. Some of the problems we
have encountered are?
1) The 'rsExecutionNotFound' error when trying to refresh a report, as in
the original post.
2) Our users get the message "This report requires a default or
user-defined value for the report parameter 'Id'. To run or subscribe to
this report, you must provide a parameter value.
(rsReportParameterValueNotSet)" when they click a drilldown '+' after a
report has been sitting in the browser for about 5-10 minutes.
3) 'rsInternalError' generated when using the &rc:Toolbar=false with some
reports that contain subreports. This error says "See the error log for
more details" but where is the error log?
What has changed in RS2005 to cause these problems? And, what do I need to
do to resolve them?
Thanks,
Tom
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
> Hi Tom,
> Welcome to MSDN newsgroup.
> From your description, I learned that you're upgrading your SQLServer
> Reporting services reports from 2000 to 2005 version. And you found that
> since the default session timeout setting is changed to 60 in the report
> server application, there will occur 'rsExecutionNotFound' error.
> Currently
> you're wondering whether there is any means to enlarge the session timeout
> to a large enough value to avoid such issue, correct?
> Based on my understanding, SQL Server reporting service use ASP.NET web
> application as its report server application, therefore the session
> timeout
> you mentioned should be ASP.NET web application's session timeout setting.
> And this timeout setting controls how long data stored in ASP.NET session
> state can be persisted. Generally, we don't recommend that we set the
> timeout to a too large value because session state consumes server's
> memory
> resource and will hit server application's performance.
> In addition, for the 90 seconds you mentioned, I'm thinking it could be
> the
> ASP.NET http request's execution timeout setting since executionTimeout's
> default value is 90 seconds(set in server's machine.config in .net
> framework config dir). This timeout controls how long each ASP.NET
> request
> can run on the server. For example, if our web page or web report page
> will
> need to run a long task, we need to enlarge this timeout setting:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
> ml/gngrfhttpruntimesection.asp
> <system.web>
> <httpRuntime
> executionTimeout="45"
> />
> Hope this helps.
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> --
> | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | Subject: rsExecutionNotFound
> | Date: Wed, 25 Jan 2006 14:33:47 -0600
> | Lines: 23
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:67516
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | We have just upgraded to SQL Server Reporting Service 2005 and our
> reports
> | were consistently generating 'rsExecutionNotFound' errors, like the one
> | shown below. The errors happen when a report was refreshed or a
> drilldown
> | '+' was clicked 90 seconds after the report was initially delivered.
> |
> | We found the value for SessionTimeout was set to 60 instead of the
> default
> | value of 600. We had changed the value to 60 while attempting to
> decrease
> | the startup time for delivering a report. I'm not really sure how a 60
> | second setting got translated to a 90 second timeout but it was very
> | consistent.
> |
> | When we changed the value to back to 600, the 90 second timeout ceased.
> | However, we have several users who like to keep the report up all day
> and
> | periodically hit 'Refresh' to see any updates. I suspect the current
> | SessionTimeout setting of 10 minutes will not be satisfactory.
> |
> | How high can we set the value for SessionTimeout before causing problems
> | with Reporting Services or IIS?
> |
> | Thanks,
> | Tom
> |
> |
> |
>|||Thanks for your response Tom,
Em, as far as I known, there hasn't any particular changes regarding on the
timeout setting you mentioned, such setting is ususally adjusted by some
peformance tuning consideration compared to previous version.
Does the problem specific to machine or just concerned with those
particular reports?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--
| From: "Tom Bean" <tbean@.newsgroup.nospam>
| References: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
<JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl>
| Subject: Re: rsExecutionNotFound
| Date: Thu, 26 Jan 2006 11:20:14 -0600
| Lines: 138
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <urYRNzpIGHA.3936@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:67581
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Steven,
|
| We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
| that could possibly cause the reports to timeout but the reports
continued
| to throw 'rsExecutionNotFound' after 90 seconds. The only change that
| eliminated the error was increasing 'SessionTimeout' in the
| ConfigurationInfo table.
|
| Since sending my original message, I have recalled why we had lowered the
| 'SessionTimeout' setting to 60. We lowered the value to see new results
in
| a refreshed report sooner and under RS2000 there were no timeout problems.
|
| We are noticing other problems with reports that worked perfectly in
RS2000.
| These problems appear to be the result of timeouts. Some of the problems
we
| have encountered are?
|
| 1) The 'rsExecutionNotFound' error when trying to refresh a report, as
in
| the original post.
|
| 2) Our users get the message "This report requires a default or
| user-defined value for the report parameter 'Id'. To run or subscribe to
| this report, you must provide a parameter value.
| (rsReportParameterValueNotSet)" when they click a drilldown '+' after a
| report has been sitting in the browser for about 5-10 minutes.
|
| 3) 'rsInternalError' generated when using the &rc:Toolbar=false with
some
| reports that contain subreports. This error says "See the error log for
| more details" but where is the error log?
|
| What has changed in RS2005 to cause these problems? And, what do I need
to
| do to resolve them?
|
| Thanks,
| Tom
|
| "Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
| news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
| > Hi Tom,
| >
| > Welcome to MSDN newsgroup.
| >
| > From your description, I learned that you're upgrading your SQLServer
| > Reporting services reports from 2000 to 2005 version. And you found that
| > since the default session timeout setting is changed to 60 in the report
| > server application, there will occur 'rsExecutionNotFound' error.
| > Currently
| > you're wondering whether there is any means to enlarge the session
timeout
| > to a large enough value to avoid such issue, correct?
| >
| > Based on my understanding, SQL Server reporting service use ASP.NET web
| > application as its report server application, therefore the session
| > timeout
| > you mentioned should be ASP.NET web application's session timeout
setting.
| > And this timeout setting controls how long data stored in ASP.NET
session
| > state can be persisted. Generally, we don't recommend that we set the
| > timeout to a too large value because session state consumes server's
| > memory
| > resource and will hit server application's performance.
| >
| > In addition, for the 90 seconds you mentioned, I'm thinking it could be
| > the
| > ASP.NET http request's execution timeout setting since
executionTimeout's
| > default value is 90 seconds(set in server's machine.config in .net
| > framework config dir). This timeout controls how long each ASP.NET
| > request
| > can run on the server. For example, if our web page or web report page
| > will
| > need to run a long task, we need to enlarge this timeout setting:
| >
| >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
| > ml/gngrfhttpruntimesection.asp
| >
| > <system.web>
| > <httpRuntime
| > executionTimeout="45"
| > />
| >
| > Hope this helps.
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > Get Secure! www.microsoft.com/security
| > (This posting is provided "AS IS", with no warranties, and confers no
| > rights.)
| >
| >
| >
| > --
| > | From: "Tom Bean" <tbean@.newsgroup.nospam>
| > | Subject: rsExecutionNotFound
| > | Date: Wed, 25 Jan 2006 14:33:47 -0600
| > | Lines: 23
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| > | X-RFC2646: Format=Flowed; Original
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| > | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
| > | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.sqlserver.reportingsvcs:67516
| > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
| > |
| > | We have just upgraded to SQL Server Reporting Service 2005 and our
| > reports
| > | were consistently generating 'rsExecutionNotFound' errors, like the
one
| > | shown below. The errors happen when a report was refreshed or a
| > drilldown
| > | '+' was clicked 90 seconds after the report was initially delivered.
| > |
| > | We found the value for SessionTimeout was set to 60 instead of the
| > default
| > | value of 600. We had changed the value to 60 while attempting to
| > decrease
| > | the startup time for delivering a report. I'm not really sure how a
60
| > | second setting got translated to a 90 second timeout but it was very
| > | consistent.
| > |
| > | When we changed the value to back to 600, the 90 second timeout
ceased.
| > | However, we have several users who like to keep the report up all day
| > and
| > | periodically hit 'Refresh' to see any updates. I suspect the current
| > | SessionTimeout setting of 10 minutes will not be satisfactory.
| > |
| > | How high can we set the value for SessionTimeout before causing
problems
| > | with Reporting Services or IIS?
| > |
| > | Thanks,
| > | Tom
| > |
| > |
| > |
| >
|
|
||||Steven,
The problem outlined in 1) occurred with every report until we increased
'SessionTimeout'. The problem in 2) still occurs with every report. In
RS2000, if the report sat too long, the '+' didn't expand the subreport but
they didn't produce the error message which makes us look bad to our users.
We would prefer the stale reports just quit working rather than exposing an
error message to our users.
After working more with the report that caused problem 3), I discovered the
'rsInternalError' only happened when the report returned an empty dataset.
I have no idea why removing the &rc:Toolbar=false parameter would make the
problem to go away. As I said, the report ran fine in RS2000. It also ran
fine in designer. However, when put into production the error occurred, so
there is a definite disconnect between running reports in designer and in a
browser. Do you know of any changes in the way RS2005 handles empty
datasets?
Another irritation we have noticed is that the field names in RS2005 seem to
be case sensitive which wasn't the case with RS2000. This has caused
problems with parameters in the URL also.
As far as changes to performance tuning settings, we upgraded our
installation of RS2000 to RS2005 with no changes to the settings of IIS.
Any changes made to any settings must have been made by RS2005 but we don't
know what they are. Can you give us any more information?
Thanks,
Tom
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:Z6Utq%23XJGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Thanks for your response Tom,
> Em, as far as I known, there hasn't any particular changes regarding on
> the
> timeout setting you mentioned, such setting is ususally adjusted by some
> peformance tuning consideration compared to previous version.
> Does the problem specific to machine or just concerned with those
> particular reports?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> --
> | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | References: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> <JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl>
> | Subject: Re: rsExecutionNotFound
> | Date: Thu, 26 Jan 2006 11:20:14 -0600
> | Lines: 138
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | Message-ID: <urYRNzpIGHA.3936@.TK2MSFTNGP12.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:67581
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Steven,
> |
> | We changed 'Idle Timeout', 'Execution Timeout', and anything else in IIS
> | that could possibly cause the reports to timeout but the reports
> continued
> | to throw 'rsExecutionNotFound' after 90 seconds. The only change that
> | eliminated the error was increasing 'SessionTimeout' in the
> | ConfigurationInfo table.
> |
> | Since sending my original message, I have recalled why we had lowered
> the
> | 'SessionTimeout' setting to 60. We lowered the value to see new results
> in
> | a refreshed report sooner and under RS2000 there were no timeout
> problems.
> |
> | We are noticing other problems with reports that worked perfectly in
> RS2000.
> | These problems appear to be the result of timeouts. Some of the
> problems
> we
> | have encountered are?
> |
> | 1) The 'rsExecutionNotFound' error when trying to refresh a report, as
> in
> | the original post.
> |
> | 2) Our users get the message "This report requires a default or
> | user-defined value for the report parameter 'Id'. To run or subscribe to
> | this report, you must provide a parameter value.
> | (rsReportParameterValueNotSet)" when they click a drilldown '+' after a
> | report has been sitting in the browser for about 5-10 minutes.
> |
> | 3) 'rsInternalError' generated when using the &rc:Toolbar=false with
> some
> | reports that contain subreports. This error says "See the error log for
> | more details" but where is the error log?
> |
> | What has changed in RS2005 to cause these problems? And, what do I need
> to
> | do to resolve them?
> |
> | Thanks,
> | Tom
> |
> | "Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
> | news:JeK3rYlIGHA.3944@.TK2MSFTNGXA02.phx.gbl...
> | > Hi Tom,
> | >
> | > Welcome to MSDN newsgroup.
> | >
> | > From your description, I learned that you're upgrading your SQLServer
> | > Reporting services reports from 2000 to 2005 version. And you found
> that
> | > since the default session timeout setting is changed to 60 in the
> report
> | > server application, there will occur 'rsExecutionNotFound' error.
> | > Currently
> | > you're wondering whether there is any means to enlarge the session
> timeout
> | > to a large enough value to avoid such issue, correct?
> | >
> | > Based on my understanding, SQL Server reporting service use ASP.NET
> web
> | > application as its report server application, therefore the session
> | > timeout
> | > you mentioned should be ASP.NET web application's session timeout
> setting.
> | > And this timeout setting controls how long data stored in ASP.NET
> session
> | > state can be persisted. Generally, we don't recommend that we set the
> | > timeout to a too large value because session state consumes server's
> | > memory
> | > resource and will hit server application's performance.
> | >
> | > In addition, for the 90 seconds you mentioned, I'm thinking it could
> be
> | > the
> | > ASP.NET http request's execution timeout setting since
> executionTimeout's
> | > default value is 90 seconds(set in server's machine.config in .net
> | > framework config dir). This timeout controls how long each ASP.NET
> | > request
> | > can run on the server. For example, if our web page or web report page
> | > will
> | > need to run a long task, we need to enlarge this timeout setting:
> | >
> | >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/ht
> | > ml/gngrfhttpruntimesection.asp
> | >
> | > <system.web>
> | > <httpRuntime
> | > executionTimeout="45"
> | > />
> | >
> | > Hope this helps.
> | >
> | > Steven Cheng
> | > Microsoft Online Support
> | >
> | > Get Secure! www.microsoft.com/security
> | > (This posting is provided "AS IS", with no warranties, and confers no
> | > rights.)
> | >
> | >
> | >
> | > --
> | > | From: "Tom Bean" <tbean@.newsgroup.nospam>
> | > | Subject: rsExecutionNotFound
> | > | Date: Wed, 25 Jan 2006 14:33:47 -0600
> | > | Lines: 23
> | > | X-Priority: 3
> | > | X-MSMail-Priority: Normal
> | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | > | X-RFC2646: Format=Flowed; Original
> | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | > | Message-ID: <uyp3x6eIGHA.3984@.TK2MSFTNGP14.phx.gbl>
> | > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | > | NNTP-Posting-Host: 71.4.140.141.ptr.us.xo.net 71.4.140.141
> | > | Path:
> TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> | > | Xref: TK2MSFTNGXA02.phx.gbl
> | > microsoft.public.sqlserver.reportingsvcs:67516
> | > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> | > |
> | > | We have just upgraded to SQL Server Reporting Service 2005 and our
> | > reports
> | > | were consistently generating 'rsExecutionNotFound' errors, like the
> one
> | > | shown below. The errors happen when a report was refreshed or a
> | > drilldown
> | > | '+' was clicked 90 seconds after the report was initially
> delivered.
> | > |
> | > | We found the value for SessionTimeout was set to 60 instead of the
> | > default
> | > | value of 600. We had changed the value to 60 while attempting to
> | > decrease
> | > | the startup time for delivering a report. I'm not really sure how a
> 60
> | > | second setting got translated to a 90 second timeout but it was very
> | > | consistent.
> | > |
> | > | When we changed the value to back to 600, the 90 second timeout
> ceased.
> | > | However, we have several users who like to keep the report up all
> day
> | > and
> | > | periodically hit 'Refresh' to see any updates. I suspect the
> current
> | > | SessionTimeout setting of 10 minutes will not be satisfactory.
> | > |
> | > | How high can we set the value for SessionTimeout before causing
> problems
> | > | with Reporting Services or IIS?
> | > |
> | > | Thanks,
> | > | Tom
> | > |
> | > |
> | > |
> | >
> |
> |
> |
>|||Thanks for your further followup Tom,
Since the reports used to work without any problem in Reporting Service
2000 but suffering the problem when upgraded to 2005, I think there may
have some certain issues according to your scenario. So far I haven't heard
any known issue on this, however, I don't think manually enlarge session
timeout is the formal means since there is not document on this also and
session state is a raw setting which more related to ASP.NET rather than
reporting service from SQL Server standpoint. So if this is an urgent
issue for you, I suggest you try contacting PSS for thorough
throubleshooting, it'll be better if you can provide a simplified version
of your report and application to them. Also, you can also submit this to
the MSDN feedback center to report the issue in case that this might be an
hidden issue.
http://lab.msdn.microsoft.com/productfeedback/default.aspx
Thanks & Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

rsDataExtensionNotFound for using XML

Hi all,

I am using SQL Server 2005 reporting service and I am attempting to create a report via xml returned from a web service. Everything works fine while I am in the report designer of visual studio 2005.

However, when I attempt to deploy the report to the report server, it will complain that the xml data extension is not registered with the report server, giving me a rsDataExtensionNotFound. A check on the report server config file does show the xml data extension with all the microsoft namespaces. I had thought that Reporting Services in SQL Server 2005 does natively support xml data source.

Has anyone encountered a similar problem? Does anyone have any suggestions?

Does it matter that the SQL Server 2005 that I have is the workgroup edition ?

Thanks

HI,krayek:

As far as i know ,XML data sources are not supported in SQL Express:

http://msdn2.microsoft.com/en-us/library/ms365166.aspx

(See "Unsupported Features" section.

If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

|||

Thanks for the reply.

However, my SQL version is SQL Server 2005 workgroup edition.

So, I am wondering if this SQL Server 2005 workgroup edition also does not support XML data extension ?

Regards,

David K

|||

HI, David K

No, SQL Server 2005 workgroup edition did not support non relational data source.

Features/Reporting Services Enhancements

EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit)SE (32-bit) SE (64-bit)WG (32-bit)SSE (32-bit)SSEA (32-bit)Support for remote and nonrelational data sourcesYesYesNoNoNo

Please refer this article: http://msdn2.microsoft.com/en-us/library/ms143761.aspx

|||

Hi Rex,

Thanks for that info. Darn, looks like I need to get the standard edition then.. =)

Thanks again for the help, appreciate it.

Regards,

David K

|||

You are welcome,David.

It's my pleasure!

RSClientPrint.Print method

Does anyone know the ReportService web service API calls that are made by
this method?
RSClientPrint.Print(ReportServerURL, ReportPath, ShortReportNameForPrinter);
RSClientPrint.Print('http://servername/ReportServer',
'%2fReport1%2fSalesOrders', 'SalesOrders');It is using URL access to render a report (
http://msdn2.microsoft.com/en-us/library/ms154493.aspx )
You can see all those requests in IIS log
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"brian" <brian@.discussions.microsoft.com> wrote in message
news:D3AFC98A-CF64-481B-8936-0366DA032CDC@.microsoft.com...
> Does anyone know the ReportService web service API calls that are made by
> this method?
> RSClientPrint.Print(ReportServerURL, ReportPath,
> ShortReportNameForPrinter);
> RSClientPrint.Print('http://servername/ReportServer',
> '%2fReport1%2fSalesOrders', 'SalesOrders');

Monday, March 26, 2012

rsactivate returns error, unable to activate error

Failure starting the web service:
Unexpected database error (-2147159548) 0x80004002Hi, possibly your configuration is bad, try runnig, rsconfig.exe with the
new parameters and then try with this again, in most cases this problem is
for bad configuration.
"hcas" wrote:
> Failure starting the web service:
> Unexpected database error (-2147159548) 0x80004002|||Hi, the problem is because the ASPNet is not reg over IIS, with this command
you can repair this.
c> "%windir%\Microsoft.NET\Framework\v1.0.375\aspnet_regiis.exe" -i
regsvr32 %windir%\Microsoft.NET\Framework\v1.0.3705\aspnet_isapi.dll
the aspnet_regiis.exe is a command of .net Framework
Best Regards
John Bocachica
Colombia|||HI John:
I have already tried quite a few different rsconfig.exe settings and users
with no luck. I also re-registered aspnet (I am using a higher version,
1.1.4322) and its dll. The same error occurs when I attempt to use the
rsactivate command. If I use the server name as opposed to the config file,
I get the following error.
Failure initializing remote NT Service:
Unexpected database error (-2147159548) 0x80004002
"John Bocachica" wrote:
> Hi, the problem is because the ASPNet is not reg over IIS, with this command
> you can repair this.
> c> "%windir%\Microsoft.NET\Framework\v1.0.375\aspnet_regiis.exe" -i
> regsvr32 %windir%\Microsoft.NET\Framework\v1.0.3705\aspnet_isapi.dll
> the aspnet_regiis.exe is a command of .net Framework
> Best Regards
> John Bocachica
> Colombia

rsactivate error message

Hello all,

Since I installed SQL Server 2005 on the same server than SQL 2000, my Reporting Service is getting me this error:

"The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content and then restart the service. Check the documentation for more information. (rsReportServerDisabled) Get Online Help

Bad Data. (Exception from HRESULT: 0x80090005)"

I looked over some other logs and forums, and pretty much all pointed to use the rsactivate utility. Well, I am getting frustrated trying to run the rsactivate utility since I typed in the command rsactivate -r and got an error message that didn't expect to get.

Ej:

C:\>rsactivate -r
Either the WMI provider or the path to the local config file must be specified

Then I typed in the path and still got this:

C:\>rsactivate -r "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config"
Either the WMI provider or the path to the local config file must be specified

Does someone out there have had this situation or escenario before and what you did to solve it?....

I really need an input or hint on this, so I will appreciate any help.

Thanks in advance.

Hi I think your using the wrong command... To reactivate you must use the -c option, try this command reactivate -c "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config"

rsactivate error message

Hello all,

Since I installed SQL Server 2005 on the same server than SQL 2000, my Reporting Service is getting me this error:

Bad Data. (Exception from HRESULT: 0x80090005)"

Ej:

C:\>rsactivate -r
Either the WMI provider or the path to the local config file must be specified

Then I typed in the path and still got this:

C:\>rsactivate -r "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config"
Either the WMI provider or the path to the local config file must be specified

Does someone out there have had this situation or escenario before and what you did to solve it?....

I really need an input or hint on this, so I will appreciate any help.

Thanks in advance.

RSActivate Error

I am getting the following error when attempting to run RSActivate to add a
server to a web farm:
Failure starting the web service:
The local NT service is not activated
The log file contains the following entries:
w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Initializing crypto as user:
NT AUTHORITY\NETWORK SERVICE
w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Exporting public key
w3wp!crypto!7c8!08/17/2004-10:30:11:: w WARN: Web Service not activated
w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Client is a local admin.
Activating web service via RPC.
w3wp!library!7c8!08/17/2004-10:30:11:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information. -->
System.Runtime.InteropServices.COMException (0x80004005): -2147159550
at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32 mainError,
Int32 extendedError)
at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID, Int32
clientType)
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
-- End of inner exception stack trace --
w3wp!webserver!7c8!08/17/2004-10:30:15:: e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information. -->
System.Runtime.InteropServices.COMException (0x80004005): -2147159550
at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32 mainError,
Int32 extendedError)
at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID, Int32
clientType)
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at
Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
at Microsoft.ReportingServices.Library.ConnectionManager.get_Connection()
at Microsoft.ReportingServices.Library.Storage.get_Connection()
at
Microsoft.ReportingServices.Library.Storage.NewStandardSqlCommand(String
storedProcedureName)
at
Microsoft.ReportingServices.Library.DBInterface.GetOneConfigurationInfo(Stri
ng key)
at
Microsoft.ReportingServices.Library.CachedSystemProperties.GetSystemProperty
(String name)
at Microsoft.ReportingServices.Library.CachedSystemProperties.Get(String
name)
at
Microsoft.ReportingServices.Library.CachedSystemProperties.GetParameter(Stri
ng name)
at Microsoft.ReportingServices.Library.RSService.get_MyReportsEnabled()
at Microsoft.ReportingServices.Library.RSService.PathToInternal(String
source)
at
Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
path, Boolean validate, Boolean convert, Boolean translate)
at
Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
path)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageCon
tent()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()What error do you see in the Windows service log file?
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Jason Nissen" <Jason.Nissen@.cunamutual.com> wrote in message
news:%23b86E%23GhEHA.2812@.tk2msftngp13.phx.gbl...
> I am getting the following error when attempting to run RSActivate to add
a
> server to a web farm:
> Failure starting the web service:
> The local NT service is not activated
> The log file contains the following entries:
> w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Initializing crypto as user:
> NT AUTHORITY\NETWORK SERVICE
> w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Exporting public key
> w3wp!crypto!7c8!08/17/2004-10:30:11:: w WARN: Web Service not activated
> w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Client is a local admin.
> Activating web service via RPC.
> w3wp!library!7c8!08/17/2004-10:30:11:: e ERROR: Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information. -->
> System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32 mainError,
> Int32 extendedError)
> at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
Int32
> clientType)
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> -- End of inner exception stack trace --
> w3wp!webserver!7c8!08/17/2004-10:30:15:: e ERROR: Reporting Services error
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information. -->
> System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32 mainError,
> Int32 extendedError)
> at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
Int32
> clientType)
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> -- End of inner exception stack trace --
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> at
Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
> at
> Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
> at
Microsoft.ReportingServices.Library.ConnectionManager.get_Connection()
> at Microsoft.ReportingServices.Library.Storage.get_Connection()
> at
> Microsoft.ReportingServices.Library.Storage.NewStandardSqlCommand(String
> storedProcedureName)
> at
>
Microsoft.ReportingServices.Library.DBInterface.GetOneConfigurationInfo(Stri
> ng key)
> at
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetSystemProperty
> (String name)
> at
Microsoft.ReportingServices.Library.CachedSystemProperties.Get(String
> name)
> at
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetParameter(Stri
> ng name)
> at Microsoft.ReportingServices.Library.RSService.get_MyReportsEnabled()
> at Microsoft.ReportingServices.Library.RSService.PathToInternal(String
> source)
> at
> Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> path, Boolean validate, Boolean convert, Boolean translate)
> at
> Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> path)
> at
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageCon
> tent()
> at
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
>|||Here is what I see in the Windows service log file:
ReportingServicesService!crypto!764!8/17/2004-10:29:51:: i INFO: Exporting
public key
ReportingServicesService!crypto!764!8/17/2004-10:29:51:: i INFO: NT Service
not activated
ReportingServicesService!library!764!8/17/2004-10:29:51:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information.
ReportingServicesService!library!764!8/17/2004-10:29:51:: Exception caught
while starting service. Error:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
ception: The report server installation is not initialized. Check the
documentation for more information.
at Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
at
Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
ReportingServicesService!library!764!8/17/2004-10:29:51:: Attempting to
start service again...
"Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
news:O0xHpDIhEHA.3540@.TK2MSFTNGP10.phx.gbl...
> What error do you see in the Windows service log file?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Jason Nissen" <Jason.Nissen@.cunamutual.com> wrote in message
> news:%23b86E%23GhEHA.2812@.tk2msftngp13.phx.gbl...
> > I am getting the following error when attempting to run RSActivate to
add
> a
> > server to a web farm:
> >
> > Failure starting the web service:
> > The local NT service is not activated
> >
> > The log file contains the following entries:
> >
> > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Initializing crypto as
user:
> > NT AUTHORITY\NETWORK SERVICE
> > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Exporting public key
> > w3wp!crypto!7c8!08/17/2004-10:30:11:: w WARN: Web Service not activated
> > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Client is a local admin.
> > Activating web service via RPC.
> > w3wp!library!7c8!08/17/2004-10:30:11:: e ERROR: Throwing
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > ception: The report server installation is not initialized. Check the
> > documentation for more information., ;
> > Info:
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > ception: The report server installation is not initialized. Check the
> > documentation for more information. -->
> > System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> > at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32
mainError,
> > Int32 extendedError)
> > at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
> Int32
> > clientType)
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > -- End of inner exception stack trace --
> > w3wp!webserver!7c8!08/17/2004-10:30:15:: e ERROR: Reporting Services
error
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > ception: The report server installation is not initialized. Check the
> > documentation for more information. -->
> > System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> > at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32
mainError,
> > Int32 extendedError)
> > at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
> Int32
> > clientType)
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > -- End of inner exception stack trace --
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > at
> Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
> > at
> > Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
> > at
> Microsoft.ReportingServices.Library.ConnectionManager.get_Connection()
> > at Microsoft.ReportingServices.Library.Storage.get_Connection()
> > at
> > Microsoft.ReportingServices.Library.Storage.NewStandardSqlCommand(String
> > storedProcedureName)
> > at
> >
>
Microsoft.ReportingServices.Library.DBInterface.GetOneConfigurationInfo(Stri
> > ng key)
> > at
> >
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetSystemProperty
> > (String name)
> > at
> Microsoft.ReportingServices.Library.CachedSystemProperties.Get(String
> > name)
> > at
> >
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetParameter(Stri
> > ng name)
> > at
Microsoft.ReportingServices.Library.RSService.get_MyReportsEnabled()
> > at
Microsoft.ReportingServices.Library.RSService.PathToInternal(String
> > source)
> > at
> >
Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> > path, Boolean validate, Boolean convert, Boolean translate)
> > at
> >
Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> > path)
> > at
> >
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageCon
> > tent()
> > at
> >
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
> >
> >
>|||Are you reusing a database from a previous installation? It looks like the
windows service is not activating automatically because it thinks another
report server is using the database. If this is not the case, you can clear
out the old entries by running rskeymgmt -d, then restart the windows and
web service.
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Jason Nissen" <Jason.Nissen@.cunamutual.com> wrote in message
news:upNDrRJhEHA.3980@.TK2MSFTNGP12.phx.gbl...
> Here is what I see in the Windows service log file:
> ReportingServicesService!crypto!764!8/17/2004-10:29:51:: i INFO: Exporting
> public key
> ReportingServicesService!crypto!764!8/17/2004-10:29:51:: i INFO: NT
Service
> not activated
> ReportingServicesService!library!764!8/17/2004-10:29:51:: e ERROR:
Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information.
> ReportingServicesService!library!764!8/17/2004-10:29:51:: Exception caught
> while starting service. Error:
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> ception: The report server installation is not initialized. Check the
> documentation for more information.
> at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
> at
Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
> at
> Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
> ReportingServicesService!library!764!8/17/2004-10:29:51:: Attempting to
> start service again...
>
> "Brian Hartman [MSFT]" <brianhartman@.hotmail.com> wrote in message
> news:O0xHpDIhEHA.3540@.TK2MSFTNGP10.phx.gbl...
> > What error do you see in the Windows service log file?
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights
> >
> > "Jason Nissen" <Jason.Nissen@.cunamutual.com> wrote in message
> > news:%23b86E%23GhEHA.2812@.tk2msftngp13.phx.gbl...
> > > I am getting the following error when attempting to run RSActivate to
> add
> > a
> > > server to a web farm:
> > >
> > > Failure starting the web service:
> > > The local NT service is not activated
> > >
> > > The log file contains the following entries:
> > >
> > > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Initializing crypto as
> user:
> > > NT AUTHORITY\NETWORK SERVICE
> > > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Exporting public key
> > > w3wp!crypto!7c8!08/17/2004-10:30:11:: w WARN: Web Service not
activated
> > > w3wp!crypto!7c8!08/17/2004-10:30:11:: i INFO: Client is a local admin.
> > > Activating web service via RPC.
> > > w3wp!library!7c8!08/17/2004-10:30:11:: e ERROR: Throwing
> > >
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > > ception: The report server installation is not initialized. Check the
> > > documentation for more information., ;
> > > Info:
> > >
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > > ception: The report server installation is not initialized. Check the
> > > documentation for more information. -->
> > > System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> > > at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32
> mainError,
> > > Int32 extendedError)
> > > at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
> > Int32
> > > clientType)
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > > -- End of inner exception stack trace --
> > > w3wp!webserver!7c8!08/17/2004-10:30:15:: e ERROR: Reporting Services
> error
> > >
> >
>
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedEx
> > > ception: The report server installation is not initialized. Check the
> > > documentation for more information. -->
> > > System.Runtime.InteropServices.COMException (0x80004005): -2147159550
> > > at RSRemoteRpcClient.RemoteLogon.ThrowFriendlyRpcError(Int32
> mainError,
> > > Int32 extendedError)
> > > at RSRemoteRpcClient.RemoteLogon.ActivateService(String instanceID,
> > Int32
> > > clientType)
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > > -- End of inner exception stack trace --
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
> > > at
> > Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
> > > at
> > >
Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection()
> > > at
> > Microsoft.ReportingServices.Library.ConnectionManager.get_Connection()
> > > at Microsoft.ReportingServices.Library.Storage.get_Connection()
> > > at
> > >
Microsoft.ReportingServices.Library.Storage.NewStandardSqlCommand(String
> > > storedProcedureName)
> > > at
> > >
> >
>
Microsoft.ReportingServices.Library.DBInterface.GetOneConfigurationInfo(Stri
> > > ng key)
> > > at
> > >
> >
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetSystemProperty
> > > (String name)
> > > at
> > Microsoft.ReportingServices.Library.CachedSystemProperties.Get(String
> > > name)
> > > at
> > >
> >
>
Microsoft.ReportingServices.Library.CachedSystemProperties.GetParameter(Stri
> > > ng name)
> > > at
> Microsoft.ReportingServices.Library.RSService.get_MyReportsEnabled()
> > > at
> Microsoft.ReportingServices.Library.RSService.PathToInternal(String
> > > source)
> > > at
> > >
> Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> > > path, Boolean validate, Boolean convert, Boolean translate)
> > > at
> > >
> Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String
> > > path)
> > > at
> > >
> >
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageCon
> > > tent()
> > > at
> > >
> >
>
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
> > >
> > >
> >
> >
>

Friday, March 23, 2012

RS2005 service using Report Services 2000 databases

Hi folks.
Is it possible setup RS 2005 keeping reporting services databases in sql
2000 or RS2005 works only with sql 2005?
[]s
RobsonNo problem at all. 100% supported. I did this as an upgrade (just pick RS
2005 and don't upgrade SQL Server). I assume from scratch that you would
just pick RS 2005 when installing..
Note that you do need a SQL Server 2005 license.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Robson Luiz" <robsonbr_2004@.yahoo.com.br> wrote in message
news:uU0LqTm%23FHA.3708@.TK2MSFTNGP10.phx.gbl...
> Hi folks.
> Is it possible setup RS 2005 keeping reporting services databases in sql
> 2000 or RS2005 works only with sql 2005?
> []s
> Robson
>sql

RS2005 on Win2000

I've followed a couple of threads on this, but still haven't quite resolved the issue. RS 2005 is installed on a Win 2000 Server. The service seems to be running perfectly, but when I navigate to <localhost>\ReportServer, I get:

Reporting Services Error
--
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Access to the path 'D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied.

--
SQL Server Reporting Services

I've manually configured the webserviceaccount to the default aspnet machine logon since it's greyed out in the rs configuration screen. Once I manually added that logon, I've not had any errors or warnings in my log files. I've also tried messing with the folder permissions for this path, but no luck. So, I've read and tried a lot of things suggested on this forum. Anyone have the magic wand out there?

Thanks

OK, problem solved. The ASPNET machine logon permissions weren't propogating down the full folder structure for some reason. It works now.

Wednesday, March 21, 2012

RS2005 configuration problem ASPNET account and DBs

Hi all,
I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
configuration I get problems in two areas. First under "Web Service
Identity" no account is listed. ASPNET account is set up on my machine
correctly. Second, under "Database Setup" I can't set up dbs. When I
click "New" and create ReportServer db and then click "Apply" I get an
error that says something like "Virtual Directories have to be crated
first." Under IIS I have ReportServer and Reports directories.
What may be the problem?
Thanks,
StanHi, Stan
just for fun...try running the command line tool "aspnet_regiis -i"
(you can get to it from the VS.NET Command Prompt, or by opening a
regular cmd window and browsing to
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
Once that's run, open your IIS Manager, and check the virtual
directories for Reports and ReportServer web apps. Make sure that they
are running and that the .net mappings are setup appropriately in the
Configuration... > Mappings tab, and also check the security for those
2 folders (use windows auth).
Then try running the RS2005 config tool again, and setup the virtual
directories and apply changes before moving along the different steps
in the tool.
Hope that works.
Regards,
Thiago Silva
MCAD.NET
suslikovich wrote:
> Hi all,
> I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> configuration I get problems in two areas. First under "Web Service
> Identity" no account is listed. ASPNET account is set up on my machine
> correctly. Second, under "Database Setup" I can't set up dbs. When I
> click "New" and create ReportServer db and then click "Apply" I get an
> error that says something like "Virtual Directories have to be crated
> first." Under IIS I have ReportServer and Reports directories.
> What may be the problem?
> Thanks,
> Stan|||Hi Thiago,
Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
-i' but I need to look at othet things you mentioned about mappings and
security. I will do that tonight.
Thanks again,
Stan
tafs7 wrote:
> Hi, Stan
> just for fun...try running the command line tool "aspnet_regiis -i"
> (you can get to it from the VS.NET Command Prompt, or by opening a
> regular cmd window and browsing to
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> Once that's run, open your IIS Manager, and check the virtual
> directories for Reports and ReportServer web apps. Make sure that they
> are running and that the .net mappings are setup appropriately in the
> Configuration... > Mappings tab, and also check the security for those
> 2 folders (use windows auth).
> Then try running the RS2005 config tool again, and setup the virtual
> directories and apply changes before moving along the different steps
> in the tool.
> Hope that works.
> Regards,
> Thiago Silva
> MCAD.NET
> suslikovich wrote:
> > Hi all,
> > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > configuration I get problems in two areas. First under "Web Service
> > Identity" no account is listed. ASPNET account is set up on my machine
> > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > click "New" and create ReportServer db and then click "Apply" I get an
> > error that says something like "Virtual Directories have to be crated
> > first." Under IIS I have ReportServer and Reports directories.
> > What may be the problem?
> >
> > Thanks,
> >
> > Stan|||I did "aspnet_regiis -i" once again. Looked at IIS directories.
Mappings look ok. I am quite puzzled about where to check
authentication. In any case, the problem remains. Any other
suggestions?
Thanks,
Stan
suslikovich wrote:
> Hi Thiago,
> Thanks for the quick reply. I forgot to mention I ran 'aspnet_regiis
> -i' but I need to look at othet things you mentioned about mappings and
> security. I will do that tonight.
> Thanks again,
> Stan
> tafs7 wrote:
> > Hi, Stan
> >
> > just for fun...try running the command line tool "aspnet_regiis -i"
> > (you can get to it from the VS.NET Command Prompt, or by opening a
> > regular cmd window and browsing to
> > c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)
> >
> > Once that's run, open your IIS Manager, and check the virtual
> > directories for Reports and ReportServer web apps. Make sure that they
> > are running and that the .net mappings are setup appropriately in the
> > Configuration... > Mappings tab, and also check the security for those
> > 2 folders (use windows auth).
> >
> > Then try running the RS2005 config tool again, and setup the virtual
> > directories and apply changes before moving along the different steps
> > in the tool.
> >
> > Hope that works.
> >
> > Regards,
> > Thiago Silva
> > MCAD.NET
> >
> > suslikovich wrote:
> > > Hi all,
> > > I have instaled SQL Server 2005 on my W2K SP4 machine. When I go to RS
> > > configuration I get problems in two areas. First under "Web Service
> > > Identity" no account is listed. ASPNET account is set up on my machine
> > > correctly. Second, under "Database Setup" I can't set up dbs. When I
> > > click "New" and create ReportServer db and then click "Apply" I get an
> > > error that says something like "Virtual Directories have to be crated
> > > first." Under IIS I have ReportServer and Reports directories.
> > > What may be the problem?
> > >
> > > Thanks,
> > >
> > > Stansql

RS2000: Subscriptions "Logon Failed"

Hi,
We get an "Logon Failed" message when running subscriptions;
ReportServer service runs using an domain account. Domain account has
run-as-a-service, logon-locally and "impersonate a client after
authentication" and the apprioriate database rights.
What is the "required privilege" (see below) the reportserver is requiring?
Regards,
Erik Tamminga
ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed. --> System.Runtime.InteropServices.COMException (0x80070522):
A required privilege is not held by the client.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
at
Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
userName, String userPwd, String domain)From here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
Hope it helps
1.. Decide which accounts to use for Report Server services. Reporting
Services requires three accounts:
2.. Report Server Windows service requires an account to log on to the
local system. Microsoft recommends that you use Local System if you are
installing on Windows 2000. For more information about this recommendation,
see Service Account.
3.. Report Server Web service requires an account to log on to the local
system. Because it is an ASP.NET application, it runs using the ASPNET
account. If you are running Windows 2000, you cannot specify a different
account to use during Setup; you must use the account that is defined for
ASP.NET. If you are running Windows Server 2003, the default is Network
Service, but you can choose to run the service as Local System.
4.. Report Server Web service requires an account to log on to the SQL
Server instance that hosts the report server database. You can specify a
domain account, a SQL Server login, or Local System. You can also use the
credentials that the Report Server Web service uses to log on to the system.
For more information, see Report Server Database Setup.
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi,
> We get an "Logon Failed" message when running subscriptions;
> ReportServer service runs using an domain account. Domain account has
> run-as-a-service, logon-locally and "impersonate a client after
> authentication" and the apprioriate database rights.
> What is the "required privilege" (see below) the reportserver is
> requiring?
> Regards,
> Erik Tamminga
> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed. --> System.Runtime.InteropServices.COMException
> (0x80070522): A required privilege is not held by the client.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> at
> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> userName, String userPwd, String domain)
>|||Thanks Beth,
But; RS is able to start, login to the databases. RS WebApplication works as
expected but only the Subscriptions give me a logon failed when they're
scheduled to run. It seems to have something to do with RS not being able to
render the reports using the account used for subscriptions. Any idears on
how to fix this?
Erik
"Beth" <scratchbakery@.msn.com> wrote in message
news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> From here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> Hope it helps
> 1.. Decide which accounts to use for Report Server services. Reporting
> Services requires three accounts:
> 2.. Report Server Windows service requires an account to log on to the
> local system. Microsoft recommends that you use Local System if you are
> installing on Windows 2000. For more information about this
> recommendation, see Service Account.
> 3.. Report Server Web service requires an account to log on to the local
> system. Because it is an ASP.NET application, it runs using the ASPNET
> account. If you are running Windows 2000, you cannot specify a different
> account to use during Setup; you must use the account that is defined for
> ASP.NET. If you are running Windows Server 2003, the default is Network
> Service, but you can choose to run the service as Local System.
> 4.. Report Server Web service requires an account to log on to the SQL
> Server instance that hosts the report server database. You can specify a
> domain account, a SQL Server login, or Local System. You can also use the
> credentials that the Report Server Web service uses to log on to the
> system. For more information, see Report Server Database Setup.
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> We get an "Logon Failed" message when running subscriptions;
>> ReportServer service runs using an domain account. Domain account has
>> run-as-a-service, logon-locally and "impersonate a client after
>> authentication" and the apprioriate database rights.
>> What is the "required privilege" (see below) the reportserver is
>> requiring?
>> Regards,
>> Erik Tamminga
>> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> Throwing
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed., ;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed. --> System.Runtime.InteropServices.COMException
>> (0x80070522): A required privilege is not held by the client.
>> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo)
>> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
>> at
>> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> userName, String userPwd, String domain)
>|||Hi Erik,
i think for the subscription to work you need to have Credentials stored
securely in the report server. Subscription will not work for reports which
dont have this stored credentials. When you run the report it will work, but
subscription will not work. The reason is DataSources for that report does
not have stored credentials i.e it has either have windows credential or no
credential. in order that reports have subscrpiton enabled you have to check
the "Credentials stored securely in the report server" and enter the user
name and pwd. you can either enter a sql login or windows login based on the
authentication type. and finally click Apply button to store it. Then do the
subscrpion it will work.
Bava
"Erik Tamminga" wrote:
> Thanks Beth,
> But; RS is able to start, login to the databases. RS WebApplication works as
> expected but only the Subscriptions give me a logon failed when they're
> scheduled to run. It seems to have something to do with RS not being able to
> render the reports using the account used for subscriptions. Any idears on
> how to fix this?
> Erik
> "Beth" <scratchbakery@.msn.com> wrote in message
> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> > From here:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> > Hope it helps
> > 1.. Decide which accounts to use for Report Server services. Reporting
> > Services requires three accounts:
> > 2.. Report Server Windows service requires an account to log on to the
> > local system. Microsoft recommends that you use Local System if you are
> > installing on Windows 2000. For more information about this
> > recommendation, see Service Account.
> > 3.. Report Server Web service requires an account to log on to the local
> > system. Because it is an ASP.NET application, it runs using the ASPNET
> > account. If you are running Windows 2000, you cannot specify a different
> > account to use during Setup; you must use the account that is defined for
> > ASP.NET. If you are running Windows Server 2003, the default is Network
> > Service, but you can choose to run the service as Local System.
> > 4.. Report Server Web service requires an account to log on to the SQL
> > Server instance that hosts the report server database. You can specify a
> > domain account, a SQL Server login, or Local System. You can also use the
> > credentials that the Report Server Web service uses to log on to the
> > system. For more information, see Report Server Database Setup.
> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> Hi,
> >>
> >> We get an "Logon Failed" message when running subscriptions;
> >>
> >> ReportServer service runs using an domain account. Domain account has
> >> run-as-a-service, logon-locally and "impersonate a client after
> >> authentication" and the apprioriate database rights.
> >>
> >> What is the "required privilege" (see below) the reportserver is
> >> requiring?
> >>
> >> Regards,
> >>
> >> Erik Tamminga
> >>
> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> Throwing
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed., ;
> >> Info:
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> (0x80070522): A required privilege is not held by the client.
> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> errorCode, IntPtr errorInfo)
> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> >> at
> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> userName, String userPwd, String domain)
> >>
> >
> >
>
>|||Hi,
Thanks for the reply, but all of my data sources already use stored
credentials (sql-server's sa user, ..., yeah I know ...). So I still think
it has something to do with the win2000 environment and rs supplied
credentials. Have another look at the reported error, it talks about
impersonation, tokens and the windows user/password/domain combo wich are
not used by SQL authenticating data sources.
Regads,
Erik
"Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> Hi Erik,
> i think for the subscription to work you need to have Credentials stored
> securely in the report server. Subscription will not work for reports
> which
> dont have this stored credentials. When you run the report it will work,
> but
> subscription will not work. The reason is DataSources for that report does
> not have stored credentials i.e it has either have windows credential or
> no
> credential. in order that reports have subscrpiton enabled you have to
> check
> the "Credentials stored securely in the report server" and enter the user
> name and pwd. you can either enter a sql login or windows login based on
> the
> authentication type. and finally click Apply button to store it. Then do
> the
> subscrpion it will work.
> Bava
> "Erik Tamminga" wrote:
>> Thanks Beth,
>> But; RS is able to start, login to the databases. RS WebApplication works
>> as
>> expected but only the Subscriptions give me a logon failed when they're
>> scheduled to run. It seems to have something to do with RS not being able
>> to
>> render the reports using the account used for subscriptions. Any idears
>> on
>> how to fix this?
>> Erik
>> "Beth" <scratchbakery@.msn.com> wrote in message
>> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
>> > From here:
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
>> > Hope it helps
>> > 1.. Decide which accounts to use for Report Server services. Reporting
>> > Services requires three accounts:
>> > 2.. Report Server Windows service requires an account to log on to the
>> > local system. Microsoft recommends that you use Local System if you are
>> > installing on Windows 2000. For more information about this
>> > recommendation, see Service Account.
>> > 3.. Report Server Web service requires an account to log on to the
>> > local
>> > system. Because it is an ASP.NET application, it runs using the ASPNET
>> > account. If you are running Windows 2000, you cannot specify a
>> > different
>> > account to use during Setup; you must use the account that is defined
>> > for
>> > ASP.NET. If you are running Windows Server 2003, the default is Network
>> > Service, but you can choose to run the service as Local System.
>> > 4.. Report Server Web service requires an account to log on to the SQL
>> > Server instance that hosts the report server database. You can specify
>> > a
>> > domain account, a SQL Server login, or Local System. You can also use
>> > the
>> > credentials that the Report Server Web service uses to log on to the
>> > system. For more information, see Report Server Database Setup.
>> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
>> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> >> Hi,
>> >>
>> >> We get an "Logon Failed" message when running subscriptions;
>> >>
>> >> ReportServer service runs using an domain account. Domain account has
>> >> run-as-a-service, logon-locally and "impersonate a client after
>> >> authentication" and the apprioriate database rights.
>> >>
>> >> What is the "required privilege" (see below) the reportserver is
>> >> requiring?
>> >>
>> >> Regards,
>> >>
>> >> Erik Tamminga
>> >>
>> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> >> Throwing
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed., ;
>> >> Info:
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed. --> System.Runtime.InteropServices.COMException
>> >> (0x80070522): A required privilege is not held by the client.
>> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> >> errorCode, IntPtr errorInfo)
>> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
>> >> pImpToken)
>> >> at
>> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> >> userName, String userPwd, String domain)
>> >>
>> >
>> >
>>|||Hi,
Are you using any custom dataset extension or custom assemblie?
why cant you give a domain\windowuser and pwd and click the check box below
"Use as Windows credentials when connecting to the data source" in the
datasource and try running the report. see if its work.
Bava
"Erik Tamminga" wrote:
> Hi,
> Thanks for the reply, but all of my data sources already use stored
> credentials (sql-server's sa user, ..., yeah I know ...). So I still think
> it has something to do with the win2000 environment and rs supplied
> credentials. Have another look at the reported error, it talks about
> impersonation, tokens and the windows user/password/domain combo wich are
> not used by SQL authenticating data sources.
> Regads,
> Erik
> "Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
> news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> > Hi Erik,
> > i think for the subscription to work you need to have Credentials stored
> > securely in the report server. Subscription will not work for reports
> > which
> > dont have this stored credentials. When you run the report it will work,
> > but
> > subscription will not work. The reason is DataSources for that report does
> > not have stored credentials i.e it has either have windows credential or
> > no
> > credential. in order that reports have subscrpiton enabled you have to
> > check
> > the "Credentials stored securely in the report server" and enter the user
> > name and pwd. you can either enter a sql login or windows login based on
> > the
> > authentication type. and finally click Apply button to store it. Then do
> > the
> > subscrpion it will work.
> >
> > Bava
> >
> > "Erik Tamminga" wrote:
> >
> >> Thanks Beth,
> >>
> >> But; RS is able to start, login to the databases. RS WebApplication works
> >> as
> >> expected but only the Subscriptions give me a logon failed when they're
> >> scheduled to run. It seems to have something to do with RS not being able
> >> to
> >> render the reports using the account used for subscriptions. Any idears
> >> on
> >> how to fix this?
> >>
> >> Erik
> >>
> >> "Beth" <scratchbakery@.msn.com> wrote in message
> >> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> >> > From here:
> >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> >> > Hope it helps
> >> > 1.. Decide which accounts to use for Report Server services. Reporting
> >> > Services requires three accounts:
> >> > 2.. Report Server Windows service requires an account to log on to the
> >> > local system. Microsoft recommends that you use Local System if you are
> >> > installing on Windows 2000. For more information about this
> >> > recommendation, see Service Account.
> >> > 3.. Report Server Web service requires an account to log on to the
> >> > local
> >> > system. Because it is an ASP.NET application, it runs using the ASPNET
> >> > account. If you are running Windows 2000, you cannot specify a
> >> > different
> >> > account to use during Setup; you must use the account that is defined
> >> > for
> >> > ASP.NET. If you are running Windows Server 2003, the default is Network
> >> > Service, but you can choose to run the service as Local System.
> >> > 4.. Report Server Web service requires an account to log on to the SQL
> >> > Server instance that hosts the report server database. You can specify
> >> > a
> >> > domain account, a SQL Server login, or Local System. You can also use
> >> > the
> >> > credentials that the Report Server Web service uses to log on to the
> >> > system. For more information, see Report Server Database Setup.
> >> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> >> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> We get an "Logon Failed" message when running subscriptions;
> >> >>
> >> >> ReportServer service runs using an domain account. Domain account has
> >> >> run-as-a-service, logon-locally and "impersonate a client after
> >> >> authentication" and the apprioriate database rights.
> >> >>
> >> >> What is the "required privilege" (see below) the reportserver is
> >> >> requiring?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Erik Tamminga
> >> >>
> >> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> >> Throwing
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed., ;
> >> >> Info:
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> >> (0x80070522): A required privilege is not held by the client.
> >> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> >> errorCode, IntPtr errorInfo)
> >> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> >> >> pImpToken)
> >> >> at
> >> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> >> userName, String userPwd, String domain)
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>

Monday, March 12, 2012

RS Web Service to programmatically render reports

Hello, when I call the render method of a ReportService() object with the
following...
data = rs.Render("/OnlineInvoice", "PDF", Nothing, Nothing, paramaters,
Nothing, Nothing, encoding, mimeType, parametersUsed, warnings, streamIds)
with the argument paramaters being...
Dim paramaters(2) As ParameterValue
paramaters(0) = New ParameterValue
paramaters(0).Name = "P_ClientID"
paramaters(0).Value = 815
paramaters(1) = New ParameterValue
paramaters(1).Name = "P_InvoiceID"
paramaters(1).Value = 22230
I get the error...
System.Web.Services.Protocols.SoapException: The value of parameter
'Parameters' is not valid. Check the documentation for information about
valid values. --> The value of parameter 'Parameters' is not valid.
Any Ideas? thank you for the help!
--See if you need to use 1 instead of 2 in array declaration:
Dim paramaters(1) As ParameterValue
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"Richard Cranium" <mgreco40@.hotmail.com> wrote in message
news:edWp1rjoEHA.1712@.tk2msftngp13.phx.gbl...
> Hello, when I call the render method of a ReportService() object with the
> following...
> data = rs.Render("/OnlineInvoice", "PDF", Nothing, Nothing, paramaters,
> Nothing, Nothing, encoding, mimeType, parametersUsed, warnings, streamIds)
> with the argument paramaters being...
> Dim paramaters(2) As ParameterValue
> paramaters(0) = New ParameterValue
> paramaters(0).Name = "P_ClientID"
> paramaters(0).Value = 815
> paramaters(1) = New ParameterValue
> paramaters(1).Name = "P_InvoiceID"
> paramaters(1).Value = 22230
> I get the error...
> System.Web.Services.Protocols.SoapException: The value of parameter
> 'Parameters' is not valid. Check the documentation for information about
> valid values. --> The value of parameter 'Parameters' is not valid.
> Any Ideas? thank you for the help!
>
>
> --
>
>

RS Web Service Reference File

Where do I go to add a constractor of "this.Timeout=..." to a the Web Service
reference file?
Challenge: Long running reports are timing out
Thank you for your assistance.Find ReportingService() class in a reference file.
it looks like :
public class ReportingService :
System.Web.Services.Protocols.SoapHttpClientProtocol
{
.....
}
replace "public ReportingService() {...}" with
public ReportingService()
{
this.Timeout=1200000;
}
or you can even overload that constructor by adding the following
public ReportingService(string url)
{
this.Url = url;
this.Timeout=1200000;
}
do not regenerate it, otherwise you'll loose your changes.
another way is to extend ReportingService class.
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:76DCAFF8-F66B-4666-8C96-4A1817D13CD6@.microsoft.com...
> Where do I go to add a constractor of "this.Timeout=..." to a the Web
> Service
> reference file?
> Challenge: Long running reports are timing out
> Thank you for your assistance.
>
>|||Thank you very much!
"Oleg Yevteyev" wrote:
> Find ReportingService() class in a reference file.
> it looks like :
> public class ReportingService :
> System.Web.Services.Protocols.SoapHttpClientProtocol
> {
> ......
> }
> replace "public ReportingService() {...}" with
> public ReportingService()
> {
> this.Timeout=1200000;
> }
> or you can even overload that constructor by adding the following
> public ReportingService(string url)
> {
> this.Url = url;
> this.Timeout=1200000;
> }
> do not regenerate it, otherwise you'll loose your changes.
> another way is to extend ReportingService class.
>
> "Terry" <Terry@.discussions.microsoft.com> wrote in message
> news:76DCAFF8-F66B-4666-8C96-4A1817D13CD6@.microsoft.com...
> > Where do I go to add a constractor of "this.Timeout=..." to a the Web
> > Service
> > reference file?
> >
> > Challenge: Long running reports are timing out
> >
> > Thank you for your assistance.
> >
> >
> >
>
>

Wednesday, March 28, 2012

rsExecutionNotFound

rsDataExtensionNotFound for using XML

RSClientPrint.Print method

Monday, March 26, 2012

rsactivate returns error, unable to activate error

rsactivate error message

rsactivate error message

RSActivate Error

Friday, March 23, 2012

RS2005 service using Report Services 2000 databases

RS2005 on Win2000

Wednesday, March 21, 2012

RS2005 configuration problem ASPNET account and DBs

RS2000: Subscriptions "Logon Failed"

Monday, March 12, 2012

RS Web Service to programmatically render reports

RS Web Service Reference File

RS and HTTPS

Blog Archive

About Me