To: ozMOSS
Subject: Re: MOSS 2007 Content Deployment Problems
This looks tricky as stsadm - backup/restore is much more robust than stsadm
import.
In most cases when we had issue with export-import -- backup/restore has worked
well.
Can you do one quick test to validate if it's the data in site
: MOSS 2007 Content Deployment Problems
** **
Hi,
** **
Just an update. I made some progress by running: psconfig -cmd upgrade
-inplace b2b -wait on the host where the pending upgrade was flagged.
This completed and then Content Deployment started working.
** **
Now gets
:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On
Behalf Of *Chris Howell
*Sent:* Wednesday, 2 November 2011 4:32 PM
*To:* ozMOSS
*Subject:* Re: MOSS 2007 Content Deployment Problems
** **
Hi,
** **
Just an update. I made some progress by running: psconfig -cmd
the same in both farms?
Have you tried turning off UAC on the destination farm?
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf
Of Chris Howell
Sent: Wednesday, 2 November 2011 4:32 PM
To: ozMOSS
Subject: Re: MOSS 2007 Content Deployment Problems
Hi,
Just
Hi,
Just an update. I made some progress by running: psconfig -cmd upgrade
-inplace b2b -wait on the host where the pending upgrade was flagged. This
completed and then Content Deployment started working.
Now gets to the point where the Content Deployment job exports to the new
server. Job then
