By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,934 Members | 1,527 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,934 IT Pros & Developers. It's quick & easy.

DTS error

P: n/a
Hello, I have been trying to solve this problem for a couple of weeks
now with no progress. I created a package that works when it runs
from my computer but when it runs as a scheduled job, it fails. I
found references to this quite a few times and the responses have
always pointed to permissions, but I am a System Administrator. My
role is Sysadmin. I changed the Windows/NT owner of the job to sa and
that didn't work either. I made sure that the account that runs from
SQL Server has Sysadmin permissions.

The problem I think has to do with the AS400 connection that I make to
pull data out of the AS400 to put into SQL Server 2000. In the
Connection of the package there is a place for User and Password. I
had the person who definitely has all Rumba permissions put his
username and password in there and it came back with the same error.
The Error message is below. I am sure at a loss. Does anyone have
any ideas? I would really appreciate anything. Could this have
anything to do with MDAC?

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: [Wall Data][RUMBA Data Access][RUMBA95]Communication link
failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Wall Data][RUMBA Data Access][RUMBA95]Communication
link failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. 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.
Jul 20 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
ph********@yahoo.com (Rowan) wrote in message news:<4b**************************@posting.google. com>...
Hello, I have been trying to solve this problem for a couple of weeks
now with no progress. I created a package that works when it runs
from my computer but when it runs as a scheduled job, it fails. I
found references to this quite a few times and the responses have
always pointed to permissions, but I am a System Administrator. My
role is Sysadmin. I changed the Windows/NT owner of the job to sa and
that didn't work either. I made sure that the account that runs from
SQL Server has Sysadmin permissions.

The problem I think has to do with the AS400 connection that I make to
pull data out of the AS400 to put into SQL Server 2000. In the
Connection of the package there is a place for User and Password. I
had the person who definitely has all Rumba permissions put his
username and password in there and it came back with the same error.
The Error message is below. I am sure at a loss. Does anyone have
any ideas? I would really appreciate anything. Could this have
anything to do with MDAC?

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: [Wall Data][RUMBA Data Access][RUMBA95]Communication link
failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Wall Data][RUMBA Data Access][RUMBA95]Communication
link failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. 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.


As a complete guess, does the Rumba driver use information stored in
your profile? I recall that the IBM Client Access driver used to do
this - AS/400 connections were defined and stored in each user's
profile, so when a task was scheduled, it failed, because the profile
wasn't available.

Simon
Jul 20 '05 #2

P: n/a
What's your DSN setup look like (for iSeries connection)?
ph********@yahoo.com (Rowan) wrote in message news:<4b**************************@posting.google. com>...
Hello, I have been trying to solve this problem for a couple of weeks
now with no progress. I created a package that works when it runs
from my computer but when it runs as a scheduled job, it fails. I
found references to this quite a few times and the responses have
always pointed to permissions, but I am a System Administrator. My
role is Sysadmin. I changed the Windows/NT owner of the job to sa and
that didn't work either. I made sure that the account that runs from
SQL Server has Sysadmin permissions.

The problem I think has to do with the AS400 connection that I make to
pull data out of the AS400 to put into SQL Server 2000. In the
Connection of the package there is a place for User and Password. I
had the person who definitely has all Rumba permissions put his
username and password in there and it came back with the same error.
The Error message is below. I am sure at a loss. Does anyone have
any ideas? I would really appreciate anything. Could this have
anything to do with MDAC?

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: [Wall Data][RUMBA Data Access][RUMBA95]Communication link
failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Wall Data][RUMBA Data Access][RUMBA95]Communication
link failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. 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.

Jul 20 '05 #3

P: n/a
We are using a NetManage ODBC for AS400/Rumba with TCP/IP enabled. We
have it look directly at the library where we are trying to get the
data from. The connection has been made on the SQL Server box in
control panel. Is that what you mean?

I have literally tried everything I can think of. I am very
frustrated.
ar***********@bigfoot.com (Terence) wrote in message news:<44**************************@posting.google. com>...
What's your DSN setup look like (for iSeries connection)?
ph********@yahoo.com (Rowan) wrote in message news:<4b**************************@posting.google. com>...
Hello, I have been trying to solve this problem for a couple of weeks
now with no progress. I created a package that works when it runs
from my computer but when it runs as a scheduled job, it fails. I
found references to this quite a few times and the responses have
always pointed to permissions, but I am a System Administrator. My
role is Sysadmin. I changed the Windows/NT owner of the job to sa and
that didn't work either. I made sure that the account that runs from
SQL Server has Sysadmin permissions.

The problem I think has to do with the AS400 connection that I make to
pull data out of the AS400 to put into SQL Server 2000. In the
Connection of the package there is a place for User and Password. I
had the person who definitely has all Rumba permissions put his
username and password in there and it came back with the same error.
The Error message is below. I am sure at a loss. Does anyone have
any ideas? I would really appreciate anything. Could this have
anything to do with MDAC?

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: [Wall Data][RUMBA Data Access][RUMBA95]Communication link
failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0 Error Detail
Records: Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: [Wall Data][RUMBA Data Access][RUMBA95]Communication
link failure. APPC Primary RC = Parameter_Check; Secondary RC =
Bad_LU_Alias. 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.

Jul 20 '05 #4

P: n/a
I found a reference to this when searching. It may be of help to you.

http://support.microsoft.com/?kbid=269074

I have a similar problem in that my DTS package runs for me (with sa
privileges) but I can't get it to run as a scheduled task. I've not
found the solution yet, but if I do, I'll post something here in case
it is of use.

Ryan
Jul 20 '05 #5

P: n/a
Thanks. I had read through that article a few times. I appreciate
your help and would love to hear your solution if you find one.
Today, I stopped all the services, changed the sql server account to
System and rebooted hoping that would solve my problem. It did solve
another problem I was having with a catalog failing to populate, but
it did not fix my package problem.

Something I left out is that my scheduled backups run just fine. So I
am wondering, if the problem is with SQL Agent permissions...wouldn't
the scheduled backups not run either? If that is the case, then is it
possible that the connection I am making to the AS400 is somehow not
getting the Username and password I specified in the connection
properties? If that could be the problem, does anybody have any
suggestions on how I might test that or fix it? I can't think of
anything else to try. I am out of ideas.

ry********@hotmail.com (Ryan) wrote in message news:<78**************************@posting.google. com>...
I found a reference to this when searching. It may be of help to you.

http://support.microsoft.com/?kbid=269074

I have a similar problem in that my DTS package runs for me (with sa
privileges) but I can't get it to run as a scheduled task. I've not
found the solution yet, but if I do, I'll post something here in case
it is of use.

Ryan

Jul 20 '05 #6

P: n/a
Well, I finally got it to work today. After reading everything I
could get my hands on I put the right peices together. I had to
first, give the domain user, in our case, domain\Administrator
sysadmin rights in SQL Server. I figured that one out a while ago.
Then I had to go to the Domain Security, User Rights Assigns in Active
Directory. I modified the administrator user rights assignments to
allow it to Act as part of the operating System, Increase Quotas,
Replace a proces level token, Log on as a batch job, and Log on as a
service. To make sure everything was in sync, I stopped all services,
made sure SQL Server's account was that of the
domain\Administrator...made sure that the SQL Server Agent had the
same account, rebooted SQL Server, which restarted all the services,
and voila...my scheduled jobs will now run. Thanks to all who tried
to help. I knew it had to do with permissions, but darned if I could
figure out what to do about it. Maybe this will help someone else.
ph********@yahoo.com (Rowan) wrote in message news:<4b**************************@posting.google. com>...
Thanks. I had read through that article a few times. I appreciate
your help and would love to hear your solution if you find one.
Today, I stopped all the services, changed the sql server account to
System and rebooted hoping that would solve my problem. It did solve
another problem I was having with a catalog failing to populate, but
it did not fix my package problem.

Something I left out is that my scheduled backups run just fine. So I
am wondering, if the problem is with SQL Agent permissions...wouldn't
the scheduled backups not run either? If that is the case, then is it
possible that the connection I am making to the AS400 is somehow not
getting the Username and password I specified in the connection
properties? If that could be the problem, does anybody have any
suggestions on how I might test that or fix it? I can't think of
anything else to try. I am out of ideas.

ry********@hotmail.com (Ryan) wrote in message news:<78**************************@posting.google. com>...
I found a reference to this when searching. It may be of help to you.

http://support.microsoft.com/?kbid=269074

I have a similar problem in that my DTS package runs for me (with sa
privileges) but I can't get it to run as a scheduled task. I've not
found the solution yet, but if I do, I'll post something here in case
it is of use.

Ryan

Jul 20 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.