September 17, 2009 at 4:38 pm
Hi,
Am trying to schedule a package that contains an excel connection manager on a 64 bit clustered install of MS SQL 2005.
I had my server guys look at http://msdn.microsoft.com/en-us/library/ms141766.aspx and hopefully install the 32 bit tools on the machine(s) the other day.
I run the operating system command as a step in the job:
dtexec.exe /DTS "\MSDB\packagename" /SERVER myservername /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
but it errors with:
Executed as user: domain\username. ...00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:19:08 AM Info: 2009-09-18 08:19:09.29 Code: 0x4004300A Source: Import xls DTS.Pipeline Description: Validation phase is beginning. End Info Progress: 2009-09-18 08:19:09.29 Source: Import xls Validating: 0% complete End Progress Progress: 2009-09-18 08:19:09.56 Source: Import xls Validating: 50% complete End Progress Error: 2009-09-18 08:19:09.71 Code: 0xC0202009 Source: packagename Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2009-09-18 08:19:09.71 Code: 0xC020801C Source: Import xls source excel file [1] Descrip... Process Exit Code 1. The step failed.
So I suspect something is still not quite right.
Do you have any advice on how to check the install and any tips on what to do next?
September 17, 2009 at 4:53 pm
Your install is almost certainly fine, your problem is very clear, and is well known..
It all becomes clear right here:
Executed as user: domain\username. ...00.3042.00 for 64-bit
You are trying to run the package with the 64-bit executable, at current THIS WILL NEVER SUCCEED.
There are no 64-bit Excel drivers.
The next question is, ok, what do I do..
The answer, although not elegant is very simple. Find the path to the 32-bit version of DTExec.exe, it will be up the C:\Program Files (x86)\ path somewhere..
In your Agent job you specify Operating System command, and fill out the whole command line starting with the path you just found followed by "\DTExec.exe " and the rest of your command line.
You cannot execute it using the SSIS option in SQL Agent.
CEWII
September 20, 2009 at 5:51 pm
Full path was required:
"c:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /DTS "\MSDB\packagename" /SERVER servername /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V
thanks!
September 21, 2009 at 8:31 am
You are very welcome..
CEWII
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply