April 25, 2006 at 8:57 am
We are trying to install Reporting Services 2005 on a separate Windows 2003 then our database server. Our database server is SQL Server 2005 Standard Edition. One of the main reasons we are doing this is because we want the dbase server to be isolated and don't want to install IIS or have any more processing on that server. So, we are going to have a separate server have RS installed and connect to a remote dbase. We are able to connect and see the dbases on the dbase server, but receive an initialization failure. Can someone advise us on this setup? Is this the wrong way to go? How would licensing work on this for production - would this require another SQL Server license?
April 26, 2006 at 8:33 am
There really not enough information to work with. Reporting Services can throw a plethora of errors that can be considered initialization errors because there are some many seperate componants that need to be given correct rights on the various servers.
Your basic configuration is fairly standard there is no requirement that they DB and IIS share the same server.
Here is a link that can help you pay particular attention to how the rights are set up:
http://www.mathgv.com/sql2005docs/SQL2005ReportingServicesInstall.htm
June 13, 2006 at 1:59 pm
As far as licensing, you need one license for each SQL instance regardless of whether it has RS on it. The RS license "rides" on the SQL DB license.
That's my understanding.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgViewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply