I’ve created a SSIS package that has 2 tasks. The first is selecting some information from a SQL Server table and the second is exporting this information to a flat file.
I created the package on my desktop client and I am able to run it successfully in Debug mode from my client. The information is selected from the LIVE SQL Server database and the file is created on the LIVE SQL Server.
I have built the package for deployment, copied it to the LIVE SQL Server and have run the manifest file to deploy it.
I’ve logged into the SSIS on the LIVE server and the package is listed there. However when I right click on it and run it I get some error messages indicating that the dataflow tasks have no components, presumably the select statement and the export to the flat file.
It’s as if when I build the package the data components are not being included or when I deploy it on the LIVE server the data components are not being deployed.
Does anyone have suggestions?
Could you report the actual error message you are getting? Empty data flows only generate warnings, not errors.|||The exact error is:
DocumentL Listing
Validation has started.
Export Document Listing
Validation has started
Warning: The DataFlow task has no components. Add components or remove the task
Validation is completed
Validation has started
Warning: The DataFlow task has no components. Add components or remove the task
...
|||Rob,
I know about this problem only too well. Are you using a source control system?
-Jamie
|||We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.
Are you saying that this may be a problem with the Source Safe integration with SQL 2005?
|||
Rob Woods wrote:
We are using Visual source Safe, but I do not believe that it is installed on any of the computers discussed here.
So that package that we're talking about. Does it ever get stored in SourceSafe?
Are you saying that this may be a problem with the Source Safe integration with SQL 2005?
Not exactly. There's a problem with all source control systems when used in conjunction with the SSIS Designer - I have seen it happen with SourceSafe and TFS. The SSIS team are aware of it and are investigating. Long answer is that the contents of the data-flow doesn't get serialized correctly into the .dtsx file due to some sort of problem when used with a source control system. Short answer is that there is a bug.
I really should blog this 
-Jamie
|||So is there a work around?|||
So is there a work around?
Best I can offer is that seeing as you are using a source control system you can go back and find the most recent version that still contains all the components, and redo all of your changes. Not great!
-Jamie
|||
I really should blog this
And now I have done: http://blogs.conchango.com/jamiethomson/archive/2007/04/24/SSIS_3A00_-Bug-when-using-source-control-systems.aspx
-Jamie
No comments:
Post a Comment