AIRWALKER-375999 (12/21/2010)
Hi Elliott thanks for your response,the excel file our ssis packages uses goes on a short journey before it end up on the database server,
it is uploaded to an ftp server from a client machine, and then is downloaded from the ftp server by another ssis package to our database server, then it is moved to a directory where the ssis package that is throwing this error is located.
Are you still having issues with this? I just solved my (very frustrating) problem.
My package has a hard coded "Excel File Path", which as far as I know, you can't avoid. I then have an expression that sets the Excel File Path to a variable that is set by a script task. All this works fine on my development machine, because my original excel file is still at that hard coded path. Upon deploying to my prod server, this package starts throw the error detailed in this thread. Copying the excel file to the server machine so it can be found by the package (even though it is not used) fixed the problem. I do have "Delay Validation" = true, so I don't know a way around this other than to make sure that the package can find a file at the hard coded Excel File Path. Very frustrating indeed >:|