I upgraded an SSIS 2008R2 package to SSIS 2016 using the upgrade wizard. It upgraded successfully. I do have both 2008R2 and 2016 SQL Server loaded on my server. I am executing a batch file that calls the upgraded package. The batch file is calling DTEXEC.exe from "C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\". I receive these errors:
0xC001700A The version number in the package is not valid. The version number cannot be greater than current version number.
0xC0016020 Package migration from version 8 to version 6 failed with error 0xC001700A.
0xC0010018 Error loading value ",DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">8" from node "DTS:Property".
Any suggestions on what I can try next?
Try changing the path to DTEXEC.exe in your batch file to the following
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\
Detailed Explanation
The error is likely from you running the DTEXEC.exe from the SSIS 2008 installation folder i.e. from C:\Program Files (x86)\Microsoft SQL Server\110\DTS.
The equivalent folder for SSIS 2016, if you had done the default installation, is as follows
32-bit SSIS: C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\
64-bit SSIS: C:\Program Files\Microsoft SQL Server\110\DTS\Binn\
From your question, it looks like you are trying to execute the 32-bit version of DTEXEC.exe, so the right path to call it from, in your batch file is
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\
References:
File Locations for Default and Named Instances of SQL Server
dtexec Utility - Considerations on Computers with Side-by-Side Installations
Related
Reproduction steps:
Stack: Windows 10, Visual Studio 2019 professional, BizTalk Server 2020 developer edition CU1.
In Visual Studio create a new Biztalk Server Project
Manage Nuget Package, Add a nuget package. pick one:
Known to break the build
autofac 6.0, 6.1, 6.2
nodatime 3.0.5
Azure.Storage.Blobs 12.9.1
Known to not break the build
autofac 5.2
many others I tested.
F6 (Build) or run msbuild
As far as my testing was going, whenever the nuget packages directly list a variant with a .net framework as a dependency, it works. Listing only .net standard and .net 5 as a dependency, as in the list above, fails the buil.
actual error:
PS C:\code\autofacRepro> msbuild
Microsoft (R) Build Engine version 16.11.0+0538acc04 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
Build started 8/24/2021 3:01:10 PM.
Project "C:\code\autofacRepro\autofacRepro.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Project "C:\code\autofacRepro\autofacRepro.sln" (1) is building "C:\code\autofacRepro\autofacRepro.btproj" (2) on node 1 (default targets).
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: The "AddBizTalkHiddenReferences" task failed unexpectedly. [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: System.ArgumentException: String cannot have zero length. [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at System.Reflection.AssemblyName..ctor(String assemblyName) [C:\code\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.VisualStudio.BizTalkProject.BuildTasks.AddBizTalkHiddenReferences.GetAssemblyNamesFromItems(ITaskItem[] items) [C:\co
de\autofacRepro\autofacRepro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.VisualStudio.BizTalkProject.BuildTasks.AddBizTalkHiddenReferences.Execute() [C:\code\autofacRepro\autofacRepro.btproj
]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [C:\code\autofacRepro\autofacRep
ro.btproj]
C:\Program Files (x86)\MSBuild\Microsoft\BizTalk\BizTalkCommon.targets(190,9): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() [C:\code\autofacRepro\autofacRepro.btproj]
Done Building Project "C:\code\autofacRepro\autofacRepro.btproj" (default targets) -- FAILED.
Done Building Project "C:\code\autofacRepro\autofacRepro.sln" (default targets) -- FAILED.
Build FAILED.
A repro zip package is available in this github issue. (at first I thougt, it was a special issue with autofac, but it is not)
My old stack (windows server 2016, visual studio 2015, biztalk 2016) is not affected. We are using autofac 6.1 in biztalk projects there without any issue.
I feel like this is a BizTalk bug but I am not smart enough to find the way Microsoft allows reporting it.
So finally the question is, is there a workaround or a bugfix?
I've had this with one of my own packages. This package was targeting .NET Standard 2.0. I had to add .NET Framework 4.8 (in my case) specifically as a target framework in the class library and recreate the package for it.
For public packages, you may want to create a PR or make a fork to include targeting of .NET Framework. Your BizTalk project then needs to reference the .NET Framework assembly rather than the .NET Standard one.
I have some old legacy code that requires:
C:\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0\webdev.webserver40.exe
but how do I install that? From the above it seems I need to install VS 2010 so I tried to download VS 2010 Express:
en_visual_studio_2010_vb_express_web_installer_x86_516528
and install that, but that did not install anything in:
C:\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0\webdev.webserver40.exe
Any suggestions?
That server is ASP.NET Development Server and your "legacy" code should not depend on it at all. Revise that to use other solutions please.
Besides, if you do insist installing it, you need to install Visual Studio Express for Web, not VB.
My command prompt is not working for some .exe files. I DO have the file in my path, I even can try opening the file directly and it does nothing. If I click on troubleshoot compatibility, it says incompatible application detected, but if I switch to other options, nothing works. I can open up other programs fine. I can open up Rgui and its fine, Rcmd works fine too. R.exe does nothing which prevents me from running certain things I need. I have tried other old versions of R too and nothing works.
operating system: Windows 7 64 bit (all updates installed)
program: RRO, R
C:\Windows\SysWOW64>which R
/c/Program Files/RRO/R-3.2.2/bin/x64/R
C:\Windows\SysWOW64>R
C:\Windows\SysWOW64>
C:\Windows\SysWOW64>R.exe
C:\Windows\SysWOW64>
C:\Windows\SysWOW64>cd C:\Program Files\RRO\R-3.2.2\bin\x64
C:\Program Files\RRO\R-3.2.2\bin\x64>R.exe
C:\Program Files\RRO\R-3.2.2\bin\x64>
C:\Program Files\RRO\R-3.2.2\bin\x64>python
Python 2.7.8 |Anaconda 2.1.0 (64-bit)| (default, Jul 2 2014, 15:12:11) [MSC v.1
500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://binstar.org
>>>
C:\Program Files\RRO\R-3.2.2\bin\x64>echo %path%
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\Wind
owsPowerShell\v1.0\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\WIDCOMM
\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Pro
gram Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Mic
rosoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tool
s\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x8
6)\MATLAB\R2013b\bin;C:\Program Files\MATLAB\R2013b\runtime\win64;C:\Program Fil
es\MATLAB\R2013b\bin;C:\Program Files\RRO\R-3.2.2\bin\x64;C:\Program Files (x86)
\Riverbed\Steelhead Mobile\;C:\Program Files (x86)\Microsoft SQL Server\100\Tool
s\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\C
ommon7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DT
S\Binn\;C:\Program Files\TortoiseHg\;C:\Program Files\Microsoft SQL Server\110\T
ools\Binn\;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\QuickTime\QTSys
tem\;C:\Anaconda;C:\Anaconda\Scripts;C:\TDM-GCC-64\bin;C:\tomlab\shared;C:\Progr
am Files\Microsoft Windows Performance Toolkit\;C:\Program Files (x86)\Windows K
its\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\Microsoft SDKs\TypeS
cript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Bin\;C:\cygwin64\bin;
C:\Program Files (x86)\CMake\bin;C:\cygwin64\sbin;C:\opencv\build\x64\vc12\bin;C
:\Program Files (x86)\Skype\Phone\;c:\Rtools\bin;c:\Rtools\gcc-4.6.3\bin;;%CREAT
OOLS_DIRS%;C:\Program Files (x86)\CreaTools\crea_TPdlls-3.2.0\bin
try "C:\Program Files\RRO\R-3.2.2\bin\x64\Rgui.exe"
I am trying to deploy a web application built in VS 2012 on IIS7. Getting the error "Could not load file or assembly 'Microsoft.SqlServer.Replication.dll' or one of its dependencies. The specified module could not be found."
I have checked, I have this DLL in the following locations -
1 - My project location bin directory
2 - C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies
But I find that the DLLs are of different size at different places, at one place it is 1.53 MB where as other is 1.68 MB.
This machine is 64 bit. And I have installed SQL Server 2008 Express and SQL Server 2008 Express Management Studio.
I have just found the answer for this problem. It started working as soon as I replaced the replication dll in my bin folder. The problem was with the version of this DLL.
I was wondering if anybody is using TFS 2010 beta 2 build server to build BizTalk 2009 projects created in VS 2008?
I created new BizTalk project in VS 2008 adding simple schema with promoted property. Then I created new build definition from VS 2008 Team Explorer and queued up new build on our TFS 2010 build server...
I'm getting compilation errors due to the conflicts in .NET Framework versions. Here is a snippet from compilation log:
CoreCompile:
C:\Windows\Microsoft.NET\Framework\v3.5\Csc.exe /noconfig /nowarn:1701,1702 /errorreport:prompt /warn:4 /define:TRACE /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Configuration.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.RuntimeTypes.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Interop.Agent.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Messaging.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.Engine.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.BizTalk.Engine.dll" /reference:"C:\Program Files\Common Files\Microsoft BizTalk\Microsoft.RuleEngine.dll" /reference:"C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.XLANGs.BizTalk.ProcessInterface.dll" /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Xml.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Data.dll /reference:C:\Windows\Microsoft.NET\Framework\v4.0.21006\System.Web.Services.dll /reference:"C:\Program Files\Common Files\Microsoft BizTalk\Microsoft.BizTalk.TOM.dll" /debug:pdbonly /keyfile:somekey.snk /optimize+ /out:obj\Release\TestSchemas.dll /target:library /warnaserror- Properties\AssemblyInfo.cs "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\SomeSchema.xsd.cs" "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\PropertySchema.xsd.cs"
CSC : warning CS1685: The predefined type 'System.Runtime.InteropServices.DefaultParameterValueAttribute' is defined in multiple assemblies in the global alias; using definition from 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
PropertySchema.xsd.cs(64,35): error CS0433: The type 'System.Xml.XmlQualifiedName' exists in both 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.XML.dll' and 'c:\Windows\Microsoft.NET\Framework\v4.0.21006\System.XML.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
PropertySchema.xsd.cs(72,36): error CS0433: The type 'System.Xml.XmlQualifiedName' exists in both 'c:\Windows\Microsoft.NET\Framework\v2.0.50727\System.XML.dll' and 'c:\Windows\Microsoft.NET\Framework\v4.0.21006\System.XML.dll' [C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj]
Done Building Project "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestSchemas\TestSchemas.btproj" (default targets) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\Sources\TestBizTalkApp\TestBizTalkApp.sln" (default targets) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CompileSolution target(s)) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CompileConfiguration target(s)) -- FAILED.
Done Building Project "C:\Builds\2\Test Project\Test Build\BuildType\TFSBuild.proj" (CoreCompile target(s)) -- FAILED.
As you can see, there are references to the same assemblies for two different framework versions (2.0 and 4.0) which is causing conflicts.
Our setup is: Win2008 box with BizTalk 2009, VS 2008 SP1 and we installed TFS 2010 beta 2 build service on the same box and configured to run only as an build agent. Then we've got another Win2008 box with TFS 2010 beta 2 which is configured as a source control and build server with only a build controller set-up.
Any help on how to get rid of the references to framework 4.0 from build would be much appreciated. Thanks!
We installed final version of TFS 2010 but had the same issue with conflicting assemblies. It turns out there is a bug in BizTalk build task. Details and workaround can be found here.
I submitted a bug report to Microsoft and here is reply:
We had a previous report around building BizTalk projects with TFS 2010 and I'm happy to say that it's been resolved for the release candidate. Thanks for reporting the issue.
I guess the only option now is to wait for RC and hope they really fixed that issue.