April 23, 2009 at 4:41 am
Hi, I'm relatively new to SSIS but have managed to create a package that does what I need OK. I have it sitting as a file on the same server as SQL is running on, and when I run it in SSIS Studio it runs fine.
Running the same package in dtexec using the /F parameter gives me a large 0800470C8 error where it suggests all sorts of column names are not synchronised. They are properly mapped in the package as far as I can see, but if I rename them the problem will go away (I tried this on a small table, but not yet on the larger one). Also the package fails when run within SQL server but I guess this uses dtexec anyway?
Any suggestions before I give up my weekend to rename 16 columns and search and replace loads of code!?
April 23, 2009 at 8:25 am
when you say runs in sql I am assuming you are running via the agent. In which case it's probably an issue of the agent security level with the file / databases you are using.
I suggest you create a credential with the authority needed to all resources used by the package then create a proxy for SSIS package execution then set the job to Run As the proxy.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply