Main Topics
Browse All TopicsHello Experts,
I have developed an SSIS package on my production machine and ran it with no problems.
However, when I schedule the package to run (and set ssis logging on), I find that it fails with the following error:
"Version of component "___" is not compatible with this version of the DataFlow".
I mention that I've developed and executed the package successfully on the same production machine because I've read several threads where people suggest a conflict between anything from service packs to 32/64 bit conflict. This can not be the case here, in my opinion.
The only wild reason I can muster up for this conflict is my attempt to take shortcuts by doing a copy/paste of components within the package and from other packages in the solution. I can see where the components GUID maybe registered to another package (and I'll test this first thing tomorrow).. but this doesn't explain why the package runs with no errors when I execute it manually. (from VS).
If anyone ran into this type of problem, or can help confirm / deny the possibility of conflict in cross-package copy/paste, that would be great!
Any help is much appreciated. Thank you all in advance.
- Eyal
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: poogy21Posted on 2007-12-31 at 13:40:37ID: 20557496
Additional note:
so I simplified it down to an SSIS package that does only one thing; Load a flat file into the database.
This failes with the following error:
Executed as user: SQL1-LAX\Administrator. ....3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:23:39 PM Error: 2007-12-31 13:23:40.64 Code: 0xC0048020 Source: load bandwidth load bandwidth (DTS.Pipeline) Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. End Error Error: 2007-12-31 13:23:40.65 Code: 0xC0048020 Source: load bandwidth DTS.Pipeline Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. End Error Error: 2007-12-31 13:23:40.70 Code: 0xC0048021 Source: load bandwidth Flat File Source [1] Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Flat File Source;Microsoft Corporation;Microsoft SqlServer v9; (C) 2005 Microsoft Corporation; All Rights R... The package execution fa... The step failed.
It looks like error code "0xC0048021" refers to a Service Pack version conflict, but I'm running SQL 2005 64bit Ent. with SP2.
Also, just as a procationary matter, I've setup permissions to the flat file for full-control on all users. and my sql agent is running is local administrator. The file is located on a local drive (not a network drive)..
And so, again.. I ask for any help you can provide and thank you all in advance.