Hi,
We are currently provisioning a CM12 R2 environment. Our solution spans multiple disconnected (secure) environments and hence requires export/import of objects created in the Integration environment into Test and Production environments.
We've hit upon an issue which I think is the same as this one: http://social.technet.microsoft.com/Forums/en-US/8365bf61-ed85-430d-8761-d213aa295ced/action?threadDisplayName=sccm-2012-r2-quotthe-export-application-wizard-completed-with-errorsquot
Unfortunately the OP of that issue worked around and never got to the bottom of the issue. Summary of the problem follows:
1) We create an application that has complex source (i.e. Office 2013)
2) If we immediately export this application it exports fine
3) If we have to make any changes to the application (i.e. adding new files to the source such as scripts) and therefore create additional revisions the application fails to export - error message indicates one of the nested folders as the cause of the failure because it is not a file
4) We can recreate the issue on demand and with different applications - definitely not a permissions issue
5) If we revert to an earlier revision (before the source was updated) then the export succeeds, even though the actual source directory now contains different files
It looks very much like there is a bug in R2 (we've also applied CU1 and confirmed the problem remains) which is causing something within the content library to get messed up when source is updated. We have a customer running CM12 SP1 (not R2) and this behaviour cannot be recreated, so seems to be an issue introduced in R2. Does anyone else have this problem?
For now we are able to workaround the issue by recreating the application once all source code updates have been completed, but this is adding lots of overhead to the process.
Thanks