Status: Open
Status: Answered
Status: Closed
Status: Duplicate

MBPM Deployment error for a process converted from 7.6 to 9

0
Posted Feb 17 by Deleep Nair.

Getting the following error when deploying the solution:

Fatal -> System.Data.SqlClient.SqlException (0x80131904): String or binary data would be truncated.

The statement has been terminated.

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.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.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
at Metastorm.Deployment.Maps.MapDeployer.InsertActions(Map map, IEntity rootEntity, DeploymentInfo info)
at Metastorm.Deployment.Maps.MapDeployer.PrepareInsertStageCommand(DeploymentInfo info, IEntity rootEntity, IStageInfo stageInfo, Int32 priority)
at Metastorm.Deployment.Maps.MapDeployer.ProcessStages(Map map, IEntity rootEntity, DeploymentInfo info, PrepareStageCommand prepareStageCommand, ProcessFolderPages processFolderPages)
at Metastorm.Deployment.Maps.MapDeployer.InsertStages(Map map, IEntity rootEntity, DeploymentInfo info)
at Metastorm.Deployment.Maps.MapDeployer.PrepareInsertStageCommand(DeploymentInfo info, IEntity rootEntity, IStageInfo stageInfo, Int32 priority)
at Metastorm.Deployment.Maps.MapDeployer.ProcessStages(Map map, IEntity rootEntity, DeploymentInfo info, PrepareStageCommand prepareStageCommand, ProcessFolderPages processFolderPages)
at Metastorm.Deployment.Maps.MapDeployer.InsertStages(Map map, IEntity rootEntity, DeploymentInfo info)
at Metastorm.Deployment.Maps.MapDeployer.Deploy(IEnumerable1 entitiesToDeploy, IEntity rootEntity, DeploymentInfo info) <br />at Metastorm.Deployment.Core.DeploymentService.DoDeploy(IEntity rootEntity, IEnumerable1 entities)
at Metastorm.Deployment.Core.DeploymentService.Deploy(IEntity root, IEnumerable`1 entities)
ClientConnectionId:764624a3-5b35-4439-ac3a-81ceea03ea69 -> 2/17/2016 4:53:36 PM

2 Answers

1
BEST ANSWER: As chosen by the author.

By "converted" do you mean you ran it through the V7->V9 solution migrator? If so, did you do clean-up after? (There tends to be a lot that doesn't convert well, so manual intervention is needed after before it can successfully deploy. Though I wouldn't think it would be truncate issue, but just wouldn't validate.)


0
BEST ANSWER: As chosen by the author.

This has been resolved. Brian you are correct, it was an issue of not cleaning up everything. Even though, the error message said it is an issue with inserting action, the culprit was the "Auto-forward Folder To" value set on a system stage which was higher than the allowed 250 characters.


 You have subscribed and will receive email notifications of updates to this topic. To unsubscribe, uncheck the checkbox.

Statistics

Related categories

Your answer

To leave an answer, please sign in.