Error message when server first starts

When the server first starts after you have migrated the databases, you might see a database communication error about too many results. This error can safely be ignored. However, if you are using a SQL Server database, and you see errors about invalid object names, you must turn off XACT_ABORT.

If the error message is similar to the following message, it can safely be ignored:

com.ibm.mm.server.persistence.rdbms.dao.ibatis.BaseDaoreadPathByPath BMWSD0429E: An SQLException was encountered while communicating with the database.  Error code: 0, SQL State:  null, Message:  Error: executeQueryForObject returned too many results.

If the error message is similar to the following messages, fix it by turning off XACT_ABORT before you start the server.

Line 62310: [7/5/17 14:50:10:916 PDT] 00000073 SQLServerExce 1
*** SQLException: com.microsoft.sqlserver.jdbc.SQLServerException:Invalid object name 'FNGCD'.
Msg 208, Level 16, State 1, Invalid objectname 'FNGCD'.
Line 62724: [7/5/17 14:50:10:948 PDT] 00000073 SQLServerExce 1
*** SQLException: com.microsoft.sqlserver.jdbc.SQLServerException:Invalid object name 'FNGCD_ADDON'. 
Msg 208, Level 16, State 1, Invalidobject name 'FNGCD_ADDON'.
[7/3/17 15:51:17:172 PDT] 00000072 WSJdbcPrepare <  execute Exitcom.microsoft.sqlserver.jdbc.SQLServerException: 
Distributedtransaction completed. Either enlist this session in a new transaction
or the NULL transaction.atcom.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)