Can't create a SSISDB catalog due to missing SSISDBBackup.bak file, even though SSIS is installed
To check if SSIS installed, open Sql Server Configuration Manager, in the SQL Server Services, is something like 'SQL Server Integration Services 13.0' running?
Comments
-
Cenderze almost 2 years
I've downloaded SQL Server 2016 standard edition trial along with SSDT in order to test what one can do with a standard edition in SSIS, SSRS, and SSAS.
I also wanted to know whether standard version's SSISDB logging capabilities differs from the one in Enterprise. For this I wanted to create an SSISDB catalog under
Integration Services Catalogs
in SSMS.When I try to do this, however, I get the error saying that
The catalog backup file 'C:\Program Files\Microsoft SQL Server\130\DTS\binn\SSISDBBackup.bak could not be accessed. Make sure the database file exists, and the SQL server service account is able to access it
From googling this issue it appears as this message shows up whenever someone doesn't have SSIS installed, but I have SSIS on the machine, I've even made a small Project and executed it from within SSIS without any issues just to verify.
I have set this up on
localhost
where I am the admin. Does anyone have any ideas why this won't work?Regards,
Cenderze
-
Cenderze about 7 yearsSorry for late reply. This is strange. By checking SQL Server Confirugration Manager, I saw that SQL Server integration services is indeed not running. How can that be, seeing as I've opened up SSIS, and I have created a Project and a package (but I can't deploy them due to the error of the thread).
-
Rich about 7 yearsSSIS in SQL Server Data Tools is the development environment and you can open them up and work with them in there, independently of the SSIS service on the server.