Hi - my config is as follows:
- RS Standard on Windows Server 2003 (server1)
- SQL Server 2000 for repository on a different server server2 (same domain)
- I am logged onto server1 as domain admin (full SQL perms to server2)
- I have successfully installed other RS repositories to server2 (different
db names of course)
Installation fails at the "Configuring Microsoft SQL Server" part with error
message: "SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT Authority\Anonymous
Logon'. "
It appears to be losing my interactively logged on credentials.
Here is info from the log:
SQL_ERROR (-1) in SQLDriverConnectW
sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error 29545. SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'.
Refer to the Server error logs and setup logs for more detailed information.
MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
Standard Edition -- Error 29545. SQL Setup failed to connect to the database
service for server configuration. The error was: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Refe
r to the Server error logs and setup logs for more detailed information.
--
Thoughts?
thanksHow are permissions configured for server2? I've had some problems in the
past connecting from a local machine account to a domain sql server
(configured with mixed security). I was attempting SQL authentication. It
started working when I changed the service to run with a domain user
identity rather than a local machine user; then it connected with SQL
authentication just fine. That was odd, because I expected SQL
authentication to work regardless of the windows login identity.
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same
> domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2
> (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with
> error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT
> Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for
> server
> configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed
> information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the
> database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||Hi Jeff - Just to clarify my understanding of the installation process as a
baseline assumption so we're on the same page - it's the ID of the
interactively logged on user performing the install who the repository
database is created under.
Regarding permissions for server2, the user I am logged onto server1 as is
domainA\userA. This user is a domain admin and has full admin to server1 and
server2, as well as SQL Server on server2.
regards
"Jeff A. Stucker" wrote:
> How are permissions configured for server2? I've had some problems in the
> past connecting from a local machine account to a domain sql server
> (configured with mixed security). I was attempting SQL authentication. It
> started working when I changed the service to run with a domain user
> identity rather than a local machine user; then it connected with SQL
> authentication just fine. That was odd, because I expected SQL
> authentication to work regardless of the windows login identity.
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
> news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> > Hi - my config is as follows:
> >
> > - RS Standard on Windows Server 2003 (server1)
> > - SQL Server 2000 for repository on a different server server2 (same
> > domain)
> > - I am logged onto server1 as domain admin (full SQL perms to server2)
> > - I have successfully installed other RS repositories to server2
> > (different
> > db names of course)
> >
> > Installation fails at the "Configuring Microsoft SQL Server" part with
> > error
> > message: "SQL Setup failed to connect to the database service for server
> > configuration. The error was: Login failed for user 'NT
> > Authority\Anonymous
> > Logon'. "
> >
> > It appears to be losing my interactively logged on credentials.
> >
> > Here is info from the log:
> >
> > SQL_ERROR (-1) in SQLDriverConnectW
> > sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > Error 29545. SQL Setup failed to connect to the database service for
> > server
> > configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS
> > LOGON'.
> > Refer to the Server error logs and setup logs for more detailed
> > information.
> > MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> > Standard Edition -- Error 29545. SQL Setup failed to connect to the
> > database
> > service for server configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS LOGON'.
> > Refe
> > r to the Server error logs and setup logs for more detailed information.
> >
> > --
> >
> > Thoughts?
> > thanks
>
>|||I had the same problem when I installed RS yesterday. For some reason the
credentials are not passed correctly and I had to run the setup program from
the command line and explicitly pass it credentials with which to run the
setup program. The command to run setup ends up looking something like this:
setup /i "setup\rsrun.msi" RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
I've been told you can use any credentials you want (domain administrator,
etc.), but I just used the sql sa account, and that worked correctly.
I had the same problem when installing sp1. I had to manually extract the
.cab file and run setup from the command line once again:
sp1setup RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
Hope this helps.
David
"ISGADMIN" wrote:
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2 (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||> Installation fails at the "Configuring Microsoft SQL Server" part
with error
> message: "SQL Setup failed to connect to the database service for
server
> configuration. The error was: Login failed for user 'NT
Authority\Anonymous
> Logon'. "
>
Another fix for this - add the 'NT Authority\Anonymous Logon' account
as Local Admin on the SQL Server box and then be sure
Builtin\Administrators has SA access on the SQL Server.
Run the install and then change the dbowner to "sa" and remove the
account.
That's how I finally got it installed on a Win2003 box...
-Annette
Showing posts with label follows. Show all posts
Showing posts with label follows. Show all posts
Wednesday, March 7, 2012
Saturday, February 25, 2012
RS Does Not Recognize Temp Table Fields
I am using the generic query designer and have defined 2 temp tables as
follows:
DECLARE @.MainTable
DECLARE @.JoinTable
INSERT INTO @.MainTable
SELECT...
INSERT INTO @.JoinTable
SELECT...
SELECT FROM @.MainTable JOIN ON @.JoinTable...
My problem is the field list does not recognize all the fields; all the
original fields are in the @.MainTable but only the first 3 from the
@.JoinTable. I tried to add additional fields to the @.MainTable and they are
not recognized. I have tried the Field Refresh Button, manually adding
fields to the list and hacking the RDL field list. Each time I manually add,
I get an index out of bounds error when trying to run the report. If I then
hit the refresh button the fields I have manually added are removed'
Also, must the field names be unique among the temp tables? I assumed not
since they are in separate queries.
Many thanks for any helpFirst off, even if you get this to work it won't work for you. Let me
explain. What happens with using temp tables in the generic query designer
is the same thing that happens if you post the below code in query analyzer
and hit execute twice. The first time it will work, the second time it will
error out because the tables already exist. So even if this worked for you
in development when you deploy it the report would work the first time. If
the user click on refresh report it will die (I haven't done this in 2005
but I did try this out in 2000 and I doubt if this would have changed). The
reason is what is going on with connection pooling. Dropping the tables at
the end would probably not work either because it would probably do this
before RS is done with them.
I suggest creating a stored procedure. Do not drop the temp tables, just let
them fall out of scope. Have your select statement be the last statement.
I do this all the time (multiple temp tables, lots of inserts, updates, join
etc between them).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
news:uloHfFM7FHA.2692@.tk2msftngp13.phx.gbl...
>I am using the generic query designer and have defined 2 temp tables as
>follows:
> DECLARE @.MainTable
> DECLARE @.JoinTable
> INSERT INTO @.MainTable
> SELECT...
> INSERT INTO @.JoinTable
> SELECT...
> SELECT FROM @.MainTable JOIN ON @.JoinTable...
> My problem is the field list does not recognize all the fields; all the
> original fields are in the @.MainTable but only the first 3 from the
> @.JoinTable. I tried to add additional fields to the @.MainTable and they
> are not recognized. I have tried the Field Refresh Button, manually adding
> fields to the list and hacking the RDL field list. Each time I manually
> add, I get an index out of bounds error when trying to run the report. If
> I then hit the refresh button the fields I have manually added are
> removed'
> Also, must the field names be unique among the temp tables? I assumed not
> since they are in separate queries.
> Many thanks for any help
>|||Bruce
Many thanks for your prompt reply. I found my problem was a simple one where
I had not included all the new fields in all the select statements. Your
point is well taken though and the use of the temp tables was a last resort
because I could not get the original more straight-forward query to work. I
was getting redundant hits as a result of a subquery so had to use this
approach to get it working for a deadline.
Surprisingly this approach does work in the preview panel as well as
deployed to the web. However the query does not execute inside of the data
panel; it just dies without any errors. I assume this is what you are
referring to.
Many thanks for all your help up here!
Mike
follows:
DECLARE @.MainTable
DECLARE @.JoinTable
INSERT INTO @.MainTable
SELECT...
INSERT INTO @.JoinTable
SELECT...
SELECT FROM @.MainTable JOIN ON @.JoinTable...
My problem is the field list does not recognize all the fields; all the
original fields are in the @.MainTable but only the first 3 from the
@.JoinTable. I tried to add additional fields to the @.MainTable and they are
not recognized. I have tried the Field Refresh Button, manually adding
fields to the list and hacking the RDL field list. Each time I manually add,
I get an index out of bounds error when trying to run the report. If I then
hit the refresh button the fields I have manually added are removed'
Also, must the field names be unique among the temp tables? I assumed not
since they are in separate queries.
Many thanks for any helpFirst off, even if you get this to work it won't work for you. Let me
explain. What happens with using temp tables in the generic query designer
is the same thing that happens if you post the below code in query analyzer
and hit execute twice. The first time it will work, the second time it will
error out because the tables already exist. So even if this worked for you
in development when you deploy it the report would work the first time. If
the user click on refresh report it will die (I haven't done this in 2005
but I did try this out in 2000 and I doubt if this would have changed). The
reason is what is going on with connection pooling. Dropping the tables at
the end would probably not work either because it would probably do this
before RS is done with them.
I suggest creating a stored procedure. Do not drop the temp tables, just let
them fall out of scope. Have your select statement be the last statement.
I do this all the time (multiple temp tables, lots of inserts, updates, join
etc between them).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mike Harbinger" <MikeH@.Cybervillage.net> wrote in message
news:uloHfFM7FHA.2692@.tk2msftngp13.phx.gbl...
>I am using the generic query designer and have defined 2 temp tables as
>follows:
> DECLARE @.MainTable
> DECLARE @.JoinTable
> INSERT INTO @.MainTable
> SELECT...
> INSERT INTO @.JoinTable
> SELECT...
> SELECT FROM @.MainTable JOIN ON @.JoinTable...
> My problem is the field list does not recognize all the fields; all the
> original fields are in the @.MainTable but only the first 3 from the
> @.JoinTable. I tried to add additional fields to the @.MainTable and they
> are not recognized. I have tried the Field Refresh Button, manually adding
> fields to the list and hacking the RDL field list. Each time I manually
> add, I get an index out of bounds error when trying to run the report. If
> I then hit the refresh button the fields I have manually added are
> removed'
> Also, must the field names be unique among the temp tables? I assumed not
> since they are in separate queries.
> Many thanks for any help
>|||Bruce
Many thanks for your prompt reply. I found my problem was a simple one where
I had not included all the new fields in all the select statements. Your
point is well taken though and the use of the temp tables was a last resort
because I could not get the original more straight-forward query to work. I
was getting redundant hits as a result of a subquery so had to use this
approach to get it working for a deadline.
Surprisingly this approach does work in the preview panel as well as
deployed to the web. However the query does not execute inside of the data
panel; it just dies without any errors. I assume this is what you are
referring to.
Many thanks for all your help up here!
Mike
RS deployment on load balanced servers
Could anybody offer any advice on the internal mechanics of report server?
Our server setup is as follows.
SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
One of which is a publisher with files replicated to the other two.
We'd like to set up reporting services, but need a bit of advice as to the
role of the report server.
Our plan is to set up RS on all three servers for load balancing, all
pointing to the same SQL cluster.
As I understand it, when an rdl file is deployed or uploaded to report
server, report server takes the file, breaks it down, encrypts it and
publishes it to the RS database. Is this correct? Doe RS have any other
function at this point? Are references to the reports stored on the IIS
server?
In our setup when we publish to http://abcdefg/ReportServer, our content
switches will decide which server the report is sent to. If it *doesn't* go
to our publishing server, do we need to be concerned with replication?
Also, what issues do we face RE encryption key on the three servers? We need
to ensure that they are all the same. Is this something that can be specified
during setup?
I Hope this makes sense!
JoeThis is 100% supported configuration. Search BOL for web farm (if you do not
have RS installed yet and don't have BOL then you can search the Microsoft
site for this). I don't have a web farm configuration but based on my
experience with RS this is what happens: In a web farm all the server front
ends use the same SQL Server database. So, when you deploy you only need to
deploy once and that gets the information used by the app into the database.
RS has three parts. The SQL Server database object store, and two asp.net
1.1 applications. One of the applications is core to the product, it does
all the rendering of the reports and uses the object store. The other
(Report Manager) you can consider a portal. This is optional, some people
use either URL integration or webservices and have their own front end
instead of using Report Manager.
Note that for a web farm you need to have enterprise licenses. Not only for
the SQL server cluster you have but you need an SQL Server interprise
license for each IIS server in your web farm. Every server used by RS has to
have a SQL Server license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> Could anybody offer any advice on the internal mechanics of report server?
> Our server setup is as follows.
> SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> One of which is a publisher with files replicated to the other two.
> We'd like to set up reporting services, but need a bit of advice as to the
> role of the report server.
> Our plan is to set up RS on all three servers for load balancing, all
> pointing to the same SQL cluster.
> As I understand it, when an rdl file is deployed or uploaded to report
> server, report server takes the file, breaks it down, encrypts it and
> publishes it to the RS database. Is this correct? Doe RS have any other
> function at this point? Are references to the reports stored on the IIS
> server?
> In our setup when we publish to http://abcdefg/ReportServer, our content
> switches will decide which server the report is sent to. If it *doesn't*
go
> to our publishing server, do we need to be concerned with replication?
> Also, what issues do we face RE encryption key on the three servers? We
need
> to ensure that they are all the same. Is this something that can be
specified
> during setup?
> I Hope this makes sense!
> Joe|||Thanks for the information Bruce. It looks like our options are to compromise
our SQL cluster by putting IIS and RS on it, something anybody with an ounce
of sense wouldn't do, or to pay MS for 3 additional enterprise liscences! I
don't know about you, but this seems to me like this is a liscence to print
money!
"Bruce L-C [MVP]" wrote:
> This is 100% supported configuration. Search BOL for web farm (if you do not
> have RS installed yet and don't have BOL then you can search the Microsoft
> site for this). I don't have a web farm configuration but based on my
> experience with RS this is what happens: In a web farm all the server front
> ends use the same SQL Server database. So, when you deploy you only need to
> deploy once and that gets the information used by the app into the database.
> RS has three parts. The SQL Server database object store, and two asp.net
> 1.1 applications. One of the applications is core to the product, it does
> all the rendering of the reports and uses the object store. The other
> (Report Manager) you can consider a portal. This is optional, some people
> use either URL integration or webservices and have their own front end
> instead of using Report Manager.
> Note that for a web farm you need to have enterprise licenses. Not only for
> the SQL server cluster you have but you need an SQL Server interprise
> license for each IIS server in your web farm. Every server used by RS has to
> have a SQL Server license.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > Could anybody offer any advice on the internal mechanics of report server?
> >
> > Our server setup is as follows.
> >
> > SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> > One of which is a publisher with files replicated to the other two.
> >
> > We'd like to set up reporting services, but need a bit of advice as to the
> > role of the report server.
> >
> > Our plan is to set up RS on all three servers for load balancing, all
> > pointing to the same SQL cluster.
> >
> > As I understand it, when an rdl file is deployed or uploaded to report
> > server, report server takes the file, breaks it down, encrypts it and
> > publishes it to the RS database. Is this correct? Doe RS have any other
> > function at this point? Are references to the reports stored on the IIS
> > server?
> >
> > In our setup when we publish to http://abcdefg/ReportServer, our content
> > switches will decide which server the report is sent to. If it *doesn't*
> go
> > to our publishing server, do we need to be concerned with replication?
> >
> > Also, what issues do we face RE encryption key on the three servers? We
> need
> > to ensure that they are all the same. Is this something that can be
> specified
> > during setup?
> >
> > I Hope this makes sense!
> >
> > Joe
>
>|||Depends on your licensing how bad a hit it is. If you are doing processor
licenses then it is a pretty big hit. If all you are paying for is the
server license then not too bad (especially if you compare against Crystal
or BO). In my case my corporation has SQL Server client licenses covered for
all PCs so I have no CALs to do, just the server license. It is a different
story if you are doing processor licenses.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:EECC39FD-C9F0-4F5A-B6EE-C19D689A2F15@.microsoft.com...
> Thanks for the information Bruce. It looks like our options are to
compromise
> our SQL cluster by putting IIS and RS on it, something anybody with an
ounce
> of sense wouldn't do, or to pay MS for 3 additional enterprise liscences!
I
> don't know about you, but this seems to me like this is a liscence to
print
> money!
> "Bruce L-C [MVP]" wrote:
> > This is 100% supported configuration. Search BOL for web farm (if you do
not
> > have RS installed yet and don't have BOL then you can search the
Microsoft
> > site for this). I don't have a web farm configuration but based on my
> > experience with RS this is what happens: In a web farm all the server
front
> > ends use the same SQL Server database. So, when you deploy you only need
to
> > deploy once and that gets the information used by the app into the
database.
> > RS has three parts. The SQL Server database object store, and two
asp.net
> > 1.1 applications. One of the applications is core to the product, it
does
> > all the rendering of the reports and uses the object store. The other
> > (Report Manager) you can consider a portal. This is optional, some
people
> > use either URL integration or webservices and have their own front end
> > instead of using Report Manager.
> >
> > Note that for a web farm you need to have enterprise licenses. Not only
for
> > the SQL server cluster you have but you need an SQL Server interprise
> > license for each IIS server in your web farm. Every server used by RS
has to
> > have a SQL Server license.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Joe" <Joe@.discussions.microsoft.com> wrote in message
> > news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > > Could anybody offer any advice on the internal mechanics of report
server?
> > >
> > > Our server setup is as follows.
> > >
> > > SQL Server 2000 clusters in active/passive. Load balanced web servers
x 3.
> > > One of which is a publisher with files replicated to the other two.
> > >
> > > We'd like to set up reporting services, but need a bit of advice as to
the
> > > role of the report server.
> > >
> > > Our plan is to set up RS on all three servers for load balancing, all
> > > pointing to the same SQL cluster.
> > >
> > > As I understand it, when an rdl file is deployed or uploaded to report
> > > server, report server takes the file, breaks it down, encrypts it and
> > > publishes it to the RS database. Is this correct? Doe RS have any
other
> > > function at this point? Are references to the reports stored on the
IIS
> > > server?
> > >
> > > In our setup when we publish to http://abcdefg/ReportServer, our
content
> > > switches will decide which server the report is sent to. If it
*doesn't*
> > go
> > > to our publishing server, do we need to be concerned with replication?
> > >
> > > Also, what issues do we face RE encryption key on the three servers?
We
> > need
> > > to ensure that they are all the same. Is this something that can be
> > specified
> > > during setup?
> > >
> > > I Hope this makes sense!
> > >
> > > Joe
> >
> >
> >|||Per processor licenses!!
Our server setup is as follows.
SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
One of which is a publisher with files replicated to the other two.
We'd like to set up reporting services, but need a bit of advice as to the
role of the report server.
Our plan is to set up RS on all three servers for load balancing, all
pointing to the same SQL cluster.
As I understand it, when an rdl file is deployed or uploaded to report
server, report server takes the file, breaks it down, encrypts it and
publishes it to the RS database. Is this correct? Doe RS have any other
function at this point? Are references to the reports stored on the IIS
server?
In our setup when we publish to http://abcdefg/ReportServer, our content
switches will decide which server the report is sent to. If it *doesn't* go
to our publishing server, do we need to be concerned with replication?
Also, what issues do we face RE encryption key on the three servers? We need
to ensure that they are all the same. Is this something that can be specified
during setup?
I Hope this makes sense!
JoeThis is 100% supported configuration. Search BOL for web farm (if you do not
have RS installed yet and don't have BOL then you can search the Microsoft
site for this). I don't have a web farm configuration but based on my
experience with RS this is what happens: In a web farm all the server front
ends use the same SQL Server database. So, when you deploy you only need to
deploy once and that gets the information used by the app into the database.
RS has three parts. The SQL Server database object store, and two asp.net
1.1 applications. One of the applications is core to the product, it does
all the rendering of the reports and uses the object store. The other
(Report Manager) you can consider a portal. This is optional, some people
use either URL integration or webservices and have their own front end
instead of using Report Manager.
Note that for a web farm you need to have enterprise licenses. Not only for
the SQL server cluster you have but you need an SQL Server interprise
license for each IIS server in your web farm. Every server used by RS has to
have a SQL Server license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> Could anybody offer any advice on the internal mechanics of report server?
> Our server setup is as follows.
> SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> One of which is a publisher with files replicated to the other two.
> We'd like to set up reporting services, but need a bit of advice as to the
> role of the report server.
> Our plan is to set up RS on all three servers for load balancing, all
> pointing to the same SQL cluster.
> As I understand it, when an rdl file is deployed or uploaded to report
> server, report server takes the file, breaks it down, encrypts it and
> publishes it to the RS database. Is this correct? Doe RS have any other
> function at this point? Are references to the reports stored on the IIS
> server?
> In our setup when we publish to http://abcdefg/ReportServer, our content
> switches will decide which server the report is sent to. If it *doesn't*
go
> to our publishing server, do we need to be concerned with replication?
> Also, what issues do we face RE encryption key on the three servers? We
need
> to ensure that they are all the same. Is this something that can be
specified
> during setup?
> I Hope this makes sense!
> Joe|||Thanks for the information Bruce. It looks like our options are to compromise
our SQL cluster by putting IIS and RS on it, something anybody with an ounce
of sense wouldn't do, or to pay MS for 3 additional enterprise liscences! I
don't know about you, but this seems to me like this is a liscence to print
money!
"Bruce L-C [MVP]" wrote:
> This is 100% supported configuration. Search BOL for web farm (if you do not
> have RS installed yet and don't have BOL then you can search the Microsoft
> site for this). I don't have a web farm configuration but based on my
> experience with RS this is what happens: In a web farm all the server front
> ends use the same SQL Server database. So, when you deploy you only need to
> deploy once and that gets the information used by the app into the database.
> RS has three parts. The SQL Server database object store, and two asp.net
> 1.1 applications. One of the applications is core to the product, it does
> all the rendering of the reports and uses the object store. The other
> (Report Manager) you can consider a portal. This is optional, some people
> use either URL integration or webservices and have their own front end
> instead of using Report Manager.
> Note that for a web farm you need to have enterprise licenses. Not only for
> the SQL server cluster you have but you need an SQL Server interprise
> license for each IIS server in your web farm. Every server used by RS has to
> have a SQL Server license.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > Could anybody offer any advice on the internal mechanics of report server?
> >
> > Our server setup is as follows.
> >
> > SQL Server 2000 clusters in active/passive. Load balanced web servers x 3.
> > One of which is a publisher with files replicated to the other two.
> >
> > We'd like to set up reporting services, but need a bit of advice as to the
> > role of the report server.
> >
> > Our plan is to set up RS on all three servers for load balancing, all
> > pointing to the same SQL cluster.
> >
> > As I understand it, when an rdl file is deployed or uploaded to report
> > server, report server takes the file, breaks it down, encrypts it and
> > publishes it to the RS database. Is this correct? Doe RS have any other
> > function at this point? Are references to the reports stored on the IIS
> > server?
> >
> > In our setup when we publish to http://abcdefg/ReportServer, our content
> > switches will decide which server the report is sent to. If it *doesn't*
> go
> > to our publishing server, do we need to be concerned with replication?
> >
> > Also, what issues do we face RE encryption key on the three servers? We
> need
> > to ensure that they are all the same. Is this something that can be
> specified
> > during setup?
> >
> > I Hope this makes sense!
> >
> > Joe
>
>|||Depends on your licensing how bad a hit it is. If you are doing processor
licenses then it is a pretty big hit. If all you are paying for is the
server license then not too bad (especially if you compare against Crystal
or BO). In my case my corporation has SQL Server client licenses covered for
all PCs so I have no CALs to do, just the server license. It is a different
story if you are doing processor licenses.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:EECC39FD-C9F0-4F5A-B6EE-C19D689A2F15@.microsoft.com...
> Thanks for the information Bruce. It looks like our options are to
compromise
> our SQL cluster by putting IIS and RS on it, something anybody with an
ounce
> of sense wouldn't do, or to pay MS for 3 additional enterprise liscences!
I
> don't know about you, but this seems to me like this is a liscence to
> money!
> "Bruce L-C [MVP]" wrote:
> > This is 100% supported configuration. Search BOL for web farm (if you do
not
> > have RS installed yet and don't have BOL then you can search the
Microsoft
> > site for this). I don't have a web farm configuration but based on my
> > experience with RS this is what happens: In a web farm all the server
front
> > ends use the same SQL Server database. So, when you deploy you only need
to
> > deploy once and that gets the information used by the app into the
database.
> > RS has three parts. The SQL Server database object store, and two
asp.net
> > 1.1 applications. One of the applications is core to the product, it
does
> > all the rendering of the reports and uses the object store. The other
> > (Report Manager) you can consider a portal. This is optional, some
people
> > use either URL integration or webservices and have their own front end
> > instead of using Report Manager.
> >
> > Note that for a web farm you need to have enterprise licenses. Not only
for
> > the SQL server cluster you have but you need an SQL Server interprise
> > license for each IIS server in your web farm. Every server used by RS
has to
> > have a SQL Server license.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Joe" <Joe@.discussions.microsoft.com> wrote in message
> > news:0739946E-1912-4EB1-BDC1-E4DA34740295@.microsoft.com...
> > > Could anybody offer any advice on the internal mechanics of report
server?
> > >
> > > Our server setup is as follows.
> > >
> > > SQL Server 2000 clusters in active/passive. Load balanced web servers
x 3.
> > > One of which is a publisher with files replicated to the other two.
> > >
> > > We'd like to set up reporting services, but need a bit of advice as to
the
> > > role of the report server.
> > >
> > > Our plan is to set up RS on all three servers for load balancing, all
> > > pointing to the same SQL cluster.
> > >
> > > As I understand it, when an rdl file is deployed or uploaded to report
> > > server, report server takes the file, breaks it down, encrypts it and
> > > publishes it to the RS database. Is this correct? Doe RS have any
other
> > > function at this point? Are references to the reports stored on the
IIS
> > > server?
> > >
> > > In our setup when we publish to http://abcdefg/ReportServer, our
content
> > > switches will decide which server the report is sent to. If it
*doesn't*
> > go
> > > to our publishing server, do we need to be concerned with replication?
> > >
> > > Also, what issues do we face RE encryption key on the three servers?
We
> > need
> > > to ensure that they are all the same. Is this something that can be
> > specified
> > > during setup?
> > >
> > > I Hope this makes sense!
> > >
> > > Joe
> >
> >
> >|||Per processor licenses!!
Subscribe to:
Posts (Atom)