The Scheduler not working after upgrade

[Adam Levitt]

Following our upgrade from JIRA 6.2.5 to 7.0, the scheduler add-on was listed as expired. It was actually expired Nov 2016, but still working prior to the upgrade and did not generate any error of it being expired. We had paid for the license already though, and I reapplied the license with no issue. However, the add-on is not generating tasks and the site https://jira.dimensional.com/secure/AccessManager!default.jspa returns 404 error.

I consulted with Atlassian support, and they ended up siting the following fix: ALTER TABLE [JIRA].[dbo].[AO_A406ED_SCHEDULED_ISSUE] DROP CONSTRAINT [U_AO_A406ED_SCHEDUL1453239299]

Attached is our support zip. I wanted to check with your team before moving forward with this fix.

[Adam Levitt]

What would be the rollback command for this?

ALTER TABLE [JIRA].[dbo].[AO_A406ED_SCHEDULED_ISSUE] DROP CONSTRAINT [U_AO_A406ED_SCHEDUL1453239299]

[Łukasz Modzelewski]

Duplicate of #129.

[Łukasz Modzelewski]

Hi Adam,

Please check linked issue: https://bitbucket.org/apdc/the-scheduler/issues/129/the-scheduler-can-not-access-access

There is an explanation and solution provided.

Cheers,

Łukasz

[Adam Levitt]

What would be the rollback command for this? ALTER TABLE [jiradbschema].[AO_A406ED_SCHEDULED_ISSUE] DROP CONSTRAINT [U_AO_A406ED_SCHEDUL1453239299]

[Bartosz Gilewski]

Hello Adam,

If I understand correctly, are you asking for a command that would put back the constraint (undo changes from command from "ALTER TABLE [jiradbschema].[AO_A406ED_SCHEDULED_ISSUE] DROP CONSTRAINT [U_AO_A406ED_SCHEDUL1453239299]" ) in case you would want to get back to JIRA 6.2.5 ?

Best regards, Bartosz

[Adam Levitt]

We will not be going to v6.2.5. Are you suggesting that this constraint does not need to be there ever if we are on v7.0 and beyond? My assumption was that if this fix does not solve our problem then we should put the constraint back.

[Adam Levitt]

Will we need to restart JIRA? Will we need to stop services to run this drop statement?

[Bartosz Gilewski]

This constraint comes from the older versions of The Scheduler (before 3.3.x) and was later removed, so it does not need to be in the versions for JIRA 7.0+ Plugin should have automatically removed constraint during the upgrade, but for some reason that did not happen, and because of the existing constraint plugin is not working correctly.

Yes, you have to stop JIRA before executing drop statement.

Best regards, Bartosz