Ошибка при публикации visual studio

При публикации веб-приложения из Visual Studio разработчик может столкнуться с некоторыми проблемами, и не всегда текст ошибки может помочь избавиться от проблем и правильно настроить сервер.
Ниже я опишу наиболее распространенные из них.
Надеюсь, что данная статья поможет сэкономить время, большое количество которого я потратил при изучении проблем.

Давайте попробуем развернуть приложение на чистый сервер Windows 2008 R2, на котором установлена роль «Web Server (IIS)».

1. Для этого в Visual Studio (у меня Visual Studio 2012 Professional) кликаем правой мышкой на проекте и выбираем пункт меню «Publish…»

Откроется окно мастера публикации, в котором нужно создать профиль

Вводим имя профиля (я назвал профиль также, как называется мой веб-сервер — «app10») и нажимаем кнопку «ОК».
Затем заполняем поля ввода и нажимаем кнопку «Validate Connection».

И тут начинается самое интересное.

2. Валидация завершилась с ошибкой.
Для того, чтобы посмотреть текст ошибки, нужно щелкнуть на гиперссылке «Failed (click for details)»

3. Первая ошибка:
Could not connect to the destination computer ("app10"). On the remote computer, make sure that Web Deploy is installed and that the required process ("The Web Management Service") is started.)

Студия не получила ответа от сервера.
Необходимо проверить настройки веб-сервера (в моем случае он имеет доменное имя «app10»), для чего необходимо зайти в Server Manager (у меня на сервере установлена англоязычная версия Windows 2008 R2, поэтому я буду писать английский наименования пунктов меню и заголовков окон).

4. Откройте диспетчер служб IIS и выберите узел с именем машины:

Я скрыл имя пользователя на скриншоте.

5. В разделе «Management» нужно проверить наличие пунктов «IIS Manager Permissions», «IIS Manager Users» и «Management Service».
У меня их нет, поэтому нужно установить.
Для этого щелкните правой мышкой на пункт «Web Server (IIS)» в левой части окна «Server Manager» и выберите пункт «Add Role Services».
Откроется окно выбора роли.
В разделе «Management Tools» отметьте пункт «Management Service» и нажмите кнопку «Next».

В следующем окне мастера добавления роли нажмите кнопку «Install».

Необходимо дождаться окончания процесса добавления роли и убедиться, что все прошло успешно:

Закрываем окно добавления роли и опять переходим к разделу «Management» (см. пункт 5).
Необходимые нам пункты появились.

6. Необходимо проверить, что Брендмауэр Windows не мешает установлению соединения.
Для этого откройте оснастку «Windows Firewall with Advanced Security», которая находится в меню «Пуск» — «Administrative Tools».
Необходимо убедиться, что входящие соединения на порт 8172 разрешены.
(У меня брендмауэр вообще отключен).

7. Необходимо убедиться, что Web Management Service слушает порт 8172.
Для этого откройте в настройках сервера дважды щелкните мышкой по пункту «Management Service»

В открывшемся окне проверьте, что указан порт 8172, а также разрешите удаленные подключения, установив галочку «Enable remote connection».
Если не поставить эту галочку, то в мастере публикации в Visual Studio будет возникать ошибка:
Could not connect to the remote computer ("app10") using the specified process ("The Web Management Service") because the server did not respond. Make sure that the process ("The Web Management Service") is started on the destination computer. The remote server returned an error: (403) Forbidden.

Теперь нажмите кнопку «Apply» с зеленой галочкой в правой части окна надстроек.
После применения настроек нажмите там же кнопку «Start», что приведет к запуску службы.

8. Переключаемся в Visual Studio и снова нажимаем кнопку «Validate Connection» в мастере публикации.
У меня открылась ошибка сертификата, но ее можно просто игнорировать и нажать кнопку «Accept», предварительно поставив галочку «Save this certificate for future sessions of Visual Studio».

9. После этого у меня возникла ошибка 404:
Could not connect to the remote computer ("app10"). On the destination computer, make sure that Web Deploy is installed and that the required process ("The Web Management Service") is started. The remote server returned an error: (404) Not Found.

Необходимо убедиться, что установлен инструмент «Microsoft Web Deploy 2.0».
Для этого пройдите в «Пуск» — «Control Panel» — «Programs and Features» и проверьте наличие установленного продукта «Microsoft Web Deploy 2.0».
Если его нет, то скачайте его отсюда и установите на сервере.
Во время установки нужно выбрать тип установки «Custom» и выбрать для установки все пункты, предлагаемые инсталлятором:

Выполните установку.

После чего обновите окно «Programs and Features» и он у вас появится.

10. После установки «Microsoft Web Deploy 2.0» необходимо перезапустить службу «Web Management Service».
Теперь нажимаем кнопку «Validate Connection» в мастере публикации в Visual Studio и ВУАЛЯ!!!
Проверка успешно пройдена.

Нажимаем кнопку «Next» дважды и публикуем приложение на веб-сервер, нажав кнопку «Publish».

В завершение данной статьи хочу сказать, что наиболее информативные сообщения при возникновении ошибок во время публикации веб-приложения можно найти в файле логов IIS, который по умолчанию находится по следующему пути:
%SystemDrive%InetpublogsWMSvc
Только помните, что как и в случае с другими журналами IIS, данные не записываются в журнал сразу, так что вам, возможно, придется подождать пару минут, чтобы увидеть последние сообщения, или перезапустить службы веб-управления, чтобы сбросить данные журнала в лог-файл.

Удачи!

UPDATE 03.08.2015

Если во время проверки соединения с сервером (при нажатии на кнопку «Validate Connection») возникает ошибка:
Could not complete an operation with the specified provider ("contentPath") when connecting using the Web Management Service.


необходимо в диспетчере служб IIS выбрать узел с именем машины и дважды кликнуть левой клавишей мыши на пункте «Management Service Delegation»:

В открывшемся окне необходимо добавить новое правило, нажав в правой верхней части на ссылку «Add Rule…» и выбрав пункт «Deploy Applications with Content» и нажав кнопку «ОК»:

В открывшемся окне необходимо указать пользователя, учетные данные которого вы используете для публикации из Visual Studio:

А также в выпадающем меню Providers необходимо дополнительно выбрать пункты «createApp» и «setAcl»:

После нажатия кнопки «ОК» откроется окно добавления пользователя.
Здесь в поле «Name» можно поставить * и нажать кнопку ОК:

После выполнения данных действий, окно правил «Management Service Delegation» будет иметь следующий вид:

И описанная ошибка исчезнет.

UPDATE 19.01.2017

Если во время проверки соединения с сервером (при нажатии на кнопку «Validate Connection») возникает ошибка:
Could not connect to the remote computer ("serverName") 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...

а в конце текста ошибки написано «The remote server returned an error: (550)».

Это говорит о том, что вы опечатались в параметре «Site name» в окне настроек публикации.
Проверьте имя сайта и сравните его с тем, куда публикуете своё приложение.

title	description	ms.custom	ms.date	ms.topic	f1_keywords	dev_langs	helpviewer_keywords	ms.assetid	author	ms.author	manager	ms.technology	ms.workload
Troubleshooting errors (ClickOnce deployments)	This article describes common errors that can occur when you deploy a ClickOnce application and provides steps to resolve each problem.	SEO-VS-2020	11/04/2016	troubleshooting	Microsoft.VisualStudio.Publish.ClickOnceProvider.ErrorPrompt.UncRequired Microsoft.VisualStudio.Publish.ClickOnceProvider.ErrorPrompt.NoInstallUrl	VB CSharp C++	deploying applications, ClickOnce troubleshooting ClickOnce deployments ClickOnce deployment, troubleshooting	22dfe8f1-8271-4708-9c25-6bbb13920ac8	mikejo5000	mikejo	jmartens	vs-ide-deployment	multiple

Troubleshoot specific errors in ClickOnce deployments

[!INCLUDE Visual Studio]
This article lists the following common errors that can occur when you deploy a [!INCLUDEndptecclick] application, and provides steps to resolve each problem.

General errors

When you try to locate an application file, nothing occurs, or XML renders in Internet Explorer, or you receive a Run or Save As dialog box

This error is likely caused by content types (also known as MIME types) not being registered correctly on the server or client.

First, make sure that the server is configured to associate the .application extension with content type «application/x-ms-application.»

If the server is configured correctly, check that the .NET Framework 2.0 is installed on your computer. If the .NET Framework 2.0 is installed, and you are still seeing this problem, try uninstalling and reinstalling the .NET Framework 2.0 to re-register the content type on the client.

Error message says, «Unable to retrieve application. Files missing in deployment» or «Application download has been interrupted, check for network errors and try again later»

This message indicates that one or more files being referenced by the [!INCLUDEndptecclick] manifests cannot be downloaded. The easiest way to debug this error is to try to download the URL that [!INCLUDEndptecclick] says it cannot download. Here are some possible causes:

• If the log file says «(403) Forbidden» or «(404) Not found,» verify that the Web server is configured so that it does not block download of this file. For more information, see Server and Client Configuration Issues in ClickOnce Deployments.

• If the .config file is being blocked by the server, see the section «Download error when you try to install a [!INCLUDEndptecclick] application that has a .config file» later in this article.

• Determine whether this error occurred because the deploymentProvider URL in the deployment manifest is pointing to a different location than the URL used for activation.

• Ensure that all files are present on the server; the [!INCLUDEndptecclick] log should tell you which file was not found.

• See whether there are network connectivity issues; you can receive this message if your client computer went offline during the download.

Download error when you try to install a ClickOnce application that has a .config file

By default, a Visual Basic Windows-based application includes an App.config file. There will be a problem when a user tries to install from a Web server that uses Windows Server 2003, because that operating system blocks the installation of .config files for security reasons. To enable the .config file to be installed, click Use «.deploy» file extension in the Publish Options dialog box.

You also must set the content types (also known as MIME types) appropriately for .application, .manifest, and .deploy files. For more information, see your Web server documentation.

For more information, see «Windows Server 2003: Locked-Down Content Types» in Server and client configuration issues in ClickOnce deployments.

Error message: «Application is improperly formatted;» Log file contains «XML signature is invalid»

Ensure that you updated the manifest file and signed it again. Republish your application by using [!INCLUDEvsprvs] or use Mage to sign the application again.

You updated your application on the server, but the client does not download the update

This problem might be solved by completing one of the following tasks:

• Examine the deploymentProvider URL in the deployment manifest. Ensure that you are updating the bits in the same location that deploymentProvider points to.

• Verify the update interval in the deployment manifest. If this interval is set to a periodic interval, such as one time every six hours, [!INCLUDEndptecclick] will not scan for an update until this interval has passed. You can change the manifest to scan for an update every time that the application starts. Changing the update interval is a convenient option during development time to verify updates are being installed, but it slows down application activation.

• Try starting the application again on the Start menu. [!INCLUDEndptecclick] may have detected the update in the background, but will prompt you to install the bits on the next activation.

During update you receive an error that has the following log entry: «The reference in the deployment does not match the identity defined in the application manifest»

This error may occur because you have manually edited the deployment and application manifests, and have caused the description of the identity of an assembly in one manifest to become out of sync with the other. The identity of an assembly consists of its name, version, culture, and public key token. Examine the identity descriptions in your manifests, and correct any differences.

First time activation from local disk or CD-ROM succeeds, but subsequent activation from Start Menu does not succeed

[!INCLUDEndptecclick] uses the Deployment Provider URL to receive updates for the application. Verify that the location that the URL is pointing to is correct.

Error: «Cannot start the application»

This error message usually indicates that there is a problem installing this application into the [!INCLUDEndptecclick] store. Either the application has an error or the store is corrupted. The log file might tell you where the error occurred.

You should do the following:

• Verify that the identity of the deployment manifest, identity of application manifest, and identity of the main application EXE are all unique.

• Verify that your file paths are not longer than 100 characters. If your application contains file paths that are too long, you may exceed the limitations on the maximum path you can store. Try shortening the paths and reinstall.

PrivatePath settings in application config file are not honored

To use PrivatePath (Fusion probing paths), the application must request full trust permission. Try changing the application manifest to request full trust, and then try again.

During uninstall a message appears saying, «Failed to uninstall application»

This message usually indicates that the application has already been removed or the store is corrupted. After you click OK, the Add/Remove Program entry will be removed.

During installation, a message appears that says that the platform dependencies are not installed

You are missing a prerequisite in the GAC (global assembly cache) that the application needs in order to run.

Publishing with Visual Studio

Publishing in Visual Studio fails

Ensure that you have the right to publish to the server that you are targeting. For example, if you are logged in to a terminal server computer as an ordinary user, not as an administrator, you probably will not have the rights required to publish to the local Web server.

If you are publishing with a URL, ensure that the destination computer has FrontPage Server Extensions enabled.

Error message: Unable to create the Web site ‘<site>’. The components for communicating with FrontPage Server Extensions are not installed.

Ensure that you have the Microsoft Visual Studio Web Authoring Component installed on the machine that you are publishing from. For Express users, this component is not installed by default.

Error message: Could not find file ‘Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b64144ccf1df, ProcessorArchitecture=*, Type=win32’

This error message appears when you attempt to publish a WPF application with visual styles enabled. To resolve this issue, see How to: Publish a WPF Application with Visual Styles Enabled.

Using Mage

You tried to sign with a certificate in your certificate store and a received blank message box

In the Signing dialog box, you must:

• Select Sign with a stored certificate, and

• Select a certificate from the list; the first certificate is not the default selection.

Clicking the «Don’t Sign» button causes an exception

This issue is a known bug. All [!INCLUDEndptecclick] manifests are required to be signed. Just select one of the signing options, and then click OK.

Additional errors

The following table shows some common error messages that a client-computer user may receive when the user installs a [!INCLUDEndptecclick] application. Each error message is listed next to a description of the most probable cause for the error.

Error message	Description
Application cannot be started. Contact the application publisher. Cannot start the application. Contact the application vendor for assistance.	These are generic error messages that occur when the application cannot be started, and no other specific reason can be found. Frequently this means that the application is somehow corrupted, or that the [!INCLUDEndptecclick] store is corrupted.
Cannot continue. The application is improperly formatted. Contact the application publisher for assistance. Application validation did not succeed. Unable to continue. Unable to retrieve application files. Files corrupt in deployment.	One of the manifest files in the deployment is syntactically not valid, or contains a hash that cannot be reconciled with the corresponding file. This error may also indicate that the manifest embedded inside an assembly is corrupted. Re-create your deployment and recompile your application, or find and fix the errors manually in your manifests.
Cannot retrieve application. Authentication error. Application installation did not succeed. Cannot locate applications files on the server. Contact the application publisher or your administrator for assistance.	One or more files in the deployment cannot be downloaded because you do not have permission to access them. This can be caused by a 403 Forbidden error being returned by a Web server, which may occur if one of the files in your deployment ends with an extension that makes the Web server treat it as a protected file. Also, a directory that contains one or more of the application’s files might require a username and password in order to access.
Cannot download the application. The application is missing required files. Contact the application vendor or your system administrator for assistance.	One or more of the files listed in the application manifest cannot be found on the server. Check that you have uploaded all the deployment’s dependent files, and try again.
Application download did not succeed. Check your network connection, or contact your system administrator or network service provider.	[!INCLUDEndptecclick] cannot establish a network connection to the server. Examine the server’s availability and the state of your network.
URLDownloadToCacheFile failed with HRESULT ‘<number>’. An error occurred trying to download ‘<file>’.	If a user has set Internet Explorer Advanced Security option «Warn if changing between secure and not secure mode» on the deployment target computer, and if the setup URL of the ClickOnce application being installed is redirected from a non-secure to a secure site (or vice-versa), the installation will fail because the Internet Explorer warning interrupts it. To resolve this error, you can do one of the following tasks: — Clear the security option. — Make sure the setup URL is not redirected in such a way that changes security modes. — Remove the redirection completely and point to the actual setup URL.
An error has occurred writing to the hard disk. There might be insufficient space available on the disk. Contact the application vendor or your system administrator for assistance.	This may indicate insufficient disk space for storing the application, but it may also indicate a more general I/O error when you are trying to save the application files to the drive.
Cannot start the application. There is not enough available space on the disk.	The hard disk is full. Clear off space and try to run the application again.
Too many deployed activations are attempting to load at once.	[!INCLUDEndptecclick] limits the number of different applications that can start at the same time. This is largely to help protect against malicious attempts to instigate denial-of-service attacks against the local [!INCLUDEndptecclick] service; users who try to start the same application repeatedly, in rapid succession, will only end up with a single instance of the application.
Shortcuts cannot be activated over the network.	Shortcuts to a [!INCLUDEndptecclick] application can only be started on the local hard disk. They cannot be started by opening a URL that points to a shortcut file on a remote server.
The application is too large to run online in partial trust. Contact the application vendor or your system administrator for assistance.	An application that runs in partial trust cannot be larger than half of the size of the online application quota, which by default is 250 MB.

See also

• ClickOnce security and deployment
• Troubleshoot ClickOnce deployments
• Visual Studio troubleshooting

title	description	ms.custom	ms.date	ms.topic	f1_keywords	dev_langs	helpviewer_keywords	ms.assetid	author	ms.author	manager	ms.technology	ms.workload
Troubleshooting errors (ClickOnce deployments)	This article describes common errors that can occur when you deploy a ClickOnce application and provides steps to resolve each problem.	SEO-VS-2020	11/04/2016	troubleshooting	Microsoft.VisualStudio.Publish.ClickOnceProvider.ErrorPrompt.UncRequired Microsoft.VisualStudio.Publish.ClickOnceProvider.ErrorPrompt.NoInstallUrl	VB CSharp C++	deploying applications, ClickOnce troubleshooting ClickOnce deployments ClickOnce deployment, troubleshooting	22dfe8f1-8271-4708-9c25-6bbb13920ac8	mikejo5000	mikejo	jmartens	vs-ide-deployment	multiple

Troubleshoot specific errors in ClickOnce deployments

[!INCLUDE Visual Studio]
This article lists the following common errors that can occur when you deploy a [!INCLUDEndptecclick] application, and provides steps to resolve each problem.

General errors

When you try to locate an application file, nothing occurs, or XML renders in Internet Explorer, or you receive a Run or Save As dialog box

This error is likely caused by content types (also known as MIME types) not being registered correctly on the server or client.

First, make sure that the server is configured to associate the .application extension with content type «application/x-ms-application.»

If the server is configured correctly, check that the .NET Framework 2.0 is installed on your computer. If the .NET Framework 2.0 is installed, and you are still seeing this problem, try uninstalling and reinstalling the .NET Framework 2.0 to re-register the content type on the client.

Error message says, «Unable to retrieve application. Files missing in deployment» or «Application download has been interrupted, check for network errors and try again later»

This message indicates that one or more files being referenced by the [!INCLUDEndptecclick] manifests cannot be downloaded. The easiest way to debug this error is to try to download the URL that [!INCLUDEndptecclick] says it cannot download. Here are some possible causes:

• If the log file says «(403) Forbidden» or «(404) Not found,» verify that the Web server is configured so that it does not block download of this file. For more information, see Server and Client Configuration Issues in ClickOnce Deployments.

• If the .config file is being blocked by the server, see the section «Download error when you try to install a [!INCLUDEndptecclick] application that has a .config file» later in this article.

• Determine whether this error occurred because the deploymentProvider URL in the deployment manifest is pointing to a different location than the URL used for activation.

• Ensure that all files are present on the server; the [!INCLUDEndptecclick] log should tell you which file was not found.

• See whether there are network connectivity issues; you can receive this message if your client computer went offline during the download.

Download error when you try to install a ClickOnce application that has a .config file

By default, a Visual Basic Windows-based application includes an App.config file. There will be a problem when a user tries to install from a Web server that uses Windows Server 2003, because that operating system blocks the installation of .config files for security reasons. To enable the .config file to be installed, click Use «.deploy» file extension in the Publish Options dialog box.

You also must set the content types (also known as MIME types) appropriately for .application, .manifest, and .deploy files. For more information, see your Web server documentation.

For more information, see «Windows Server 2003: Locked-Down Content Types» in Server and client configuration issues in ClickOnce deployments.

Error message: «Application is improperly formatted;» Log file contains «XML signature is invalid»

Ensure that you updated the manifest file and signed it again. Republish your application by using [!INCLUDEvsprvs] or use Mage to sign the application again.

You updated your application on the server, but the client does not download the update

This problem might be solved by completing one of the following tasks:

• Examine the deploymentProvider URL in the deployment manifest. Ensure that you are updating the bits in the same location that deploymentProvider points to.

• Verify the update interval in the deployment manifest. If this interval is set to a periodic interval, such as one time every six hours, [!INCLUDEndptecclick] will not scan for an update until this interval has passed. You can change the manifest to scan for an update every time that the application starts. Changing the update interval is a convenient option during development time to verify updates are being installed, but it slows down application activation.

• Try starting the application again on the Start menu. [!INCLUDEndptecclick] may have detected the update in the background, but will prompt you to install the bits on the next activation.

During update you receive an error that has the following log entry: «The reference in the deployment does not match the identity defined in the application manifest»

This error may occur because you have manually edited the deployment and application manifests, and have caused the description of the identity of an assembly in one manifest to become out of sync with the other. The identity of an assembly consists of its name, version, culture, and public key token. Examine the identity descriptions in your manifests, and correct any differences.

First time activation from local disk or CD-ROM succeeds, but subsequent activation from Start Menu does not succeed

[!INCLUDEndptecclick] uses the Deployment Provider URL to receive updates for the application. Verify that the location that the URL is pointing to is correct.

Error: «Cannot start the application»

This error message usually indicates that there is a problem installing this application into the [!INCLUDEndptecclick] store. Either the application has an error or the store is corrupted. The log file might tell you where the error occurred.

You should do the following:

• Verify that the identity of the deployment manifest, identity of application manifest, and identity of the main application EXE are all unique.

• Verify that your file paths are not longer than 100 characters. If your application contains file paths that are too long, you may exceed the limitations on the maximum path you can store. Try shortening the paths and reinstall.

PrivatePath settings in application config file are not honored

To use PrivatePath (Fusion probing paths), the application must request full trust permission. Try changing the application manifest to request full trust, and then try again.

During uninstall a message appears saying, «Failed to uninstall application»

This message usually indicates that the application has already been removed or the store is corrupted. After you click OK, the Add/Remove Program entry will be removed.

During installation, a message appears that says that the platform dependencies are not installed

You are missing a prerequisite in the GAC (global assembly cache) that the application needs in order to run.

Publishing with Visual Studio

Publishing in Visual Studio fails

Ensure that you have the right to publish to the server that you are targeting. For example, if you are logged in to a terminal server computer as an ordinary user, not as an administrator, you probably will not have the rights required to publish to the local Web server.

If you are publishing with a URL, ensure that the destination computer has FrontPage Server Extensions enabled.

Error message: Unable to create the Web site ‘<site>’. The components for communicating with FrontPage Server Extensions are not installed.

Ensure that you have the Microsoft Visual Studio Web Authoring Component installed on the machine that you are publishing from. For Express users, this component is not installed by default.

Error message: Could not find file ‘Microsoft.Windows.Common-Controls, Version=6.0.0.0, Culture=*, PublicKeyToken=6595b64144ccf1df, ProcessorArchitecture=*, Type=win32’

This error message appears when you attempt to publish a WPF application with visual styles enabled. To resolve this issue, see How to: Publish a WPF Application with Visual Styles Enabled.

Using Mage

You tried to sign with a certificate in your certificate store and a received blank message box

In the Signing dialog box, you must:

• Select Sign with a stored certificate, and

• Select a certificate from the list; the first certificate is not the default selection.

Clicking the «Don’t Sign» button causes an exception

This issue is a known bug. All [!INCLUDEndptecclick] manifests are required to be signed. Just select one of the signing options, and then click OK.

Additional errors

The following table shows some common error messages that a client-computer user may receive when the user installs a [!INCLUDEndptecclick] application. Each error message is listed next to a description of the most probable cause for the error.

Error message	Description
Application cannot be started. Contact the application publisher. Cannot start the application. Contact the application vendor for assistance.	These are generic error messages that occur when the application cannot be started, and no other specific reason can be found. Frequently this means that the application is somehow corrupted, or that the [!INCLUDEndptecclick] store is corrupted.
Cannot continue. The application is improperly formatted. Contact the application publisher for assistance. Application validation did not succeed. Unable to continue. Unable to retrieve application files. Files corrupt in deployment.	One of the manifest files in the deployment is syntactically not valid, or contains a hash that cannot be reconciled with the corresponding file. This error may also indicate that the manifest embedded inside an assembly is corrupted. Re-create your deployment and recompile your application, or find and fix the errors manually in your manifests.
Cannot retrieve application. Authentication error. Application installation did not succeed. Cannot locate applications files on the server. Contact the application publisher or your administrator for assistance.	One or more files in the deployment cannot be downloaded because you do not have permission to access them. This can be caused by a 403 Forbidden error being returned by a Web server, which may occur if one of the files in your deployment ends with an extension that makes the Web server treat it as a protected file. Also, a directory that contains one or more of the application’s files might require a username and password in order to access.
Cannot download the application. The application is missing required files. Contact the application vendor or your system administrator for assistance.	One or more of the files listed in the application manifest cannot be found on the server. Check that you have uploaded all the deployment’s dependent files, and try again.
Application download did not succeed. Check your network connection, or contact your system administrator or network service provider.	[!INCLUDEndptecclick] cannot establish a network connection to the server. Examine the server’s availability and the state of your network.
URLDownloadToCacheFile failed with HRESULT ‘<number>’. An error occurred trying to download ‘<file>’.	If a user has set Internet Explorer Advanced Security option «Warn if changing between secure and not secure mode» on the deployment target computer, and if the setup URL of the ClickOnce application being installed is redirected from a non-secure to a secure site (or vice-versa), the installation will fail because the Internet Explorer warning interrupts it. To resolve this error, you can do one of the following tasks: — Clear the security option. — Make sure the setup URL is not redirected in such a way that changes security modes. — Remove the redirection completely and point to the actual setup URL.
An error has occurred writing to the hard disk. There might be insufficient space available on the disk. Contact the application vendor or your system administrator for assistance.	This may indicate insufficient disk space for storing the application, but it may also indicate a more general I/O error when you are trying to save the application files to the drive.
Cannot start the application. There is not enough available space on the disk.	The hard disk is full. Clear off space and try to run the application again.
Too many deployed activations are attempting to load at once.	[!INCLUDEndptecclick] limits the number of different applications that can start at the same time. This is largely to help protect against malicious attempts to instigate denial-of-service attacks against the local [!INCLUDEndptecclick] service; users who try to start the same application repeatedly, in rapid succession, will only end up with a single instance of the application.
Shortcuts cannot be activated over the network.	Shortcuts to a [!INCLUDEndptecclick] application can only be started on the local hard disk. They cannot be started by opening a URL that points to a shortcut file on a remote server.
The application is too large to run online in partial trust. Contact the application vendor or your system administrator for assistance.	An application that runs in partial trust cannot be larger than half of the size of the online application quota, which by default is 250 MB.

See also

• ClickOnce security and deployment
• Troubleshoot ClickOnce deployments
• Visual Studio troubleshooting

Не могу опубликовать абсолютно любой проект (даже пустой) в Visual Studio 2019 Community.
В журнале вывода такая информация:

2>------ Начало публикации: проект: Empty1, Конфигурация: Release Any CPU ------
2>Определение проектов для восстановления...
2>Не удалось загрузить индекс службы для источника https://api.nuget.org/v3/index.json.
2>  Произошла ошибка при отправке запроса.
2>  Запрос был прерван: Не удалось создать защищенный канал SSL/TLS.
========== Сборка: успешно: 1, с ошибками: 0, без изменений: 0, пропущено: 0 ==========
========== Публикация: успешно: 0, с ошибками: 1, пропущено: 0 ==========

В файле «tmp4D94.tmp» такая информация:

22.09.2021 17:05:44
System.AggregateException: Произошла одна или несколько ошибок. ---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: При публикации произошла ошибка. Не удалось определить причину ошибки. Дополнительные сведения см. в журнале вывода.
--- Конец трассировки внутреннего стека исключений ---

В чем проблема, уважаемые пользователи?

Время на прочтение
5 мин

Количество просмотров 43K

При публикации веб-приложения из Visual Studio разработчик может столкнуться с некоторыми проблемами, и не всегда текст ошибки может помочь избавиться от проблем и правильно настроить сервер.
Ниже я опишу наиболее распространенные из них.
Надеюсь, что данная статья поможет сэкономить время, большое количество которого я потратил при изучении проблем.

Давайте попробуем развернуть приложение на чистый сервер Windows 2008 R2, на котором установлена роль «Web Server (IIS)».

1. Для этого в Visual Studio (у меня Visual Studio 2012 Professional) кликаем правой мышкой на проекте и выбираем пункт меню «Publish…»

Откроется окно мастера публикации, в котором нужно создать профиль

Вводим имя профиля (я назвал профиль также, как называется мой веб-сервер — «app10») и нажимаем кнопку «ОК».
Затем заполняем поля ввода и нажимаем кнопку «Validate Connection».

И тут начинается самое интересное.

2. Валидация завершилась с ошибкой.
Для того, чтобы посмотреть текст ошибки, нужно щелкнуть на гиперссылке «Failed (click for details)»

3. Первая ошибка:
Could not connect to the destination computer ("app10"). On the remote computer, make sure that Web Deploy is installed and that the required process ("The Web Management Service") is started.)

Студия не получила ответа от сервера.
Необходимо проверить настройки веб-сервера (в моем случае он имеет доменное имя «app10»), для чего необходимо зайти в Server Manager (у меня на сервере установлена англоязычная версия Windows 2008 R2, поэтому я буду писать английский наименования пунктов меню и заголовков окон).

4. Откройте диспетчер служб IIS и выберите узел с именем машины:

Я скрыл имя пользователя на скриншоте.

5. В разделе «Management» нужно проверить наличие пунктов «IIS Manager Permissions», «IIS Manager Users» и «Management Service».
У меня их нет, поэтому нужно установить.
Для этого щелкните правой мышкой на пункт «Web Server (IIS)» в левой части окна «Server Manager» и выберите пункт «Add Role Services».
Откроется окно выбора роли.
В разделе «Management Tools» отметьте пункт «Management Service» и нажмите кнопку «Next».

В следующем окне мастера добавления роли нажмите кнопку «Install».

Необходимо дождаться окончания процесса добавления роли и убедиться, что все прошло успешно:

Закрываем окно добавления роли и опять переходим к разделу «Management» (см. пункт 5).
Необходимые нам пункты появились.

6. Необходимо проверить, что Брендмауэр Windows не мешает установлению соединения.
Для этого откройте оснастку «Windows Firewall with Advanced Security», которая находится в меню «Пуск» — «Administrative Tools».
Необходимо убедиться, что входящие соединения на порт 8172 разрешены.
(У меня брендмауэр вообще отключен).

7. Необходимо убедиться, что Web Management Service слушает порт 8172.
Для этого откройте в настройках сервера дважды щелкните мышкой по пункту «Management Service»

В открывшемся окне проверьте, что указан порт 8172, а также разрешите удаленные подключения, установив галочку «Enable remote connection».
Если не поставить эту галочку, то в мастере публикации в Visual Studio будет возникать ошибка:
Could not connect to the remote computer ("app10") using the specified process ("The Web Management Service") because the server did not respond. Make sure that the process ("The Web Management Service") is started on the destination computer. The remote server returned an error: (403) Forbidden.

Теперь нажмите кнопку «Apply» с зеленой галочкой в правой части окна надстроек.
После применения настроек нажмите там же кнопку «Start», что приведет к запуску службы.

8. Переключаемся в Visual Studio и снова нажимаем кнопку «Validate Connection» в мастере публикации.
У меня открылась ошибка сертификата, но ее можно просто игнорировать и нажать кнопку «Accept», предварительно поставив галочку «Save this certificate for future sessions of Visual Studio».

9. После этого у меня возникла ошибка 404:
Could not connect to the remote computer ("app10"). On the destination computer, make sure that Web Deploy is installed and that the required process ("The Web Management Service") is started. The remote server returned an error: (404) Not Found.

Необходимо убедиться, что установлен инструмент «Microsoft Web Deploy 2.0».
Для этого пройдите в «Пуск» — «Control Panel» — «Programs and Features» и проверьте наличие установленного продукта «Microsoft Web Deploy 2.0».
Если его нет, то скачайте его отсюда и установите на сервере.
Во время установки нужно выбрать тип установки «Custom» и выбрать для установки все пункты, предлагаемые инсталлятором:

Выполните установку.

После чего обновите окно «Programs and Features» и он у вас появится.

10. После установки «Microsoft Web Deploy 2.0» необходимо перезапустить службу «Web Management Service».
Теперь нажимаем кнопку «Validate Connection» в мастере публикации в Visual Studio и ВУАЛЯ!!!
Проверка успешно пройдена.

Нажимаем кнопку «Next» дважды и публикуем приложение на веб-сервер, нажав кнопку «Publish».

В завершение данной статьи хочу сказать, что наиболее информативные сообщения при возникновении ошибок во время публикации веб-приложения можно найти в файле логов IIS, который по умолчанию находится по следующему пути:
%SystemDrive%InetpublogsWMSvc
Только помните, что как и в случае с другими журналами IIS, данные не записываются в журнал сразу, так что вам, возможно, придется подождать пару минут, чтобы увидеть последние сообщения, или перезапустить службы веб-управления, чтобы сбросить данные журнала в лог-файл.

Удачи!

UPDATE 03.08.2015

Если во время проверки соединения с сервером (при нажатии на кнопку «Validate Connection») возникает ошибка:
Could not complete an operation with the specified provider ("contentPath") when connecting using the Web Management Service.


необходимо в диспетчере служб IIS выбрать узел с именем машины и дважды кликнуть левой клавишей мыши на пункте «Management Service Delegation»:

В открывшемся окне необходимо добавить новое правило, нажав в правой верхней части на ссылку «Add Rule…» и выбрав пункт «Deploy Applications with Content» и нажав кнопку «ОК»:

В открывшемся окне необходимо указать пользователя, учетные данные которого вы используете для публикации из Visual Studio:

А также в выпадающем меню Providers необходимо дополнительно выбрать пункты «createApp» и «setAcl»:

После нажатия кнопки «ОК» откроется окно добавления пользователя.
Здесь в поле «Name» можно поставить * и нажать кнопку ОК:

После выполнения данных действий, окно правил «Management Service Delegation» будет иметь следующий вид:

И описанная ошибка исчезнет.

UPDATE 19.01.2017

Если во время проверки соединения с сервером (при нажатии на кнопку «Validate Connection») возникает ошибка:
Could not connect to the remote computer ("serverName") 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...

а в конце текста ошибки написано «The remote server returned an error: (550)».

Это говорит о том, что вы опечатались в параметре «Site name» в окне настроек публикации.
Проверьте имя сайта и сравните его с тем, куда публикуете своё приложение.