Can anyone throw any light on why I'm getting the following error...

Step Error Source: Microsoft OLE DB Provider for ODBC Drivers
Step Error Description:[Microsoft][ODBC Driver Manager] Driver's
SQLAllocHandle on SQL_HANDLE_ENV failed
Step Error code: 80004005

here's the setup.....:
I have a DTS package that connects to an Oracle server and retrieves
data (using an Oracle ODBC connection)
I can run the package manually and it works fine
If I run the package through a SQL Agent Job, I get the above error
(either scheduled or manually)
I have all the neccessary Oracle drivers/client/Net8 etc. installed and
the Path environment variables seem to be set correctly also.

I suspect it's somerthing to do with the user account that the job is
running under? this is a domain Admin account with full access rights to
both the SQL Server and the Oracle Server.

Any ideas?

Brian

still can't resolve this issue, anyone any ideas????

desperate


"Brian" <bfordSPAMOFF (AT) markem (DOT) com> wrote

Not sure if this will help, but it may have something to do with agent
account not having the proper path to the Oracle dll's. If it runs OK
for you, but not for the agent, that may be a good place to start. What
account is the package being run under for the job?

I found this on the web
http://www.easysoft.com/products/999...0&product=2002


Simon Worth

Brian wrote:

Simon,

Thanks for your input, thankfuly I managed to solve the issue, here's how
for your info:

The problem lies with the security that is set on the oracle home folder,
can't remember the URL where I found the solution but here's what to do:

- you need to right click the oracle home folder and select 'Properties'
from there click the 'Security' tab
- highlight 'Authenticated Users' in the top list
- 'Un-check' and then 'Re-check' the 'Read & Execute' item in the bottom
list
- click 'Apply' then 'OK' to exit
- You MUST then re-boot the machine

Everything should be fine after that.

Brian

"Simon Worth" <REMOVEFIRST_simon.worth (AT) gmail (DOT) com> wrote

I experienced the same problem. I stopped/started the SQL Agent instead
of rebooting the box and this resolved the problem.

Zep
Brian wrote: