Customer is trying to go through Delete/Change Vendors. Enters in the starting and ending customer records and then prints the listing.  Prompted to post the Delete/Change Vendors and they hit yes. At the end, prior to completing the process, I get the attached messages.

Can't find anything about error for Delete/Change vendors anywhere. Anyone have any ideas on what to look for? I've tried clearing out all the records and keying in 1 at a time and errors out no matter what.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)
------------------------------

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators
------------------------------

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)
------------------------------

Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators
------------------------------

This somewhat-similar KB article says it's 3rd party related:



------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 01-13-2023 14:10
From: Chris Love
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators

Thanks Therese and Brett. I took a look and saw what happens is Delete and Change Vendors spins thru the dictionary looking for tables with APDivisionNo and VendorNo as fields. It builds that list into a string then populates CI_ChangeWork + sessionID.m4t with that info, 1 record per table. The problem is the size of the source tables/fields list when it reaches a specific J/C table (JC_UnbilledJobBillingWork) exceeds the CI_ChangeWork record size of 4864. That WRITE fails with the Error 1.

On this system although J/C module is not installed, I saw there is some dependency/integration on just the J/C dict entries alone being present. Therefore I could not just remove them from dict as that would result in new errors when going into screens.

Smells like a bug but in the end I worked around error by using the Data Dictionary Maint tool to increase the record size of CI_ChangeWork. Now Delete and Change Vendors worked.

------------------------------
Alnoor Cassim
------------------------------

Original Message:
Sent: 01-13-2023 14:48
From: Brett Zimmerman
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

This somewhat-similar KB article says it's 3rd party related:

Error: "1 SY_DeleteChange.pvc 416"

Created on 05-15-2017 / Last modified on 04-01-2021

<kanisa_authored_doc>

Summary

<content>

Error: "1 SY_DeleteChange.pvc 416" when Using the Accounts Receivable Delete and Change Customers Utility

</content>

Cause

<content>

Third-party software

</content>

Resolution

<content>This message is a result of a third-party software enhancement. Contact the third-party developer for assistance.</content>

</kanisa_authored_doc>

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 01-13-2023 14:10
From: Chris Love
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators

** ADMIN - This can be moved out of Sage Urgent Support **

------------------------------
Alnoor Cassim
------------------------------

Original Message:
Sent: 01-13-2023 16:58
From: Alnoor Cassim
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Thanks Therese and Brett. I took a look and saw what happens is Delete and Change Vendors spins thru the dictionary looking for tables with APDivisionNo and VendorNo as fields. It builds that list into a string then populates CI_ChangeWork + sessionID.m4t with that info, 1 record per table. The problem is the size of the source tables/fields list when it reaches a specific J/C table (JC_UnbilledJobBillingWork) exceeds the CI_ChangeWork record size of 4864. That WRITE fails with the Error 1.

On this system although J/C module is not installed, I saw there is some dependency/integration on just the J/C dict entries alone being present. Therefore I could not just remove these J/C entries from dict as that would result in new errors when going into screens. I couldn't find out enough info about the J/C integration but it strongly smells of a bug. I worked around it by using the Data Dictionary Maint tool to increase the record size of CI_ChangeWork. Now Delete and Change Vendors worked.

------------------------------
Alnoor Cassim
------------------------------


Original Message:
Sent: 01-13-2023 14:48
From: Brett Zimmerman
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

This somewhat-similar KB article says it's 3rd party related:

Error: "1 SY_DeleteChange.pvc 416"

Created on 05-15-2017 / Last modified on 04-01-2021

<kanisa_authored_doc>

Summary

<content>

Error: "1 SY_DeleteChange.pvc 416" when Using the Accounts Receivable Delete and Change Customers Utility

</content>

Cause

<content>

Third-party software

</content>

Resolution

<content>This message is a result of a third-party software enhancement. Contact the third-party developer for assistance.</content>

</kanisa_authored_doc>

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 01-13-2023 14:10
From: Chris Love
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators

Very ls similar issue reported by one of my clients on Monday.    Sage says they are "investigating (11/11/22).  @Alnoor Cassim - Would the resolution be the same?​​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------

Original Message:
Sent: 01-13-2023 17:01
From: Alnoor Cassim
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

** ADMIN - This can be moved out of Sage Urgent Support **

------------------------------
Alnoor Cassim
------------------------------


Original Message:
Sent: 01-13-2023 16:58
From: Alnoor Cassim
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Thanks Therese and Brett. I took a look and saw what happens is Delete and Change Vendors spins thru the dictionary looking for tables with APDivisionNo and VendorNo as fields. It builds that list into a string then populates CI_ChangeWork + sessionID.m4t with that info, 1 record per table. The problem is the size of the source tables/fields list when it reaches a specific J/C table (JC_UnbilledJobBillingWork) exceeds the CI_ChangeWork record size of 4864. That WRITE fails with the Error 1.

On this system although J/C module is not installed, I saw there is some dependency/integration on just the J/C dict entries alone being present. Therefore I could not just remove these J/C entries from dict as that would result in new errors when going into screens. I couldn't find out enough info about the J/C integration but it strongly smells of a bug. I worked around it by using the Data Dictionary Maint tool to increase the record size of CI_ChangeWork. Now Delete and Change Vendors worked.

------------------------------
Alnoor Cassim


Original Message:
Sent: 01-13-2023 14:48
From: Brett Zimmerman
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

This somewhat-similar KB article says it's 3rd party related:

Error: "1 SY_DeleteChange.pvc 416"

Created on 05-15-2017 / Last modified on 04-01-2021

<kanisa_authored_doc>

Summary

<content>

Error: "1 SY_DeleteChange.pvc 416" when Using the Accounts Receivable Delete and Change Customers Utility

</content>

Cause

<content>

Third-party software

</content>

Resolution

<content>This message is a result of a third-party software enhancement. Contact the third-party developer for assistance.</content>

</kanisa_authored_doc>

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 01-13-2023 14:10
From: Chris Love
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators

Yes. I'll send you some steps if you dare to try.

------------------------------
Alnoor Cassim
------------------------------

Original Message:
Sent: 01-18-2023 11:14
From: Jeff Schwenk
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Very ls similar issue reported by one of my clients on Monday.    Sage says they are "investigating (11/11/22).  @Alnoor Cassim - Would the resolution be the same?​​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------


Original Message:
Sent: 01-13-2023 17:01
From: Alnoor Cassim
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

** ADMIN - This can be moved out of Sage Urgent Support **

------------------------------
Alnoor Cassim


Original Message:
Sent: 01-13-2023 16:58
From: Alnoor Cassim
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Thanks Therese and Brett. I took a look and saw what happens is Delete and Change Vendors spins thru the dictionary looking for tables with APDivisionNo and VendorNo as fields. It builds that list into a string then populates CI_ChangeWork + sessionID.m4t with that info, 1 record per table. The problem is the size of the source tables/fields list when it reaches a specific J/C table (JC_UnbilledJobBillingWork) exceeds the CI_ChangeWork record size of 4864. That WRITE fails with the Error 1.

On this system although J/C module is not installed, I saw there is some dependency/integration on just the J/C dict entries alone being present. Therefore I could not just remove these J/C entries from dict as that would result in new errors when going into screens. I couldn't find out enough info about the J/C integration but it strongly smells of a bug. I worked around it by using the Data Dictionary Maint tool to increase the record size of CI_ChangeWork. Now Delete and Change Vendors worked.

------------------------------
Alnoor Cassim


Original Message:
Sent: 01-13-2023 14:48
From: Brett Zimmerman
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

This somewhat-similar KB article says it's 3rd party related:

Error: "1 SY_DeleteChange.pvc 416"

Created on 05-15-2017 / Last modified on 04-01-2021

<kanisa_authored_doc>

Summary

<content>

Error: "1 SY_DeleteChange.pvc 416" when Using the Accounts Receivable Delete and Change Customers Utility

</content>

Cause

<content>

Third-party software

</content>

Resolution

<content>This message is a result of a third-party software enhancement. Contact the third-party developer for assistance.</content>

</kanisa_authored_doc>

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 01-13-2023 14:10
From: Chris Love
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

No JC, not even installed as shown in System Config.  I don't think it's in the log, apparently the issue is in CI_ChangeEntityWork table generated when trying to process the changes.

------------------------------
Chris Love
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 01-13-2023 14:06
From: Therese Logeais
Subject: AP Delete/Change Vendors - Error 1: Logical End-Of-Record reached

Do they have JC? What version? Wasn't there an issue with JC causing errors when it wasn't even installed (product updates/conversion)? Is that the work table for the log? Maybe reinitialize it?

------------------------------
Therese Logeais, Technology Integrators