I get the following error when adding a Data Flow Task:

TITLE: Microsoft Visual Studio
------------------------------

The task with the name "Data Flow Task" and the creation name
"DTS.Pipeline.1" is not registered for use on this computer.
Contact Information:
Data Flow Task

------------------------------
BUTTONS:

OK
------------------------------


I've uninstalled and reinstalled SQL Server 2005 multiple times and I
still get the error. Esentially, I can't do any imports or data flows.

Anyone have any ideas?

I am having this exact issue - I've attempted a reinstall as well with no
success - has anyone solved this issue?

"davidsems (AT) gmail (DOT) com" wrote:

I am getting the same error....please help!

Jason Saidoo wrote:

I've found the solution!! It has to do with insufficient registry
permissions for the user with which the SSIS services uses to logon (by
default it's the NT AUTHORITY\Network Service account). There are a very few
situations which cause a few keys in the registry (under the
HKEY_CLASSES_ROOT\Clsid node) to deny permission to the average user.

You can change the SSIS service to logon as a user with more permissions
(I'm not sure to what level). OR you can change the registry permission for
the offending keys. To do the latter, execute the following code AS A
NON-ADMINISTRATIVE USER (meaning you have to create and build an application,
create a user, assign that user to ONLY the users group, log off, log back on
with the newly created user, run the app, note the keys it finds, log off,
log back on as an admin, and in regedit, change the permissions of the keys
you found).

Here is the code as taken from
http://forums.microsoft.com/msdn/sho...eid=1&PageID=1 (about half way down)

using System;
using Microsoft.Win32;

namespace CheckClsidPerm
{
class Program
{
static void Main(string[] args)
{
RegistryKey clsid =
Registry.LocalMachine.OpenSubKey(@"Software\Classe s\CLSID");
string[] clsids = clsid.GetSubKeyNames();
Console.WriteLine("found {0} keys", clsids.Length);

foreach (string s in clsids)
{
try
{
using(RegistryKey clsidKey = clsid.OpenSubKey(s))
{
using(RegistryKey ic =
clsidKey.OpenSubKey("Implemented Categories"))
{
}
}
}
catch( Exception e )
{
Console.WriteLine("error while reading key {0}: {1}", s,
e.Message);
}
}
}
}
}


"davidsems (AT) gmail (DOT) com" wrote:

I had a similar error, for "DTS.Pipeline.1" The resolution was to grant "Read & Execute", "List Folder Contents" and "Read" permissions to the

\Program Files\Microsoft SQL Server\90\DTS\Binn

directory for the group

SQLServer2005DTSUser$[MACHINE_NAME]

Notes:

• The NT Authority\NetworkService account was part of this group, and is the account that the SSIS service runs as
• Permissions on the DTSPipeline.dll file were already okay

I had the same problem and the simlest way I found to get around it is to simply have the service log on as a local system account.