Ошибка 0х80131500 visual studio
After downloading the Visual Studio 2017 Enterprise Edition and adding Service Fabric SDK. Steps to reproduce:
File new project, Service Fabric, ASPNET Core Serverless application.
It will throw the error. The curious thing: if I install the community edition, and selecting the same items, it works fine.
The text was updated successfully, but these errors were encountered:
thdotnet commented Oct 27, 2017
@taxiatms from both: VS installer and WebPI
taxiatms commented Oct 27, 2017
@thdotnet Are you able to setup a cluster without deploying any apps to it? You can do that by using the "Service Fabric Local Cluster Manager" tray icon.
thdotnet commented Oct 27, 2017
I am using Vs Community at this moment. I could not wait for a response / solution. I've just reported this issue because it's affecting others (like the stackoverflow link)
taxiatms commented Oct 27, 2017
@dbreshears Customer is saying VS enterprise has some issues and VS Community doesn't.
dbreshears commented Oct 27, 2017
@thdotnet, @taxiatms , I don't know of any installation issues are specific to Enterprise SKU. What I have seen is that VS 2017 Install fails for another reason and thus doesn't get to installing our project / service templates properly. In that case, a Repair of the VS installation with Azure Workload and Service Fabric tools should fix this issue, assuming the repair is successful. The StackOverflow issue was specific to 2015 and WebPI and thus a different issue at the time, the HRresult error being thrown is fairly generic and can manifest in more than one way, but typically has indicated issues with the template isntallation
dbreshears commented Oct 27, 2017
thdotnet commented Oct 27, 2017
I know it's outdated, but it's exactly the same error. And the problem is exactly what you've described, it seems that it's not installing the templates properly (only for VS 2017 Enterprise). Feel free to close this if you think it's not an issue, I just would like to report it because it can affect others too.
thdotnet commented Oct 27, 2017
dbreshears commented Oct 27, 2017
Curious, did you happen to have Azure SDK installed on this machine?
thdotnet commented Oct 27, 2017
dbreshears commented Oct 27, 2017
Ok, what "might" have occurred as I have seen it happen several times now, is that if the Azure Storage emulator is running (tray icon) when the VS installation is going, the storagemulator msi fails to install and thus kills the VS 2017 installation as well, prior to installing our templates. There is an open issue with the address this with the storageemulator msi
dbreshears commented Oct 27, 2017
I closed, please re-open if you need to revisit this.
thdotnet commented Oct 27, 2017
that was not the case. A brand new laptop with no VS / emulator on it.
maxamorim commented Nov 28, 2017 •
I've faced the same problem today with VS Community 2017, i've discovered in my case that was the language package. I have pt-BR installed and no english package, i've uninstalled my current language package and installed the english package, done(maybe service fabric only work with english package). Hope this helps.
dbreshears commented Nov 28, 2017
thdotnet commented Dec 5, 2017
I think I first did the installation through web platform. And then, the VS one. Maybe it was a conflict between the two. I'm not sure what I did, but I could only solve installing the VS Community. VS enterprise was not working even after some repairs and reinstalling it.
robertoprjr commented Jan 24, 2018
@maxamorim, I was with the same problem that you were and when I've changed the language package for English, it works!! Probably some incompatibility with pt-BR
And I get 0x80131500 error code, with no detailed description. Only this: Deployment of application to device failed.
Has anyone encountered such a problem. How it can be solved?
same problem i am facing, i have tried run emulator from Hyper-V manager saparately, it was running successfully. and it is happend after installation of this Windows8.1-KB2917929-x64.msu file installation, i didn't know how to uninstall, i tried to restore, but did not work for me.
12 Answers 12
Windows 8.1 Preview does not support the Windows Phone 8 sdk to run on the Visual Studio 2012 . You cannot run Emulator as well so better you should use a stable Windows 8 version for WP8 development. This is the statement right from Microsoft Support
After you upgrade your OS to Windows 8.1 Preview, you cannot run Windows Phone 8 Software Development Kit (SDK) emulator (XDE.exe) in Microsoft Visual Studio 2012
What is the resolution of this issue. Right now i have installed VS2012 with Update 4 but emulator is not running.
In my case, updating Windows Phone SDK and VS Express 2012 helped on Windows 8.1, but performance is poor. If it's helpful try installing update to VS:
And updating SDK:
For some one who is looking for an answer who has the same issue while working on a virtual environment, here is a nice article on it
Setup: Visual Studio 2013 + Windows 8.1 (no betas) + this did work
Resolution: Restart the Hyper-V service
I'm also receving this error while simulating the program. i hav win 8 only and vs12 windows phone.
but when i serach info. regarding this error i get i have not hyper-v windows feature. try this feature you have or not and enable it..
I found this is the key thing to check, as per (WP8) Emulator (XDE) Troubleshooting Tips on msdn:
Launch the “Network Connections” manager (from the home screen, type in “View Network Connections”, It will be listed under Settings)
Right click on the adapter named: “vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)”
For that adapter, the only items that should be checked under “This connection uses the following items:” should be:
Перечень ошибок, код: 0x80131500 , 0x80072EFD , 0x80072F30 , 0x80072EE7 , 0x80240438 .
При этом компьютер подключен к интернет.
Способы исправления:
- Очистка кеша Microsoft Store;
- Включение протокола TLS 1.2;
- Проверка файла hosts;
- Переустановка Microsoft Store;
- Сброс настроек брандмауэра;
- Установка последних обновлений Windows.
Статья на других языках:
Очистка кеша Microsoft Store
- Нажмите сочетание клавиш Windows+R для открытия диалогового окна Выполнить ;
- Введите wsreset.exe и нажмите кнопку ОК .
Откроется пустое окно командной строки.
Через десять секунд оно закроется и Microsoft Store откроется автоматически.
Включение протокола TLS 1.2
Одной из причин ошибок Microsoft Store может являться отключенный в Windows 10 протокол защиты транспортного уровня TLS 1.2
Использование данного протокола в Windows задается в оснастке Свойства:Интернет (настройки браузера Internet Explorer).
Для включения протокола:
- Нажмите сочетание клавиш Windows+R для открытия диалогового окна Выполнить ;
- Введите inetcpl.cpl и нажмите ОК ;
- Перейдите на вкладку Дополнительно ;
- Отметьте в списке пункт Использовать TLS 1.2 и нажмите ОК .
Повторите попытку запуска Microsoft Store, если проблема была в использовании версии протокола TLS — запуск магазин приложений Windows будет успешен.
💡 Для доступа к этой настройке вы можете запустить браузер Internet Explorer (в Windows 10, папка C:\Program Files\Internet Explorer\ , запустить файл iexplore.exe ), щелкните по кнопке Сервис и выберите Настройки браузера .
Проверка файла hosts
Еще одной причиной ошибки подключения Microsoft Store может являться перенаправление адресов серверов Microsoft на несуществующий (или локальный) сетевой адрес, на локальном компьютере в файле hosts .
hosts — текстовый файл, содержащий базу данных доменных имен и используемый при их трансляции в сетевые адреса узлов. Запрос к этому файлу имеет приоритет перед обращением к DNS-серверам. В отличие от системы DNS, содержимое файла задаётся администратором компьютера.
Википедия
Файл hosts располагается в системной папке Windows 10:
Откройте файл с помощью текстового редактора (например Блокнот).
Пример содержимого чистого файла hosts:
Milan has been enthusiastic about PCs ever since his childhood days, and this led him to take interest in all PC-related technologies. Before joining WindowsReport, he worked as a front-end web developer. Read more
- Some users complained that they get the 0x80131500 error when trying to download apps from the Microsoft Store.
- In order to fix this issue, you should disable certain antivirus and firewall features .
- Changing regional settings can positively affect this error by removing it.
- You can also create a new user account and move all your personal files to the new one.
To fix various PC problems, we recommend Restoro PC Repair Tool:
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
- Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here) .
- Click Start Scan to find Windows issues that could be causing PC problems.
- Click Repair All to fix issues affecting your computer's security and performance
- Restoro has been downloaded by 0 readers this month.
The Microsoft Store is an important part of Windows 10 and 11 since it allows you to download all sorts of applications with ease.
Unfortunately, many users reported error 0x80131500 while trying to use this program, so today we’re going to show you how to fix it.
This type of error is caused by slow Internet connections, a poorly managed DNS server, or a faulty installation of various patches.
Also, another seemingly trivial thing can lead to this annoying error, such as the date and time not being synchronized on your PC.
To see what are the right solutions to quickly solve the error code 0x80131500, below we have detailed all the steps.
How is this error displayed?
The 0x80131505 error can cause many problems on your PC a nd prevent you from using the Microsoft Store. To combat this type of error, it is advisable to check the network connection.
Whether you’re using Wi-Fi or Ethernet, make sure you’re getting not just enough signal, but a very good one before proceeding with our solutions.
Users also reported the following problems:
- 0x80131505 Windows 10 Store – This error usually appears when trying to access Microsoft Store; try some of our solutions
- The server stumbled error code 0x80131500 – It’s just a variation in the message received so you should be able to fix it with the solutions below
- Microsoft Store problems – If you’re having Microsoft Store problems, you might be able to fix this problem by running the Microsoft Store troubleshooter
- Visual Studio error code 0x80131500 – This means that you cannot access the Microsoft server or there are issues with the SQL server (we have prepared a more detailed explanation below, so read on).
0x80131500 with SSIS
Speaking about Visual Studio, there is one particular variation of the infamous code: 0x80131500 that caught our attention.
Apparently, users are unable to install SQL Server Integration Services Projects (in short SSIS) for Visual Studio 2019, but to no avail.
The process is abruptly interrupted by the following errors: SQL server integration services project setup failed: unknown error 0x80131500 or Setup Failed Unknown error (0x80131500).
Here’s what we suggest to fix it:
- Don’t run parallel installations as they can trigger error messages such as the ones mentioned above
- Try updating your SSIS version (users mostly complained about v3.10 and v3.15, so if you’re running any of these versions, consider upgrading or switching to another one)
- Reboot your machine and retry the installation
- Locate msiexec.exe in the Task Manager, stop the process, and retry the installation
Now, we have to stress out the fact that MsiExec.exe is a legitimate Microsoft process that belongs to the Windows Installer package and it helps to install MSI files. This is not a process that you want to permanently remove, but it is worth giving it a shot this one time.
Finally, it’s worth mentioning that Microsoft launched a new version of Visual Studio earlier in February. This fresh version is available in the Microsoft Store, so you might want to check it out as well.
Fortunately, there are plenty of solutions to fix the 0x80131500 error in the Microsoft Store, which you can find below, so read on.
How can I fix the 0x80131500 error on Windows 10 & 11?
1. Check the services
2. Run the Windows Store Apps troubleshooter
If you’re getting 0x80131500 error whenever you try to access Microsoft Store, the problem might be a bug with your Universal apps or the bug with the Microsoft Store itself.
If that’s the case, you might be able to fix the problem simply by running the Windows Store Apps troubleshooter.
3. Reset the Microsoft Store app
4. Re-register all the Microsoft Store apps
5. Uninstall and reinstall Microsoft Store
- Type cmd in the Search tab, then click on Run as administrator to start Command Prompt with full privileges.
- Paste the following command to remove the Microsoft Store apps package: Get-AppxPackage -allusers *WindowsStore* | Remove-AppxPackage
- Now paste the following command to fresh install them: Get-AppxPackage -allusers *WindowsStore* | Foreach
- The apps should work just fine at this point.
6. Run the Windows Update troubleshooter
7. Disable your antivirus and firewall
In some cases, the 0x80131500 error can appear due to your antivirus or firewall that may block some apps.
Having a good antivirus is important if you want to protect yourself from online threats, however, sometimes your antivirus can interfere with Windows apps and cause this problem to appear.
To fix the issue, it might be a good idea to disable certain antivirus features and check if that solves the problem. If your antivirus has a built-in firewall, disable it and check if that helps.
If you can’t find the feature that is causing this, you might want to disable your antivirus entirely.
Sometimes the issue can persist even after you disable your antivirus. If this happens, your last option is to temporarily remove your antivirus from your PC. Once you remove the antivirus, check if the issue still persists.
For the Norton users, we’ve got a dedicated guide on how to uninstall Norton Antivirus with ease .
If you’re using any antivirus solution, and you want to completely remove it from your PC, be sure to check out our amazing list with the best uninstaller software you can use right now.
Assuming that removing the antivirus solves the problem, you should consider switching to a different antivirus. There are many great antivirus solutions available.
We recommend you try an antivirus that offers comprehensive security and online privacy, multi-platform protection, keeps your banking secure, and protects your IoT and webcam.
Expert Tip: Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken. We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.
ESET Internet Security doesn’t interfere with the Microsoft Store, and it offers intelligent security protection for your PC. It’s worth giving it a chance and you won’t be disappointed.
И я получаю код ошибки 0x80131500 без подробного описания. Только это: Не удалось развернуть приложение на устройство.
Кто-нибудь сталкивался с такой проблемой. Как это можно решить?
Windows 8.1 Preview не поддерживает запуск Windows Phone 8 sdk на Visual Studio 2012 . Вы также не можете запустить эмулятор, поэтому лучше использовать стабильную версию Windows 8 version для разработки WP8 . Это заявление прямо из Microsoft Support
После обновления ОС до Windows 8.1 Preview вы не сможете запустить эмулятор Windows Phone 8 Software Development Kit (SDK) (XDE.exe) в Microsoft Visual Studio 2012
Я решил с помощью следующей последовательности ремонта:
Удалите Hyper-V Reboot
DISM.exe / Online / Cleanup-image / Scanhealth
DISM.exe / Online / Cleanup-image / Restorehealth
Перезагрузить Установить Hyper-V
Служба удаленного сервера у вас отключена. Вы можете включить удаленный сервер! И не могу переустановить Hyper-V. у меня это работает!
Попробуйте выполнить следующие действия, если используете VS 2012 с Windows 8.1 Pro:
- Удалить Hyper-V
- перезагрузка
- Установить Hyper-V
- перезагрузка
Это должно помочь.
Я столкнулся с той же проблемой. Позже мне удалось решить эту проблему, загрузив и установив Visual Studio 2012 Update 4 с веб-сайта Microsoft.
Я установил Windows Phone 8 SDK. Эмулятор не работал, потому что Hyper-V не был включен. Я установил Hyper-V из раздела «Программы и компоненты» и получил ошибку 0x80131500.
Visual Studio 2012 с обновлением 4 устраняет проблему.
Я обнаружил, что это ключевая вещь, которую нужно проверить в соответствии с советами по устранению неполадок (WP8) эмулятора (XDE) на msdn:
Запустите менеджер «Сетевые подключения» (на главном экране введите «Просмотр сетевых подключений», он будет указан в разделе «Настройки»).
Щелкните правой кнопкой мыши адаптер с именем: «vEthernet (внутренний коммутатор эмулятора Windows Phone для внутреннего порта Ethernet)».
Для этого адаптера единственными элементами, которые должны быть отмечены в разделе «Это соединение использует следующие элементы:», должны быть:
- Клиент для сетей Microsoft
- Планировщик пакетов QoS
- Общий доступ к файлам и принтерам для сетей Microsoft
- Драйвер протокола Microsoft LLDP
- Драйвер ввода-вывода сопоставителя обнаружения топологии канального уровня
- Ответчик обнаружения топологии канального уровня
- Интернет-протокол версии 6 (TCP / IPv6)
- Интернет-протокол версии 4 (TCP / IPv4)
Все остальные пункты должны быть сняты.
Я также получаю эту ошибку при моделировании программы. У меня только Win 8 и Windows Phone против 12 .
Но когда я ищу информацию. Что касается этой ошибки, я получаю, что у меня нет функции Hyper-V Windows. попробуйте эту функцию у вас есть или нет и включите ее ..
Настройка: Visual Studio 2013 + Windows 8.1 (без бета-версий) + это сработало
Решение: перезапустите службу Hyper-V.
Для тех, кто ищет ответ и сталкивается с той же проблемой при работе в виртуальной среде, здесь хорошая статья об этом
В моем случае обновление Windows Phone SDK и VS Express 2012 помогло в Windows 8.1, но производительность оставляет желать лучшего. Если это полезно, попробуйте установить обновление для VS:
Читайте также: