An unknown wininet error has occurred code 12113

FTP Publish Error in Visual Studio — An unknown WinINet error has occurred (code 12113) — How to fix it

A rather common issue that you can experience while working with Visual Studio — be it 2010, 2013, 2015 and even 2017 — is the following error appearing on your Output window right after you try to publish your project to a remote FTP location:

Unable to add ‘file.ext’ to the Web site. An unknown WinINet error has occurred (code 12113).

This usually means that there are networking/connection issues between your Visual Studio development machine and the remote FTP server. To fix the issue you can try one of the following methods:

Enable the FTP Passive Mode

The first thing you can try is to enable FTP Passive mode on your publish settings configuration, so FTP will be able to work even behind NAT routers or dedicated firewalls. To change your publish settings, right-click to the project node in Solution Explorer, then select Publish. to access the modal window. Select your publishing template from the drop-down list, navigate to the Connection tab and activate Passive mode in the following way:

In most cases this will enough. However, chances are that your FTP server is unable to support Passive mode. If that’s the case, your Output window will show the following error:

Unable to add ‘file.ext’ to the Web site. FTP Passive Mode is not available.

If you get this and are unable to set your FTP server to allow Passive mode connections, keep reading: the same goes if you are unable to fix your issue this way.

Allow inbound connections for Visual Studio

The next thing you can try is to configure your built-in Windows Firewall (or any other firewall you have replaced it with) to accept inbound connections to the Visual Studio main executable file, which is the devenv.exe (usually located in C : Program Files ( x86 ) Microsoft Visual Studio XY . Z Common7 IDE , where XY.Z are the Visual Studio build numbers (find yours here). You can do that by creating a custom inbound rule in your firewall pointing to that file.

If you’re using Windows Firewall, here’s how you can do that:

• Open the Control Panel by right-clicking to the bottom-left Windows icon.
• Select the Windows Firewall icon.
• Select Advanced Settings from the left navigation panel.
• Add a new Inbound Rule for the devenv.exe executable file (check the full path here).
• In the Advanced menu, activate the rule for all profiles (Public, Private and Domain) and also be sure that Allow Edge Traversal is selected in the appropriate dropdown list as in the screenshow below:

That should do it. However, in case you still have issues, keep reading.

Deactivate Port-Blocking Software

If you’re still getting that error — or are otherwise unable to estabilish a proper FTP connection — after the above workarounds, it probably means that there’s something in your system which is either blocking or scanning your port(s), thus preventing VS from properly communicating with the server. This is a list of the software you could try to temporarily disable in order to overcome your issue:

• Antivirus software such as Kaspersky, BitDefender, Avira, AVG
• Web Content filters such as Kerio Control
• Web Protection Suites such as Symantec, McAfee and so on
• Internet proxies and/or software TCP/IP filters
• Windows Firewall (or other Firewall software)

Be sure to promptly reactivate them right after you find the culprit — and/or execute your upload. If the issue is still there, it could be also wise to perform a virus/malware scan, just in case.

That’s it for now: happy publishing!

About Ryan

IT Project Manager, Web Interface Architect and Lead Developer for many high-traffic web sites & services hosted in Italy and Europe. Since 2010 it’s also a lead designer for many App and games for Android, iOS and Windows Phone mobile devices for a number of italian companies. Microsoft MVP for Development Technologies since 2018.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

An unknown wininet error has occurred code 12113

Лучший отвечающий

Вопрос

I’m running ASDK with SQL and App Service providers, they seems working just fine. I successfully created a web app and was able to browser the site and open the home page. I downloaded the «publish Profile».

However, when I tried to deploy/publish a Web App application from Visual Studio 2017, got an error. From VS publish menu, I selected Import profile, then selected the previous downloaded profile.

When I selected WebDeploy, the validation fails: Cannot connect to remote computer.

Web deployment task failed. (Could not connect to the remote computer («eateamportal.scm.appservice.local.azurestack.external») using the specified process («Web Management Service») because the server did not respond. Make sure that the process («Web Management Service») is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)

When I tried FTP deploy, first, it errored out on passive mode. So, I unchecked «Passive Mode» for FTP, then got following error:

2>Copying all files to temporary location below for package/publish:
2>objReleasePackagePackageTmp.
2>Publishing folder /.
2>Unable to add ‘ApplicationInsights.config’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘favicon.ico’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘Global.asax’ to the Web site. An unknown WinINet error has occurred (code 12113).

Any suggestions to fix it. What’s the right process to build and deploy web project to Azure Stack? I couldn’t find any instructions on deploying to Azure Stack from VS directly. There are some instructions about using VSTS, but my company is not using VSTS.

Источник

An unknown wininet error has occurred code 12113

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m running ASDK with SQL and App Service providers, they seems working just fine. I successfully created a web app and was able to browser the site and open the home page. I downloaded the «publish Profile».

However, when I tried to deploy/publish a Web App application from Visual Studio 2017, got an error. From VS publish menu, I selected Import profile, then selected the previous downloaded profile.

When I selected WebDeploy, the validation fails: Cannot connect to remote computer.

Web deployment task failed. (Could not connect to the remote computer («eateamportal.scm.appservice.local.azurestack.external») using the specified process («Web Management Service») because the server did not respond. Make sure that the process («Web Management Service») is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)

When I tried FTP deploy, first, it errored out on passive mode. So, I unchecked «Passive Mode» for FTP, then got following error:

2>Copying all files to temporary location below for package/publish:
2>objReleasePackagePackageTmp.
2>Publishing folder /.
2>Unable to add ‘ApplicationInsights.config’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘favicon.ico’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘Global.asax’ to the Web site. An unknown WinINet error has occurred (code 12113).

Any suggestions to fix it. What’s the right process to build and deploy web project to Azure Stack? I couldn’t find any instructions on deploying to Azure Stack from VS directly. There are some instructions about using VSTS, but my company is not using VSTS.

Источник

An unknown wininet error has occurred code 12113

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m running ASDK with SQL and App Service providers, they seems working just fine. I successfully created a web app and was able to browser the site and open the home page. I downloaded the «publish Profile».

However, when I tried to deploy/publish a Web App application from Visual Studio 2017, got an error. From VS publish menu, I selected Import profile, then selected the previous downloaded profile.

When I selected WebDeploy, the validation fails: Cannot connect to remote computer.

Web deployment task failed. (Could not connect to the remote computer («eateamportal.scm.appservice.local.azurestack.external») using the specified process («Web Management Service») because the server did not respond. Make sure that the process («Web Management Service») is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)

When I tried FTP deploy, first, it errored out on passive mode. So, I unchecked «Passive Mode» for FTP, then got following error:

2>Copying all files to temporary location below for package/publish:
2>objReleasePackagePackageTmp.
2>Publishing folder /.
2>Unable to add ‘ApplicationInsights.config’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘favicon.ico’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘Global.asax’ to the Web site. An unknown WinINet error has occurred (code 12113).

Any suggestions to fix it. What’s the right process to build and deploy web project to Azure Stack? I couldn’t find any instructions on deploying to Azure Stack from VS directly. There are some instructions about using VSTS, but my company is not using VSTS.

Источник

An unknown wininet error has occurred code 12113

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I’m running ASDK with SQL and App Service providers, they seems working just fine. I successfully created a web app and was able to browser the site and open the home page. I downloaded the «publish Profile».

However, when I tried to deploy/publish a Web App application from Visual Studio 2017, got an error. From VS publish menu, I selected Import profile, then selected the previous downloaded profile.

When I selected WebDeploy, the validation fails: Cannot connect to remote computer.

Web deployment task failed. (Could not connect to the remote computer («eateamportal.scm.appservice.local.azurestack.external») using the specified process («Web Management Service») because the server did not respond. Make sure that the process («Web Management Service») is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)

When I tried FTP deploy, first, it errored out on passive mode. So, I unchecked «Passive Mode» for FTP, then got following error:

2>Copying all files to temporary location below for package/publish:
2>objReleasePackagePackageTmp.
2>Publishing folder /.
2>Unable to add ‘ApplicationInsights.config’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘favicon.ico’ to the Web site. An unknown WinINet error has occurred (code 12113).
2>Unable to add ‘Global.asax’ to the Web site. An unknown WinINet error has occurred (code 12113).

Any suggestions to fix it. What’s the right process to build and deploy web project to Azure Stack? I couldn’t find any instructions on deploying to Azure Stack from VS directly. There are some instructions about using VSTS, but my company is not using VSTS.

Источник

A rather common issue that you can experience while working with Visual Studio — be it 2010, 2013, 2015 and even 2017 — is the following error appearing on your Output window right after you try to publish your project to a remote FTP location:

Unable to add ‘file.ext’ to the Web site. An unknown WinINet error has occurred (code 12113).

This usually means that there are networking/connection issues between your Visual Studio development machine and the remote FTP server. To fix the issue you can try one of the following methods:

Enable the FTP Passive Mode

The first thing you can try is to enable FTP Passive mode on your publish settings configuration, so FTP will be able to work even behind NAT routers or dedicated firewalls. To change your publish settings, right-click to the project node in Solution Explorer, then select Publish… to access the modal window. Select your publishing template from the drop-down list, navigate to the Connection tab and activate Passive mode in the following way:

In most cases this will enough. However, chances are that your FTP server is unable to support Passive mode. If that’s the case, your Output window will show the following error:

Unable to add ‘file.ext’ to the Web site. FTP Passive Mode is not available.

If you get this and are unable to set your FTP server to allow Passive mode connections, keep reading: the same goes if you are unable to fix your issue this way.

Allow inbound connections for Visual Studio

The next thing you can try is to configure your built-in Windows Firewall (or any other firewall you have replaced it with) to accept inbound connections to the Visual Studio main executable file, which is the devenv.exe (usually located in
C:Program Files (x86)Microsoft Visual Studio XY.ZCommon7IDE , where XY.Z are the Visual Studio build numbers (find yours here). You can do that by creating a custom inbound rule in your firewall pointing to that file.

If you’re using Windows Firewall, here’s how you can do that:

• Open the Control Panel by right-clicking to the bottom-left Windows icon.
• Select the Windows Firewall icon.
• Select Advanced Settings from the left navigation panel.
• Add a new Inbound Rule for the devenv.exe executable file (check the full path here).
• In the Advanced menu, activate the rule for all profiles (Public, Private and Domain) and also be sure that Allow Edge Traversal is selected in the appropriate dropdown list as in the screenshow below:

That should do it. However, in case you still have issues, keep reading.

Deactivate Port-Blocking Software

If you’re still getting that error — or are otherwise unable to estabilish a proper FTP connection — after the above workarounds, it probably means that there’s something in your system which is either blocking or scanning your port(s), thus preventing VS from properly communicating with the server. This is a list of the software you could try to temporarily disable in order to overcome your issue:

• Antivirus software such as Kaspersky, BitDefender, Avira, AVG
• Web Content filters such as Kerio Control
• Web Protection Suites such as Symantec, McAfee and so on
• Internet proxies and/or software TCP/IP filters
• Windows Firewall (or other Firewall software)

Be sure to promptly reactivate them right after you find the culprit — and/or execute your upload. If the issue is still there, it could be also wise to perform a virus/malware scan, just in case.

That’s it for now: happy publishing!

How
to: Create an Inbound Rule in Windows Firewall for the Port of Microsoft
Dynamics NAV Web Client

This
procedure describes how to modify Windows Firewall to allow inbound
communication on the port that is used by the Microsoft Dynamics NAV Web
client. By default, the port is 8080. You use this procedure after you install
the Microsoft Dynamics NAV Web Server components on a computer that is running
Windows 7 or if you change the Microsoft Dynamics NAV Web client port to a port
other than 8080.

To create an inbound rule