SSIS 2008 Add Reference No Template Information Found
When attempting to add a reference to an SSIS 2008 Script Task of an SSIS package using Visual Studio 2008 or BIDS 2008, Ireceive error "No Template Information Found. See the application log in Event Viewer for more details." Peforming the tasks mentioned in the event viewer do not work for this particular problem. I have seen others report this problem with no fix found. I have this same problem on *EVERY*box with BIDS 2008 thatI've tried this with no matter what reference I'm trying to add. Others are replying to similar messages saying they have the same problem, but no real answers. This appears to be so easily repeatable across different machines:Install SQL Server 2008 on a server(or install Visual Studio 2008 on a workstation and choose SQL Server 2008 Express as an option)Run BIDS 2008Create a new Integrated Services PackageInside the package, start a script task(VB.NET)Edit the ScriptSelect Project inside the script window, then Add ReferenceSelect any reference and click OK.Error appearsI can actually choose my intended reference (for example Oracle.DataAccess), click OK to getpast the error, then run the script and everything works. However, the next time I open thepackage, the reference is gone.
August 11th, 2009 3:03pm

Is this a custom assembly that you are referencing, or a standard part of the .NET Framework?John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 3:14pm

Standard part of the .NET Framework.
August 11th, 2009 3:35pm

Which one? I had some issues with this back before RTM, but I haven't run into it since.John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 3:46pm

On my workstation:Microsoft Visual Studio 2008Version 9.0.30729.1 SPMicrosoft .NET FrameworkVersion 3.5 SP1 Installed Edition: Professional Microsoft Visual Studio Tools for Applications 2.0 91605-270-0880775-60593 SQL Server Integration Services Microsoft SQL Server Integration Services DesignerVersion 10.0.2531.0 ((Katmai_PCU_Main).090329-1015 ) On a newly installed server:Microsoft Visual Studio 2008Version 9.0.30729.1 SPMicrosoft .NET FrameworkVersion 3.5 SP1 Installed Edition: IDE Standard SQL Server Integration Services Microsoft SQL Server Integration Services DesignerVersion 10.0.2531.0 ((Katmai_PCU_Main).090329-1015 )
August 11th, 2009 4:14pm

Sorry, I meant what assembly are you referencing?John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 4:41pm

Initally noticed problem when I tried to reference Oracle.DataAccess.However, I've also tried others such as Microsoft.Build.Engine with same result.
August 11th, 2009 4:45pm

Are you trying this in a Script component (not a Script task)? Are you using VB or C#? I can add references fine in the Script task. If I add the reference in the Script component in C#, it works fine. It does not work if I use VB. Maybe try using C# to see if that works around the issue.John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2009 5:13pm

That's what is happening to everybody. C# seems to be the only workaround. I have ZERO C# experience but I guess I'll have to work with it for now.
August 11th, 2009 5:18pm

I have been using a custom C# assembly in a SSIS project/task for a while it had been working fine until recently. I needed to make some changes to the assembly and now when I try to reference to new changed assembly I'm getting this same error. I don't think that using C# will be the solution to the problem. I'm now trying to fix this issue as well.
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2010 6:15pm

Has this issue been resolved for Script Tasks/Components written in VB? I find it odd that adding a reference in a task or component works fine if the language is set to C#, but not VB. What happens with all of the 2005 scripts (only written in VB) that are converted? This is the problem I am having now. I would appreciate any information on whether this problem has been resolved or not as we are migrating to SQL Server 2008. Thanks, Jeff Tolman EandM Electric
February 9th, 2011 3:02pm

Possible solution: http://www.sqlis.com/post/Script-TaskComponent-and-Template-Information.aspx
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 1:58am

As proposed by Valentino Vranken http://www.sqlis.com/post/Script-TaskComponent-and-Template-Information.aspx The solution at this link worked for me
July 17th, 2012 10:16am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics