Error on first project creation after clean install

[Justin Kelly]

I have been fighting getting my Jira installation going since Friday with no help related to the issues I am seeing.

Versions:

Windows 10 Pro 10.0.16299

Jira 7.7.2

MySql Community 5.7.21.0

JDBC driver mysql-connector-java-5.1.45-bin.jar (in Jira lib folder)

Here's what happens:

1) Install MySql

2) Set collation to utf8_bin in MySql database

3) Install Jira 7.7.2

4) Arrive at "Welcome!" page

5) Select "Create a new project"

6) Select "Project management"

7) Next screen, Click "Next"

8) Next screen, Click "Select" to choose the workflow

9) Next screen, specify project name and key, and click Submit

10) See "oops" Error 500 show in browser

11) Hit back button, can't create the project again because it says it already exists!

The jirasoftware190218175645-stdout.2018-02-19.log file shows errors (see below).

Very first error in the log is:

2018-02-19 18:08:51,994 http-nio-8080-exec-4 ERROR anonymous 1088x36x1 qyzoho 0:0:0:0:0:0:0:1 /secure/SetupMailNotifications.jspa [c.a.j.p.hipchat.service.HipChatPluginLauncher] Unexpected error during launch
com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.labs.hipchat.hipchat-for-jira-plugin]
at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95)
at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86)
at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:38)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:MySQL
- version:5.7.21
- minor version:7
- major version:5
- name:MySQL Connector Java
- version:mysql-connector-java-5.1.45 ( Revision: 9131eefa398531c7dc98776e8a3fe839e544c5b2 )

Subsequent errors are all like:

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'ao_587b34_glance_config' already exists

...

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'ao_e8b6cc_issue_mapping' already exists

...

2018-02-19 18:08:52,432 http-nio-8080-exec-4 ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.jira.event.issue.field.CustomFieldCreatedEvent@7778f1a1] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.greenhopper.customfield.lexorank.LexoRankCFListener.onCustomFieldCreated(com.atlassian.jira.event.issue.field.CustomFieldCreatedEvent), listener=com.atlassian.greenhopper.customfield.lexorank.LexoRankCFListener@f53588a}]
java.lang.RuntimeException: bundle [com.pyxis.greenhopper.jira]. Listener: com.atlassian.greenhopper.customfield.lexorank.LexoRankCFListener event: com.atlassian.jira.event.issue.field.CustomFieldCreatedEvent

[Justin Kelly]

The following resolved my issue, hopefully this will help anyone that experiences the project creation errors and the "table already exists" errors I saw.

As odd as it sounds, it related to HipChat integration settings when I don't have or need Hipchat.

I started here:

https://community.atlassian.com/t5/Jira-Software-questions/Crashes-at-creating-a-project/qaq-p/651662

and followed what it says here:

https://confluence.atlassian.com/confkb/how-to-disable-hipchat-integration-pop-up-dialog-794500518.html

I searched for anything "hipchat" while on the system "manage add-ons" page and disabled all of them.

Once I did this, I was able to create a new Jira project with no errors that occur or when I click on anything or select any options within the Jira application.  It finally works!

Just a guess...the initial project creation error related to hipchat somehow left things in a half-baked state. No idea, but it works now.

[Nic Brough -Adaptavist-]

"Table already exists" suggests that you are pointing a new Jira install at a database that already has a Jira installation.

Do not do that, it will not work.  Install your Jira with an empty database.  Or tell the installer to upgrade an existing Jira in there, not create a new one.

[Justin Kelly]

Additionally, if you actually read my log listing above for this issue, it was a different version (7.7.2) and the initial error wasn't "table already exists".

It was a hipchat bundle integration error of some sort.  I don't even have hip chat or need it.

[Justin Kelly]

In case this might help, I haven't added anything with HipChat as part of my installation/environment.  Just the Jira Server, and just MySql server backing database.

And regarding the "table already exists" errors I'm quite clear I've deleted MySql before re-install as it will tell you the database folder exists during installation, at which point I have canceled MySql installation, deleted the C:\ProgramData\MySql folder, and re-launched the MySql installer.  Besides, I've uninstalled and re-installed MySql and Jira Server so many times it's not easy to forget the database deletion step.

Any true investigation of why I'd be getting that first error and then the subsequent ones would be much appreciated.

Does anyone know if the Jira engineers have worked with the versions I listed together in their own lab environment to repeat the "table already exists" issue I see?  Specifically these:

Windows 10 Pro 10.0.16299

Jira 7.7.2

MySql Community 5.7.21.0

JDBC driver mysql-connector-java-5.1.45-bin.jar (in Jira lib folder)

...or all of those but with Jira 7.7.1?