Data Flow Task Problem

I have a Windows XP X64 machine with SQL 2005 Developer and VS 2005 Team Edition for Architects on it. For the most part it appears that all normal VS and SQL functions are working properly with the exception of SSIS. If I open the developer studio and drag a Data Flow Task onto the design surface I get the message below. I have tried doing an unistall and reinstall of Integration Services as well as a repair on VS 2005 with no success. I've searched the web and newsgroups and can't find any mention of the problem I'm having. Any help greatly appreciated.
===================================

Failed to create the task. (Microsoft Visual Studio)

===================================

The designer could not be initialized. (Microsoft.DataTransformationServices.Design)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=TaskDesignerCouldNotBeInitialized&LinkId=20476

Program Location:

at Microsoft.DataTransformationServices.Design.PipelineTaskView.Microsoft.SqlServer.Dts.Runtime.Design.IDtsTaskUI.Initialize(TaskHost taskWrapper, IServiceProvider serviceProvider)
at Microsoft.DataTransformationServices.Design.DtrTaskDesigner.InitializeTaskUI()
at Microsoft.DataTransformationServices.Design.DtrTaskDesigner.OnNewTaskAdded()
at Microsoft.DataTransformationServices.Design.DtsBasePackageDesigner.CreateExecutable(String moniker, IDTSSequence container, String name)

Try this.

Go to Windows services, check account under which "SQL Server Integration Services" run.

Switch it to "Local System account"

BAZ

|||

I don't see how the service will effect a designer issue. The service is only used for server storage support or during execution. Local System is not very good practice either, you should understand the security risks involved.

Unfortunately I don't have a solution to the original problem either. Maybe try a Reset Toolbox, as this should clean out any rubbish, and it seems like some tasks are rubbish, or at least not installed correctly. This may prompt something.

|||Hi,

I had the error below when adding data flow tasks in the designer, and Baz' advice worked. Must be some strange permission issue, but i do not know enough about this stuff yet to comment further.

Registration information about the Data Flow task could not be retrieved. Confirm that this task is installed properly on the computer.

ADDITIONAL INFORMATION:

TaskHost "{C3BF9DC1-4715-4694-936F-D3CFDA9E42C5}"' is not installed correctly on this computer. (Microsoft.DataTransformationServices.Design)|||I recently ran into this problem and BAZ's suggestion fixed the issue.
|||BAZMIC solution did'nt worked for me... don't know what to do...
|||I had the exact same problem and BAZMIC's solution worked for me as well.|||

Regarding how the IS service affects the designer...

When the designer starts, it needs to know what IS components (e.g. data flow components, tasks, enumerators, etc) are available on the machine. The discovery process can delay the designer start-up enough to cause a bad user experience. To improve the start-up time, the service caches the information which can then be accessed by the designer and saves it from having to go through the discovery process each time. If the designer starts up and the service is not started, the service will attempt to start and fill its cache. Knowing this might help you troubleshoot these kinds of issues further.

|||

I have just upgraded my SQL 2005 to SP2.

I had the error stated in this thread, and tried Baz's solution.

However now I am getting this error message whenever I try to open a DataTask in SSIS:

TITLE: Microsoft Visual Studio

Cannot show the editor for this task.

ADDITIONAL INFORMATION:

The task returned an unsupported control editor type. (Microsoft.DataTransformationServices.Design)

Can anyone please offer some advice?

|||

Anonymous581024 wrote:

BAZMIC solution did'nt worked for me... don't know what to do...

I tried everything and it never worked. I finally deinstalled SQL Server 2005 Integration Services and reinstalled it.
|||Thanks Bazmic it works with me |||This is apparantly in some cases a problem with the SP2 that was deployed. After installing this on the SQL Server 2005 I have had a variety of problems including this one.