0

I'm trying to add some secure FTP code to an SSIS package. I've used the EnterpriseDT product successfully on other .NET projects, so I wanted to incorporate it into an SSIS 2008 package I'm working on.

If I create a Script Task (VB), edit the script, choose Project | Add Reference, and select the editFTPnetPRO.dll file, it comes back with this error:

No template information found. See the application log in Event Viewer for more details.

To open Event Viewer, click Start, click Control Panel, double-click Administrative Tools, and then double-click Event Viewer.

The application log doesn't contain any pertinent details.

I have no idea what this is trying to tell me. I've gone down a couple dead ends searching for this error message and following the prescribed fixes, but nothing has fixed it yet. Any idea what might be going wrong?

P.S. - I tried the devenv.exe /installvstemplates fix, which didn't change anything.

Update: Here is the error captured in the SSIS package when you try to run it:

Error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'edtFTPnetPRO, Version=6.3.1.20, Culture=neutral, PublicKeyToken=0dce1ad63760d80b' or one of its dependencies. The system cannot find the file specified.

Where is it looking for this file? I tried copying it to the project direcory, the bin folder, and the C:\WINDOWS\Microsoft.NET\Framework\v2.0.nnnn folder, but it still can't find it, and it won't tell me where it's looking.

Community
  • 1
  • 1
gfrizzle
  • 12,419
  • 19
  • 78
  • 104

3 Answers3

0

Put your DLL into C:\Program Files\Microsoft SQL Server\100\DTS\Binn and try again.

John Saunders
  • 160,644
  • 26
  • 247
  • 397
Rajja
  • 9
  • 1
0

I have encountered this error a few times while attempting to add a reference from the .NET tab of the Add Reference dialog.

The (painfully simple) fix is to use the Browse tab to add the reference.

addReferenceDialog-browseTab

dev_etter
  • 1,156
  • 13
  • 32
0

I'm now having this same problem with a custom C# assembly that I created to use with SSIS. I have added the assembly to the Windows\assembly and C:\WINDOWS\Microsoft.NET\Framework\v2.0.nnnn folders.

Aaron
  • 413
  • 1
  • 4
  • 14