Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SQL exception thrown by the Active Objects library after upgrading to 8.15 - Something went wrong



after upgrade to 8.15 we got the following error in the admin panel:

Bildschirmfoto 2021-03-06 um 07.43.53.png

The instance health shows no error but in the logs following entry is shown:

2021-03-06 06:58:43,344+0100 http-nio-8080-exec-13 url: /jira/rest/insight/1.0/global/config; user: pmarx ERROR pmarx 418x5210x1 9kws0h x.x.x.x.x.x,0:0:0:0:0:0:0:1 /rest/insight/1.0/global/config [] RuntimeException:bundle [com.riadalabs.jira.plugins.insight]com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.riadalabs.jira.plugins.insight] at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$ at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$ at at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:Database: - name:Microsoft SQL Server - version:13.00.4259 - minor version:0 - major version:13 - name:Microsoft JDBC Driver 7.2 for SQL Server - Auf die pk_AO_8542F1_IFJ_OBJ_ATTR_ID-Einschränkung wird von der AO_8542F1_IFJ_OBJ_ATTR_VAL-Tabelle, FOREIGN KEY-Einschränkung "fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id" verwiesen. at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate( 


How can we fix that?

Thanks and regards


1 answer

I'm having the same problem after upgrading to Jira 8.20, did you find a reason/solution?

Dear Dimitri, 

the Insight Application caused the error. Please find below the answer from the atlassian support team:

Those errors usually occur if you have upgraded Insight from a version below 8.4 (You may have been done it in the past) without first carry out the database changes needed,  and now we are carrying over those errors.

We have a KB,  to help to get rid of those errors.

In your case, can you please follow the steps below:

Steps required direct modification in the database. Before applying it to a Production instance, please test on an instance where the issue can also be reproduced, and/or take a database backup before applying the database changes.

  1. Stop Jira.
  2. Execute the SQL below in the database:
    ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL DROP CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id;
    UPDATE propertystring SET propertyvalue = '75' WHERE id = ( SELECT id FROM propertyentry WHERE property_key = 'com.riadalabs.jira.plugins.insight:build');
  1. Start Jira.
  2. Execute the following in the database.
    ALTER TABLE AO_8542F1_IFJ_OBJ_ATTR_VAL ADD CONSTRAINT fk_ao_8542f1_ifj_obj_attr_val_object_attribute_id
  1. Run a clean re-index of Insight.

    Jira > Administration > Manage apps > Indexing Insight > Clean Re-Index

  2. After it, please let me know if you get "Something went wrong. Contact administrator" message.

Hope it helps.



Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you