I'm getting error.jsp and blank page while jira URL is entering

Mahesh Kallepalli_u4afak

Pelase find below logs and let me know what's the problem and how to resolve it .

at java.lang.Thread.run(Thread.java:748)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'MOVED_ISSUE_KEY'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:259)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1547)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:857)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:757)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7344)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:224)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:204)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:659)
at org.apache.commons.dbcp2.DelegatingStatement.executeQuery(DelegatingStatement.java:207)
at org.apache.commons.dbcp2.DelegatingStatement.executeQuery(DelegatingStatement.java:207)
at com.atlassian.jira.startup.DatabaseLauncher.cleanupDatabaseTableName(DatabaseLauncher.java:238)

Andy Heinzer

HI Manesh,

I see that you appear to be getting a MS SQL exception in your stack trace.   Unfortunately, this specific error is not common enough for us to know the precise cause yet.  I suspect that Jira is trying to access this database element, but either it does not exist, or Jira does not have the proper SQL permissions to access it.

Could you let us know some more about your environment?  Such as:

1. When did this problem start?
2. What version of Jira is this?
3. What version of MS SQL database is this? (2008, 2012, 2014, etc)
4. When does this error happen exactly?  It seems like this might be the startup of Jira.
5. Are you trying to setup Jira for the first time here?  Or is this a database migration or upgrade of Jira?

It might also help to take a closer look at the stacktraces before and after this one to see if one of these might contain a complete SQL query that triggered this specific error.  It could help us to better understand what exactly caused this error message.

 

I have a suspicion that Jira might be using an unsupported database version for the version of Jira you are using, OR that the way that database is setup is incorrect.  It is also potentially something that could be caused by a misconfiguration of Jira's own $JIRAHOME/dbconfig.xml file.  But without knowing more, this is just a hunch right now.   The answers to the questions above should help us to narrow the scope of troubleshooting here.

Regards,

Andy