If you try and create an Integration Services Catalog and you receive the error SSISDBBackup.bak could not be accessed, it could be because you do not have Integration Services installed on your SQL Server instance.
Below I am going to attempt and create an Integration Services Catalog, by right clicking the item within SSMS and choosing Create Catalog.
You can read more about the benefits of using a catalog by following the link below: https://docs.microsoft.com/en-us/sql/integration-services/catalog/ssis-catalog?view=sql-server-2017. If you are going to run/manage many SSIS packages, using a catalog makes life a lot easier.
It then prompts you with some options, I choose the items below.
I press OK, but then I get the error below. It could not find the backup file to restore and create the catalog.
Looking in the directory, it shows that the file does not exist. Hmmm.
To fix this error, you need to make sure that you install Integration Services for this instance. Start up the installer and select the add features to an existing installation (highlighted in yellow below)
Now select Integration Services from the options below and press Next.
It should install without issues, but you will need to reboot after installing.
After rebooting, you can look in the directory and see that the SSISDBBackup.bak file is now located in the directory.
Now you can go through the process of creating the catalog and not receive the missing file error. When it is installed, it will look like the screenshot below. You can now deploy your SSIS projects and packages to the Catalog.
I only had a “default instance” in my example, but if you have a named instance, you would select that and it would install into the correct directory.
You have to look for the folder that contains the original .exe file or the original install disc that you used to instal SQL.
The message that appears is very confusing when its telling you to select the ‘install’ folder. Really should ask you where the original install exe is? smh
It then prompts you with some options, I choose the items below.
To fix this error, you need to make sure that you install Integration Services for this instance. Start up the installer and select the add features to an existing installation (highlighted in yellow below)
Now select Integration Services from the options below and press Next.
It should install without issues, but you will need to reboot after installing.
After rebooting, you can look in the directory and see that the SSISDBBackup.bak file is now located in the directory.
Now you can go through the process of creating the catalog and not receive the missing file error. When it is installed, it will look like the screenshot below. You can now deploy your SSIS projects and packages to the Catalog.
Jim Salasek's SQL Server Blog 
Which folder path do we need to apply after selecting “add features to an existing installation” ??
LikeLike
I only had a “default instance” in my example, but if you have a named instance, you would select that and it would install into the correct directory.
LikeLike
You have to look for the folder that contains the original .exe file or the original install disc that you used to instal SQL.
The message that appears is very confusing when its telling you to select the ‘install’ folder. Really should ask you where the original install exe is? smh
LikeLike
Thank you Eddy, I agree….sometimes the messages are not very clear on what they are asking for.
LikeLike
Excelente Post…. Diste en el mero problema.
LikeLike
Perfect… Thanks …
LikeLike
Thank you. Nice post
LikeLike