I am getting the following error when carrying out a release against a server with Enterprise Library 5.0 already installed and used by ESB 2.1 (cannot just uncomment out references in machine.config):
16/01/2015 13:58:54 - Error - (1120, 1116) - [A]Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection cannot be cast to [B]Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection. Type A originates from 'Microsoft.Practices.EnterpriseLibrary.Common, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\Windows\assembly\GAC_MSIL\Microsoft.Practices.EnterpriseLibrary.Common\5.0.414.0__31bf3856ad364e35\Microsoft.Practices.EnterpriseLibrary.Common.dll'. Type B originates from 'Microsoft.Practices.EnterpriseLibrary.Common, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context 'Default' at location 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\bin\Microsoft.Practices.EnterpriseLibrary.Common.dll'.: \r\n\r\n at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceFactory.Create()
at Microsoft.TeamFoundation.Release.Data.Model.DataErrorPropertyChangedBase.Validate()
at Microsoft.TeamFoundation.Release.Data.Model.DataErrorPropertyChangedBase.OnPropertyChanged(String propertyName, Boolean setDirty, Boolean validate)
at Microsoft.TeamFoundation.Release.Data.Model.SystemSettings..ctor(Rtm13Services rtm13Services)
The Deployment Agent 2013 software installs to 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\bin\Microsoft.Practices.EnterpriseLibrary.Common.dll'.
I managed to get deployments working by removing references to Enterprise Library 5.0 in the machine.config file but understand these are needed by the ESB 2.1 software utilised by our BizTalk developers - I understand commenting out in machine.config is not an option.
Does anyone know how to resolve this?
Related
SQL Server version: SQL Server 2016 SP2 GDR 2019 (KB4505220) -
13.0.5101.9 (x64) Issue: Analysis Services Processing Task: Error: Could not load file or assembly
'Microsoft.AnalysisServices.AdomdClientUI, Version=13.0.0.0,
Culture=neutral, PublicKey Token=89845dcd8080cc91' or one of its
dependencies. The system cannot find the file specified.
Actions Made so far:
Follow the option 3 assembly binding from this site. Got this error after: Analysis Service Processing Task: Error: Method not found: 'Boolean Microsoft.analysisServices.AdomdClientUI.AdomdConnectionStringBuilder.IsAzure()'
Install CU2 but during install it states that current SP2-GDR is latest
Any idea on the fix?
We were able to fix the missing dll file when patching to SQL 2016 SP2 version 13.0.5622.0 (CU11 + Security Update) Release Date Feb 25, 2020.
We have a Windows server where we are reading some SSIS packages and processing them through a web app eg:
SSIS.Application app = new SSIS.Application();
SSIS.Package pkg = app.LoadPackage(txtSSISPackagePath.Text.Trim(), null);
pkg.EnableConfigurations = true;
string ConfigurationFilepath = txtSSISPackagePath.Text.Trim().Replace(".dtsx", ".dtsConfig");
pkg.ImportConfigurationFile(ConfigurationFilepath);
pkg.Execute();
We have installed the .NET Framework but no Visual Studio or SQL Server on this server. We are getting an error while running this project on the server:
Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
When we verified in the GAC and Assembly folder, this dll is in fact missing. We have copy pasted the assembly from local but it didn't work both in bin folder and in Assembly/GAC folder. Also tried register with GACUtil but that tool is not available in the server.
Is there any way to add this dll to resolve the reference problem like registering this dll or installing some sdk (not SQL Server) to resolve this problem?
NOTE:
We are using .NET framework 4.6.1
SSIS = Microsoft.SqlServer.ManagedDTS.Runtime
It was working in 2008 Server (no SQL installed) and now its not working 2012 Server
I recently have attempted to migrate a solution created and developed in Visual Studio (VS) 2012 to VS 2017.
I've managed to migrate all projects of my solution except for a Report Server Project. When I try to open my solution in VS 2017 I get the following message:
I click on Yes and VS automatically upgrades the project file (this is a file having the extension .rptproj)
When I now try to build the project I get the following error message:
Error Copying file Reports\Report\Project1\MyReportProject.rptproj.user to
obj\Debug\AspnetCompileMerge\Source\Reports\Report
Project1\MyReportProject.rptproj.user failed. Could not find file
'Reports\Report Project1\MyReportProject.rptproj.user'
I thought the upgrade would be performed transparently. Am I missing something? Is there any extra step I should take in order to do the upgrade?
Note: I've already downloaded and installed the latest version of Microsoft Reporting Services Projects .vsix package.
You can try the latest msbuild.exe for SSRS is here.
This includes steps of up-gradation of SSRS for both VS15 and VS17.
Once you install the latest update, depending on which version of Visual Studio you’re using, the new files enabling MSBuild for your projects will be installed in different folder path:
In Visual Studio 2017, it’ll will be a nested folder in your Visual Studio folder hierarchy. For example, the location with the Community Edition is in the Community folder:
Edit 1:
Try these steps:
1) Close Visual Studio - 17
2) Open VS-17 Installer
3) Try to install the SSDT workflow as:
I am receiving the following error when trying to execute an SSIS package using Visual Studio 2012:
Error 39 Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: The
package failed to load due to error 0xC0011008 "Error loading from
XML. No further detailed error information can be specified for this
problem because no Events object was passed where detailed error
information can be stored.". This occurs when CPackage::LoadFromXML
fails. ---> System.Runtime.InteropServices.COMException: The package
failed to load due to error 0xC0011008 "Error loading from XML. No
further detailed error information can be specified for this problem
because no Events object was passed where detailed error information
can be stored.". This occurs when CPackage::LoadFromXML fails.
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackagePersist100.LoadPackageFromXML(Object
vSource, Boolean vbSourceIsLocation, IDTSEvents100 pEvents) at
Microsoft.SqlServer.Dts.Runtime.Package.LoadFromXML(String packageXml,
IDTSEvents events) --- End of inner exception stack trace ---
at Microsoft.SqlServer.Dts.Runtime.Package.LoadFromXML(String
packageXml, IDTSEvents events) at
Microsoft.SqlServer.Dts.Runtime.Project.LoadPackage(IProjectStorage
storage, Package package, String streamName, IDTSEvents events) at
Microsoft.SqlServer.Dts.Runtime.PackageItem.Load(IDTSEvents events)
at Microsoft.SqlServer.Dts.Runtime.PackageItem.get_Package() at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.IncrementalBuildThroughObj(IOutputWindow
outputWindow) at
Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.BuildIncremental(IOutputWindow
outputWindow)
0 0
The package is stored in TFS and I can open the package/solution without any errors. I just get the error when i try to excecute the package or any step in the package.
I created a new package on my machine (64 bit) and it worked fine. I'm just having trouble running the package when opening from TFS.
thanks
Scott
I resolved a very similar situation by changing the SQL Server sdk version that my solution was pointing.
I had SQL Server Express 2008 installed, and was using VS 2012 with BI Tools 2012. So, my solution was referencing the assembly Microsoft.SqlServer.ManagedDTS.dll version 10. For my case, the correct was the version 12.
I had this problem when trying to open an SSIS package which used a component which I did not have installed. In my case, it was the "Azure Feature Pack".
I had similar errors on a Win64, VS2013, SQL2012 system. The SSIS package did not load correctly.
Identify: I created a local copy of the whole package, and narrowed the problem with reduction to a single sub-package.
Reason: different date format.
Solution: I had to change the Windows date format to UK (source of the package), and since then everything is fine.
You have to copy the reference libraries to the Program Files directly as well.
I saw that in the (x86) path, the files were there, but not in the 64-bit folder of Program Files. I'm using Visual Studio 2010.
1 - C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Connections
2 - C:\Program Files\Microsoft SQL Server\110\DTS\Connections
The referenced DLL was found in location 1, but not in 2.
I closed Visual Studio, copied the DLL over to path 2, and opened VS again. The package just worked like normal.
I resolved a very similar situation by changing the TargetServerVersion in the project general configuration properties. I use Visual Studio 2015. By default SQL Server vNext was selected, whereas I have SQL Server 2012 installed.
I used the wizard once last week with no problems. Now, after installing Silverlight 5 I get:
c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\Templates\Includes\EF.Utility.CS.ttinclude(1024,76) : error CS0433: Compiling transformation: The type 'System.Xml.XmlReader' exists in both 'c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v5.0\System.Xml.dll' and 'c:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.XML.dll'
I realize you asked this forever ago but I happened upon a solution that worked for me...
This is actually a bug in the EF Power Tools that they are actively working on ...
If you edit
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\Templates\Includes\EF.Utility.CS.ttinclude
or
EF.Utility.VB.ttinclude if you are using VB
change the assembly lines that include the XML assemblies to explicitly not use the SL libraries then it starts working
so change them to
<## assembly name="System.Xml, Version=4.0.0.0, Culture=neutral" #>
<## assembly name="System.Xml.Linq, Version=4.0.0.0, Culture=neutral"#>
Then it should start working