SSMS version : 17.7
Log file: Log_file
I have SQL Server 2016 and Visual Studio 2017 Community Edition.
I tried reinstalling both tools but the error is still the same.
Some links mention registry values and I tried that as well, but the problem remains the same.
I have restarted the system multiple times, but the restart pending is still showing.
I found a couple of other methods on some sites, tried them as well, but still the error message is showing.
It stops at the point shown below--not sure about Visual Studio 2015 as I'm using VS2017. I have tried repairing VS and SQL Server 2017 as well.
I had this problem, after force uninstalling Visual Studio 2015 Shell (Isolated) the SSMS install completed normally. I did this by searching for vs_isoshell.exe in C:\ProgramData\Package Cache and then running vs_isoshell.exe /uninstall /force from an administrative command prompt from its folder. In my case this was C:\ProgramData\Package Cache\FE948F0DAB52EB8CB5A740A77D8934B9E1A8E301\redist
Search the registry with "visual studio 2015" and deleted all the keys which are either related to shell or prerequisites. Repaired the SQL server 2016 and then installed SSMS. It somehow worked for me.
In my case, find and delete all registry keys with name "Visual Studio 2015 Shell" and it worked
Now i found the solution, i was uninstalled VS 2015(isolated) and concern VS and deleted all "C:\ProgramData\Package Cache" and after that restart the pc and installed SSMS2017 again,It was ok.
In my case, i've got it working forcing uninstalling vs_isoshell.exe (search for it in C:\ProgramData\Package Cache ) then, delete all files and folders in C:\ProgramData\Package Cache, reboot and reinstall...
Related
I used SQL Server 2019 express version on my laptop butI uninstalled. Now I am trying to install SQL Server 2019 Developer edition but I get an error:
Exit code (Decimal): -2068119551 Exit message: Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\150\ConfigurationState'.
Error description: Invalid command line argument. Consult the windows installer SDK for detailed command line help.
Environment: Dell/Inspiron/Windows 10 Home/16gb ram/256 SSD / 1TB HDD /Corei7
Can anyone help me how to solve the problem? Thanks
PS: attaching screenshot for kind reference
You can try below options, based on the reference article
Run the setup.exe again, repair the installation.
Run the Setup.exe as administrator
See whether you have clearly uninstalled the previous SQL Server setup and try again.
Did you modify the registry setting earlier. If so, please revert the changes and try the installation. Eg., changing the default installation to D:, instead of C: etc.
I fed up the below problem
Unable to install SQL Server (setup.exe).
Exit code (Decimal): -2068119551 Exit message: Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\150\ConfigurationState'. Error description: The specified service does not exist as an installed service.
I fixed the above problem
DR-2033 avatar image
Click to vote
1 Vote"
1
DR-2033 answered • Dec 21 2021 at 4:03 AM | EricK-0825 commented • Mar 21 2022 at 3:20 AM
Unable to install SQL Server (setup.exe)
I'm trying to work on a version problem with LocalDB. The command "sqllocaldb i" seems to work.
C:\WINDOWS\system32>sqllocaldb i
MSSQLLocalDB
ProjectsV12
But, when I ask for something specific, I get only errors. (I'm on Windows 10)
C:\WINDOWS\system32>sqllocaldb i MSSQLLocalDB
FormatMessageW failed. Error code returned: 15100
FormatMessageW failed. Error code returned: 15105
FormatMessageW failed. Error code returned: 15105
FormatMessageW failed. Error code returned: 15105
FormatMessageW failed. Error code returned: 15105
Thanks for the reply Paul. I have also removed all older SQL installs, but to get information on a particular LocalDB server instance using the SqlLocalDB.exe utility, I had to install the 2017 version. For instance I can now get information on an instance of SQLLocalDB (2016 version) that I created and called 'TAS_LocalDB_V13' using the command -
SqlLocalDB i TAS_LocalDB_V13
But, since there are now two versions of SQLLocalDB installed, there are two executables named SqlLocalDB.exe. The one that will run depends on the system environment path variable. I had to edit the path variable so that the path to SqlLocalDB.exe appearing first in the list was the 2017 version (which works).
Note - even though the i command in 2016 version does not work, other important commands like 'c' to create a server instance do work.
I fixed this by removing all traces of SQL from my machine and re-installing only what I needed (2016 in my case). Basically, search for "SQL" in Control Panel and remove whatever shows up.
I think this has to do with having multiple versions installed, and/or corruption happening when you update them, because:
I had SQL components ranging from 2008-2017 installed (both standard and express), and,
the problem started happening right after I applied the latest cumulative updates, which were mainly for SQL 2016.
UPDATE: it looks like the fix for this is closer to: re-install 2016 and install the 2017 sqllocaldb - no need to clean up other versions as I did. See Victor's subsequent post as well as my comment there.
I am having trouble getting TimescaleDB to work on my windows server 2016 machine with Postgres 10.
I open up a fresh windows server 2016 instance with AWS and I install Postgres using the windows GUI installer. (C:\Postgres).
The installer automatically updates the path to include the bin directory (C:\PostgreSQL\pg10\bin).
I stop postgres.
I run the TimescaleDB windows installer file and it says it's successfully completed.
I update the conf file. (shared_preload_libraries = 'timescaledb').
I restart my computer and start postgres, but postgres never sucessfully starts. The windows event yells at me, saying I 2018-03-29 17:01:35 UTC [952]: [1-1] user=,db=,app=,client= FATAL: could not load library "C:/POSTGR~1/pg10/../pg10/lib/postgresql/timescaledb.dll": The specified module could not be found.
Any idea whats going on?
This may be related to https://github.com/timescale/timescaledb/issues/485#issuecomment-377533298 which is caused by a missing dependency, Visual C++ Redistributable for Visual Studio 2015.
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:
Ultimately, I'm trying to schedule SSIS packages to run on a regular basis using Task Scheduler in an Azure VM (Windows Server 2016 Datacenter). From the command line on my development machine (Windows 10), I'm able to run...
dtexec.exe /Project "pathToMy.ispac" /Package "pathToMy.dtsx"
...and it works as expected. However, when I try to do the same from the Azure VM I get the following error:
Microsoft (R) SQL Server Execute Package Utility Version 11.0.6020.0
for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.
Started: 2:17:46 PM Could not load package
"MyPackage.dtsx" because of error 0x80131500.
Description: 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. Source: MyPackage
Started: 2:17:46 PM Finished: 2:17:47 PM Elapsed: 0.547 seconds
On both machines, I have the same version of SQL Server 2016 Developer (w/ SSIS) and Visual Studio 2015 installed. Also, I'm able to run the package fine on the VM from within Visual Studio. It's only from dtexec.exe that I have issues.
I've tried every solution on here from other posts getting similar errors and none have helped. Any ideas?
Thanks,
Ian
Thanks to #Nick.McDermaid, the answer to this riddle has been found. By running dtexec.exe (with no parameters) on the dev machine and on the VM, I was able to see that the VM version was v11 and the dev version was v13 which explained why I was getting the error and why one worked and another didn't.
I then did a File Explorer search on the VM for dtexec.exe copies and found several. Apparently, the environment path was set to find the older version. I probably could have found the variable causing this problem and changed it. However, out of concern about breaking something else and wanting a quick solution, I chose to execute using the full path to the correct version. For v13, this ended up being...
"C:\Program Files\Microsoft SQL Server\130\DTS\Binn\dtexec.exe"
So, for my schedule task I set the following properties for my "Start a program" action.
Program/Script: "C:\Program Files\Microsoft SQL Server\130\DTS\Binn\dtexec.exe"
Add Arguments: /Project "bin/Development/myProject.ispac" /Package "myPackage.dtsx"
Start in: c:{path to my .dtsx file}