I recently created screen schemes and had deleted them too. Unfortunately, now I can't access Administration -> workflows. Its showing up the following sytem error:
Followed by a huge message. I am using JIRA enterprise version and so I am not able to get support. It would be really great if someone could help me out with this.
Ouch. I've done that in the past (it's nothing to do with "screen schemes" though, you've created a "screen", used it in the workflow, and then deleted it). It sounds a little odd to me though - I was usually able to get into the list of workflows, to have it crash out if you click on the damaged workflow.
Are you really getting the error when just going into the list of workflows? Or is it like my memory, and you on;y get it when you try to do something with a workflow?
If it's that broken, your only option might be database hacking, but I'd rather not start describing that if we can avoid it.
Hi Nic! Thank you for a quick response! You're right! I created a screen, used it in workflow and then deleted it to create a new one.
I am getting the error when I goto the list of workflows. I tried both Administration - > Global Settings -> Workflows and Workflow Schemes - > View all workflows. Both are showing the same error message. I am able to edit the already existing workflows which are linked to the workflow schemes from workflow scheme screen. But I am unable to create new workflows or copy workflows as I can't access the workflow screen.
I'm a newbie on JIRA(3 weeks old) so I got confused with the steps that I took to create a screen and wanted to try it again from the beginning.
Can we get the workflow list back someone?
I'm afraid I only know of one way to do this in Jira 3.x
Now the following error shows when I try to login to JIRA:
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist SVR4 Error: 2: No such file or directory )
Any idea what this means?
I came across this KB which can fix the issue. Try out the fix in a staging/QA environment.
This problem has been documented in the following KB:
Try to follow the instructions from it and the problem should be resolved!
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG