Thursday, 26 March 2009

Command-line support for Content Deployment Wizard now available

I'm pleased to announce I've now completed initial development on the next version of the Content Deployment Wizard - this is a beta release for the next few weeks so if you need it "just work", you should continue to use the previous version (1.1), but I'm hoping some people out there are happy to test this beta. The tool has become fairly popular as a 'handy tool to have in the SharePoint toolbox', and hopefully this release extends it's usefulness significantly for some scenarios. If you're not familiar with the tool, it provides a way to import/export site collections, webs, lists, and files or list items, either between farms or between different sites in the same farm - the Codeplex site has more details. As previously mentioned, the key new additional functionality in this release is:

  • Command-line support
  • Support for saving of import/export settings to a file (in the Windows Forms app) for later re-use
  • An installer

Having command-line support for the Wizard means that it can now be used in an automated way. Some key scenarios I think this might be useful in are:

  • Continuous integration/automated builds - if your site relies on SharePoint content, you can now move 'real' data as part of a build process, copying selected content from 'dev' to 'build' or 'test' for example. I often see static data (perhaps from an XML file or Excel spreadsheet) used in this way in nAnt/CruiseControl/MSBuild scripts, but for frequently changing data (config values, lookup lists etc.), this doesn't work so well as there is always a static file to maintain separately. 
  • Deployment scripts - if you have deployment scripts to 'bootstrap' a website on developer machines, again pulling real data from a central 'repository site' can help here.
  • As part of a production 'Content Deployment strategy' - since out-of-the-box Content Deployment is restricted to deploying a web as the smallest item, the Wizard could be used to deploy selected lists/list items/files

Obviously you might have your own ideas about where it could slot into your processes too.

How it works

  1. First, we select the content to move as we would normally using the Wizard..

    SelectExportItems
  2. ..and select the options we want to use for this export..

    SelectExportSettings 

  3. On the final screen, the new 'Save settings..' button should be used to save your selections to an XML file: 

    SaveSettingsButton  
    This will then give you an XML file which looks like this:
  4. <ExportSettings SiteUrl="http://cob.publish.dev" ExcludeDependencies="False" ExportMethod="ExportAll" 
                    IncludeVersions="LastMajor" IncludeSecurity="None" FileLocation="C:\Exports" 
                    BaseFileName="BlogSubwebAndPageTemplates.cmp">
      <ExportObjects>
        <DeploymentObject Id="b0fd667b-5b5e-41ba-827e-5d78b9a150ac" Title="Blog" Url="http://cob.publish.dev/Blog" Type="Web" IncludeDescendants="All" />
        <DeploymentObject Id="cfcc048e-c516-43b2-b5bf-3fb37cd561be" Title="http://cob.publish.dev/_catalogs/masterpage/COB.master" Url="_catalogs/masterpage/COB.master" Type="File" IncludeDescendants="None" />
        <DeploymentObject Id="670c1fb3-12f3-418b-b854-751ba80da917" Title="http://cob.publish.dev/_catalogs/masterpage/COBLayoutSimple.aspx" Url="_catalogs/masterpage/COBLayoutSimple.aspx" Type="File" IncludeDescendants="None" />
      </ExportObjects>
    </ExportSettings>

  5. So we now have an XML 'Wizard deployment settings file' which has the IDs of the objects we selected and the export options. We'll go ahead and show how this can be used at the command-line, but note also these settings can also be loaded into the Wizard UI on future deployments to save having to make the selections again - the key is the 'Load settings..' button on the first page (which we didn't show earlier):

    LoadSettingsButton 

  6. For command-line use of the Wizard a custom STSADM command is used. We pass the settings file in using the -settingsFile switch. To run the export operation we showed above, our command would look like:
    stsadm -o RunWizardExport -settingsFile "C:\DeploymentSettings\ExportBlogSubwebAndTemplates.xml" -quiet
    The -quiet parameter is optional, and suppresses some of the progress messages which are returned during the operation.

  7. For an import operation, we follow the same process - go through the Wizard and select the settings for the import operation, then click 'Save settings..' at the end to get the file (N.B. note the 'Import settings' screen has been simplified slightly from previous versions):

    SelectImportSettings
  8. The command to import looks like this:
    stsadm -o RunWizardImport -settingsFile "C:\DeploymentSettings\ImportBlogSubwebAndTemplates.xml" -quiet
    So that's both sides of it.

Using it for real

In real use of course, you may be deploying from one SharePoint farm to another. In this case, you also need to deal with copying the .cmp file from the source environment to the target if you're going across farms - if you have network access between farms (e.g. you're using it internally for automated builds/CI), a simple XCOPY in your scripts is the recommended way to do this. For production Content Deployment scenarios with no network connectivity, what I'm providing here will need to be supplemented with something else which will deal with the file transport. Clearly something web service based could be the answer.

Summary

Using the Wizard at the command-line may prove extremely useful if you need to move any SharePoint content regularly in an automated way. In contrast with other ways you might approach this, the XML definition file allows you to choose any number of webs/lists/list items/files to move in one operation, which may suit your needs better than shipping items around separately.

This is very much a beta release, but as a sidenote I'm expecting the initial issues to mainly be around the installer rather than core code - hence I'm providing a 'manual' install procedure which will get you past any such issues (see the readme). Needless to say, all the source code is also there for you on Codeplex if you're a developer happy to get your hands dirty. As I say, I'm hoping a couple of friendly testers will try it out and help me iron out the wrinkles - please submit any issues to the Codeplex site linked to below.

You can download the 2.0 beta release of the Wizard (and source code) from:

52 comments:

Anonymous said...

Thank you for this tool. It made Web part development much easier - and with real data, not just sample. Would you think of developing it as an replacement of MOSS content deployment? For ex. insert date-time range in exporting and , in imprting, a checkmark for just adding the new items?
Thank you.

Chris O'Brien said...

@Anonymous,

Thanks. I think you're referring to the idea of 'incremental' deployment i.e. deploy only content which has changed since a certain date/time.

I agree this would be useful - I'm hoping to add this functionality to the Wizard in the near future. My plan is to get this added by June 2009 - hope you can wait that long and thanks for the suggestion!

Chris.

Melissa G said...

Hi Chris,

I'm trying to automate this using the command line as specified, but I'm running into an error:

Value cannot be null.
Parameter name: type

I am running WSS 3.0.

I checked the GAC, and your .dll seems to be registered successfully.

I'm not sure if this is just my machine, or if this is something that can help provide some more feedback for your beta.

Chris O'Brien said...

@Melissa G,

I'd like to drill into this a bit more - would you be happy to continue the conversation on e-mail?

If so, suggest leaving me another comment with your e-mail address - I won't publish this but will then contact you directly over e-mail.

Thanks!

Chris.

Luckysoft said...

Hi,

I have the same problem as Melissa G.

Would greatly appreciate any information.
thanks in advance

Chris O'Brien said...

@Luckysoft,

Apologies, there was a packaging error in the files which initially got uploaded. If you re-download from Codeplex now you should be good - the thing to look for is the version number in the 12\CONFIG\stsadmcommands.COB.SPDeploymentWizard.xml file, this should be 4.0.0.0 to match the assembly in the GAC.

Apologies for the inconvenience. Let me know if you run into any other issues.

Thanks,

Chris.

Rod said...

Hi Chris

I hope you are well. I will introduce this tool in Brazil:) I used to come to the Sharepoint User GRoup in London. If I get stuck please give us a hand. Thanks for being so helpful

Regards

rodolfo

Chris O'Brien said...

@Rod,

Great! If you run into any problems let me know and I'll try to help.

Thanks,

Chris.

Anonymous said...

Hi Chris,

I am having a problem Importing the .cmp file.

I am getting a message with Exception details:"An error whilst running the import. The import log file will now opened."

Appreciate if you could please let know if there is any other alternate email address I can send you the screen shot of the error I am getting.

Chris O'Brien said...

@Anonymous,

The details of what actually went wrong are always in the log file itself - so this is where you need to check for the real error message. The log file opens automatically in Notepad at this point.

If you need further help, leave me another comment with your e-mail address (which I won't publish), and then I'll help you offline.

Thanks,

Chris.

Anonymous said...

Hi.
I've noticed in this version 2.0 there isn't the worflow folder in the tree view of objects to select in the export option, as in version 1.1.
Is this correct? I need to export workflows and now I don´t know how.
Thanks in advance.

Bernhard Mayer said...

Thank you for this tool!
Indeed, it is THE tool in my Sharepoint-ToolBox!

Kind Regards

Bernhard

Faheem said...

Hi Chris,

A question regarding the previous release, i need to move content from a List into a subfolder to that list, ideally keeping the created by etc information, is this possible in your tool (WHICH IS VERY VERY USEFUL TODATE).

Thanks
Faheem

Chris O'Brien said...

@Faheem,

Unfortunately this isn't supported - it isn't possible to move content from the 'root folder' in a list to a sub folder.

Sorry about that.

Chris.

Chris O'Brien said...

@Anonymous,

In actual fact, the lists hidden from the treeview can be overriden in the config file for the application i.e. SPDeploymentWizard.exe.config. You might need to check the code to see what appSettings key to use.

However, deployment of workflows isn't properly supported (because it isn't properly supported by SharePoint in general. This discussion on Codeplex shows how far you might be able to get though.

HTH,

Chris.

Kieran said...

Hi Chris

If I use the wizard to move a new site collcetion to a production server. Then the client starts to populate the production server with data. How do I then move further changes from development to production using the wizard?

Thanks for any advice.

Chris O'Brien said...

@Kieran,

You do this *by being selective* in what you choose to deploy from dev to production. So in a publishing site for example, you might choose to deploy files in the Master Page Gallery, Style Library etc., but deploy nothing in the Pages libraries (or only pages you *want* to overwrite on production from dev).

Clearly it's not so simple for files which you both want to update. It's probably best to avoid a "multi-master" approach for such files, as there isn't any conflict resolution built into Content Deployment as such.

HTH,

Chris.

S├ębastien said...

Hello,

I'm trying to use the command lines but it seems it has not been installed properly. The command "stsadm -o RunWinzardExport" returns me an error.

Can you give me a step by step of how to register the new commands.

Thanks in advance.

Regards

Chris O'Brien said...

@S├ębastien,

This is probably because the wrong version of a file (the stsadmcommands.COB.SPDeploymentWizard.xml file) - really sorry about that. You can either:

- download the zip file from Codeplex again (now has corrected version)
- edit your file in the 12 hive so that the assembly references point to '4.0.0.0' rather than '2.0.0.0' (this was the error)

You should then be fine.

HTH,

Chris.

JR said...

Hi Chris,

While importing a tool-generated .cmp file (actually 2, pointing to base file) I'm getting this error:

[03/07/2009 14:41:55]: Start Time: 03/07/2009 14:41:55.
[03/07/2009 14:41:55]: Progress: Initializing Import.
[03/07/2009 14:42:45]: FatalError: Could not find Feature GatWebEventsManager.
at Microsoft.SharePoint.Deployment.ImportRequirementsManager.VerifyFeatureDefinition(SPRequirementObject reqObj)
at Microsoft.SharePoint.Deployment.ImportRequirementsManager.Validate(SPRequirementObject reqObj)
at Microsoft.SharePoint.Deployment.ImportRequirementsManager.DeserializeAndValidate()
at Microsoft.SharePoint.Deployment.SPImport.VerifyRequirements()
at Microsoft.SharePoint.Deployment.SPImport.Run()
[03/07/2009 14:42:52]: Progress: Import Completed.
[03/07/2009 14:42:52]: Finish Time: 03/07/2009 14:42:52.
[03/07/2009 14:42:52]: Completed with 0 warnings.
[03/07/2009 14:42:52]: Completed with 1 errors.

Thanks in advance and congratulations for the great work!

Basem Alabbasi said...

Dear Chris,

Many thanks for the great effort being put in this tool.

Moving to my concern; i would like to know about the chances of having this process being done authomatically. Like setting a job for Exporting data (moving the .cmp file in to a certain destination), then another job that imports the .cmp file.

Chris O'Brien said...

@Basem,

Sure, this is exactly what the command-line support is for. You would use the process described in this article to save the XML config files to use, then hook up the Task Scheduler to use the STSADM -o RunWizardExport/STSADM -o RunWizardImport commands, specifying your XML files in the -settingsFile parameter of the 2 commands.

Does that make sense?

Thanks,

Chris.

Basem said...

Thank you for the quick reply;

I have passed through those steps, and i have managed to successfully Export and Copy the .cmp file to the desired the destination. However, once i tried to run "stsadm -o RunWizardImport -settingsFile" on the destination server, i have received "Missing operation name or the operation name is invalid" error, below is the scenario:

stsadm -o RunWizardExport -settingsFile "C:[Path]\[ImportXML].xml" -quiet

Any ideas ?

Thank you again ...

Chris O'Brien said...

@Basem,

Has the Wizard been installed on the destination server? Note that you'll need the '2.0 beta' release - earlier releases did not support command-line use. This release is not currently the default release on Codeplex, so you'll need to specifically download that version.

Your error indicates either:

- you're running an earlier version of the Wizard (e.g. 1.1)
- the stsadmcommands.SPDeploymentWizard.xml file is not in 12/CONFIG (e.g. because the installer hasn't run)
- a typo in the command

The installer puts the stsadmcommands.SPDeploymentWizard.xml, the assemblies in the GAC etc etc.

HTH,

Chris.

Basem said...

It Worked !!

I just manually moved the "stsadmcommands.COB.SPDeploymentWizard.xml" from the Installtion path to 12\CONFIG, and things went fine.

Thank you Chris.

Chris O'Brien said...

Great to hear :-)

Could be the installer failed to put the file there for some reason..

Chris.

Basem said...

Sorry for bothering you again;

Regarding the Import process, i have choosed to overwrite the Version Options, but the imported data didn't ovewrite the existing versions .. where new instances where created. And the same is implied when i choosed Append.

Here is the related part in the XML file:

VersionOptions="overwrite" RetainObjectIdentity="False" UserInfoUpdate="None"

Thank you.

Chris O'Brien said...

@Basem,

No problem :-)

Try again with RetainObjectIdentity set to 'True'. You'll need to import to a fresh (empty) destination environment the first time though, so you should delete that content and then proceed.

Chris.

Tycho said...

Hi Chris,

When instaling the beta in a 64bit environment the installer copy's the stsadm extension to the X86 program files folder ("C:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG") , which prevents stsadm from finding the runimportwizard extension.

Anonymous said...

Dear Chris,
Your Content Deployment Wizard is impressive, I'd developed exactly the same program with content replication in mind between two seperate sharepoint sites, using the SPExport/Import api's. Furthermore, with using the ExportMethod to be Export Changes & ChangeToken, which gives an incremental feature. However, I arrived at a problem when deserializing in the destination you lose the 'url' of the parent item. Which i tried to resolve by setting the TargetParentUrl before deserializing, which seems to work, but i get the next error:
Error: Invalid file name
The file name you specified could not be used.
Which I'm not sure what it means.

Furthermore, when RetainObjectIdentity is false, new objects are created, rather than overwriting the changed items.

Could you help give me some insight into these two areas, or comment on using this method for replication.

Many thanks
William Man

Mondo said...

Hello your tool is much appreciated. I've ran into a problem migrating with the error "Error: The file Lists/Announcements cannot be imported because its parent web /PWA/xxxx does not exist."

I've checked exclude dependencies and unchecked retain object ids but cannot get past this.
Of course the parent doesn't exist. I want to migrate it to a new spot from /PWA/xxxx
Thank you
Ray Letts

Chris O'Brien said...

@Ray,

My guess is you're missing the 'import web URL' value on the first screen. You should absolutely be able to reparent a list in this way, the two requirements are:

- specify the 'import web URL' (as well as the 'site (collection) URL', with the full path to the new parent web
- ensure 'retain object IDs and locations' is unchecked

HTH,

Chris.

Luis Herrera said...

Hi Chris, I'm running an export with the Content Deployment wizard, but it fails after a long time I receive an error message:

Exception Details:

System.Data.SqlClient.SqlException: Timeout Expired . the timeout period elapsed prior to completion of the operation or the servers are not responding...

Could you please help me ??

Thanks!

Chris O'Brien said...

@Luis,

Are you importing/exporting a huge amount of data? Is the Wizard running on a SharePoint machine in your farm?

I've never heard of a SQL timeout occurring with the Wizard before, so these are the only things I can think of.

Chris.

Anonymous said...

yes Chris its a large ammount of data

podious said...

Chris,

We need to run the export without compression, so we decided to use the command line version. However, once the export is finished we don't have a CMP file in the location we specified. We don't get any errors at all on the screen or in the log. I double-checked the XML file that was saved via the GUI and the FileLocation and BaseFileName attributes are set. A lot of DAT files are created along with a handful of XML files, but no CMP file.

Any idea what could be going on?

-Jason

Chris O'Brien said...

@podious,

Yes, that's exactly what should happen for an export without compression - that's what SharePoint does. On the import, set the FileLocation to the folder which contains all these files (I'd also say only the exported files should be in this directory - I've never tried mixing other files in there).

Essentially the .cmp file you get with file compression is all these files in a zip file renamed to .cmp.

HTH,

Chris.

Chris O'Brien said...

@Anonymous,

Can you be more precise? How much data? I know some folks have exported/imported over 15GB with the Wizard, are you way above that?

If so you might be pushing the boundaries somewhat, even though I can't think specifically what might cause a problem with such volumes.

Chris.

Gary said...

Chris,
As it has been said, thank you so much.

I am also trying to use the command line to run an import. What should BaseFileName be set to? Is there anything else I need to set to let the "import" know to expect uncompressed input?

Thanks in Advance,
Gary

Chris O'Brien said...

@Gary,

The BaseFileName property doesn't need to be specified for an import of uncompressed files - you can leave it blank.

HTH,

Chris.

Y. Burger said...

Chris, thanks for a great tool!

I am also trying the uncompressed cmdline import, but when I leave the BaseFileName property blank I get the following error msg: 'The BaseFileName property of SPDeploymentSettings object canno
t have a null or empty string value.'

Chris O'Brien said...

@Y.Burger,

Can you give me the entire command line with parameters (and the XML file) so I can look into this further?

Thanks,

Chris.

vinay said...

It is a great tool. I have performed the following tasks

1) Sub-site to Site Collection
2) Moving only lists to one site to another
I am having the following issue using the Content Deployment Wizard 2.7 (Beta)
a) I did the export using GUI
b) I did the Import until the last step (but didn't run the Import wizard using GUI) and saved the Import template(ImportSettings.xml).

While trying to run the Import file using command line i had the following command
stsadm -o RunWizardImport -settingsFile "S:\FileNamePath\ImportSettings.xml"
I am getting the following error

Microsoft.SharePoint.SPException: Failed to read package file. ---> Microsoft.SharePoint.SPException: Unable to read cabinet
info from S:\PepsiCoSales\PAFDSD-Colombia\pafdsdcolumbiavideocontent.cmp ---> System.Runtime.InteropServices.COMException (0x
8107026A): Unable to read cabinet info from S:\PepsiCoSales\PAFDSD-Colombia\pafdsdcolumbiavideocontent.cmp
at Microsoft.SharePoint.Library.SPRequestInternalClass.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFil
eLocation)
at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.<>c__DisplayClass2.b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)
at Microsoft.SharePoint.Deployment.SPImport.Run()
at COB.SharePoint.Utilities.DeploymentWizard.Core.WizardDeployment.RunImport()

It says failed to read the package file.

Would you let me know where i went wrong?

Thanks,

Vinay.

Chris O'Brien said...

@Vinay,

My suggestion would be to check for the following:

- disk space (on drive where temp files are generated)
- trying to import a .cmp file from a network share/mapped drive
- NTFS permissions

HTH,

Chris.

Vishy said...

Hey Brian, This is a good tool.
we are having sitecollection with multiple subsites, so we are creating one package for each subsite for import and export

We have many people developing so we get many packages created each day which is one xml settings file for each package seems little painful.

Can we have one import settings XML file and the tool can read through it multiple times and import all the packages at once. Do you have this in the existing tool ?

Chris O'Brien said...

@Vishay,

If you need to chain multiple operations one after the other, perhaps the best idea is to use a batch file to do all the imports. You'll still need an XML settings file per import though I'm afraid, that's just how the Wizard is designed.

The code is there on Codeplex though if you really wanted to change it to meet your requirement!

HTH,

Chris.

Eric Halsey said...

Did anyone ever get the command line import to work for uncompressed files?

vinay said...

Did Any one got using Content Deployment Tool for importing Uncompressed list exports? I tried not to give the base file name in the Export settings file and left as empty. I am getting the following error.

Error - unable to validate the deployment settings you chose. Please ensure, for example, you are not exporting a web and specific child objects in th
e same operation. Message = 'The BaseFileName property of SPDeploymentSettings object cannot have a null or empty string value.'.

Any Help is gretly Appreciated.

Dave C said...

@ Y.Burger and Eric Halsey:
I had the same problem importing uncompressed files.
Try adding FileCompression="False" to your Import.xml. Seems like this entry isnt generated by the gui when saving the Settingsfile as it doesnt support nonCompressed import yet.

HTH

Dave

MScizzy said...

Good morning, Chris.

I get the following when trying to do an import through the GUI:


[7/1/2010 10:42:36 AM]: Start Time: 7/1/2010 10:42:36 AM.
[7/1/2010 10:42:36 AM]: Progress: Initializing Import.
[7/1/2010 10:43:17 AM]: Error: Cabinet file is corrupt
[7/1/2010 10:43:17 AM]: Debug: at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.<>c__DisplayClass2.b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)
[7/1/2010 10:43:17 AM]: FatalError: Failed to read package file.
at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)
at Microsoft.SharePoint.Deployment.SPImport.Run()
*** Inner exception:
Cabinet file is corrupt
at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.<>c__DisplayClass2.b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)
[7/1/2010 10:43:19 AM]: Progress: Import Completed.
[7/1/2010 10:43:19 AM]: Finish Time: 7/1/2010 10:43:19 AM.
[7/1/2010 10:43:19 AM]: Completed with 0 warnings.
[7/1/2010 10:43:19 AM]: Completed with 2 errors.

I verified with the developer that they are NOT checking to disable compression.

Any thoughts?

Chris O'Brien said...

@MScizzy,

Hmm, I haven't seen this before. Could it be something as simple as the .cmp file genuinely being corrupt? Does it happen if the file is regenerated by exporting again?

Thanks,

Chris.

MScizzy said...

Looks like the file was actually corrupt. Not sure how, but thank you for the response.