RE: 64bit SSIS package calling 32bit SSIS package

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I got it working :)

Used filemon to see what was going on and discovered that my proxy account
was trying to use the temp folder that was owned by the account I run sql
agent under.

I've given it access to this folder and it now works. Very , very weird.
"Mike" wrote:

Hi there, having some issues with the above scenario...

64bit sql 2005 std edition.

A control package is running in 64bit mode to execute a large number of
packages in the correct order (this is parameterised through a config table
so we can turn them on and off and change the order.) As we have a number of
packages using 32bit jet theres also a config value to execute these with the
32bit dtexec instead.

I have a proxy account setup with the required rights onto the network and
associated sql servers.

I can -
Execute the control package from the command line on the server as my proxy
account user with the 64bit dtexec and it runs fine calling both 64bit &
32bit packages with no errors.

I cannot run the same package from a sql agent job as whe nthe control
package calls the 32bit dtexec it comes back with the following error -

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The
AcquireConnection method call to the connection manager
"AgencyNumbersDatabase" failed with error code 0xC0202009. There may be
error messages posted before this with more information on why the
AcquireConnection method call failed.


However if I schedule the offending 32bit package on its own from SQL Agent
it runs just fine.


Now to make matters more interesting if I change the proxy account to be in
the local admininstrators group on the server everything works. THis is the
bit I really dont understand, I cant see what extra rights it should need
running from sql agent as opposed to running from a command line.


Any idess appreciated,

Thanks, Mike.
.

Relevant Pages

  • RE: dts package error
    ... "Donna Lambert" wrote: ... > under the context of the SQL Agent account. ... > account and try to manually kick off the package. ...
    (microsoft.public.sqlserver.dts)
  • Re: Privilege in scheduling packages through sql agent jobs
    ... > How to Run a DTS Package as a Scheduled Job ... >>A programmer can schedule jobs through sql agent and the job step that is ... >>programmer runs the package interactively, ... >>attempts to schedule a package as sql agent job, ...
    (microsoft.public.sqlserver.security)
  • RE: 64bit SSIS package calling 32bit SSIS package
    ... Now tried 32bit end to end from sql agent (so running the control job in ... packages using 32bit jet theres also a config value to execute these with the ... Execute the control package from the command line on the server as my proxy ... I cannot run the same package from a sql agent job as whe nthe control ...
    (microsoft.public.sqlserver.dts)
  • RE: dts package error
    ... under the context of the SQL Agent account. ... account and try to manually kick off the package. ... > When it runs through the scheduler it cannot find the mdb file on the server. ...
    (microsoft.public.sqlserver.dts)
  • Re: Unable to Process Cube on 64bit Server with DTS package
    ... Although I am confused as to how you were able to run the package under your ... interactive account and have it work w/o having AS installed. ... > 2a) Can't do this because Analysis Services is not loaded on this Server ... Let's see if this is a SQL Agent issues or a DSO issue. ...
    (microsoft.public.sqlserver.olap)