February 13, 2013 at 8:38 am
Hello.
I have an issue that has consumed a lot of my time to date, so I've turned to the SSC community.
I have a dtsx package that quite simply uses a DB table as a data source, does a quick conversion of ASCII strings to unicode strings and outputs to an Excel document on a local share.
I am able to run this package from BIDS and I have no issues at all, however when attempting to execute the package from the server, I get the following error stack:
Error: 2013-02-13 15:12:00.64
Code: 0xC0202009
Source: Extract Workstation data for Excel document Excel Destination [1020]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80040E37.
End Error
Error: 2013-02-13 15:12:00.65
Code: 0xC02020E8
Source: Extract Workstation data for Excel document Excel Destination [1020]
Description: Opening a rowset for "Excel Destination" failed. Check that the
object exists in the database.
End Error
Error: 2013-02-13 15:12:00.68
Code: 0xC004706B
Source: Extract Workstation data for Excel document DTS.Pipeline
Description: "component "Excel Destination" (1020)" failed validation and ret
urned validation status "VS_ISBROKEN".
End Error
Progress: 2013-02-13 15:12:00.68
Source: Extract Workstation data for Excel document
Validating: 100% complete
End Progress
Error: 2013-02-13 15:12:00.69
Code: 0xC004700C
Source: Extract Workstation data for Excel document DTS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2013-02-13 15:12:00.69
Code: 0xC0024107
Source: Extract Workstation data for Excel document
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 15:11:59
Finished: 15:12:00
Elapsed: 1.467 seconds
I feel I must add that I am running a 32bit version of SQL Server 2005 on a 64bit edition of Windows Server 2008 R2. I attempted to run the package using the 32bit version of dtexec. SQL Server is at version 9.0.5069 (SP4).
If anyone could offer some advice, I'd be very grateful. I have a funny feeling that my issue may be 64/32 bit related.
February 13, 2013 at 3:37 pm
The info you provided about bitness sounds OK.
From the error I am wondering about the existence of the destination Excel file. Does it exist in the prod environment at the destination? How is it being created at runtime? SSIS will not create an Excel file on the fly by default. Maybe you have the file sitting there on your machine and it's working for testing but there is no provision to stage a file in prod to accept the data during each execution?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 14, 2013 at 2:04 am
Hi opc.three and thanks for your reply.
The file won't exist at the point this package is ran. The job that will eventually invoke this package, deletes the old file to make way for the new. I will try running this job in isolation with the file created and see what results I get, however when running the package from BIDS, the file is created without issue.
I will post back with the results.
Thanks again.
February 14, 2013 at 7:46 am
Okay, placing the file there does seem to have fixed that issue, thanks for the suggestion.
February 14, 2013 at 8:02 am
You're welcome. Thanks for the feedback.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply