LogProviders.Add fails with "not recognized as a valid log provider type." in Data Tools but not BIDS

Question

In attempting to add standard DTS logging to a package via Data Tools, I found that my attempt to execute:
        Dim provider As LogProvider = p.LogProviders.Add("DTS.LogProviderTextFile.2") 
(or any other log provider type,) resulted in:
The log provider type "DTS.LogProviderTextFile.2, {0A039101-ACC1-4E06-943F-279948323883}" specified for log provider "{CC5CB9A4-E0D5-4ECD-8F4E-1E8FB9BDE8A6}" is not recognized as a valid log provider type. This error occurs when an
attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name.
I created a new package with a single script task using only the example code from the MS documentation for Embedding Logging Programmatically at:
http://msdn.microsoft.com/en-us/library/ms136023(v=sql.110).aspx
consisting of:
Imports Microsoft.SqlServer.Dts.Runtime
Module Module1
Sub Main()
Dim p As Package = New Package()
Dim loggingConnection As ConnectionManager = p.Connections.Add("FILE")
loggingConnection.ConnectionString = "C:\SSISPackageLog.txt"
Dim provider As LogProvider = p.LogProviders.Add("DTS.LogProviderTextFile.2")
provider.ConfigString = loggingConnection.Name
p.LoggingOptions.SelectedLogProviders.Add(provider)
p.LoggingOptions.EventFilterKind = DTSEventFilterKind.Inclusion
p.LoggingOptions.EventFilter = New String() {"OnPreExecute", _
"OnPostExecute", "OnError", "OnWarning", "OnInformation"}
p.LoggingMode = DTSLoggingMode.Enabled
' Add tasks and other objects to the package.
End Sub
End Module
I get the same error as listed above in SQL Server 2012 Data Tools on three separate machines.  On my primary dev box, where the code fails in Data Tools, running the exact same code in BIDS runs without problems.
Importing the working BIDS package into Data Tools also fails with the same error.
I have not encountered any other 2012 Data Tools issues, but logging is a core pattern that makes me worry that this is a problem that may emerge with other functions in the DTS toolset.
Thanks for any help!!

Answer 1

Arthur,
Great idea, I verified that the Integration Services for 2012 was not installed.  I installed the new SSIS service and verified that SQL Server Integration Services 11.0 was running (previously only 10.0 was running.)
Initially, I experienced an error message trying to run my simple script above:
Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0,...
I followed the steps at the MS link for Could not load file or assembly ‘Microsoft.VisualStudio.Tools.Applications.Core’
and loaded the missing x64 runtime from edist/VSTA/runtime/x64/VSTA_RT30.msi
on the distribution media as recomended.
The script ran, but returned the error listed in the beginning of this message.  I then tried:
- turning off the 10.0 service
- setting the project's Run64BitRunTime value both false and true
- changing the reference to Microsoft.SqlServer.ManagedDTS.dll from C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies to C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\v4.0_11.0.0.0__89845dcd8080cc91
all of these resulted in the same failure.
Thank you for the suggestion, I really thought it would be on target.  Alas, it wasn't the fix.
It is so weird that all the other stuff I'm doing (a very elaborate programmatic package generator doing some tricky stuff,) works fine and only this super basic logging fails!!!!
Thanks again,
--Tim