I have SSIS package setup on a remote SQL Server to run on schedule via SQL Server Agent. It was setup initially by remote desktop-ing to the server and connecting to it via SSMS running on the same machine where SQL Server is running. Package source is"File System" and absolute path is specified (D:\Folder1\Package1.dtsx). There is just one step in the job - to run SSIS package. Everything works as it should.
Now I want to modify this job - change number of retry on failure attempts. I can successfully connect to this SQL Server instance via SSMS from my developer workstation. I can then go to "Advanced Settings" for this job step and change "Retry attempts" to some other number. However, when I press "OK" I get this error message:
TITLE: SSIS Execution Properties
------------------------------
Failed to open package file "D:\Folder1\Package1.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can
be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
({105912C7-6345-42B4-99B4-58566291867B})
------------------------------
ADDITIONAL INFORMATION:
Failed to open package file "D:\Folder1\Package1.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can
be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
({105912C7-6345-42B4-99B4-58566291867B})
Interestingly enough, in spite of this error message the number of retries is successfully changed.
I understand it happens because SSMS tries to locate package on my local hard drive and the same folder doesn't exist on my development PC. It still doesn't make sense to me. Does SSMS not know I am accessing remote server? How come I don't get any errors when I just execute this job via SSMS when SSMS runs on my development PC?