RS on Win2003 cannot connect to Analysis Service

I have RS installed on Win 2003 (not domain controller) and SQL server/AS on
a Win 2000 machine. I have no problem openning the report locally through IE
on the RS machine (Win 2003). However, I could not open the same report from
client machines (XP professional, Win 2000). The error message says "An error
has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'DataSourceName'.
(rsErrorOpeningConnection) Get Online Help
Database 'DatabaseName' does not exist. ".
If I pulish the same report to RS on a Win 2000 machines, I don't have any
problem to open the report from any of client machines. I guess it might
related to credentials not being passed correctly. What kind of configurate I
need on a Win 2003 machine.
Thanks.It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
admins.
Regards,
Cem Demircioglu
"BBH" <BBH@.discussions.microsoft.com> wrote in message
news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
>I have RS installed on Win 2003 (not domain controller) and SQL server/AS
>on
> a Win 2000 machine. I have no problem openning the report locally through
> IE
> on the RS machine (Win 2003). However, I could not open the same report
> from
> client machines (XP professional, Win 2000). The error message says "An
> error
> has occurred during report processing. (rsProcessingAborted) Get Online
> Help
> Cannot create a connection to data source 'DataSourceName'.
> (rsErrorOpeningConnection) Get Online Help
> Database 'DatabaseName' does not exist. ".
> If I pulish the same report to RS on a Win 2000 machines, I don't have any
> problem to open the report from any of client machines. I guess it might
> related to credentials not being passed correctly. What kind of
> configurate I
> need on a Win 2003 machine.
> Thanks.
>|||Thanks fro your reply. Are you referring to the service account which starts
the IIS?
"Cem Demircioglu" wrote:
> It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
> admins.
> Regards,
> Cem Demircioglu
>
> "BBH" <BBH@.discussions.microsoft.com> wrote in message
> news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
> >I have RS installed on Win 2003 (not domain controller) and SQL server/AS
> >on
> > a Win 2000 machine. I have no problem openning the report locally through
> > IE
> > on the RS machine (Win 2003). However, I could not open the same report
> > from
> > client machines (XP professional, Win 2000). The error message says "An
> > error
> > has occurred during report processing. (rsProcessingAborted) Get Online
> > Help
> > Cannot create a connection to data source 'DataSourceName'.
> > (rsErrorOpeningConnection) Get Online Help
> > Database 'DatabaseName' does not exist. ".
> >
> > If I pulish the same report to RS on a Win 2000 machines, I don't have any
> > problem to open the report from any of client machines. I guess it might
> > related to credentials not being passed correctly. What kind of
> > configurate I
> > need on a Win 2003 machine.
> >
> > Thanks.
> >
>
>|||I can't remember the account name but it is either IIS (IUSR*) or Report
Server account (NT Authority\Network Service). You can test it by granting
read access to everyone.
Analysis Manager > XYZ Cube > Database Roles > New ... > Membership:
Everyone
Use Windows NT integrated security on the server while creating the data
source.
Hope this helps.
Regards,
Cem Demircioglu
"BBH" <BBH@.discussions.microsoft.com> wrote in message
news:BB12FAB7-F3CE-42D8-8CD4-F3F707A0A0FF@.microsoft.com...
> Thanks fro your reply. Are you referring to the service account which
> starts
> the IIS?
> "Cem Demircioglu" wrote:
>> It is a security issue. IIS user on Win 2003 needs to be a member of OLAP
>> admins.
>> Regards,
>> Cem Demircioglu
>>
>> "BBH" <BBH@.discussions.microsoft.com> wrote in message
>> news:13B92E7D-C230-4C94-94C2-65C9411FA1F0@.microsoft.com...
>> >I have RS installed on Win 2003 (not domain controller) and SQL
>> >server/AS
>> >on
>> > a Win 2000 machine. I have no problem openning the report locally
>> > through
>> > IE
>> > on the RS machine (Win 2003). However, I could not open the same report
>> > from
>> > client machines (XP professional, Win 2000). The error message says "An
>> > error
>> > has occurred during report processing. (rsProcessingAborted) Get Online
>> > Help
>> > Cannot create a connection to data source 'DataSourceName'.
>> > (rsErrorOpeningConnection) Get Online Help
>> > Database 'DatabaseName' does not exist. ".
>> >
>> > If I pulish the same report to RS on a Win 2000 machines, I don't have
>> > any
>> > problem to open the report from any of client machines. I guess it
>> > might
>> > related to credentials not being passed correctly. What kind of
>> > configurate I
>> > need on a Win 2003 machine.
>> >
>> > Thanks.
>> >
>>

RS on the Internet

Im tring to gte my report server to work on the Internet.
It works fine locally but when I add the ReportServerExternalURL to the
config file as documented it fails saying ;
The configuration file contains an element that is not valid. The
ReportServerExternalURL element is not a configuration file element.
I am using Win2003 and RsSp1. Does anyone know what I am doing wrong?
NickIt must be something like
<Configuration>
<UI>
<ReportServerUrl>http://www.MyRSServer.com/ReportServer</ReportServerUrl>
</UI>
in RSWebApplication.config. I think ReportServerExternalURL is the wrong
property tag for this.
Hope this helps.
Regards
"Nick Jacobs" <news@.winman.co.uk> wrote in message
news:#A2Ff9tAFHA.1188@.tk2msftngp13.phx.gbl...
> Im tring to gte my report server to work on the Internet.
> It works fine locally but when I add the ReportServerExternalURL to the
> config file as documented it fails saying ;
> The configuration file contains an element that is not valid. The
> ReportServerExternalURL element is not a configuration file element.
> I am using Win2003 and RsSp1. Does anyone know what I am doing wrong?
> Nick
>
>|||You may be modifiying the wrong Config file. This change should be
made to the "RSWebApplication.config" file which is usually located at
the following path:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager
The new node will go within the UI element, alongside the
ReportServerUrl element. The value should be the fully-qualified
domain name for the external address.
<Configuration>
<UI>
<ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
<ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
</UI>
...
NOTE: Be careful because, all elements are case-sensitive and this one
has "URL" capitalized instead of Pascal cased. Improper case can also
cause this to fail.
For more details, see MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
I hope this helps,
Lance Hunt
http://weblogs.asp.net/lhunt/|||I have
<Configuration>
<UI>
<ReportServerUrl>http://COMSRV/ReportServer</ReportServerUrl>
<ReportServerExternalURL>http://remote.mydomain.co.uk/ReportServer</ReportServerExternalURL>
</UI>
In the RSWebApplication.config
Isn't this supposed to work?
Nick
"Lance" <lancehunt@.gmail.com> wrote in message
news:1106665173.525554.327200@.z14g2000cwz.googlegroups.com...
> You may be modifiying the wrong Config file. This change should be
> made to the "RSWebApplication.config" file which is usually located at
> the following path:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager
> The new node will go within the UI element, alongside the
> ReportServerUrl element. The value should be the fully-qualified
> domain name for the external address.
> <Configuration>
> <UI>
> <ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
> </UI>
> ...
>
> NOTE: Be careful because, all elements are case-sensitive and this one
> has "URL" capitalized instead of Pascal cased. Improper case can also
> cause this to fail.
> For more details, see MSDN:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
> I hope this helps,
> Lance Hunt
> http://weblogs.asp.net/lhunt/
>|||You were half right Lance. It is the case of the element but it's the MSDN
documentation that is wrong.
The element should read ReportServerExternalUrl not ReportServerExternalURL.
Thanks for pointing me in the right direction.
Nick
"Lance" <lancehunt@.gmail.com> wrote in message
news:1106665173.525554.327200@.z14g2000cwz.googlegroups.com...
> You may be modifiying the wrong Config file. This change should be
> made to the "RSWebApplication.config" file which is usually located at
> the following path:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager
> The new node will go within the UI element, alongside the
> ReportServerUrl element. The value should be the fully-qualified
> domain name for the external address.
> <Configuration>
> <UI>
> <ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
> </UI>
> ...
>
> NOTE: Be careful because, all elements are case-sensitive and this one
> has "URL" capitalized instead of Pascal cased. Improper case can also
> cause this to fail.
> For more details, see MSDN:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
> I hope this helps,
> Lance Hunt
> http://weblogs.asp.net/lhunt/
>|||Sorry about that. I usually test my suggestions locally before
posting, but I wasnt at my Dev PC when I posted that info. Now that
you mention it, I seem to recall this documentation mistake.
Regardless, I'm glad you worked it out.
Lance
http://weblogs.asp.net/lhunt/