MS SQL 2000 (Jobs) recurrent error message (Error = -2147217900 (80040E14))

Hi!

We have 200 - 300 Jobs programmed in MS SQL Server 2000 that run different Data Transformation Services packages at different times of the day -mainly reports.

We've come up with a recurrent error, at least 10 times a day with different jobs.
When looking at the Job History for the error, it goes like this:



Executed as user: [can't tell]\Administrator. .....  
DTSRun OnStart:  DTSStep_DTSExecuteSQLTask_6   DTSRun OnFinish:  DTSStep_DTSExecuteSQLTask_6  
DTSRun OnStart:  DTSStep_DTSExecuteSQLTask_4   DTSRun OnFinish:  DTSStep_DTSExecuteSQLTask_4  
DTSRun OnStart:  DTSStep_DTSActiveScriptTask_2   DTSRun OnFinish:  DTSStep_DTSActiveScriptTask_2  
DTSRun OnStart:  DTSStep_DTSExecuteSQLTask_3   DTSRun OnFinish:  DTSStep_DTSExecuteSQLTask_3  
DTSRun OnStart:  DTSStep_DTSActiveScriptTask_5   DTSRun OnFinish:  DTSStep_DTSActiveScriptTask_5  
DTSRun OnStart:  DTSStep_DTSActiveScriptTask_1   DTSRun OnFinish:  DTSStep_DTSActiveScriptTask_1  
DTSRun OnStart:  DTSStep_DTSActiveScriptTask_3   DTSRun OnFinish:  DTSStep_DTSActiveScriptTask_3  
DTSRun OnStart:  DTSStep_DTSExecuteSQLTask_1   DTSRun OnError:  
DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14)      
Error string:  OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.        
Error source:  Microsoft OLE DB Provider for SQL Server     . The step failed.


We do pass information from SQL Server to Excel files ('Microsoft.Jet.OLEDB.4.0') at some point in our queries.
But, how come it works most of the time, and all sudden reporte failures?

The part of the query we use follows.

Thank you for your help.



--we pass a parameter that tells where the Excel file is "@filepath"
 
declare @DataSource 	varchar(600)
set @DataSource = 'Excel 8.0;HDR=NO;Database='+ @FilePath + ';'
 
 
exec ('
              insert into
              OPENROWSET(''Microsoft.Jet.OLEDB.4.0'',''' + @DataSource + ''', ''SELECT * FROM [Sheet1$A4:L4]'')
              select *
              from   dbo.temp_Table
')

Open in new window

hispanicteleservicesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

James MurrellProduct SpecialistCommented:
This error means... if you try to insert/update a column that does not allow NULL values, with NULL (e.g. by hard-coding NULL into the statement, or by leaving a column - that does not have a default value defined - out of the INSERT list).
0
hispanicteleservicesAuthor Commented:
We appreciate the attemp.
I have no doubt Error -2147217900 (80040E14)      would be, under most circumstances, caused by what's been stated.
However, this was more of a traffic problem. we just had too much Jobs traffic. After moving some really heavy tasks to other schedules, the Jobs didn't fail anymore.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.