Sage 100

Since you said 'Scripts running "on-server" ' implies that this is a button script. Without being able to recreate it, this may be a pain to troubleshoot. It would be most helpful to turn on trace inside the script "Mas_Scr_Dbg = 1" to determine the failing line, but will annoy the users. I suspect what's different is in a field being passed to the script so I would look at what fields are setup to be passed and returned.

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-829-1054
------------------------------

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

Lee I just realized you said they're on 2022.2 so the hotfixes don't apply. Maybe you can try the 2023 one on the test server you have.

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

Ask Scott here (link) if they have a v2022 version of the fix available.

Lee I just realized you said they're on 2022.2 so the hotfixes don't apply. Maybe you can try the 2023 one on the test server you have.

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

Scott said the problem hasn't been reported in version 2022.

Have you seen it in Sage 100 2022?

Ask Scott here (link) if they have a v2022 version of the fix available.

Lee I just realized you said they're on 2022.2 so the hotfixes don't apply. Maybe you can try the 2023 one on the test server you have.

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

You're right... that specific issue doesn't happen in v2022.  (I copied the test scripts from that SC post into my v2020 and v2022... the error did not happen in either of those versions).

Scott said the problem hasn't been reported in version 2022.

Have you seen it in Sage 100 2022?

Ask Scott here (link) if they have a v2022 version of the fix available.

Lee I just realized you said they're on 2022.2 so the hotfixes don't apply. Maybe you can try the 2023 one on the test server you have.

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

Lee I just realized you said they're on 2022.2 so the hotfixes don't apply. Maybe you can try the 2023 one on the test server you have.

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024

Lee - I've had 5 cases in the last 3 months of scripts randomly running into Error 88s in S/O Entry or Invoice Entry or anywhere really. Each and every time it is because of a scripting bug in v2023 and v2024, more for 64-bit than 32-bit Sage but not always, primarily occurs on Premium but not always, doesn't matter whether it's button or event script but usually involves multiple scripts defined for the same entity. There is a 2023 hotfix and 2024 hotfix, either one requiring a pre-release form to be signed by your customer. I believe this was originally discovered by @Kevin Moyes for their customer some time ago but the issue has proliferated since.

Here is the Sage KB article - https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=240628223532270&page=1&position=3&q=Error%2088%20Sy_Maint.pvc

You'll need to call Support and tell them you're running into this 88 (if necessary tell them you're getting it the way the article describes even if you're getting it a different way). Tell them the client is willing to sign the pre-release form and let your client know it's coming too. In case the Support rep doesn't understand what you're saying, point them to the KB article (Issue ID 117286) and ask them to talk to Nathan in Support. This hotfix will be incorporated into the upcoming PU4 for 2023 and PU2 for 2024