Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve created a new SSIS package in Visual Studio 2010 and started deploying the package to a SQL 2012 database on a remote server.
I can connect to the DB and see the SSISDB folder but when i deploy the package I get the following error:
“The path for ‘ISServerExec.exe’ cannot be found. The operation will now exit.”
Are you sure you have SSIS 2012 installed on that machine? and the service is running? (check SQL Server Configuration Manager)
This looks like you created an SSIS catalog on a SQL Server machine that has no SSIS service running (or SQL is unable to see the correct version of SSIS running). You will be able to see the catalog and even go through the deployment wizard from visual studio, but will receive the error message you mentioned above when you finalize your deployment.