Cannot create a task with the name .....

I don't know if anyone is interested, but I was just struggling over an issue with a custom SSIS Control Flow Task and found that all referenced objects also have to be in the GAC to be able to create the custom object in the ssis designer. I guess that makes sense, but I searched all over for any reference to this error, and couldn't find anything. Hopes this sense for someone else!

Great point well made. BOL does make a nod to this here: http://msdn2.microsoft.com/en-us/library/ms403356.aspx

-Jamie

|||Thanks for the reply, and the inclusion of the article that I've had bookmarked and permanently burned into my desktop for the last week :-). Good point as well, and only to further clarify, I'm not talking about the assembly that IS the custom object, but one that is Consumed by the Custom Object. Yeah you don't get very far, if the Custom Task you're creating itself isn't in there, but all other objects need to be there too.

My specific purpose was to use a free object (that I've disassembled and etherealed) to create a custom FTP object that replaces the built in FTP object. I needed access to Passive mode that works, or at least one that works with the FTP server I have to connect to.

Anyway, its been a great lesson for me. I've totally just hacked through by replubming the object, and since have had to work through delegates, and will probably have to takle some threading. Thanks for the samples, the process would have been much harder without them!

Cannot connect to a named instance of SQL 2000 or 2005

Hi,

I am struggling connection to a named instance of SQL 2000 (SP4) from another machine but without any success. I get an error message saying that the server does not exist or access is denied.

The security configuration in this named instance is the same as the default instance (also 2000) and the remote machine can connect to it successfully.

I also configured the aliases in Client Network Utility in the client machine and set the server (machine) name and the port number used by the instance - but no help.

I use osql and Query Analyzer to connect to it, but I cannot connect by any of them.

Connecting locally, in the machine where the instance is installed, is successful.

The same behaviour appears when I try to connect to another instance on the machine which is 2005.

Something with the named instance is problematic.

Any help?

Hi,

What OSQL string did you use to connect to SQL Server. If you have a named instance you probably have another port number assigned to the additional service to listen to the network. If so, you have to prvide the port number while connecting to the server.

OSQL -SServername,Portnumber <otherparams>

HTH, Jens Suessmeyer.

|||

Thanks Jens.

I think I found the problem. it is all about Win XP SP2 firewall clocking TCP/IP connections to SQL Server.

All the asweres are in Microsfot KB articles:

841394 (http://support.microsoft.com/?scid=kb;en-us;841394&spid=2855&sid=332)

841252 (http://support.microsoft.com/kb/841252/)

841251 (http://support.microsoft.com/kb/841251/)

and the other relevant artickles referred there.