Data Download via ODBC

Server is SQL 2000 SP4. We are trying to pull some data from a Progress 9.1d
server via ODBC. If I go to the local packages, open the package in question
and execute it, everything runs fine and it gets the data. If I try and run
the job manually from the job list in the SQL server agent, it fails with
the following error showing in the job history:
Executed as user: <service account>. DTSRun: Loading... DTSRun:
Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun
OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1,
Error = -2147467259 (80004005) Error string: Specified driver could
not be loaded due to system error 126 (MERANT 3.60 32-BIT Progress SQL92
v9.1D). Error source: Microsoft OLE DB Provider for ODBC Drivers
Help file: Help context: 0 Error Detail Records:
Error: -2147467259 (80004005); Provider Error: 160 (A0) Error
string: Specified driver could not be loaded due to system error 126
(MERANT 3.60 32-BIT Progress SQL92 v9.1D). Error source: Microsoft OLE
DB Provider for ODBC Drivers Help file: Help context: 0
DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution
complete. Process Exit Code 1. The step failed.
All I've been able to find about the error code 126 is the ODBC driver and
error -2147467259 seems to indicate a problem with the ODBC driver. But if
the driver was the problem, I don't understand why it only fails when run as
a SQL server agent job. I tried changing the service account to an admin
account instead, but it didn't make a difference.
Not sure where else to turn, so I'm hoping some people here might have some
ideas.
Thanks
Brian
First, when you execute a package manually it runs from your
PC and under your security context. When you schedule it as
a job, it runs on the server and under the security context
of the Agent service account if the job is owned by a
sysadmin (otherwise it executes under the proxy account
security context).
Did you install the Merant drivers on the server? Error 126
is "Module could not be found" and the other error you are
getting is for unable to load driver. Looks like all the
needed pieces may not be installed, setup on the server -
only on your PC.
-Sue
On Mon, 26 Feb 2007 16:23:15 -0500, "Brian"
<wouldntulike2know> wrote:

>Server is SQL 2000 SP4. We are trying to pull some data from a Progress 9.1d
>server via ODBC. If I go to the local packages, open the package in question
>and execute it, everything runs fine and it gets the data. If I try and run
>the job manually from the job list in the SQL server agent, it fails with
>the following error showing in the job history:
>Executed as user: <service account>. DTSRun: Loading... DTSRun:
>Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun
>OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart:
>DTSStep_DTSDataPumpTask_1 DTSRun OnError: DTSStep_DTSDataPumpTask_1,
>Error = -2147467259 (80004005) Error string: Specified driver could
>not be loaded due to system error 126 (MERANT 3.60 32-BIT Progress SQL92
>v9.1D). Error source: Microsoft OLE DB Provider for ODBC Drivers
>Help file: Help context: 0 Error Detail Records:
> Error: -2147467259 (80004005); Provider Error: 160 (A0) Error
>string: Specified driver could not be loaded due to system error 126
>(MERANT 3.60 32-BIT Progress SQL92 v9.1D). Error source: Microsoft OLE
>DB Provider for ODBC Drivers Help file: Help context: 0
>DTSRun OnFinish: DTSStep_DTSDataPumpTask_1 DTSRun: Package execution
>complete. Process Exit Code 1. The step failed.
>All I've been able to find about the error code 126 is the ODBC driver and
>error -2147467259 seems to indicate a problem with the ODBC driver. But if
>the driver was the problem, I don't understand why it only fails when run as
>a SQL server agent job. I tried changing the service account to an admin
>account instead, but it didn't make a difference.
>Not sure where else to turn, so I'm hoping some people here might have some
>ideas.
>Thanks
>Brian
>
|||"Sue Hoegemeier" <Sue_H@.nomail.please> wrote
> First, when you execute a package manually it runs from your
> PC and under your security context.
Sorry I wasn't clear. Everything I am trying is on the server.

> Did you install the Merant drivers on the server?
Yes. They test and work correctly when I execute the package, but not when I
run the job logged on with the same authority. I also tried using the
service account authority and that didn't work either.
|||Try logging onto the server using the service account that
SQL agent runs under. While logged in using this account,
install the Merant drivers.
And it never hurts to run Component checker to make sure the
MDAC installation is correct. You can download the tool
from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 27 Feb 2007 09:47:50 -0500, "Brian"
<wouldntulike2know> wrote:

>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote
>Sorry I wasn't clear. Everything I am trying is on the server.
>
>Yes. They test and work correctly when I execute the package, but not when I
>run the job logged on with the same authority. I also tried using the
>service account authority and that didn't work either.
>

Dangerous Bug in SSIS?

Hi,

I recently seemed to have found a major bug in SSIS packages...
Well i was just showing the new SSIS to a few work collegues when i suddenly decided to show how cool it was to be able to minimize and maximize tasks containers.

Well the bug just showed up when i maximized the container again and there it was... the Conditional precedences where gone... no more visible..

Everyone is experiencing the same problem? Solutions?
Best Regards,
Luis Sim?es

Luis,
If you try and recreate the constraints it won't let you because it says the constraints already exist.

So yes, there is a bug - but I would hardly call it major. It doesn't stop the package from running successfully.

Log it at the feedback centre: http://lab.msdn.microsoft.com/productfeedback/default.aspx

-Jamie

|||And how do i change the conditions now?

The precedences are invisible... that's bad... What if someone else must use the package?

Best Regards,|||

I had the same issue with tasks inside a sequence container. The workflow arrows appeared to be missing, but they were still there, just invisible. I got them to reappear by minimizing and then expanding the sequence container.

Not a dangerous bug, just an annoying one.

Dangerous Bug in SSIS?

Hi,

I recently seemed to have found a major bug in SSIS packages...
Well i was just showing the new SSIS to a few work collegues when i suddenly decided to show how cool it was to be able to minimize and maximize tasks containers.

Well the bug just showed up when i maximized the container again and there it was... the Conditional precedences where gone... no more visible..

Everyone is experiencing the same problem? Solutions?
Best Regards,
Luis Sim?es

Luis,
If you try and recreate the constraints it won't let you because it says the constraints already exist.

So yes, there is a bug - but I would hardly call it major. It doesn't stop the package from running successfully.

Log it at the feedback centre: http://lab.msdn.microsoft.com/productfeedback/default.aspx

-Jamie

|||And how do i change the conditions now?

The precedences are invisible... that's bad... What if someone else must use the package?

Best Regards,|||

I had the same issue with tasks inside a sequence container. The workflow arrows appeared to be missing, but they were still there, just invisible. I got them to reappear by minimizing and then expanding the sequence container.

Not a dangerous bug, just an annoying one.

Dangerous Bug in SSIS?

Hi,

I recently seemed to have found a major bug in SSIS packages...
Well i was just showing the new SSIS to a few work collegues when i suddenly decided to show how cool it was to be able to minimize and maximize tasks containers.

Well the bug just showed up when i maximized the container again and there it was... the Conditional precedences where gone... no more visible..

Everyone is experiencing the same problem? Solutions?
Best Regards,
Luis Sim?es

Luis,
If you try and recreate the constraints it won't let you because it says the constraints already exist.

So yes, there is a bug - but I would hardly call it major. It doesn't stop the package from running successfully.

Log it at the feedback centre: http://lab.msdn.microsoft.com/productfeedback/default.aspx

-Jamie

|||And how do i change the conditions now?

The precedences are invisible... that's bad... What if someone else must use the package?

Best Regards,|||

I had the same issue with tasks inside a sequence container. The workflow arrows appeared to be missing, but they were still there, just invisible. I got them to reappear by minimizing and then expanding the sequence container.

Not a dangerous bug, just an annoying one.

Cutting & Pasting Tasks

Has anyone else experienced serious pain when cutting and pasting tasks between packages? In that, the default way SSIS lays out the tasks is absolutely atrocious (things on top of each other, way to far apart from each other, boxes sized to small, etc.) Is there some trickery I need to do to get it to retain the layout and formatting when I paste?
Its rubbish isn't it? I also hate the way auto-format can sometimes produce a worse layout than what you started with and there's no way of CTRL-Z-ing it.

Sorry, that's not very constructive is it? I've fed this back to MS and am hoping its on their list of things for Vnext.

For the time being Greg, I think you're stuck with it.

-Jamie

P.S. CTRL-Z is something I'd like to see across the board but I dare say you need Visual Studio hooks in order to do this - so its a VS problem!