Were you able to solve your problem of "Cannot create ActiveX component" by SSIS SQL Agent Job?
> On Tuesday, June 26, 2007 10:21 AM Ben wrote:
> Hi All
> We have a custom SSIS component in one of our packages which basically acts
> as a wrapper for an ActiveX application. As part of production, this is run
> from SQL Agent using the built in account. However, in test, we need to be
> able to run this from a different user account.
>
> The problem we're having is that each time we run the package from SQL Agent
> using the test account, we get an error "System.Exception: Cannot create
> ActiveX component".
> We're guessing that this is down to being unable to run the component due to
> permissions.
>
> We've tried to enable the Active X Jobs step for that user, but that didn't
> seem to help. Is there an OS level right that needs to be set?
>
> The account that is running the jobs is a proxy to an Domain account - I
> don't fully understand how, but it seems to allow us to run any jobs that
> don't include this wrapper component.
>
> Any thoughts?
>
> Cheers
>
> BenK
>> Stay informed about: Active X Component in SSIS Running from SQL Agent - User R..