Facing an error while deploying a Site, any idea on the root cause and fix?
Deploy Log: Status: Failed. Current step: Importing Application. Log file URL: sdfewedf:2323/.../170. Error message: Error: object null of type 236 failed to import. Error msg: An error occurred while creating site [uuid=73235167-6123a-4c2d-9088-f6f7623b024d]: org.hibernate.NonUniqueResultException: query did not return a unique result: 2.
Inspect Log: Problems (1):site 73235167-6123a-4c2d-9088-f6f7623b024d "Dummy Site Name": An error occurred while creating site [uuid=73235167-6123a-4c2d-9088-f6f7623b024d]: org.hibernate.NonUniqueResultException: query did not return a unique result: 2 (APNX-1-4071-007)
Thanks,
Discussion posts and replies are publicly visible
Hi SathishKumar,
Can you please validate that you do not have a "Dummy Site Name" site in your target environment with a different uuid?
Thanks Pedro for the response. We have checked and there is no "Dummy Site Name" site in the target environment with a different UUID.
Though not exactly the same but we found below link on Appian KB
https://community.appian.com/support/w/kb/1654/kb-2066-connected-systems-object-authorization-fails-with-query-did-not-return-a-unique-result-following-import
We are now trying to re-create the Site afresh from Dev and deploy in all higher environments.
The issue is resolved. In few UAT Appian database tables (CFG,GRP,USR), there were duplicate entries made for 'Administrator' id . Entries like 'GROUP_INDEXING_STRATEGY_VALUE, COLLAB_CONTENT_INDEXING_STRATEGY' value were duplicated. How it got entered is not known, may be because of database inconsistencies (there was some DB table space issue at that time in UAT). So, when Appian App server executes query to fetch these value from the above mentioned tables and it got a duplicate entry where its expects only a UNIQUE value. This was cause of the problem for both Tempo login issue and Site deployment issue (depends on COLAB_CONTENT_INDEXING_STRATEGY ). It was fixed with help of Appian Support Engineer by deleting the duplicate entries of 'Administrator' and re-starting the server.