April 5, 2017
.NET, .NET 4.7, .NET Core 1.0, .NET Framework, .NET Framework 4.5.2, .NET Framework 4.6, .NET Framework 4.7, ASP.NET, ASP.NET Core 1.0, ASP.NET MVC, C#.NET, Microsoft, Troubleshooting, Visual Studio 2017, VisualStudio, VS2017, WCF, Windows, Windows 10
I was frustrated by this error when I am trying to reinstall Visual Studio 2017 after my visual studio got corrupted/failed during upgrade to 15.1 ( or after a previous installation failed due to low disk space).
There is a file called ‘state.json’ , in below mentioned path, which is creating this particular issue.
- Delete/rename the folder as is or rename ‘state.json’ file to ‘something.json’ .
Found from : https://developercommunity.visualstudio.com/content/problem/2877/install-error-0x80131500-failed-to-deserialize-pac.html
Recently while installing SQL Server 2005 64bit on a Windows Server 2008 R2 Enterprise 64bit an error message displays that “An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package ‘sqlncli_x64.msi’.” as shown below.
After that, the Microsoft SQL Server 2005 Setup Progress will display some errors with a status “Setup Failed. Refer to the Setup log for details”.
When trying to install the Microsoft SQL Server Native Client Setup by hand it displays a similar error message that the file ‘sqlcli_x64.msi’ cannot be found. It’s unable to locate the sqlcli_x64.msi ( 64 bit version of SQL Server Native client). It’s puzzling, I am trying to install with 64 Bit version of SQL Server 2005 and it’s unable to locate the sqlcli_x64.msi, crazy thing is file is already available in installation folder and it’s showing me that error strange???.
After so much of trial I found solution for this problem is that someone started the installation with a wrong edition (32 vs. 64) edition and left the components there.
Go to Add/Remove Programs and remove the existing SQL 2005 components, and then reinstall.
Voila!!! It works fine.. It’s puzzling why the error comes up, but it is resolved after re-installation.