dbTalk Databases Forums  

Package fails when run from Sql Server Agent

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Package fails when run from Sql Server Agent in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Rlane
 
Posts: n/a

Default Package fails when run from Sql Server Agent - 12-07-2004 , 04:18 PM






I have a stored procedure that createz a DTS package on the fly using
the sp_OA... stored procs. The procedure copies data from a Sql table
into an Access .mdb file.

When the procedure is executed in a Sql Server Agent step, it inserts
rows into the Access file, but fails before finishing.
The logfile states that

Step error description : The number of failing rows exceeds the maximum
specified. (which is zero)
Step error code : 8004206A

Running the DTS package any other way succeeds (I save the package to a
structured storage file before it gets executed so that I can run it
other ways).

What would cause some rows to fail when using Sql Server Agent?
There's only one source table for all of teh data, so security is not
the issue.

Any clues?


Reply With Quote
  #2  
Old   
Mohamed Sharaf
 
Posts: n/a

Default RE: Package fails when run from Sql Server Agent - 12-08-2004 , 04:28 AM






I think you need to check the identity of the SQL Server Agent (by opening
SQL Server Agent properties) and change the identity with user that have
access on both the SQL server table (inside the database) and the MDB file
(file system)
HTH.

Regards,
Mohamed Sharaf
MEA Developer Support Center
ITWorx on behalf Microsoft EMEA GTSC


Reply With Quote
  #3  
Old   
rmathuln@pacbell.net
 
Posts: n/a

Default RE: Package fails when run from Sql Server Agent - 12-08-2004 , 06:55 AM



If that was the cause, the process wouldn't even start.

It always stops at the same number of rows inserted into the Access table.

In fact, I setup another process that uses a Sql server table that is structurally an identical twin but contains data from a prior month.

The second process also fails at exactly the same record number.

I changed the destination of the Access table to a destination on the local Sql Server box, get the same behavior.

I added more columns to the process, which meant the disk size of the Access table was larger, and the process stopped at the same point, so size limitations are not an issue.



nntp://msnews.microsoft.com/microsoft.public.sqlserver.dts/<GXL51CR3EHA.3200 (AT) cpmsftngxa10 (DOT) phx.gbl>

I think you need to check the identity of the SQL Server Agent (by opening
SQL Server Agent properties) and change the identity with user that have
access on both the SQL server table (inside the database) and the MDB file
(file system)
HTH.

Regards,
Mohamed Sharaf
MEA Developer Support Center
ITWorx on behalf Microsoft EMEA GTSC


[microsoft.public.sqlserver.dts]



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.