May 31, 2006 at 9:06 am
If I run the packages it works fine but I have an schedule and it sent me the next error.
Executed as user: POSWINSOC\SYSTEM. ...cuting... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnError: DTSStep_DTSExecuteSQLTask_1, Error = -2147217873 (80040E2F) Error string: The statement has been terminated. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217873 (80040E2F); Provider Error: 3621 (E25) Error string: The statement has been terminated. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217873 (80040E2F); Provider Error: 515 (203) Error string: Cannot insert the value NULL into column 'nomEmple', table 'bdValeE.dbo.tbSaldos'; column does not allow nulls. INSERT fails. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.What I am doing wrong or exist a better way to do a Job that runs a sp every day at 2:00 am.
Thanks
May 31, 2006 at 9:27 am
I don't think the error has anything to do with running the package in a job. Here's the problem:
"Error string: Cannot insert the value NULL into column 'nomEmple', table 'bdValeE.dbo.tbSaldos'; column does not allow nulls."
You tried to insert a NULL value into a column that doesn't allow nulls. Check the data you're importing.
From what you've posted, it looks like the job has a step that runs the DTS package. There's no stored procedure (SP) involved. Running the package in a job is the best way to schedule it for a particular time.
Greg
Greg
May 31, 2006 at 9:28 am
More than likely you're problem lies here...
"Cannot insert the value NULL into column 'nomEmple', table 'bdValeE.dbo.tbSaldos'; column does not allow nulls. "
What is different about the data when you attempt to schedule it a 0200? Does the data you are expecting truly exist?
May 31, 2006 at 6:36 pm
Thanks!
Today we are lauching a new proyect and yesterday we erase one table that is the one that have the nomEmple information, but we were so nervous that we didn't see that the error was so obvious.
June 1, 2006 at 6:15 am
Yeah, Sometimes it just helps to have another set of eyes take a look at something. I have a freind that routinely makes things more complicated than they have to be, but then ago he's a PM, and from what I've seen that kinda goes with the territory.
-Luke.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply