I am getting an Internal Server Error when I am trying to create a support request with Atlassian Support from within JIRA? What is causing this? My JIRA instance seems to be working just fine and I am not encountering any other issues with JIRA at the moment. I am including a screenshot. Please advise.
Well, the answer is technically "go to where ever you keep the log file and open it with a text editor of your choice", but a better one (to save asking if you've done default installations, what you've set up and so on) is
1. Go to Jira -> Administration -> System information
2. Look through that page for the log file section, it will tell you exactly where it is on the server
3. Go on to the server and open that log file
There could be quite a lot of it, so you probably want to search for a time-stamp around the time you generated this error.
Hi Nic, it mentioned something about a Crowd.properties file on the server. The log file said:
2012-09-07 /plugins/servlet/stp/view/create-support-request/execute [support.tools.salext.DefaultApplicationFileBundle] The file E:\Apps\JIRA\atlassian-jira\WEB-INF\classes\crowd.properties could not be found or is not readable, and was skipped.
2012-09-07 08:45:30/plugins/servlet/stp/view/create-support-request/execute [support.tools.salext.WildcardApplicationFileBundle] The file E:\Apps\JIRA\logs\host-manager.2012-07-18.log does not contain any data, and was skipped.
I was not able to locate the Crowd.properties file in the directory specified. Do you think it might be a hiddent file or something that is created when we login to JIRA as an administrator.
You should be able to ignore those if you aren't using Crowd for authentication. The "support request" code is looking for the files in case you have got Crowd, but as you haven't, the log is simply reporting "not there".
I'd look for other errors in the log, I don't think this one is an issue.
This error might have happened due to a bug on Support Tools plugin which affects versions 2.10, 3.0 and 3.0.8 (STP-138)
The document below describes the issue in more detail:
Let's try a silly question: are you using Crowd for authentication? Or do you use Jira for user management?
You should have several Jira logs available to you. Check the /logs directory in your Jira install directory. The catalina.out file will be the real money. Warning: the file may be large, especially if you haven't restarted Jira in a while. There are also several logfiles in $JIRA_HOME/log (Windows: %JIRA_HOME%\log).
Thank you Nick, I will keep searching for more errors. It cleared up on its own all of a suddent and I was able to send the support request to Atlassian. I dont think we use Crowd for authentication but JIRA Delegated Authentication for User Management. Thank you once again for your help and guidance.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs