Hide Forgot
Date of First Response: 2009-11-26 06:01:55 project_key: SOA If the server is configured to run against MSSQL2005 it throws an exception 2009-11-26 02:46:31,538 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.esb:service=JBPMDatabaseInitializer state=Create mode=Manual requiredState=Installed com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert explicit value for identity column in table 'JBPM_ID_USER' when IDENTITY_INSERT is set to OFF. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246) at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83) The reason is that JDatabaseInitializer service executes import.sql. This file tries to write values to identity column which is not supported for all databases. Cutomer should not be forced to change database wide config setting just for the first server startup.
1) We did not require this file for 4.2 and 4.3, so it should be possible to remove it. 2) Multiple tables with identity columns will not work with MS-SQL: http://msdn.microsoft.com/en-us/library/ms188059.aspx
Fixed with revision 4371 of: build-tools/builders/esb/pre-patch/empty_import_sql.xml (added) build-tools/builders/esb/resource/jbpm-sql/import.sql (added) Commit message: SOA-1651 Replace import.sql with an empty file. We do no need the user, group and membership details in the database on the platform.
Verified in ER5