Full backup from 4.1 to 5.0 imports objects with wrong path in Functional Structure
When upgrading from SV4.1 to SV5.0, we use the full backup tool to import system. When importing system into SV5.0, there are lots of objects that are imported outside of the functional structure root with the path [Functional Structure]Object name.
In SV4.1 these objects have many references and are duplicated from Control Strc to Functional Strc; some of them fail to import but some others not, ones that fail are under Security definition aspects, maybe is a problem maybe not.
Hi, It is better to load full backup to 5.0 system as it has dependent aspects in control structure.Try to load maintenance backup of 4.0 system to your 5.0 system. Before loading into 5.0 system,Make sure zero errors and warning in 4.0 system when you are taking backup.
Something pretty serious has gone wrong. This shouldn't happen.
- Did the Parents of the mis-placed objects get imported correctly ? - This looks like a MOD300 system. Are the MOD300 Extensions installed - ie Environment Structure etc ? - Did the objects get placed correctly in the Environment structure.
Ultimately, you will need to backtrack and import the system again. Make sure you have performed a consistency check before you backup the version 4 system. Follow the upgrade procedure carefully and follow up on any error and warning messages that you receive.