The standard mechanism for creating new archive IDs tries to create an ID by modifying the second position of the ID of the parent archive ('0' - 'Z'), i.e. the children of parent archive 'AB' get the Ids 'A0', 'A1', ...
Now, if this doesn't give a valid ID the first available ID in the range '00' - 'ZZ' is used.
The standard mechanism for creating new archive IDs tries to create an ID by modifying the second position of the ID of the parent archive ('0' - 'Z'), i.e. the children of parent archive 'AB' get the Ids 'A0', 'A1', ...
Now, if this doesn't give a valid ID the first available ID in the range '00' - 'ZZ' is used.
The customer have to deleted all archives and create new archives with other names.
Because the customer works with a lot of templates, it is hard to fix all project with this structure.
Fix needed for 7.60 and for 8.0, that this issue not more occures, that automatically illegal characters created in aggregrated archives