String or binary data would be truncated

We have a very strange issue in version 9.1.1.1. We are getting the message:
Exception 'The statement has been terminated.
String or binary data would be truncated.' occurred when attempting to 'MBO update'.

The stack trace is:
   at Metastorm.Engine.Connectors.OleDBConnector.Update(DataSet changedData)
   at Metastorm.Runtime.Core.Mbo.MboConnection.Update(DataSet changedData)
   at Metastorm.Runtime.Core.Mbo.ExternalDataMbo.SaveDataToDB()
   at Metastorm.Runtime.Core.Mbo.ExternalDataMbo.Commit()
   at Metastorm.Runtime.Models.TenderingAutomation.TA_Tender.Commit()
   at Metastorm.Runtime.Core.Maps.Map.OnCommitAction(Object sender, EventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at Metastorm.Engine.Runtime.FolderData.OnCommitAction()
   at Metastorm.Engine.Runtime.Folder.SubmitData()
   at Metastorm.Engine.Operations.FolderOperationHandler.CommitAction(String folderId)
   at Metastorm.Engine.Operations.SubmitActionHandler.Process(String sessionId, String callerId, CultureInfo culture, String clientData, DateTimeOffset requestTimestamp, String folderId, String actionName, String formName, Boolean noLayout, Boolean autoReopen, Boolean autoChain, Collection`1 fieldInputList, String serverData, String clientType)
   at Metastorm.Engine.Operations.FolderOperations.SubmitAction(String sessionId, String callerId, CultureInfo culture, String clientData, DateTimeOffset requestTimestamp, String folderId, String actionName, String formName, Boolean noLayout, Boolean autoReopen, Boolean autoChain, Collection`1 fieldInputList, String serverData, String clientType)

What is irritating is that this implies this occurs when the action submits, and yet the Designer Log entry lists the Form name and the action, which implies to me (from what I know of how the engine should work) that this occurs on the form save.

The error also points to an Editable Grid BO, as this particular has been reported when these go wrong. We do have one on the form although we are not adding or deleting rows, but I also believe that the process BO acts in a very similar way anyway.

Of course, this is impossible to reproduce in a test environment, despite using seemingly identical data.

Does anybody have an idea when this is happening, or why?

Find more posts tagged with

BPM

Comments

Brian Mellert

As mentioned in your forum, the one thing I really miss is meaningful / useful error messages when BPM encounters an error. We used to have pre/post eval and details messages in V7, but nothing of use / guidance in V9. Seeing the SQL helped to quickly identify issues. The dump below tells me little, except that "something" is too big for a particular data field.

Makes trying to find the core issue a challenge in a production enviroment where you can't start throwing in debug messages on the fly.

Robert Vignerot

Generally, I've seen this when the field size doesn't match the variable size of the Business Object. I agree it would be nice it the details included which field and business object was to blame.

Jerome_Pearce

I cannot for the life of me even discover if it is a process variable or a grid field. It appears that our error reporting has reverted to worse than even version 5.

When coupled with the fact that if any C# code does not parse correctly, every single element in the solution thows an error on validation or deployment, makes error diagnosis next to impossible. Is there really no drive to fix either of these? It would serve customers much better than adding features IMO.

Brian Mellert

It appears that our error reporting has reverted to worse than even version 5.

When coupled with the fact that if any C# code does not parse correctly, every single element in the solution thows an error on validation or deployment, makes error diagnosis next to impossible. Is there really no drive to fix either of these? It would serve customers much better than adding features IMO.

Agree fully!!