Saturday, April 20, 2019
Sign-In  |  Sign-Up  |  Contact Us  | Bookmark |  RSS Feed

Web Deploy Tool Troubleshooting  
Here are the possible troubleshooting methods for probable Web Deploy (Web Deployment Tool) errors.

Web Deploy Tool Troubleshooting Requirements

In order to perform successful troubleshooting, your system must at least have:

Web Deploy 1.0 or greater
.NET Framework 2.0 SP1 or greater

Note: Troubleshooting specifics are also made plain to base the previous install platform utilized in the installation of Web Deploy Tool

Web Deploy Tool Troubleshooting Process

In the operation of a certain level of the validation, specifically for first level, the target should be the – whatif flag. The –whatif flag permits the identification of the probable effects by after executing a command and causes to be successful. This application logic is sort of projected as a contrast or assessment flag, also limits the effect of getting many errors.

In the event that the operation alternatively ended up at negative causalities and the –whatif isn’t able to project issues, the –verbose flag can be utilized as an alternate in identifying output settings. This is highly effective in pulling out determiners which caused a sync to fail and furthermore provides supplemented details precise to the operation.

Execution with Verbose Output

In the event the a migration is executed an on process, a Run command should be as well executed with –verbose spefified: msdeploy.exe -verb:migrate -source:metakey=lm/w3svc/1,computername=ServerName1 -dest:metakey=lm/w3svc/1 -verbose >msdeploymigrate-verbose.log

Using the parameter> msdeploymigrate-verbose.log, through this parameter, the output of the operation and all other supplementary information alerts will be catalogued in a log file as an easy reference for error checks.Checking log entries are also error dependent.

Web Deploy Tool Troubleshooting Common and Probable Errors

A common error is the [Cannot Read Configuration File] and other related errors are somewhat attributed to be executed from a non-elevated command value run under Windows Server 2008. A way to resolve this is to ensure that the user executing the command has administrative rights in read and write configuration and registry settings attributes.

A particular object or other assemblies with character values such as COMMAS in its directory paths are commonly those that does not correctly sync. This is a common issue and this requisites the inclusion of a double and a single quotes which should be around the path. An alternate sample is provided as:

-source:gacAssembly="'System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'"

In the event that a sire is limited not to have a ServerComment establish on IIS 6.0, then an ABO mapper is not capable to identify those on IIS 7.0, thus migration cannot be correctly processed. Also, if IIS is absent and has not been installed on a source or on a destination machine during access attempt on IIS-related providers limitedly identified as metakey or apphostconfig, then probable error occurs:

Retrieving the COM class factory for component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} failed due to the following error: 80040154.

Web Deploy Tool Troubleshooting Remote Service Specific Errors

404 Remote file not found – causes by the absence of the remote service since it may have not been installed or may have not been correctly installed, or may have not been execute to run, another reason is that the URL may be incorrect. Since the Remote Service is oriented to be on Manual Startup, then it is always effective to ensure that it is executed manually.

Connection to the remote machine times out or revert back a timeout error – Ensure that the port for the remote service is matched and is open on the targeted machine. In the event that port has been opened already, then a command retry will work by several executions.

Print Web Deploy Tool Troubleshooting Bookmark Web Deploy Tool Troubleshooting

Related Articles  
WebDAV IIS 7.0 and 7.5 Extension
WebDAV Extension is an IIS 7.0 and 7.5 compatible augmentation which promises Web authors the capability to publish ...
FTP Publishing Service 7.5 - IIS Extension
The FTP Publishing Service is a free IIS Extension specific to IIS 7.0. This particularly grants the content creators ...
Web Deploy Tool Installation
Installing Web Deploy specifically Web Deployment Tool entails a bit of a procedural orientation in accordance with ...
Deploying IIS on Windows 7
Windows 7 OS comes with IIS pre-installed. However, it is not deployed on your machine by default and you need to ...
Web Deploy 2.0 IIS Extension
Web Deploy or Web Deployment Tool abridges the simplification of processes such as management, deployment and migration ...
Overview of IIS Web Deploy Version 2.0
Web Deployment Tool, or alternatively shortened as Web Deploy is a programming contrivance which makes the processes of ...