Errors when you use the Web Deployment tool as a delegated user over a remote IIS manager connection

This article helps you resolve an unexpected error that occurs when you use the Web Deployment Tool (Web Deploy) as a delegated user over a remote Microsoft Internet Information Services (IIS) manager connection via the Web Management Service (WMSVC).

Original product version:   Internet Information Services
Original KB number:   2023855


When you perform Web Deploy operations remotely through IIS Manager and are using the Web Management Service (WMSVC), you may receive an error message that's similar to the following example:

An error occurred when the request was processed on the remote computer.
Attempted to perform an unauthorized operation.


The problem occurs because the user hasn't been granted permissions to perform the action for the specified provider. The server administrator has to determine the provider and user that are affected, the permissions that are necessary (for example, Read or Write), and the path that is being used.


The resolution will vary depending on the message returned and the provider specified. Consult the following resources for instrumentation to assist in diagnosing the problem:

Below are some of the common issues that may be met in this scenario:

401 unauthorized when connecting to a Web site

Possible causes: This error comes from WMSVC and is usually an error with a username or password, or because the user doesn't have access to the web site.

Resolution: Verify the username and password and that the user has access to the web site.

Server error when importing or exporting an application

Possible causes: This error comes from the Web Deployment Handler and is usually a problem with the deployment rules. Since the user has connected successfully, it is not an issue with WMSVC. A deployment rule has a typo, the user perform deployment may not be authorized, or the RunAs identity may not have required access permissions.

Resolution: Configuring Web Management Service Logging and Tracing and review the logs to identify the failure.

  • Look for entries in the logs that contain failures such as:

    Details: No rule was found that could authorize user server1\siteowner, provider appPoolConfig, operation Read, path DefaultAppPool. In this case, the provider appPoolConfig isn't authorized and the user tried to use a provider for which the user didn't have permissions.

  • Another common error is if the RunAs user that is being used to create applications doesn't have proper access to configuration. In this case, Process Monitor is a useful tool for determining where an access denied error may be coming from.