This walkthrough will guide you through the process of troubleshooting an MS Deploy operation.
Article Goal: Learn troubleshooting techniques and how to enable verbose output.
Prerequisites
This article requires the following prerequisites:
• .NET Framework 2.0 SP1 or greater
• MS Deploy Beta 1
Note: If you have not already installed MS Deploy, see Installing MS Deploy.
Troubleshooting MS Deploy operations
The first level of validation for an operation should be the -whatif flag, which will show you what actions will be performed and catch some error conditions. But if the operation did not go as expected and –whatif did not find any issues, you can use the –verboseLevel flag to specify output settings. This is very useful if you need to determine what failed to sync, and often gives additional detail about the operation.
To run with verbose output
1. Let’s say we were running a migration. Run the command again, with -verbose specified:
msdeploy.exe -verb:migrate -source:metakey=lm/w3svc/1,targetName=http://computername/msdeploy/ -dest:metakey=lm/w3svc/1 -verbose >msdeploymigrate-verbose.log
By specifying > msdeploymigrate-verbose.log, the results of the operation and all the extra informational alerts will be listed in the log file and we can easily refer back to it.
Depending on the error, you should look through the log for related entries. For example, if a property wasn’t set correctly, check the verbose logging actions to see why it was missed or skipped.
Common errors
Cannot read configuration file or similar error may be due to running from a non-elevated command prompt on Windows Server 2008. Ensure you have administrative credentials for operations like reading or writing configuration or registry settings.
A web site or other object with commas in its path does not sync correctly. This is a known issue and requires using double and single quotes around the path. For example, the path to an assembly contains commas and must be specially treated: -source:gacAssembly="'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'"
If your site has no ServerComment set on IIS 6.0, the ABO Mapper component will be unable to recognize them on IIS 7.0 and they will not be migrated correctly.
If you do not have IIS installed on the source or destination machine when you are trying to access IIS-related providers such as metakey or apphostconfig, you will receive the following error message:
Retrieving the COM class factory for component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} failed due to the following error: 80040154.
Remote service errors
404 Remote file not found – the remote service is not installed or running, or the URL is incorrect. It is a Manual startup service so make sure that it is running.
The connection to the remote machine times out or returns a timeout error – verify that the port for the remote service is open on the target machine. If it is open, re-try the command. Many times it will work after a retry.
Summary
You have run operations with tracing or verbosity enabled as well as learned some errors that can occur. This article will be updated to include error cases and troubleshooting tips.
Comments