Comments on: The Long Path to Content Deployment http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/ The life of yet another consultant Fri, 09 Oct 2009 20:49:32 +0000 http://wordpress.com/ hourly 1 By: Issues with Sharepoint’s Content Deployment Temp File « Yiu San's Blog for Microsoft's Technology (Sharepoint, MOM, DPM, ISA, Exchange, etc) http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-592 Issues with Sharepoint’s Content Deployment Temp File « Yiu San's Blog for Microsoft's Technology (Sharepoint, MOM, DPM, ISA, Exchange, etc) Thu, 01 Oct 2009 05:30:19 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-592 [...] http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/ [...] [...] http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/ [...]

]]> By: Søren Nielsen http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-519 Søren Nielsen Fri, 03 Jul 2009 08:31:07 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-519 Keith: A quick reply ;-) If you have search enabled you can go to the advanced search, select the size property, greater than operator, enter a byte size of 20mill and you should find it. If not you could just open the file in notepad. You can probably glean what file type it is from that (header fields near the top). Probably some office document. Rename it to correct extension, open it and view what it is. I suppose that would give you a clue where to look for it. I'm not sure there is a good log for this. You could try to do the stsadm export command. It creates an export log file that might help you too (location next to your export package). Keith: A quick reply ;-)

If you have search enabled you can go to the advanced search, select the size property, greater than operator, enter a byte size of 20mill and you should find it.

If not you could just open the file in notepad. You can probably glean what file type it is from that (header fields near the top). Probably some office document. Rename it to correct extension, open it and view what it is. I suppose that would give you a clue where to look for it.

I’m not sure there is a good log for this. You could try to do the stsadm export command. It creates an export log file that might help you too (location next to your export package).

]]> By: Keith http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-508 Keith Tue, 30 Jun 2009 19:27:03 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-508 Hello Soren, We are also having Content Deployment problems, the latest being the 'Export ran out of memory while compressing a very large file' error. I have been able to do an export with compression turned off, and the resulting export file looks to be the right size, 104Meg. The Manifest.xml file is 30Meg, and one .dat file is 22Meg. Three other files are between 1 and 2M, and the other 2600 files are under 1M, most being very small. Can I assume it's the 22Meg .dat file which is causing the trouble? If so, how would I go about identifying which file it is on the portal? A second question, where exactly would I look for log information on this? Would it be part of the standard diagnostic logging? Thanks for this hugely helpful blog, by the way. Hello Soren,

We are also having Content Deployment problems, the latest being the ‘Export ran out of memory while compressing a very large file’ error.

I have been able to do an export with compression turned off, and the resulting export file looks to be the right size, 104Meg. The Manifest.xml file is 30Meg, and one .dat file is 22Meg. Three other files are between 1 and 2M, and the other 2600 files are under 1M, most being very small.

Can I assume it’s the 22Meg .dat file which is causing the trouble? If so, how would I go about identifying which file it is on the portal? A second question, where exactly would I look for log information on this? Would it be part of the standard diagnostic logging?

Thanks for this hugely helpful blog, by the way.

]]> By: Søren Nielsen http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-374 Søren Nielsen Fri, 31 Oct 2008 14:04:28 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-374 Arun: The only thing I can think of is to make absolutely sure that the field control is registered and works on the production site, before you try the content deployment. It should work on its own possibly just on some test site. Then you can try to do content deployment. My experiences with field controls are not good. They tend to be very fragile and once deployed you can most likely never get rid of them again. They have not failed for me with content deployment, but I'm not surprised that they might cause problems. Arun: The only thing I can think of is to make absolutely sure that the field control is registered and works on the production site, before you try the content deployment.

It should work on its own possibly just on some test site.

Then you can try to do content deployment.

My experiences with field controls are not good. They tend to be very fragile and once deployed you can most likely never get rid of them again. They have not failed for me with content deployment, but I’m not surprised that they might cause problems.

]]> By: Arun Krishnakumar http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-370 Arun Krishnakumar Mon, 27 Oct 2008 05:44:09 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-370 I am facing an issue that is killing me for 4 long days.Still i couldnt able to solve that.I have wriiten 3 custom field controls where i have deployed its dll in bin folder. Issue: I am getting this error while doing Content Deployment from authoring server to production server. The exception thrown was 'System.Security.SecurityException' : 'Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed.' I am having a custom policy file where i have given all the permissions. I did the following: 1.Deployed with Full trust,still the same error 2.Deployed with custom policy file,still the same error 3.Installed the dll in GAC(authoring server),the deployment job successfully exports from authoring server but at the time of importing in production server,i am getting the same error(in prod. server i insatlled the dll in GAC) I am getting this error only for custom field controls dll.I am having a separate dll for webparts,that doesnt give me error. Can anyone help me out to solve this issue asap. Thanks in advance. arun.k I am facing an issue that is killing me for 4 long days.Still i couldnt able to solve that.I have wriiten 3 custom field controls where i have deployed its dll in bin folder.

Issue:

I am getting this error while doing Content Deployment from authoring server to production server.

The exception thrown was ‘System.Security.SecurityException’ : ‘Request for the permission of type ‘Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ failed.’

I am having a custom policy file where i have given all the permissions.

I did the following:

1.Deployed with Full trust,still the same error

2.Deployed with custom policy file,still the same error

3.Installed the dll in GAC(authoring server),the deployment job successfully exports from authoring server but at the time of importing in production server,i am getting the same error(in prod. server i insatlled the dll in GAC)

I am getting this error only for custom field controls dll.I am having a separate dll for webparts,that doesnt give me error.

Can anyone help me out to solve this issue asap.

Thanks in advance.

arun.k

]]> By: Neil van Wyngaard http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-355 Neil van Wyngaard Mon, 29 Sep 2008 12:20:48 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-355 Thank you very much. This post was extremely usefull and safed me a lot of time. Thank you very much. This post was extremely usefull and safed me a lot of time.

]]> By: mike hodnick http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-317 mike hodnick Thu, 05 Jun 2008 18:59:36 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-317 Fayza - your comment about compression was from quite a while ago, but I discovered an STSADM command where you can disable file compression in a Content Deployment path: stsadm -o editcontentdeploymentpath One of the options you can pass in to this command is -enablecompression yes|no. Fayza – your comment about compression was from quite a while ago, but I discovered an STSADM command where you can disable file compression in a Content Deployment path:

stsadm -o editcontentdeploymentpath

One of the options you can pass in to this command is -enablecompression yes|no.

]]> By: Kots http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-287 Kots Wed, 09 Apr 2008 13:21:59 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-287 Good Article. Good Article.

]]> By: Søren Nielsen http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-286 Søren Nielsen Mon, 31 Mar 2008 20:47:12 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-286 Naresh: Please see some of my other replies higher up - the best way to troubleshoot is to run an export from the command line (please do not do an import on that data, things will break) to see what it actually tries to export. Use the no-compression parameter. Hopefully you'll learn a thing or two, e.g. what large file the system is complaining about (if it's the manifest file, you might be in trouble). Naresh: Please see some of my other replies higher up – the best way to troubleshoot is to run an export from the command line (please do not do an import on that data, things will break) to see what it actually tries to export.
Use the no-compression parameter.

Hopefully you’ll learn a thing or two, e.g. what large file the system is complaining about (if it’s the manifest file, you might be in trouble).

]]> By: Naresh Alapati http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-276 Naresh Alapati Thu, 13 Mar 2008 09:18:01 +0000 http://soerennielsen.wordpress.com/2007/06/19/the-long-path-to-content-deployment/#comment-276 Hi, I had a big issue to do......... Actually I have 2 MOSS servers(separate installations), one is at Bharain and one is at Saudi, both are on 2 different domains. Now what I need is when I uploaded some content in Bharain server, after some time Saudi server also wanted to be updated automatically(Using Synchronization). I am trying with central administration features following: Central Administration-->Operations-->Content Deployment-->Content Deployment Paths and Jobs But I am getting 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 Microsoft.SharePoint.Deployment.ExportDataFileManager.c__DisplayClass2.b__0() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.Deployment.ExportDataFileManager.Compress(SPRequest 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.' 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 Thank you........ Please reply to naren378@gmail.com Thanks, Naresh Alapati Hi,

I had a big issue to do………

Actually I have 2 MOSS servers(separate installations), one is at Bharain and one is at Saudi, both are on 2 different domains. Now what I need is when I uploaded some content in Bharain server, after some time Saudi server also wanted to be updated automatically(Using Synchronization).

I am trying with central administration features following:
Central Administration–>Operations–>Content Deployment–>Content Deployment Paths and Jobs

But I am getting 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 Microsoft.SharePoint.Deployment.ExportDataFileManager.c__DisplayClass2.b__0() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.Deployment.ExportDataFileManager.Compress(SPRequest 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.’

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 Thank you……..

Please reply to naren378@gmail.com

Thanks,
Naresh Alapati

]]>