Showing posts with label ssrs. Show all posts
Showing posts with label ssrs. Show all posts

Thursday, March 22, 2012

alert messages in SSRS

hi,

I am working on migration from crystal reports to SSRS. my crystal report has some alerting formulas, which displays pop-ups at runtime based on some conditions.How do i implement those alerting formulas in SSRS.

Thanks in advance.

I think you can call msgboxes from code, beyond that there isn't anything.

Why are you migrating from Crystal to RS?

Monday, February 13, 2012

After installing SP2 SSRS will not start

Installed SP2 and now SSRS will not start.

Errors:

    At Report Manager URL: The report server is not responding. Verify that the report server is running and can be accessed from this computer. At Report Server URL: The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError) Access to the path '<DRIIVE>\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config' is denied. In SSS Log Files: ReportingServicesService!library!8!6/20/2007-16:04:04:: i INFO: Current DB Version C.0.8.40, Instance Version C.0.8.54.
    ReportingServicesService!library!8!6/20/2007-16:04:04:: i INFO: Starting upgrade DB version from C.0.8.40 to C.0.8.54.
    ReportingServicesService!library!8!6/20/2007-16:04:04:: e ERROR: Exception caught while starting service. Error: System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database 'PD'. No entry found with that name. Make sure that the name is entered correctly.
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
    at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)
    at Microsoft.ReportingServices.Library.ConnectionManager.EnsureCorrectDBVersion()
    at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
    at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread()
    ReportingServicesService!library!8!6/20/2007-16:04:04:: e ERROR: Attempting to start service again...

When I go to the RS Configurator the Database is reported as .40 and the Upgrade Button results in an upgrade success but the Database stays the same version.

Joy....

Much help needed and appreciated....

-p

Since the upgrade went so horribly I created a NEW SSRS database using the SSRS Configuation Tool. I also had to change the permission the '<DRIIVE>\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config' file. I have NO idea why the services could r/w from the file before the upgrade and not afterwards that actually scares me the most about this because the SQL team can't fix my box with a QFE. The database upgrader is clearly buggy and that scares me as well, but I bet the SQL team could fix that and repair turfed databases via script.

The impact of doing this meant I had to re-do the following things:

Re-set all Permissions and Site Settings (I had customized the My Reports role) Recreate all Folders and Permissions. (I have top level folders and grant rights there not at the HOME folder). Re-publish all reports (for me and all my "My Users") Re-set passwords on Data Sources which needed them. Inform users all subscriptions were lost

Thursday, February 9, 2012

Advise on Licensing SSRS on NLB IIS farm

Hi All,
I have the following question, in my organization we employ a policy of
splitting out our enterprise infrastructure, IIS separated from SQL Server
etc.
We currently have a number of SQL Server 2000 and 2005 clusters and also two
NLB IIS farms (each with 4 nodes).
If I install SQL Server Reporting Services on the NLB farms (databases on
two of the SQL Server Clusters) to make this product available to to people
here then am I right in assuming that firstly I will need Enterprise Edition
of Reporting Services 2005 installed on my NLB's as this is the only edition
capable of scale out SSRS deployment.
Secondly and more importantly will I also need in addition a separate SQL
Server 2005 Enterprise Edition license on each of the nodes involved in the
NLB's (8 nodes therefore 8 licenses)?
If this is the case then I am really concerned at this supposed low cost
reporting solution from Microsoft, as I would then for this scenario need
minimum 10 Enterprise Edition SQL Server 2005 licenses (8 for the NLB nodes
and 1 for each failover cluster (Active/Passive) )
This is no longer a cheap solution for our reporting needs.
Thanks for your help.
Kind Regards,
DesYou have the licensing correct. Enterprise is the only one which supports a
web farm and any server that has Reporting Services installed must have a
server license. How expensive it is for you depends on how you license (CAL
or per processor).
If you price Crystal in such a configuration you will find that it is even
more expensive.
Unless you have one heck of a lot of reports and users then I sincerely
doubt that you need such a configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Des FitzGerald" <dfitz@.dr-sql.com> wrote in message
news:C3A94D89.73DF%dfitz@.dr-sql.com...
> Hi All,
> I have the following question, in my organization we employ a policy of
> splitting out our enterprise infrastructure, IIS separated from SQL Server
> etc.
> We currently have a number of SQL Server 2000 and 2005 clusters and also
> two
> NLB IIS farms (each with 4 nodes).
> If I install SQL Server Reporting Services on the NLB farms (databases on
> two of the SQL Server Clusters) to make this product available to to
> people
> here then am I right in assuming that firstly I will need Enterprise
> Edition
> of Reporting Services 2005 installed on my NLB's as this is the only
> edition
> capable of scale out SSRS deployment.
> Secondly and more importantly will I also need in addition a separate SQL
> Server 2005 Enterprise Edition license on each of the nodes involved in
> the
> NLB's (8 nodes therefore 8 licenses)?
> If this is the case then I am really concerned at this supposed low cost
> reporting solution from Microsoft, as I would then for this scenario need
> minimum 10 Enterprise Edition SQL Server 2005 licenses (8 for the NLB
> nodes
> and 1 for each failover cluster (Active/Passive) )
> This is no longer a cheap solution for our reporting needs.
> Thanks for your help.
> Kind Regards,
> Des
>|||Hi Bruce,
Its not a case of a lot of users or reports - it is a case of a fault
tolerance / disaster recovery solution, we have network load balanced web
farms to facilitate this setup.
The 2 web NLB farms are for integration and production, these need to be
there for our environment, the decision was taken as we are a multi site
organization to have 2 nodes of each NLB in each of our main offices and
then of these 2 nodes each one is in a separate server room, thus 4 nodes =2 per site and of the 2 per site each is separated per server room, disaster
recovery and fault tolerance taken care of.
We will need per processor licensing as intranet reports are made and CAL
will be too expensive.
This is an extremely expensive solution in this case - I have no idea of the
cost of Crystal reports and this is no place to get into this argument as it
does not help.
I just think that Microsoft should de-couple SSRS from SQL Server and make
it Microsoft Reporting Server or something like this with its own licensing
model, the databases can still be stuck to SQL Server but this would make it
more transparent and quite possibly cheaper as Enterprise SQL Server 2005
Processor licenses are not cheap and if the database and reporting server
sides are split as recommended my MS then this does lead to an expensive
solution when each of the IIS NLB nodes need separate licenses.
Thanks for the answer though.
Cheers,
Des
On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl, "Bruce
L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
> You have the licensing correct. Enterprise is the only one which supports a
> web farm and any server that has Reporting Services installed must have a
> server license. How expensive it is for you depends on how you license (CAL
> or per processor).
> If you price Crystal in such a configuration you will find that it is even
> more expensive.
> Unless you have one heck of a lot of reports and users then I sincerely
> doubt that you need such a configuration.
>|||Hi Bruce,
A final question for you, if I have SSRS 2000 and SSRS 2005 installed on
these NLBs (8 nodes total as mentioned) do I therefore also need separate
SQL Server 2000 and SQL Server 2005 Enterprise Edition CPU licenses for
these nodes?
So a total of 16 Enterprise Edition CPU licenses for the Reporting Services
setup?
Cheers,
Des
On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl, "Bruce
L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
> You have the licensing correct. Enterprise is the only one which supports a
> web farm and any server that has Reporting Services installed must have a
> server license. How expensive it is for you depends on how you license (CAL
> or per processor).
> If you price Crystal in such a configuration you will find that it is even
> more expensive.
> Unless you have one heck of a lot of reports and users then I sincerely
> doubt that you need such a configuration.
>|||I'm confused, you want to have both RS 2000 and RS 2005 installed on each
server?
Why would you do that? RS 2000 reports run fine in RS 2005. And they run
much faster.
In case you do want to do this, I believe a SQL 2005 license allows running
both 200 and 2005 so you would not need two licenses. However, I would check
with whoever you buy licenses from.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Des FitzGerald" <dfitz@.dr-sql.com> wrote in message
news:C3AA8E77.7B74%dfitz@.dr-sql.com...
> Hi Bruce,
> A final question for you, if I have SSRS 2000 and SSRS 2005 installed on
> these NLBs (8 nodes total as mentioned) do I therefore also need separate
> SQL Server 2000 and SQL Server 2005 Enterprise Edition CPU licenses for
> these nodes?
> So a total of 16 Enterprise Edition CPU licenses for the Reporting
> Services
> setup?
> Cheers,
> Des
>
> On 08/01/2008 18:00, in article OyC$EghUIHA.280@.TK2MSFTNGP03.phx.gbl,
> "Bruce
> L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote:
>> You have the licensing correct. Enterprise is the only one which supports
>> a
>> web farm and any server that has Reporting Services installed must have a
>> server license. How expensive it is for you depends on how you license
>> (CAL
>> or per processor).
>> If you price Crystal in such a configuration you will find that it is
>> even
>> more expensive.
>> Unless you have one heck of a lot of reports and users then I sincerely
>> doubt that you need such a configuration.
>