August 19, 2008 at 4:00 am
I am reading from an excel spreadsheet into a SQL server table and this is working fine locally however when I put the package into a job on our test server the following error is being displayed. I am successfully reading from a text file in the same location, the problem seems to be isolated to reading from an excel spreadsheet.
Validating: 25% complete End Progress Progress: 2008-08-19 04:57:22.51 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 50% complete End Progress Progress: 2008-08-19 04:57:22.52 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 75% complete End Progress Error: 2008-08-19 04:57:22.52 Code: 0xC0202009 Source: Exclusions_Step Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Databa... The package execution fa... The step failed.
Thanks
August 19, 2008 at 4:39 am
Is your test server 64 bit?
JET does not work with 64 bit.
Can the test server see the xls file?
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 19, 2008 at 10:02 am
The test server has a 32 bit processor, so JET Compatabile.
The excel file is sitting on another server but I am able to read text files from the server so isolated to excel files.
August 19, 2008 at 10:05 am
Odd. What was the full error message? The above seems truncated.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 19, 2008 at 10:09 am
Here is the full error....please excuse the aaaaa\aaaa this has replaced the true user..
Executed as user: aaaaaa\aaaaaaaa. ...3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:38:39 AM Progress: 2008-08-19 09:39:25.29 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 0% complete End Progress Progress: 2008-08-19 09:39:25.30 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 25% complete End Progress Progress: 2008-08-19 09:39:25.30 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 50% complete End Progress Progress: 2008-08-19 09:39:25.32 Source: Insert terminates into UPT_EXCLUDED_USERS Validating: 75% complete End Progress Error: 2008-08-19 09:39:25.32 Code: 0xC0202009 Source: Exclusions_Step Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Databa... The package execution fa... The step failed.
August 20, 2008 at 7:26 am
Hi,
I'm having a similar problem with the exact same error on a clustered config where the .xls file is local. Our set up is running full 64-bit (OS, processors, and SQL Server 05 version). So you're saying JET cannot function under those conditions? Is there a way around it? It seems odd that Management Studio can't use the Excel Source in an enterprise environment like that. Any information or recommendations would be greatly appreciated!
Thanks!
August 20, 2008 at 7:37 am
Yes - JET does not function under 64 bit. You have to use 32.
@ lke2v - The vital bit of the message is gone. The last bit where it says "Microsoft Jet....."
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 20, 2008 at 7:41 am
Indeed it is. I am now trying to run the package using Operating system and the dtsrun within the SQL Server Agent, I am finding debugging with the SQL Server Intergration Service Package almost impossible. I will keep you posted.
August 20, 2008 at 7:43 am
If you change the property, it will run 32bit in bids.
The full path to 32bit dtexec in agent will force a 32bit execution as well.
Keep us posted.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 21, 2008 at 6:44 am
Just in case anyone else was having the same problem I was encountering:
I was getting the same error while running an SSIS package that imports from an Excel spreadsheet on clustered, 64-bit edition of Windows Server 2003. I ran the package successfully by switching the runtime processing for the project in Visual Studio. If you highlight the project, right-click it, go to Properties > Debugging > Run64BitRuntime and change it to 'False' it should allow the import to run using JET.
August 21, 2008 at 7:19 pm
Hi,
Make sure you should have one excel temp file your source folder. I also face the problem. i created one temp file in source folder and created a run which should run using commend line execution mode.
Thnaks
SsiS
August 22, 2008 at 2:40 am
Hi I get the following error
DTSRun: Loading... Error: -2147467259 (80004005); Provider Error: 14 (E) Error string: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.
when I use the command
DTSRUN /SServerName\Instance /E /NPackageName
Can you see any problems with the syntax?
Thanks in advance
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply