Skip to main content

Rule "Reporting Services Catalog Database File Existence" failed

Rule "Reporting Services Catalog Database File Existence" failed error:
------------


Solution: Check for the existence of Reporting Services database files in the default location or the location where the database files are set to go. Delete the database files. Then the retry would solve the problem.

Comments

  1. AnonymousMarch 9, 2013 at 10:56 PM

    By default, when you install an instance of SQL Server 2008 Reporting Services,
    the instance setup process creates two new databases that are named
    "ReportServer_Instance_Name" and "ReportServer_Instance_nameTempDB."
    These databases are created under the following folder for the instance
    of the SQL Server that you are running:

    "" C:\Program Files\Microsoft SQL Server
    Now DELETE the folder MSSQL10_50.MSSQLSERVER ""

    This case occurs if you have previously installed and uninstalled it.



    Note For the default MSSQLSERVER instance, the database names are
    "ReportServer" and "ReportServerTempDB."

    These databases may contain user data.
    Therefore, the Setup program does not delete these databases
    when you uninstall a SQL Server 2008 Reporting Services instance.
    When you install an instance that has the same instance name,
    the Setup program detects that the Report Server databases
    already exist for that instance name. When this occurs,
    you receive the error message that is mentioned in the "Symptoms" section.

    - Veyron

    ReplyDelete
  2. Jake gardnerMarch 13, 2013 at 3:31 PM

    Thanks for this sends me on the right path, and good comment from you as well anonymous

    ReplyDelete
  3. UnknownJanuary 30, 2014 at 10:48 PM

    how can i resolve it now?

    ReplyDelete
  4. Jake GardnerAugust 28, 2014 at 2:50 PM

    Thanks for the post. I hate it when installations fail and you have to try to figure out why.

    ReplyDelete

Post a Comment

Popular posts from this blog

Deferred prepare could not be completed

This is usually an error that is encountered while querying a remote database on a different server instance which says OLEDB provider "SQLNCLI" for linked server "ABCD" returned message "Deffered prepare could not be completed" Msg 8180, Level 16, State 1, Line 1 Statement(s) could not be prepared. This is the way I could rectify, though this is not the lone mistake that gives this error every time. Just set the default to the database that is being querying to the user through which the Linked server is connecting to the database.
4 comments
Read more

Key not valid for use in specified state - SSIS

You might see the following error while a package was newly imported and is set to be called from an SQL Agent through a job. The job would fail reporting the below error. Source:        Description: Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error This is mainly because, the package protection level, which is by default set to  "EncryptWithSensitiveKey" Resolution: Set the package protection level to "DontSaveSensitive". But, if in case you know the password for the key, you could use it. How to change the SSIS Package Protection: In Business Intelligence Development Studio, open the Integration Services project that contains the package. Open the package in the SSIS designer. If the Properties window d...
Post a Comment
Read more

Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql'

As huge a database grows, that tedious are regular DBA activities become. Besides, a warehouse database, can grow with no bounds to challenge.  There was a patching on one of our databases, SP3 for SQL Server 2008 R2, which was failing due to the error below. As the error says, MASTER the heart of SQL Server  “Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 2627, state 1, severity 14. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. Cannot recover the master database. SQL Server is unable to run. Restore master from a full ...
Post a Comment
Read more