An error occurred while attempting to move the folder (Configuration Factory)

[Maxim-CADman77]

Vault administrator gets message "One or more files cannot be moved. See details for more information" during attempt to drag-n-grop IAM Configuration Factory from ordinary folder to "Library" folder using Vault Explorer Pro 2014 SR1

Detail contain the name of the IAM (file. not folder) and statement "An error occurred while attempting to move the folder".

Where to search for the root of the issue?

[r.smith1]

Hi Maxim,

Please move the factory and the members all at one time.  Will they move?  Are they in any category, or lifecycle state that might prevent them from moving?

[Maxim-CADman77]

Not sure that I uderstand correctly statement "move at one time".

If I select CF and CM-folder and drag&drop them - Vault creates shortcuts istead (same happens if try to d&d the CM-folder). 

If I select CF and CM-files (in search results) attempt to drag&drop them fails with message "The selected files do not reside in the same folder. To move a group of files, they all must be located in the same folder".

We don't use categories and lifecycles for files. All our files belong to Base category and these CMs are not linked to Items yet.

[Maxim-CADman77]

Almost a week since the last recommendation recieved ... any further suggestions yet?

PS: The case # is 09226804

[r.smith1]

Hi Maxim,

Yes, move at one time means select all of the files you need to move, and move them at one time rather than moving one file at a time.  

[Maxim-CADman77]

Please pay attention - I doesn't try to move several files (Vault does).

I'm trying to move one IAM-file (Classification = Configuration
Factory).

[subsales]

Hi Maxim,

If this is a configuration assembly, you need to try to move not only the factory assembly, that you're trying to move, but also the member folder residing with the factory.  Generally speaking though, configuration files are a little more difficult to move due to dependencies than regular files.   If it won't move (per the steps I recommended), then you may have to live with the assembly residing in the current location.  

Another option is to check out the factory, and ALL members, migrate them to the current release you are working with (if they were created in a past release) regenerate all members and then check them all back into the Vault then try to move the files.  Again if this does not work, I defer to my comment above.  

[swalton]

I gave up trying to move iAssembly factorys around Vault 2008.

I do not know if there have been any improvements in the last 6 years so I may incorrect, but I don't think you can move iassembly factory files without moving the members. 

If the members are located in a sub-directory under the factory directory, I don't know how you can grab all the required files at once.

You might be better off deleting the files from Vault, moving them with Windows explorer, and checking them back into Vault.  There are some drawbacks to this if you have lots of history or other assemblies/ipns/drawings that depend on the iAssembly factory or its members...

I gave up on using iAssemblies and Vault, execpt for very limited usage, because of this and the check-in/check-out requirements of childern when making changes to the parent.

[Maxim-CADman77]

The Configuration Factory and Configuration Members are all migrated to format of Inv2014SP1Upd2 and up-to-date.

I do not suffer any problem while moving CFs between ordinary folders (I do it quite often and every time CM-folder moves as well).