I created one Dotnet core application using VS 2017 and then published it and then copied the published folder having runtimes folder and my application dll to Windows server 2016 where I had installed the dotnet core framework.
Even time I run the application from command line I get the below error. (I found this dll is under the runtimes folder but somehow application is not able to load)
Exception has been thrown by the target of an invocation. --->
System.Reflection.TargetInvocationException: Exception has been thrown
by the target of an invocation. ---> System.DllNotFoundException:
Unable to load DLL 'CpuMathNative' or one of its dependencies: The
specified module could not be found. (Exception from HRESULT:
0x8007007E)
My server was missing this VCRuntime140.DLL and I had to install
Microsoft Visual C++ Redistributable for Visual Studio 2017
Related
VS2017 publish causes error on startup "cannot load file or assembly ..." Running directly from the build works but not from the deployment in app.publish folder. The error shows even on my development computer. However, opening the same solution in VS2010 and publishing from there, all works as expected. I cannot find this same issue on the web.
After searching for all things Click Once, I came across an answer for a different issue and tried it. I upgraded the target framework to .NET Framework 4.6.1 and updated the NuGet Packages. Afterward, I was able to publish and run the Click Once Application with no errors.
I am attempting to install SSDT v15.6.0 into an existing Visual Studio Team Explorer 2017 instance. When I run the SSDT installer, I can select Visual Studio Team Explorer 2017 from this list of existing Visual Studio instances. If I do not choose a any options (other than the required SQL Server Database option). The installation completes successfully.
If I however attempt to pick any/all of the other options the installation fails. From looking at the log files, it appears that the installation of the VSIX is failing due to a required component missing.
Below is the snippet of the SSDT-Setup installation log file which indicates that the VSIX failed to install.
[167C:1A6C][2018-05-16T15:40:41]i301: Applying execute package: Microsoft.DataTools.IntegrationServices, action: Install, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"68f392fc" /logFile:"C:\Users\golaat\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20180516153141_009_Microsoft.DataTools.IntegrationServices.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Process returned error: 0x80131500
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to execute EXE package.
[1D80:1858][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to configure per-machine EXE package.
Looking at the log file for the installation of the VSIX it seems like a required component is missing:
5/16/2018 3:41:05 PM - BEGIN: Targetting Visual Studio Team Explorer 2017,15.0.27428.2043
5/16/2018 3:41:05 PM - BEGIN: Execute batch install
5/16/2018 3:41:08 PM - BEGIN: Preparing extension Microsoft Integration Services Projects
5/16/2018 3:41:08 PM - Loading extension: Microsoft Integration Services Projects
5/16/2018 3:41:10 PM - JSON file loaded
5/16/2018 3:41:10 PM - The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).
5/16/2018 3:41:10 PM - END: Execute batch install
5/16/2018 3:41:10 PM - END: Installing
5/16/2018 3:41:10 PM - Common folder deleted: C:\Users\golaat\AppData\Local\Temp\s0ggmkmo.cwz
5/16/2018 3:41:10 PM - Microsoft.VisualStudio.Setup.Dependencies.DependencyGraphConstructionException: The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).
Is there a way to identify this missing component an perhaps install it manually?
This is how I fixed it :
Run installer normally to the end and let it fail.
When it fails the window will have a link to the log file, open it.
In this log file, 1 or 2 lines before the error(Process returned error: 0x80131500) problem component location will be revealed, something like this:
[6748:674C][2020-07-29T09:44:03]i301: Applying execute package:
ISVsix, action: Install, path: C:\ProgramData\Package
Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe,
arguments: '"C:\ProgramData\Package
Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe"
/q /admin /instanceIds:"5403e431"
/logFile:"C:\Users\xxxx\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200729093525_11_ISVsix.log"
"payload\Microsoft.DataTools.IntegrationServices.vsix"
You have to combine location of the VSIXBootstrapper with vsix component location. In my case I had vsix file under C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\payload
Copy failing component(.vsix), in this case Microsoft.DataTools.IntegrationServices.vsix to some folder before it gets deleted. If it already got deleted then restart the installer and search for this component in parent folders.
Restart your computer. I was getting "Another installation running .." error before I did.
Go to the folder where you copied the failing component and install the .vsix manually. This time it should install normally.
Repeat step 1 but this time hoping it will work normally.
I hope this at least gets you in the right direction.
This is currently broken due to a bug in Visual Studio - see this post on the Developer Community site:
SSDT cannot install onto 15.7 version of Visual Studio
It'll be fixed in a forthcoming Visual Studio update, but if you can't wait for that a workaround is to completely uninstall Visual Studio and install an older version. See my answer here for instructions:
https://stackoverflow.com/a/50349464/1184850
With the release of SSDT 15.7.1, Team Explorer no longer shows up as an existing Visual Studio install instance option within SSDT. At first I was concerned that the SSDT install would install a Visual Studio shell with no TFS connectivity, however this was not the case. It appears that the SSDT install of the Visual Studio shell picks up on the fact that Visual Studio Team Explorer 2017 is already installed on the machine and the SSDT Visual Studio shell instance has full TFS Connectivity!
I found a solution, follow these steps:
Download SQL Server and install it. In the Feature Selection step install Integration Service
Now download Visual Studio installer and install .NET desktop development and Data storage and processing
Now run Visual Studio and go to Extensions > Manage Extensions > Online, and search for SQL Server Integration Services Projects. Download and install that
You are now good to go.
I just created a .NET Core Web Application in VS2017 and I wanted to be able to serve a single page application. In order to be able to do that I tried to install the nuget package Microsoft.AspNetCore.StaticFiles. But my NuGet installer failed and threw the following error
Severity Code Description Project File Line Suppression State
Package restore failed. Rolling back package changes for 'MyApp'.
Right click on the project=>Properties and set TargetFramework to .net core 2.0(less than or equal to the packages version you are using)
build the project and then install whatever you want from nuget.
I have setup my own Team Foundation Build server and I am using Visual Studio Online to host my project online. I have a django project which I am trying to deploy on windows azure cloud service. The project can be published from my dev machine without any errors however when the build server tries to build it, it gives the following error during uploading the package:
Exception Message: Could not load file or assembly 'Microsoft.WindowsAzure.Storage, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (type FileNotFoundException)
I checked in .pyproj and found a reference to Microsoft.WindowsAzure.Storage but there the version is 2.1.0.0 and that is the version that is installed on the server as well.
Also there are no errors during the build process but only during the deployment stage. How do I make Msbuild use Storage version 2.1.0.0 instead of 2.0.0.0 . Also, which SDK version contains Storage version 2.0.0.0
I just had this problem. This is the same problem as TFS Build Controller : "Could not load file or assembly 'Microsoft.WindowsAzure.StorageClient, Version=1.7.0.0".
You'll need to copy Microsoft.WindowsAzure.Storage.dll version 2.0.0.0 to "C:\Program Files\Microsoft Team Foundation Server 12.0\Tools", and then restart the Visual Studio Team Foundation Build Service Host 2013 service.
I have a C++ console application that I want to deploy using a vs2008 setup project. When I create the setup project and add the output from my console app, the setup project detects that it needs MSVCP90.dll and MSVCR90.dll. When I build the project, those two dlls are included in the .msi file as expected.
When I download and launch the installer, everything goes as expected and the console app and the dlls are unpacked into the proper directory on the local machine.
When I try and run the app, I get the following error:
Error 1721. There is a problem with
this Windows Installer package. A
program required for this install to
complete could not be run. Contact
your support personnel or package
vendor.
I've tried compiling the app with /MT and /MD neither one works.
When I run a dependency walker against the app, it reports that it needs MSVCP90.dll and MSVCR90.dll as expected.
Finally, if I set the installer to require the Visual C++ runtime libraries, it downloads them and everything works fine.
Obviously, I would like to avoid downloading the CRT libraries.
Thanks for any help,
Jon
Check out this example on how to add the appropriate merge modules and deploy them to your target machine along with your setup.