| Subject: | Cannot Close Pay - Status Changes to "Active (approved)- String or Binary data would be trancated |
| Summary: | Issue: Cannot Close Pay - Status Changes to "Active (approved)- String or Binary data would be trancated We connected on site with Teamviewer and did the following: Verified that all processes are running as per set frequency. Process Setup is running as well. Client is able to Reject and Approve pay but the above message appears when he tries to close the pay. Next Steps: To request assistance from Development team. |
| Audit Notes: | Edited by sanjay on 31/07/26 11:39. |
| 30 Jul 2026 | 10:24AM Comment 1 by Rishup Rinesh (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 31-07-2026 10:10 AM Notes: ETC extended from: 30/07/2026 to 31/07/2026 |
| Version 15.90.251107.GA There is no changes in the setup from last payrun ID 6113 which was closed on 15/7/2026. |
|
| 30 Jul 2026 | 05:50PM Comment 2 by Sitla (Edge Business Solutions) Assigned To: Sitla (Edge Business Solutions) Followup Date: 31-07-2026 05:44 PM Time Taken: 8.00 Notes: Edited by sitla on 30/07/26 18:01. Edited by sitla on 30/07/26 17:54. Edited by sitla on 30/07/26 17:53. ETC extended from: 31/07/2026 to 31/07/2026 |
| Bula Team, We connected via TeamViewer and Teams to resolve the issue, but it was getting difficult to analyse the data. The following was done: - Upgraded the current database to Version 16.03.260723P.GA. using the case reference E03005 on the same issue. However, the issue remained.
- Current Version - 15.90.251107
- Version 16.03.260326.GA
- Applied Patch -16.03.260723.
- SQL Collation: Latin1_General_CI_AS
- Connected with Development on site to resolve the issue for Payrun ID: 6133 under Company ID: TAPL
- Since it was difficult to use the tools to analyse the data better, we requested a backup from Prageeth
- A current backup was taken
- The backup was sent to Sanjay via OneDrive to resolve the issue.
Next Steps: - Restore the backup from the OneDrive link
- Analyse the issue and provide a fix.
We will update the case once the issue is fixed. Sitla |
|
| 30 Jul 2026 | 07:19PM Comment 3 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 31-07-2026 05:54 PM Time Taken: 6.00 |
| Hi Sitla, seems like the upgrade from V14 to V15 was incomplete. The comment field was changed from 32 characters to (max) characters. To fix their issue, you can run this script below. I will check what else is missing tomorrow and let you know
--Run this on their database IF EXISTS (SELECT 1 FROM sys.columns WHERE name = N'comment' AND object_id = OBJECT_ID(N'[dbo].[PR_HIST_PAY_DET]')) BEGIN ALTER TABLE [dbo].[PR_HIST_PAY_DET] ALTER COLUMN [comment] VARCHAR(MAX) NULL; END ELSE BEGIN ALTER TABLE [dbo].[PR_HIST_PAY_DET] ADD [comment] VARCHAR(MAX) NULL; END |
|
| 30 Jul 2026 | 09:26PM Comment 4 by Sitla (Edge Business Solutions) Assigned To: Sitla (Edge Business Solutions) Followup Date: 31-07-2026 09:24 PM Time Taken: 8.00 |
| Hi Sanjay, We ran the script and mamaged tpo close the pay successfully. I will close this case after review tomorrow. Thanks for the assistance. Sitla. |
|
| 31 Jul 2026 | 11:40AM Comment 5 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 31-07-2026 05:39 PM Time Taken: 4.00 Notes: ETC extended from: 31/07/2026 to 31/07/2026 |
| I have added this script to V16.03.260730. This script will be applied in case there are other clients with this issue. |
|