Could you paste the error message from the log. Tablespace errors are usually due to running out of space. It's like filling up your hard drive. The solution is to add more space. It almost sounds like you are instead running in to the 8060 byte limit of MS SQL Server. That is a completely different issue and possible resolution, which is why I'm asking for the actual error message.

--Mark

Hi Mark, thank you for the reply! We have been told that the issue is the 8060 byte limit of MS SQL Server.  We have also been told that this is directly related to the total character count of the data stored on the lease. However, we are not seeing consistency in the leases that are getting stuck (some don't have a lot of data, some do).  

Here's one of the errors.  I'll also note that some leases throw this error, but we have one lease that won't save any additional data on it, but is not throwing any errors (that we have found).

2025-03-31 11:27:32,054 WARN  [com.tririga.platform.error.ErrorHandler](WebContainer : 12) Problem detected processing workflow: |Workflow> WFTID=14010613.29 WFIID=446320217964535 PID=none Name='triContract - Synchronous - Module level business rules' Module='triContract' BO='-Any-' Event='Pre-Create' SO=244937937 SP=10 SC=40 TS=1743438451663 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=12035157.117 WFIID=446320217964532 PID=none Name='triRealEstateContract - Synchronous - Permanent Save Validation' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=28 SC=40 TS=1743438451632 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=108817201.7 WFIID=446320217964526 PID=none Name='triRealEstateContract - Synchronous - RE Lease Validations on Submit For Accounting Review' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=16 SC=40 TS=1743438451554 TE=1743438452054 Mode=S EID=1512921039 IE=1512921039 |Event> ID=1512921039 Name='triSubmitAccountingReview' User=203707542 SO=244937937 BO=10002490 BO_NAME='triRealEstateContract' Module=21 ModuleName='triContract' IR=244937937 IEvent='triSubmitAccountingReview' IE=1512921039 IWFIID=-1 PC=false TC=1743438451538 <Event|<Workflow| .  Root cause: java.sql.SQLException: Cannot insert or update a row because total variable column size, including overhead, is 39 bytes more than the limit.[MID-2070670035]

Could you paste the error message from the log. Tablespace errors are usually due to running out of space. It's like filling up your hard drive. The solution is to add more space. It almost sounds like you are instead running in to the 8060 byte limit of MS SQL Server. That is a completely different issue and possible resolution, which is why I'm asking for the actual error message.

--Mark

Yeah, the 8060 character limit is a limitation of MS SQL Server. It's also one of the reason that every client that goes with MS SQL Server eventually moves off of it. I really wish it would get removed from the compatibility matrix as this issue almost always gets ran in to. There are a few different options that can be attempted to resolve the issue. One is you can convert columns that don't contain data to sparce columns so that there size doesn't count.  Another options is you can create another BO and offload some of the custom fields to it so that they aren't on the same object.  Final option is to migrate to oracle or db2 which do not have the same limitation. At the end of the day, this is a database issue and not a TRIRIGA issue. You'll want to work with your dba to see what they can do to help. A table rebuild can also potentially help especially if the original table creation was in a much older version of MS SQL Server than currently used. All of the options have some drawbacks. For instance if you go the sparse column route and then you modify the corresponding lease BO and publish it, TRIRIGA will not publish it with sparse columns. So you'd need to redo the sparse column conversion whenever you make changes to the underlying BO. If you are working with a business partner they should be able to help with this issue as it is not uncommon.

Best of luck,

Mark

Hi Mark, thank you for the reply! We have been told that the issue is the 8060 byte limit of MS SQL Server.  We have also been told that this is directly related to the total character count of the data stored on the lease. However, we are not seeing consistency in the leases that are getting stuck (some don't have a lot of data, some do).  

Here's one of the errors.  I'll also note that some leases throw this error, but we have one lease that won't save any additional data on it, but is not throwing any errors (that we have found).

2025-03-31 11:27:32,054 WARN  [com.tririga.platform.error.ErrorHandler](WebContainer : 12) Problem detected processing workflow: |Workflow> WFTID=14010613.29 WFIID=446320217964535 PID=none Name='triContract - Synchronous - Module level business rules' Module='triContract' BO='-Any-' Event='Pre-Create' SO=244937937 SP=10 SC=40 TS=1743438451663 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=12035157.117 WFIID=446320217964532 PID=none Name='triRealEstateContract - Synchronous - Permanent Save Validation' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=28 SC=40 TS=1743438451632 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=108817201.7 WFIID=446320217964526 PID=none Name='triRealEstateContract - Synchronous - RE Lease Validations on Submit For Accounting Review' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=16 SC=40 TS=1743438451554 TE=1743438452054 Mode=S EID=1512921039 IE=1512921039 |Event> ID=1512921039 Name='triSubmitAccountingReview' User=203707542 SO=244937937 BO=10002490 BO_NAME='triRealEstateContract' Module=21 ModuleName='triContract' IR=244937937 IEvent='triSubmitAccountingReview' IE=1512921039 IWFIID=-1 PC=false TC=1743438451538 <Event|<Workflow| .  Root cause: java.sql.SQLException: Cannot insert or update a row because total variable column size, including overhead, is 39 bytes more than the limit.[MID-2070670035]

Yeah, the 8060 character limit is a limitation of MS SQL Server. It's also one of the reason that every client that goes with MS SQL Server eventually moves off of it. I really wish it would get removed from the compatibility matrix as this issue almost always gets ran in to. There are a few different options that can be attempted to resolve the issue. One is you can convert columns that don't contain data to sparce columns so that there size doesn't count.  Another options is you can create another BO and offload some of the custom fields to it so that they aren't on the same object.  Final option is to migrate to oracle or db2 which do not have the same limitation. At the end of the day, this is a database issue and not a TRIRIGA issue. You'll want to work with your dba to see what they can do to help. A table rebuild can also potentially help especially if the original table creation was in a much older version of MS SQL Server than currently used. All of the options have some drawbacks. For instance if you go the sparse column route and then you modify the corresponding lease BO and publish it, TRIRIGA will not publish it with sparse columns. So you'd need to redo the sparse column conversion whenever you make changes to the underlying BO. If you are working with a business partner they should be able to help with this issue as it is not uncommon.

Best of luck,

Mark

Hi Mark, thank you for the reply! We have been told that the issue is the 8060 byte limit of MS SQL Server.  We have also been told that this is directly related to the total character count of the data stored on the lease. However, we are not seeing consistency in the leases that are getting stuck (some don't have a lot of data, some do).  

Here's one of the errors.  I'll also note that some leases throw this error, but we have one lease that won't save any additional data on it, but is not throwing any errors (that we have found).

2025-03-31 11:27:32,054 WARN  [com.tririga.platform.error.ErrorHandler](WebContainer : 12) Problem detected processing workflow: |Workflow> WFTID=14010613.29 WFIID=446320217964535 PID=none Name='triContract - Synchronous - Module level business rules' Module='triContract' BO='-Any-' Event='Pre-Create' SO=244937937 SP=10 SC=40 TS=1743438451663 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=12035157.117 WFIID=446320217964532 PID=none Name='triRealEstateContract - Synchronous - Permanent Save Validation' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=28 SC=40 TS=1743438451632 TE=1743438452054 Mode=S<Workflow| Called From: |Workflow> WFTID=108817201.7 WFIID=446320217964526 PID=none Name='triRealEstateContract - Synchronous - RE Lease Validations on Submit For Accounting Review' Module='triContract' BO='triRealEstateContract' Event='Pre-Create' SO=244937937 SP=16 SC=40 TS=1743438451554 TE=1743438452054 Mode=S EID=1512921039 IE=1512921039 |Event> ID=1512921039 Name='triSubmitAccountingReview' User=203707542 SO=244937937 BO=10002490 BO_NAME='triRealEstateContract' Module=21 ModuleName='triContract' IR=244937937 IEvent='triSubmitAccountingReview' IE=1512921039 IWFIID=-1 PC=false TC=1743438451538 <Event|<Workflow| .  Root cause: java.sql.SQLException: Cannot insert or update a row because total variable column size, including overhead, is 39 bytes more than the limit.[MID-2070670035]

Could you paste the error message from the log. Tablespace errors are usually due to running out of space. It's like filling up your hard drive. The solution is to add more space. It almost sounds like you are instead running in to the 8060 byte limit of MS SQL Server. That is a completely different issue and possible resolution, which is why I'm asking for the actual error message.

--Mark