Workflows and Automation

If you are experiencing intermittent failures with task notifications or email events—specifically the error Format of the initialization string does not conform to specification starting at index —but find that retries eventually succeed, it likely indicates a version mismatch. This occurs when Nintex Automation (K2) is running in a multi-server farm configuration where Fix Pack levels are inconsistent across nodes. How to Resolve: Verify Versions: Navigate to [Your-K2-Base-URL]/autodiscover/updates to check the current update status of each server. Synchronize: Ensure all servers are on the same Fix Pack level. If a mismatch is found, apply the missing Fix Pack or re-run the latest update across the entire farm to ensure uniformity.

During an upgrade, the execution of the  SourceCode.Data.5.1007.1000.0.PostUpgrade.sql script fails with: ExecuteSqlScript.Execute: Logged Error: Script execute failed: System.Exception: Script execution exception: System.Data.SqlClient.SqlException (0x80131904): Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.    at System.Data.SqlClient.SqlConnection.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.SqlCommand.RunExecuteNonQueryTds(String ...