Sửa lỗi reporting services catalog database file existence năm 2024

This happened to me because I installed MMSQL Server and then I had to uninstall it and re-install because I had the collation wrong. But during one of the pre-installation checks that SQL Server runs it come up with:

“Reporting Services Catalog Database File Existence” failed “Reporting Services Catalog Temporary Database File Existence” failed.

Sửa lỗi reporting services catalog database file existence năm 2024

To fix this problem we need to delete some files that the SQL Server uninstaller must miss for some reason.

Navigate to “C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA” then delete the following files:

Sửa lỗi reporting services catalog database file existence năm 2024

ReportServer.mdf ReportServer_log.LDF ReportServerTempDB.mdf ReportServerTempDB_log.LDF

Once you have deleted the files hit the re-run button on the pre-installation check and it will pass.

Now your problem should be resolved just continue on with your install.

Hi Everyone, I'm Jake. I have created this site basically as my own knowledge base, hopefully you find some of the information on here useful. I work with businesses across South West Victoria to leverage technology to improve the way they work & keep their data safe. If you want to connect with me look me up on LinkedIn.

But they wanted to check if there is some other solution as they are doing the setup from command prompt remotely. This means that they would need to delete the file to proceed. This would increase their work as they need to parse the log to see the error, check if this is the error then delete those files which I mentioned in my earlier blog and then run the setup again. Rather than that, they wanted an easy way to “just deploy it without error”

WORKAROUND/SOLUTION

I tried explaining to them that this error would not be seen in new/fresh installation. The error would be seen if they have done a prior installation of SQL on the machine with Reporting Services. But they wanted to know the “easy” workaround.

Here is the command which they were using

cmd /c setup.exe /q /IAcceptSQLServerLicenseTerms /Action=Install /ConfigurationFile=”C:\SQLMedia\SQLInstall.ini”

I looked into the ini file which they were using and found a solution for them. The config file has no setting provided for RSINSTALLMODE. Due to this setup was taking DefaultNativeMode. Below is explained in Microsoft documentation

If the installation includes the SQL Server Database engine, the default RSINSTALLMODE is DefaultNativeMode.If the installation does not include the SQL Server Database engine, the default RSINSTALLMODE is FilesOnlyMode. If you choose DefaultNativeMode but the installation does not include the SQL Server Database engine, the installation automatically changes the RSINSTALLMODE to FilesOnlyMode

So, I asked them to add the following line in SQLInstall.ini file.

RSINSTALLMODE=FilesOnlyMode

Now, if I read the error message, it also tells me the same. After this, the setup deployment was going fine even if SSRS files were there. Have you faced a similar issue with SQL prompt installation via command prompt?

Bạn cố gắng cài đặt lại Microsoft SQL Server 2008, nhưng trong quá trình cài đặt, bị lỗi "report services catalog database file existence". Nguyên nhân là do trước đó bạn đã gỡ bỏ phần mềm, tuy nhiên vẫn còn thư mục Data chưa được gỡ ra(tức đã tồn tại tệp tin đó). Để giải quyết vấn đề này, bạn cần phải gỡ bỏ các tệp tin hoặc đổi tên các tệp tin tồn tại trong đó. Rồi cài đặt lại.

Theo mặc định, khi bạn cài đặt instance của SQL Server 2008 Reporting Services, quá trình cài đặt tạo ra hai cơ sở dữ liệu mới được đặt tên là "ReportServer_ instance_name" và "ReportServer_ tempdb instance_name". Cơ sở dữ liệu được tạo ra trong thư mục sau đây cho trường hợp của SQL Server mà bạn đang chạy:

%ProgramFiles%\Microsoft SQL Server\MSSQL10.Instance Name\MSSQL\DATA

Lưu ý: Đối với các trường hợp MSSQLSERVER mặc định, tên cơ sở dữ liệu là "ReportServer" và "ReportServerTempDB."

Cơ sở dữ liệu có thể chứa dữ liệu người dùng. Vì vậy, chương trình cài đặt không xóa những cơ sở dữ liệu khi bạn gỡ bỏ cài đặt SQL Server 2008 Reporting Services. Trường hợp khi bạn cài đặt mà có cùng tên, chương trình cài đặt phát hiện Report Server databases đã cho cùng tên. Khi điều này xảy ra, bạn nhận được thông báo lỗi được đề cập trong phần "Symptoms".

Disasters are always bad. Recovering from disaster is a skill and needs a lot of planning and practice. One of my clients had a disaster and built a new machine to restore the backups. They tried a few attempts to install SQL Server but were having issues. Finally, they contacted me for consultation to fix rule, reporting services catalog database file existence.

I uninstalled SQL Server and started the installation again. At configuration rules checking screen, we got two items listed as failed.

Sửa lỗi reporting services catalog database file existence năm 2024

Here is the text of the message when we click on the “Failed” hyperlink.

Rule “Reporting Services Catalog Database File Existence” failed. The Reporting Services catalog database file exists. Select a Reporting Services files-only mode installation.

AND

Rule “Reporting Services Catalog Temporary Database File Existence” failed. The Reporting Services catalog temporary database file exists. Select a Reporting Services files-only mode installation.

I searched on internet and found that its due to earlier files of ReportServer and ReportServerTempDB databases which are created as a part of SSRS installation. I wanted to check setup logs to see the path. Here is the snippet from Detail.txt file

Microsoft.SqlServer.Configuration.RSExtension.DoesTempCatalogExistBlocker 2017-06-30 12:23:09 RS: Initializing the check for exisiting catalog database and temp db files. 2017-06-30 12:23:09 RS: Getting the SQL data path 2017-06-30 12:23:09 RS: Current RS install mode is ‘DefaultNativeMode’ 2017-06-30 12:23:09 RS: Using SQl data path E:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\DATA 2017-06-30 12:23:09 RS: Getting the RS database name 2017-06-30 12:23:09 RS: Using default database name. 2017-06-30 12:23:09 RS: Getting the RS database name 2017-06-30 12:23:09 RS: Using default database name. 2017-06-30 12:23:09 RS: Catalog Temp db file exists 2017-06-30 12:23:09 Slp: Evaluating rule : RS_DoesCatalogTempDBExist 2017-06-30 12:23:09 Slp: Rule running on machine: SQLCDBSVR 2017-06-30 12:23:09 Slp: Rule evaluation done : Failed 2017-06-30 12:23:09 Slp: Rule evaluation message: The Reporting Services catalog temporary database file exists. Select a Reporting Services files-only mode installation.

Now, using log we can see exact behavior of SQL Server Rule check and the location which we need to target.

WORKAROUNS/SOLUTION

If you get same error, try and look at SQL Setup logs and search for “DoesCatalogExistBlocker” and “DoesTempCatalogExistBlocker” and you should see path there. If we look at that path, we should see files like below. • ReportServer.mdf • ReportServer_log.LDF • ReportServerTempDB.mdf • ReportServerTempDB_log.LDF. In case of named instance, files would be having instance name as well. In my case, the instance name was SQL2014, so files were as below.

Sửa lỗi reporting services catalog database file existence năm 2024

As a safety measure, take a backup and remove the files from this location. Then we can use “rerun” button available on the same screen below the green bar. This should take care of making failed checks as Passed.