March 24, 2011 at 3:34 am
Before you read any further, this is more of an answer not a question as such, I just wanted to be clear on this.
I have just upgraded to a new machine, 64 bit running Windows 7 and SQL2008. My previous processes of deploying SSIS packages using the manifest file and configuration files suddenly stopped working with the above error. I was a little confused as only having installed SQL 2008, it should have been obvious to the system what the required path was.
Anyway, I started searching the various forums and came up with varying responses ranging from installing SQL2005 Client Tools (shouldn't be necessary as a workaround when using 2008) to using the Command Line options, a good alternative. Now me, I don't like workarounds, I want to know what the problem actually was and then try and fix it before succumbing to workarounds.
If you check the executable linked to the manifest file, it shows up as SQL 2005 Integration Services Package Installation Utility. That's right, 2005 even though it was a 2008 SQL installation. Best guess is that Microsoft didn't rename it or change an internal pathname as the file is different between the two versions of SQL. So, I think the executable is actually looking for a SQL 2005 installation, hence the error message about the path and the fix by installing SQL 2005 Client Tools. I simply pointed the manifest executable to a Package Installation Utility (dtsinstall.exe) in a SQL 2008 folder (\100\DTS\Binn\) and now my deployments are back to where they were. (Using dtsinstall.exe from the Command line would always have worked, I believe, as long as your path went through a 100 folder!)
Not sure if this is an optimal solution but it worked for me and hopefully it could save somebody else a bit of time in the future.:-)
May 8, 2014 at 4:17 pm
I got this error when i specify the deployment folder to network share drive. I changed to use instead the local drive and it works.
so under project->properties->deployment utility -> deploymentoutputpath--> should be local disk.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply