Logging When you run into issues with Web Deploy, there are several logging options depending on where the problem occurred. This is great place to start looking for errors on the destination server. For a full list of error codes, see. Note that the error message may be different depending on how Web Deploy is invoked. For example, Microsoft WebMatrix chooses to show custom error messages instead of error codes whereas the command line will always show error codes if they are logged. Could not install Web Deploy on a valid OS Symptoms The OS is correct, the version and bitness of Web Deploy are correct, but the installation does not succeed. Web Deploy does not function after upgrade Symptoms Web Deploy does not work after a version upgrade. Root Cause Web Deploy does not restart services after an upgrade. Could not install Web Deploy 32-bit version on 64-bit hardware Symptoms Root Cause Trying to install 32-bit on 64-bit OS is a check inside the Web Deploy MSI that will fail because it doesn't support WoW64 mode. Could not install Web Deploy 64-bit version on 32-bit hardware Symptoms Root Cause Trying to install 64-bit on 32-bit OS is a check inside Web Deploy's MSI that will fail. Could not initialize Microsoft. Dll during start-up Symptoms Remote Agent Service fails to start Root Cause msdepsvc. Remote Agent Service is not started Symptoms Microsoft. Make sure the remote agent service is installed and started on the target computer. WebException: The remote server returned an error: 404 Not Found. Trying to connect to server where HTTP is not listening or allowed Symptoms Microsoft. DeploymentAgentUnavailableException: Remote agent URL could not be contacted. Make sure the remote agent service is installed and started on the target computer. Trying to connect to server with Method Not Allowed error Symptoms Microsoft. DeploymentException: Could not complete the request to remote agent URL ''. WebException: The remote server returned an error: 405 Method Not Allowed. Root Cause Request was picked up by IIS itself instead of MS Deploy, because the path to msdepsvc. Trying to access Remote Agent Service as a non-administrator Symptoms Microsoft. DeploymentException: Could not complete the request to remote agent URL ''. WebException: The remote server returned an error: 401 Unauthorized. Root Cause Remote Agent Service requires that the caller is a member of the Administrators group or from a domain account that has been added to the Administrators group. A local administrator which is not the built-in account will not work with the Remote Agent Service because of a bug in Web Deploy 2. The exception details are as follows: Microsoft. DeploymentClientServerException: The client and server are not compatible. The lowest version supported by the client is '7. The highest version supported by the server is '7. Root Cause Some versions do not work together, so Web Deploy blocks them from working together. This is typically done to block pre-release versions from operating with released versions. Remote Agent Service could not start listening on URL Symptoms The Remote Agent Service could not start listening on the URL '0'. Make sure that the URL is not in use. Root Cause Usually indicates a URL conflict. Further details on URL customization are found here: Web Management Service 1. Web Management Service not started Symptoms Web Management Service is not started. The service should be started by default. Not Authorized: User not authorized by deployment handler rules Symptoms Could not complete an operation with the specified provider when connecting using the Web Management Service. This can occur if the server administrator has not authorized the user for this operation. Root Cause A non-administrator user tried to perform a restricted action with a provider. This usually indicates that a matching delegation rule was not found. Either the username, provider, operation or provider path is wrong. Further details on delegation rules can be found here: Case Study: Diagnosing Publishing Errors in Visual Studio 2010 This case study shows how to diagnose common errors encountered in Visual Studio 2010. The steps below walk through the series of errors you are likely to encounter when trying to publish from Visual Studio to a server that has not been correctly configured. To collect the screenshots and errors below, we used a new ASP. The destination server was a clean install of Windows Server 2008 R2 SP1 with IIS. No additional configuration was done. The first error you are likely to encounter will look something like this in Visual Studio's output window. To make it easier to read, the full text of the message is reproduced below the screenshot. Web deployment task failed. This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server. Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192. On the destination server, open IIS Manager and select the machine name node. In the Features view, scroll down to the Management section and look for these Icons: If they are not there, you need to install the Web Management Service. · Through the Web Platform Installer from the Products tab. Note that after you install the Management Service, you will need to start it, as it is not started automatically. Once the Web Management Service is installed, Visual studio may show this error: Web deployment task failed. The remote server returned an error: 403 Forbidden. Is the Web Management Service configured to allow remote connections? You must stop the service to make changes, so be sure to restart it. Is Windows Firewall blocking the request? It should be enabled for all profiles. If you are using a 3rd party firewall, make sure inbound TCP connections on port 8172 are allowed. If Visual Studio is able to contact the Management Service, the error message changes: Web deployment task failed. The requested resource does not exist, or the requested URL is incorrect. The remote server returned an error: 404 Not Found. Is the Web Deployment IIS7 Deployment Handler installed? Click Next to complete the Wizard. Once Web Deploy and the Web Management Service are correctly configured, you will need to set up Web Management Service delegation rules to allow users to update content. For permissions issues, there are several different errors you may see in Visual Studio. For example: Web deployment task failed. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. The remote server returned an error: 401 Unauthorized. In the Web Management Service log, you will see 2011-05-12 15:50:12 192. This is a simple logon failure. If the user is authenticated, but does not have the rights needed to publish, the log entry will look like 2011-05-12 15:55:38 192. This can occur if the server administrator has not authorized this operation for the user credentials you are using. The WMSvc log will show HTTP 200 responses for these requests. The most likely cause is file system permissions. This can occur if the server administrator has not authorized this operation for the user credentials you are using. DeploymentException: The error code was 0x80070005. RaiseIOExceptionFromErrorCode Win32ErrorCode errorCode, String maybeFullPath at Microsoft. CreateDirectory String path at Microsoft. CreateDirectory String fullPath, DeploymentObject source at Microsoft. Add DeploymentObject source, Boolean whatIf --- End of inner exception stack trace --- --- End of inner exception stack trace --- This message tells you where permissions need to be granted for this particular error. Another permissions error you may see in Visual Studio is Web deployment task failed. The server experienced an issue processing the request. Contact the server administrator for more information. This particular error does not give you much to go on, but the picture becomes much clearer if you look at the Web Deploy error log in Event Viewer. UnauthorizedAccessException: Attempted to perform an unauthorized operation. SetSecurityInfo ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl at System. Persist String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext at System. Persist String name, AccessControlSections includeSections, Object exceptionContext at Microsoft. Persist String path at Microsoft. Add DeploymentObject source, Boolean whatIf at Microsoft. Update DeploymentObject source, DeploymentSyncContext syncContext at Microsoft. HandleUpdate DeploymentObject destObject, DeploymentObject sourceObject at Microsoft. SyncChildrenOrder DeploymentObject dest, DeploymentObject source at Microsoft. ProcessSync DeploymentObject destinationObject, DeploymentObject sourceObject From this, we can see that User1 does not have rights to set security information. In this case, the user does not have Modify permissions on the content. If you cannot browse a. Other symptoms are that.
