 |
|
|
|
Next: Which Column Has the Data?
|
| Author |
Message |
External
Since: Aug 15, 2006
Posts: 1
|
(Msg. 1) Posted: Wed Jan 24, 2007 8:19 am
Post subject: intermittant OLEDB query failure
Archived from groups: microsoft>public>sqlserver>programming (more info?)
|
|
|
I have the following query that I'm using to update pricing from a
spreadsheet to a MS SQL(1005) DB Table as we prepare to move to a new
quoting system.
UPDATE DT
SET [BasePrice] = ST.RawPrice
,[BaseCost] = ST.RawCost
from [MIPreStain].[dbo].[Products] DT inner join
(Select * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\DevProjects\QuotePrep\pricing.xls;HDR=YES',
'SELECT * FROM [Products$]')) ST on DT.PInventoryID = ST.InventoryCode
I'm currently using this with everything (DB & excel files) on my local
machine while I'm prepping for deployment. Usually, it works fine but
maybe every 3rd or 4th time it fails with the following error.
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server
"(null)" reported an error. The provider did not give any information
about the error.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider
"Microsoft.Jet.OLEDB.4.0" for linked server "(null)"."
I am on the same PC, same everything, I can't seem to isolate the
problem. Any suggestions? |
|
| Back to top |
|
 | |
External
Since: Jan 04, 2007
Posts: 143
|
(Msg. 2) Posted: Wed Jan 24, 2007 9:18 am
Post subject: Re: intermittant OLEDB query failure [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Debralous,
Make sure you don't have the spreadsheet open in Excel. That's all I can
think of.
-- Bill
"Debralous" wrote in message
>I have the following query that I'm using to update pricing from a
> spreadsheet to a MS SQL(1005) DB Table as we prepare to move to a new
> quoting system.
>
> UPDATE DT
> SET [BasePrice] = ST.RawPrice
> ,[BaseCost] = ST.RawCost
> from [MIPreStain].[dbo].[Products] DT inner join
> (Select * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\DevProjects\QuotePrep\pricing.xls;HDR=YES',
> 'SELECT * FROM [Products$]')) ST on DT.PInventoryID = ST.InventoryCode
>
>
> I'm currently using this with everything (DB & excel files) on my local
> machine while I'm prepping for deployment. Usually, it works fine but
> maybe every 3rd or 4th time it fails with the following error.
>
> "Msg 7399, Level 16, State 1, Line 1
> The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server
> "(null)" reported an error. The provider did not give any information
> about the error.
> Msg 7303, Level 16, State 1, Line 1
> Cannot initialize the data source object of OLE DB provider
> "Microsoft.Jet.OLEDB.4.0" for linked server "(null)"."
>
> I am on the same PC, same everything, I can't seem to isolate the
> problem. Any suggestions?
> |
|
| Back to top |
|
| |
External
Since: Apr 02, 2007
Posts: 1
|
(Msg. 3) Posted: Tue Feb 13, 2007 1:31 pm
Post subject: Re: intermittant OLEDB query failure [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Debralous,
did you ever get this resolved? if so, what was the solution? I am trying
to import a ss into a sql table via the query analyzer and I keep getting
this error:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
Can anyone help me?
Thanks!
SA
"AlterEgo" wrote:
> Debralous,
>
> Make sure you don't have the spreadsheet open in Excel. That's all I can
> think of.
>
> -- Bill
>
>
> "Debralous" wrote in message
>
> >I have the following query that I'm using to update pricing from a
> > spreadsheet to a MS SQL(1005) DB Table as we prepare to move to a new
> > quoting system.
> >
> > UPDATE DT
> > SET [BasePrice] = ST.RawPrice
> > ,[BaseCost] = ST.RawCost
> > from [MIPreStain].[dbo].[Products] DT inner join
> > (Select * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> > 'Excel 8.0;Database=C:\DevProjects\QuotePrep\pricing.xls;HDR=YES',
> > 'SELECT * FROM [Products$]')) ST on DT.PInventoryID = ST.InventoryCode
> >
> >
> > I'm currently using this with everything (DB & excel files) on my local
> > machine while I'm prepping for deployment. Usually, it works fine but
> > maybe every 3rd or 4th time it fails with the following error.
> >
> > "Msg 7399, Level 16, State 1, Line 1
> > The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server
> > "(null)" reported an error. The provider did not give any information
> > about the error.
> > Msg 7303, Level 16, State 1, Line 1
> > Cannot initialize the data source object of OLE DB provider
> > "Microsoft.Jet.OLEDB.4.0" for linked server "(null)"."
> >
> > I am on the same PC, same everything, I can't seem to isolate the
> > problem. Any suggestions?
> >
>
>
> >> Stay informed about: intermittant OLEDB query failure |
|
| Back to top |
|
| |
External
Since: Feb 26, 2007
Posts: 1
|
(Msg. 4) Posted: Mon Feb 26, 2007 6:04 am
Post subject: Re: intermittant OLEDB query failure [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I'm getting the same error trying to access an Access MDB file using;
select * from openrowset('Microsoft.Jet.OLEDB.4.0', '\\server
\database.mdb';'admin';'','SELECT TOP * FROM TABLE')
The error message I receive is;
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)"
returned message "Unspecified error".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider
"Microsoft.Jet.OLEDB.4.0" for linked server "(null)".
The server is;
Windows Server 2003 R2
SQL Server 2005 SP1
If anyone else has run across this, I'd love to know what the
resolution is.
Thanks!
Alex Kinsella >> Stay informed about: intermittant OLEDB query failure |
|
| Back to top |
|
| |
External
Since: Feb 18, 2009
Posts: 1
|
(Msg. 5) Posted: Wed Feb 18, 2009 7:25 am
Post subject: RE: intermittant OLEDB query failure [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
while upload the data from excel to sql server i am getting the below error
"The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. The provider did not give any information about the error. Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)". "
can you help me in this?what is the solution for this?
From http://www.google.se/search?hl=sv&q=solution+for+the+error,The+OLE+DB+provider+"Microsoft.Jet.OLEDB.4.0"+for+linked+server+"(null)"+reported+an+error.+The+provider+did+not+give+any+information+about+the+error.+Cannot+initialize+the+data+source+object+of+OLE+DB+provider+"Microsoft.Jet.OLEDB.4.0"+for+linked+server+"(null)".+Source:+.Net+SqlClient+Data+Provider+String+value:+System.Data.SqlClient.SqlException:.&meta=
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/ >> Stay informed about: intermittant OLEDB query failure |
|
| Back to top |
|
| |
| Related Topics: | problem using oledb + informix - Hi all. I have a problem writing a table on informix (IDS 10.0) using a linked server on SqlServer Express: This is the insert: INSERT INTO unixdb1.practor.informix.ven_rilcld (rilcld_rilcld,rilcld_entazi, rilcld_numter, rilcld_codbar, rilcld_qta, ..
openrowset and jet.oledb - Please help, since the introduction of SQL2005 the default mode for opening access mdb databases with Openrowset appears to be in exclusive open mode I wish to open the database in share mode so the other (non net) ADO threads can open the database at....
Microsoft.Jet.OLEDB.4.0 - Error - Hi, I am using SQL Server 2005 (SP1) on Windows Server 2003 EE (SP1). I get following error while accessing Excel or Text file data sources with OPENROWSET or OpenDataSource and Microsoft.Jet.OLEDB.4.0: From SQLAgent Job Log file: Cannot initialize....
Need a deadly row lock through oledb - Hi, I might have asked this before, but since SQL 2005 was there, MS strongly modified locking in favor of scalability. I never got an answer that solved the problem. I have an app that really needs to lock a certain row to be locked so that other..
Launching oracle jobs from oledb - perhaps the wrong group, but I suspect somebody here has tried it... Greetings. I have a vb.net oledb procedure that can schedules an oracle procedure to run and returns to me an oracle job number. It looks like this: FUNCTION CPM_SUBMIT (iprocname i... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
