Part 1 – The Basics
Part 2 – The Basics continued
Part 3 – Configuration
Part 4 – Communication
Part 5 – Quick Deployment
Part 6 – Logging
Part 7 – Change Token Basics
Part 8 – Job and Change Token
Part 9 – Job and Timerjob
Both Content Deployment and the Content Deployment and Migration API use the ULS log to report problems and progress information using the following categories:
For the WSS Content Deployment and Migration API:
- Category: Upgrade
For the MOSS Content Deployment feature:
- Category: Content Deployment
To troubleshoot, content deployment issues these two categories should be set to Verbose:
This will ensure that the whole progress of content deployment is logged into the ULS logs.
In some situations it might be required to add additional categories (such as “General”) as the content deployment and migration API uses the WSS object model during export and import. If a problem occurs inside the WSS object model the error will show up in the related category first.
An often requested feature is to get the same log files as you will automatically get them using STSADM -o export/import.
There are two possible ways to get this log file for content deployment:
If you have this patch level or later these logfiles are always automatically generated and can be found on the export server of the source farm. The location of these logfiles can be found in the content deployment job report:
The name in front of the path is the machine name where the logfiles can be found. The logfiles are stored on this server in cab file format.
The directory will be in the ImportExportLogs directory which will be created in the directory configured as temporary path in the content deployment general settings.
Starting with October 2009 CU these log files will always be created. [Update Nov 13th, 2009] The number of logs kept is the same as the configured number of deployment reports to keep. It is not necessary to clean the logs manually.
The second option is available also with previous builds. If you enable verbose logging for the “Upgrade” category you will find the entries which are usually written to the export/import logs in the ULS log. You only have to filter the logfile for the “Upgrade” category
The problem with this method is that you will only see the entries AFTER you changed the logging option to verbose. So you will usually not have this information available when the deployment failed the first time.
I really love your posts about the Content Deployment. It really clears up a lot of things.
I have a question about understanding the job reports. How are the number of objects defined ? Is one page, image or document each an object ? We are seeing minimal changes resulting in a very large number of object being replicated.
each job run leads to one report.
Independent from the number of lines in the report.
You can see historical reports using the "view job history" option.
Hi, I have a problem importing MOSS 2007 content to MOSS 2010 blank site. This is error:
FatalError: The version of the package 18.104.22.168 is different from the current version this program supports, 22.214.171.124.
[11/26/2009 11:54:05 AM] Debug: at Microsoft.SharePoint.Deployment.SPDeploymentSchemaVersion.Validate(SPSite site)
Can You help me?
sorry this is not possible. The package format is different between MOSS and SP 2010.