The other day I ran into an issue where the admins were seeing an Event ID in the application log that indicated that a content deployment job had failed. Well the actual details were something like this: content was copied successfully to the destination server, but could not find the web app to import into.
Now, content deployment jobs in this scenario had been stopped and deleted a few months back and the admins did not know why this was happening, what I found was the following:
- There was still a content deployment file in the content deployment folder of the destination server.
- Even though content deployment is turned off, if there is a file in the folder SharePoint will try and try to import the contents.
- The error was always after the default admin app pool recycle period.
Just though you would be interested. Remember to delete this file when cancelling content deployment jobs!