MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

problem with synchronization (content deployment paths and jobs)

  Asked By: Mindy    Date: Sep 17    Category: MOSS    Views: 2582

I have a great job for you, can you solve this? Ok check that..!

Actually we have 2 MOSS servers, one is at UK and one is at INDIA, both are on 2
different domains and 2 separate installations. Now what we need is when I
upload some content in UK server, after some time INDIA server also wanted to be
updated automatically with the same content (using Synchronization).

I tried with central administration features as follows:
Central Administration-->Operations-->Content Deployment-->Content Deployment
Paths and Jobs

But I am got the following 2 error's:
1)Export ran out of memory while compressing a very large file. To successfully
export, turn compression off by specifying the -nofilecompression parameter. at
ss>b__0() at
secureCode) at
request) at Microsoft.SharePoint.Deployment.SPExport.Run()

2)Content deployment job 'Home Deploy' failed.The exception thrown was
'Microsoft.SharePoint.SPException' : 'Export ran out of memory while compressing
a very large file. To successfully export, turn compression off by specifying
the -nofilecompression parameter.'

Then I deleted larger files, whose capacity is more than 50 Mb, as that’s the
size limit in MOSS.

Now I am facing a new error as mentioned below:

1) The remote upload Web request failed.

What might be the problem and how to resolve it? It's very important and need to
resolve as soon as possible, please concern with high priority and do needful

I appreciate if you forward any material / article’s on content deployment
paths and jobs



1 Answer Found

Answer #1    Answered By: Destiny Lewis     Answered On: Sep 17

Don't worry about the errors for the moment, because the real problem  is that
you can't use content  deployment in the way you are trying to use it. Content
Deployment is designed to be used to deploy content from a Web Content
Management Authoring Environment to a Publication Web site. It is strictly a
one way synchronization  and can't be used in both directions. One of the
requirements is that the destination path for the first run of the Content
Deployment job  must be a "Blank Site" in a site collection. The blank site
can't have any subsites at this point either. Now to the errors.

Error #1 is as you have already figured out because you are trying to transfer
too much content or too big a file at once.

Error #2 is more than likely because your destination is not a blank site.
(Note: when you re-run the job later to send changes the site doesn't need to
be blank anymore.) Also, if people will be adding content on the India side of
the deployment  you may run into issues with re-running the job. Content changed
in India may be overwritten by new content from UK.

In short. You can't use Content Deployment to do what you are describing.