Web Deploy error codes

For certain common error cases, Web Deploy will show an error code. This table explains why the error occurs and steps the user can take to avoid the error. Note that the error message may be different depending on how Web Deploy is invoked e.g. Microsoft WebMatrix chooses to show custom error messages. The error messages listed below show up on the msdeploy.exe command line and API:
Error Code Error message Diagnosis Resolution
MySqlDumpNotFound The utility to get the database script could not be found at ''C:\Program Files\MySQL\MySQL Server 5.1\bin". Web Deploy cannot find the mysqldump.exe executable. This executable is required for MySQL database deployments. There are two workarounds:
1. Place the executable in C:\Program Files\MySQL\MySQL Server 5.1\bin
2. Set a REG_SZ registry key to point to the executable: e.g. (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\2\MySqlDumpPath is set to “c:\mysqldump\mysqldump.exe”
RemoteAppNotFound The remote application could not be found. This can happen if you try to do a dump of "remotesite/remoteapp" where "remoteapp" does not actually exist Specify a remote application name that actually exists
FileOrFolderNotFound NOTE: Error is actual file-system level error This can happen if you try to do a SetAcl on a file or folder that does not exist. Specify a file or folder that exists.
ERROR_DESTINATION_INVALID Could not connect to 'remote-server.com'. Please check if the computer name is correct and that you can reach this computer. Computer name is mistyped, or the computer is not reachable. Try to check if the computername is valid. Try pinging the computer manually.
ERROR_DESTINATION_NOT_REACHABLE Could not connect to the destination computer ("remote-server.com"). On the destination computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Web Management Service or Remote Agent is not installed or unreachable on the remote computer. Verify that Remote Agent Service or Web Management Service are started on the remote computer, depending on which one you are connecting to. You can do a "net start wmsvc & net start msdepsvc" on the remote computer to ensure these services are started. Also, ensure that a firewall is not interrupting communications with the destination.
ERROR_USER_UNAUTHORIZED Connected to the destination computer ("remote-server.com") using the Web Management Service, but could not authorize. 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. This error code can surface because of a number of different reasons. It typically indicates an authentication or authorization problem, and can happen because of any of hte following reasons:
  • User does not exist
  • User does not have IIS Manager access to site if connecting using Web Management Service
  • Site does not exist
  • Password is incorrect
If connecting using the Web Management Service:
  • Verify that the username and password are correct
  • Verify that the site exists
  • Verify that the user has IIS Manager Permissions to the site's scope
If connecting using the Remote Agent Service:
  • Verify that the username and password are correct
  • Verify that the user account you specified is a member of the Administrators group on the remote computer. NOTE: Because of a bug in Web Deploy 2.0, the user must be either the built-in Administrator or a member of the Domain Administrators security group. Attempts to sync with any other user account, even if it is an administrator, will see this error code.
  • Verify that the site exists
ERROR_USER_NOT_ADMIN Connected to 'remote-server.com' using the Web Deployment Agent Service, but could not authorize. Make sure you are an admin on 'remote-server.com'. This happens if you try to connect to the Remote Agent Service but have not provided appropriate administrator credentials. The Remote Agent Service accepts either built-in Administrator or Domain Administrator credentials. Because of a bug in Web Deploy, any other administrator credentials (e.g. member of the local Administrators group) will not work and will cause this error.
ERROR_CERTIFICATE_VALIDATION_FAILED Connected to the destination computer ("remote-server.com") using the specified process ("Web Management Service"), but could not verify the server’s certificate. If you trust the server, connect again and allow untrusted certificates. The certificate presented by the Web Deploy endpoint is untrusted or invalid. This typically happens if the remote server has a self-signed certificate for the Remote Agent Service or the Web Management Service. Either install a trusted certificate on the endpoint, or try bypassing certificate validation.
  • From the msdeploy.exe command line, you can do this by passing the -allowUntrusted flag.
  • From the Visual Studio 2010 publish UI, you can check "Allow untrusted"
  • From a Visual Studio 2010 deployment package (e.g. MyApp.deploy.cmd), you can pass the -allowUntrusted flag
ERROR_PROXY_GATEWAY Could not connect to the destination computer ("remote-server") using the specified process ("Web Management Service"). This can happen if a proxy server is interrupting communication with the destination server. Disable the proxy server and try again. A proxy gateway is preventing Web Deploy from communicating with the remote Web Deploy endpoint. Web Deploy does not read system proxy settings. As a workaround, try disabling the system proxy:
  • Start Internet Explorer
  • Click Tools > Options
  • Click Connection
  • Click LAN Settings
  • Disable all checkboxes
ERROR_SITE_DOES_NOT_EXIST Site 'MySite' does not exist. Specified IIS site does not exist. Verify that the specified site actually exists.
ERROR_APP_DOES_NOT_EXIST Application does not exist. The specified application does not exist in IIS. Check IIS Manager to make sure you have correctly specified the name of the application path.
ERROR_USER_NOT_AUTHORIZED_FOR_IISAPP
ERROR_USER_NOT_AUTHORIZED_FOR_DBFULLSQL
ERROR_USER_NOT_AUTHORIZED_FOR_DBMYSQL
ERROR_USER_NOT_AUTHORIZED_FOR_SETACL
ERROR_USER_NOT_AUTHORIZED_FOR_APPPOOLNETFX
ERROR_USER_NOT_AUTHORIZED_FOR_APPPOOLPIPELINE
ERROR_USER_NOT_AUTHORIZED_FOR_RECYCLEAPP
ERROR_USER_NOT_AUTHORIZED_FOR_CREATEAPP
ERROR_USER_NOT_AUTHORIZED_FOR_CONTENTPATH		 Could not complete an operation with the specified provider ("SpecificProviderName") when connecting using the Web Management Service. This can occur if the server administrator has not authorized the user for this operation. A non-administrative user attempted to perform an operation with a Web Deploy provider for which the user is not currently authorized. Web Deploy 2.0 setup, by default, creates Management Service Delegation Rules which allow non-administrators to perform operations with this provider. It is possible that a delegation rule required for this provider has not been setup correctly.

Workaround: From the Programs Control Panel, run Repair on Web Deploy 2.0. Alternatively, create the delegation rule manually.
ERROR_USER_NOT_AUTHORIZED_FOR_DEPLOYMENTPROVIDER Could not complete an operation with the specified provider ("SomeWebDeployProvider") when connecting using the Web Management Service. This can occur if the server administrator has not authorized the user for this operation. A non-administrative user attempted to perform an operation with a Web Deploy provider for which the user is not currently authorized. This error code surfaces if the user attempts to perform an operation with a provider for which Web Deploy 2.0's setup does not create a delegation rule. Web Deploy 2.0 setup does not create a delegation rule for this provider. Create the delegation rule manually.
ERROR_INSUFFICIENT_ACCESS_TO_SITE_FOLDER NOTE: Error is actual file system-level error This error code can surface if connecting over the Web Management Service as a non-administrator:
  • If connecting using IIS Manager credentials, the Web Management Service's identity (typically Local Service) needs Full Control permissions on the site's root folder to be able to create files and folders underneath.
  • If connecting using Windows credentials, the Windows user needs Full Control over the site's root folder to be able to create files and folders underneath.
 Grant the appropriate account Full Control on the site's root folder. Alternatively:
  • Start IIS Manger and right click on the site in question
  • Click Deploy > Configure for Web Deploy Publishing
  • Select the appropriate username
  • Click Setup
ERROR_INSUFFICIENT_ACCESS_TO_APPHOSTCONFIG Could not mark the folder as an application on the destination server. This can occur if the server administrator has not authorized this operation for the user credentials that you are using. The RunAs identity specified for the createApp delegation rule needs Write access to the IIS server's applicationHost.config file. Grant the RunAs identity of the createApp delegation rule Write access to the IIS server's applicationHost.config file.
ERROR_INVALID_CONNECTION_STRING Could not complete the database operation because of invalid information in the connection string. Check the connection string and try again. An invalid database connection string was specified which caused a dbFullSql or dbMySql provider to not run correctly. This can happen if a connection string is malformed (e.g. Sevver=localhost;...) or if the connection string contains keys which the target database server does not recognize. Verify that the connection string is valid.
ERROR_SQL_EXECUTION_FAILURE NOTE: Error is actual SQL execution failure message A SQL script execution failure occurred. This can happen for a va This can happen for a number of reasons. Please read more here.
ERROR_TYPE_NOT_FOUND_IN_ASSEMBLY An error occurred when performing this operation. dbFullSql provider of Web Deploy requires Server Management Objects version 10 or higher. The SQL provider cannot run because of a missing dependency. Please make sure that Microsoft SQL Server Management Objects (Version 10 or higher) is installed.
ERROR_OBJECT_TO_BE_DELETED_DOES_NOT_EXIST Object to be deleted does not exist. Web Deploy originally found an object to be deleted but when it tried to delete it, it was missing. Make sure there are no other external processes that are modifying the target while doing a sync.
ERROR_APPPOOL_VERSION_MISMATCH The application pool that you are trying to use has the version property set to <versionSource>. This application requires <versionDestination>. The source application pool version is different from the destination application pool version. You can manually change the application pool versions to match between the source and destination, or use the apppoolnetfx provider to do it automatically.
ERROR_CENTRAL_CERT_STORE_SETTINGS_CANNOT_BE_READ The central certificate store is only supported on IIS 8 or later.

Or

This provider cannot be used to access the Central Certificate Store while running from a 32-bit process on a 64-bit operating system.		 The central certificate store cannot be used in your current configuration. 1. You need to make sure you are using IIS 8 or later.
2. If you are running msdeploy.exe on a 64-bit server, make sure that you are using the 64-bit version of the executable.
ERROR_COULD_NOT_CONNECT_TO_REMOTESVC Could not connect to the destination computer using the specified process  because the server did not respond. Make sure that the process is started on the destination computer. Web Deploy cannot connect to the remote service. Make sure:
1. You can ping the remote machine
2. That the msdepsvc or wmsvc service is started on the remote server.
3. Your firewall is not blocking incoming connections of your ports on the destination.  If you used the default installation, then it would be 80 for msdepsvc and 8172 for wmsvc.
ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH The versions of the .NET Framework Configuration Provider are different on the source and destination. This can occur if you are doing a web server sync between two machines that have different versions of .Net installed.

By default, Web Deploy will favor running in the version of .Net that is specified in its configuration file.  If the version of .Net that Web Deploy is using on the client is different from the version on the server, we will block a Web Server sync to prevent settings from different versions of .Net from being migrated.  To get around this, you have two options:

1. Use the netFxVersion provider setting to tell Web Deploy exactly which .Net settings to migrate.  Here is a command line example which forces Web Deploy to sync .Net 2.0 settings: 
msdeploy.exe -verb:sync -source:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2 -dest:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2,computername=destServername
2. Run Web Deploy in the same version of .Net between client and server.  On the client side, you can change the ordering of the supportedRuntime version element in the "%programfiles%\IIS\Microsoft Web Deploy V3\msdeploy.exe.config" file for the version of .Net that is specified first (see gacInstall provider for an example of this).  This will indicate the version of .Net that will be loaded, assuming it is installed on your system.  On the server side, you can do the same for "%programfiles%\IIS\microsoft web deploy\msdepsvc.exe.config".  If you modify this file, make sure to restart the Web Deployment Agent Service (net stop msdepsvc & net start msdepsvc).
ERROR_HTTPCERT_BINDING_NOT_FOUND Could not find a binding that matched the input <binding>. The specified binding could not be found. Run "netsh http show sslcert" from the command line to verify that the specified binding exists.  If it is not found, then you may need to recreate it through IIS Manager.
ERROR_INCORRECT_PARAMETER_TAG A <Tag Name> tag was passed when either SQL, SQLCE or MYSQL was expected. An incorrect parameter tag was passed. Rerun msdeploy with the tag SQL, SQLCE, or MYSQL.
ERROR_INVALID_PATH The provider path is invalid. The provider path is invalid. Depending on the provider you are using, the required path for your provider may be different.  Visit http://technet.microsoft.com/en-us/library/dd569040(WS.10).aspx to find out more about the provider you are using.
ERROR_INVALID_SETTING_SPECIFIED The specified setting <setting name> is invalid. The setting is invalid. Visit http://technet.microsoft.com/en-us/library/dd569040(WS.10).aspx to find out more about the provider you are using.
ERROR_INVALID_SETTING_VALUE_SPECIFIED The setting value is invalid. The setting value is invalid. Visit http://technet.microsoft.com/en-us/library/dd569040(WS.10).aspx to find out more about the provider you are using.
ERROR_SNI_BINDINGS_NOT_SUPPORTED SNI Bindings are only supported on IIS 8 or later. SNI Bindings are only supported on IIS 8 or later. SNI Bindings can only be created on IIS 8 or later.
 

Submit article feedback

You must Log In to submit feedback.