September 19, 2007 at 5:50 pm
Let me throw in my 2 cents on the solution to this problem...since I have been spending a few days trying to solve it.
Basically, the problem that others are having (as well as the problem I was having) is that I was not DEPLOYING the completed project. Follow the directions in the guide here (http://www.mssqltips.com/tip.asp?tip=1024) and it will show you what is missing.
Using this method, I was able to succesfully get this to work WITHOUT all of the mumbo-jumbo suggestions offerered above. Basically, it was about 10 steps that I had failed to do. And I was receiving the identical errors as above. It would save the the "c:\....|tmp" file could not be found the next day. It would always work the FIRST time....but the next day.....would never work.
In fact, I was so happy when this worked, I actually took the time to return to this guide to post this entry (which is usually unlike me). Apparently, the Lord really blessed me with a great solution to my problem. The irony is that in my 1000+ SQL 2005 book...I cannot remember the Chapter that described the "Package Installation Wizard". Oh, well. Apparently the editor just knew a lot of stuff...and had never really had to go out and make it work.
Good luck all.
C.J.
September 19, 2007 at 6:04 pm
You'd be suprised how many people actually dom't know about deploying packages, i've seen a lot of people put 'production' packages out there and require the end user to execute these via BIDS. I hate to point it out but you could have read the same info from the BOL, simply googling SSIS package deploy would have returned it in the first it or two (http://msdn2.microsoft.com/en-us/library/ms365338.aspx 
Steve.
September 20, 2007 at 6:34 pm
I found this link in your link which most people may not understand so Microsoft support create the link I posted as a short version of it.
http://msdn2.microsoft.com/en-us/library/ms162810.aspx
Kind regards,
Gift Peddie
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply