To confirm what you are saying: Before the upgrade, in your AyaNova 3, there was no duplicates of Head Offices, but now there is - correct?
What configuration of AyaNova were you usingt with AyaNova 3 and that you are using with AyaNova 4.1.5 - stand-alone default or network Firebird Server or SQL Express or SQL Server 2000 or SQL Server 2005?
What was the exact full version of AyaNova before you upgraded - Were you using AyaNova 188.8.131.52 before upgrading to AyaNova 4.1.5?
When you first ran AyaNova 4 on your database, did you confirm that no other AyaNova program such as network Generator, dataportal, etc was running?
I would recommend that if your database was 184.108.40.206 to make sure all AyaNova programs are shut down, than restore your AyaNova 3 database again, and than on the server run AyaNova and let it update to AyaNova 4.
If you continue to experience an issue, please send directly to email@example.com the following:
copy of your AyaNova 3 database file backup - zipped using WinZip
The exact full version of AyaNova 3 before you upgraded to 4.1.5 (i.e. 220.127.116.11, or 18.104.22.168 etc)
What configuration was your AyaNova 3 - standalone, network Firebird Server, SQL Express, SQL Server 2000 or SQL Server 2005
Is this the same configuration of your AyaNova 4
zipped copy of your ayalog.txt from the AyaNova 4 program folder
If possible, zipped copy of your ayalog.txt file from your AyaNova 3 program folder.
AyaNova Administrator username and password
Do let me know if restoring from backup and repeating the upgrade steps fixes this, as well as answers to the info above, or if redoing that does not work, that you will be sending the information and database requested.