Kinetic 2022.2 STRING_SPLIT Error

Getting a STRING_SPLIT error logging onto client on the server for the first time after installing 2022.2

Anyone else getting this error?

Ice.Common.EpicorServerException: Invalid object name 'STRING_SPLIT'.
 ---> System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'STRING_SPLIT'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Ice.Resources.Translation.TranslateList(SqlConnection dbConnection, String languageId, String programId, String companyId, Boolean findSimilar, List`1 transList) in C:\_releases\ICE\ICE4.2.100.12\Source\Server\Framework\Epicor.Ice\Translation\Translation.cs:line 501
   at Ice.Resources.Translation.TranslateList(IDataContext ctx, String languageID, String programID, Boolean findSimilar, TranslationEntryList& transList) in C:\_releases\ICE\ICE4.2.100.12\Source\Server\Framework\Epicor.Ice\Translation\Translation.cs:line 402
   at Ice.Resources.Translation.TranslateDictionary(IDataContext ctx, String languageID, String programID, Boolean findSimilar, Dictionary`2 dict, Boolean returnOnlyTranslated) in C:\_releases\ICE\ICE4.2.100.12\Source\Server\Framework\Epicor.Ice\Translation\Translation.cs:line 300
   at Ice.Resources.ResourceStringManager.GetString(String id, String programID) in C:\_releases\ICE\ICE4.2.100.12\Source\Server\Framework\Epicor.Ice\Resources\ResourceStringManager.cs:line 156
   at Ice.Resources.StringsBase`1.GetString(String id, Object[] args) in C:\_releases\ICE\ICE4.2.100.12\Source\Shared\Framework\Epicor.ServiceModel\Resources\StringsBase.cs:line 83
   at Ice.Lib.SessionMod.Resources.Strings.SeedDataMgrErr(Object arg0, Object arg1) in C:\_releases\ICE\ICE4.2.100.0\Source\Server\Services\Lib\SessionMod\Resources\Strings.Designer.cs:line 134
   at Ice.Services.Lib.SessionModSvc.Handshake(Version clientVersion) in C:\_releases\ICE\ICE4.2.100.0\Source\Server\Services\Lib\SessionMod\SessionMod.cs:line 344
   at Ice.Services.Lib.SessionModSvcFacade.Handshake(Version clientVersion) in C:\_releases\ICE\ICE4.2.100.0\Source\Server\Services\Lib\SessionMod\SessionModSvcFacade.cs:line 464
   at Microsoft.Extensions.Internal.ObjectMethodExecutor.<>c__DisplayClass33_0.<WrapVoidMethod>b__0(Object target, Object[] parameters)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.VoidResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
ClientConnectionId:9f838cb4-d75a-4a91-9f95-a5ba3c5d8738
Error Number:208,State:1,Class:16
   --- End of inner exception stack trace ---

Did you report it to support?
Looks like your database compatibility level is low and does not understand STRING_SPLIT function

3 Likes

Did the same exact thing last week… You need to change your db compatibility level in SQL BEFORE pushing the db through the upgrade process.

2 Likes

oh, i thought it is cloud. For local DB, yes, you have to update compatibility level yourself.

1 Like