Hi Folks, I am getting this strange error while scheduling a DTS.
What I am trying to do is copy data from DB2 on mainframe to a SQL
server table. I created the DTS package and runs fine manually. But
when I schedule it, I get this error :

Executed as user: MYDOMAIN/SQLADMIN. 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 = -2147217900 (80040E14) Error string: Internal NetLib
Error Error source: Microsoft DB2 OLE DB Provider Help file:
Help context: 0 Error Detail Records: Error:
-2147217900 (80040E14); Provider Error: 0 (0) Error string:
Internal NetLib Error Error source: Microsoft DB2 OLE DB Provider
Help file: Help context: 0 DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1 DTSRun: Package execution complete.
Process Exit Code 1. The step failed.



Here are the steps I did :

1. I created a Domain account SQLADMIN
2. I added the domain/SQLADMIN to Admin group in the server.
3. I used domain/sqladmin to start SQLserver service and sqlagent
service
4. I added domain/sqladmin to SYSADIM role
5. I logged on the server as domain/sqladmin
6. I created a DTS package : It deletes rows from local table and then
copies data from DB2 on mainframe to sqlserver.
7. I executed the package, it runs fine
8. When I schedule it as a job. I get the above error

I cannot figure it out. BUT.....when I change the service accounts to
Local systems, then it works fine. Now I have no idea why that works.
!!
I scheduled a backup using domain/sqladmin...that works fine too. The
DTS is not working.


Could anybody please help me

TIA

It is almost certainly permission related and is maybe something to do with
the fact that the drivers cannot be seen by that account.

Here is an article to read

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

And also. If the job is owned by a sysadmin then log in as the SQL Server
Agent account on the server itself and try to execute the package locally.


Still work?



--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"sql rookie" <anytasks (AT) gmail (DOT) com> wrote

The error indicates that it is a Network Library error . .
also the fact that the Local System Account works but not the
domain account you created. this appears to be a symptom of the SSPI context
error
and the reason why the local system works is because the NamedPipes netlib
is being used instead of TCPIP netlib. You have 1 of 2 choices I think,

1) is to create a client connection(using client network utility on the
server) using NamedPipes - this will ensure that NamedPipes is used instead
of TCPIP, however this is just a work around

OR

2) investigate the permissions necessary on for the domain account(sqlserver
service account) to be able to create an SPN on the network. . .(search the
KB for 'SSPI connext' )

one of the permissions necessary for the sqlserver and sqlserveragent
account is 'impersonate authenticated users' - something like that and then
restart sqlserver services. then try the DTS through the sqlserveragent
schedule.



"sql rookie" <anytasks (AT) gmail (DOT) com> wrote

set the owner as the sqladmin login or create a sqljobs sql server login
with sysadmin and use it as the owner of the job.

"sql rookie" <anytasks (AT) gmail (DOT) com> wrote