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

Digging into a long running job

Revisiting the blogger to finally start again blogging about the SQL Server after a long long time.  This post is on analyzing and digging into what is causing a job significant time to complete. This will be a basic level of approach and I wish, I could have done better. But, its was enough in my case to get to a conclusion, with the knowledge I equip.   Issue : A job that's scheduled to run every three hours, was running for more than 48hours. Average job run time, 1.5hrs.  Analysis : First and foremost thing to do, is to find out on what session id is the job running on the instance. You may use the below query to fetch the session id of the job from the job name. declare @Var1 varchar(36) select @Var1=substring(REPLACE(CAST(job_id AS VARCHAR(36)),'-',''),17,16) from sysjobs where name =' JOB_NAME ' select * from sys.sysprocesses where program_name like '%'+@Var1+'%' You may get a single row or multiple rows with ...
Post a Comment
Read more

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

Incorrect SET Options with Filtered Indexes

Rebuild Index|Create Index|DML on a Table with Filtered Index fails with the error: The following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934).  The step failed. The Operation above might succeed when its through SSMS. But, would fail when the operation is from a SQL Agent Job. This is because, SQL Agent by default, do not have the SET Options enabled (ON). They are OFF. Reason: The following are the SET Options that are needed while operation on a table with a filtered index. Required SET Options for Filtered Indexes The SET options in the Required Value column are required whenever any of the following conditions occur: Create a filtered index. INSERT, UPDATE, DELETE, or MERGE operation modifies the data in a...
Post a Comment
Read more