Solved

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

Posted on 2008-10-21
2
546 Views
Last Modified: 2013-11-30
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

0
Comment
Question by:hispanicteleservices
2 Comments
 
LVL 31

Expert Comment

by:James Murrell
ID: 22767890
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
 

Accepted Solution

by:
hispanicteleservices earned 0 total points
ID: 22820381
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

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Join & Write a Comment

When you hear the word proxy, you may become apprehensive. This article will help you to understand Proxy and when it is useful. Let's talk Proxy for SQL Server. (Not in terms of Internet access.) Typically, you'll run into this type of problem w…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now