Error after server migration

[eguemie...@dartdigital.com.br]

Hello.

This error occured after migration to another server. Anybody knows which the problem? How to resolve it?

"Exception sending context initialized event to listener instance of class org.sonar.server.platform.PlatformServletContextListener

org.apache.ibatis.executor.BatchExecutorException: org.sonar.db.property.PropertiesMapper.insert (batch index #2) failed. 1 prior sub executor(s) completed successfully, but will be rolled back. Cause: java.sql.BatchUpdateException: Cannot insert the value NULL into column 'id', table 'SonarQube.dbo.properties'; column does not allow nulls. INSERT fails."

Tks for help.

[Simon Brandhof]

Hi,

It's hard to help you without more details. You should at least provide informations about versions (initial and target), database and plugins. Full logs would also be helpful.

Regards 

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/7d809fe6-0331-43e7-a276-e85beaf1dcf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

[eguemie...@dartdigital.com.br]

Adding more information.

The version of Sonar is the 5.4 with the same database version and plugins are: C# 5.1, Java 3.13.1, JavaScript 2.12, Jira 1.2, SCM Git 1.2, SCM SVN 1.3.

The log file is at link Log Sonar.

Tks for your help.

Att,

[Simon Brandhof]

Hi,

Your problem is strangely similar to this issue in Atlassian JIRA : https://confluence.atlassian.com/jirakb/cannot-insert-the-value-null-into-column-id-table-jira_backlog_test-dbo-ao_60db71_lexorank-column-does-not-allow-nulls-insert-fails-849065670.html

Quoting the article: "This issue has been observed to happen after a database collation change in MS SQL server. [...] The cause is still not known.".

This is the case in SonarQube 5.3, mssql collation is being changed, so I suppose that you're upgrading from a version <= 5.3.

I recommend to give a try to version 6.1, which improves management of collation (see SONAR-7988). If it does not work, you should try the resolution suggested by Atlassian by re-adding the missing primary keys.

I hope it helps.

Regards

--

You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/9245d27f-fbb6-4a6d-b3ce-c43a2c772998%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.