Sage 100

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

Is it the timeout issue?  Does the script take any time to process anything on the server? 

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems
------------------------------


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Phil - This is what Kevin is talking about: https://communityhub.sage.com/us/sage100/f/business-object-interface/259602/tablacus-script-host-timeout-error-during-button-script-execution

I've been involved with this beyond the Sage community post.

On Adv and Prem 64-bit the "Tablacus" error isn't seen but something else less obvious happens. On Standard,64-bit  the Tablacus error is seen. In short, if the button can take longer than 10 seconds to finish, this issue can happen and the ScriptTimeout values you put in SOTA.INI are ignored.

It is now fixed in 2025.2 and 2024.4. So just install the PU if possible. Another way to fix is take the SWCOCX from a v2026 install and on 2025 64-bit or 2024 64-bit, place it on the server's \mas90\SOA and on every PC / Terminal Server where Workstation Setup was run in that \mas90\SOA folder. It is safe to do this (per Sage) and I had a highly affected client do just that. You still need to set the ScriptTimeout=90000 for example (90 secs) in server's SOTA.INI. The user should close their Launcher and restart Sage for it to take effect.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 04-22-2026 19:41
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Phil - This is what Kevin is talking about: https://communityhub.sage.com/us/sage100/f/business-object-interface/259602/tablacus-script-host-timeout-error-during-button-script-execution

I've been involved with this beyond the Sage community post.

On Adv and Prem 64-bit the "Tablacus" error isn't seen but something else less obvious happens. On Standard,64-bit  the Tablacus error is seen. In short, if the button can take longer than 10 seconds to finish, this issue can happen and the ScriptTimeout values you put in SOTA.INI are ignored.

It is now fixed in 2025.2 and 2024.4. So just install the PU if possible. Another way to fix is take the SWCOCX from a v2026 install and on 2025 64-bit or 2024 64-bit, place it on the server's \mas90\SOA and on every PC / Terminal Server where Workstation Setup was run in that \mas90\SOA folder. It is safe to do this (per Sage) and I had a highly affected client do just that. You still need to set the ScriptTimeout=90000 for example (90 secs) in server's SOTA.INI. The user should close their Launcher and restart Sage for it to take effect.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 04-22-2026 19:41
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

@Alnoor Cassim - Does this apply to 32-bit as well?  

------------------------------
Phil McIntosh
Friendly Systems
------------------------------


Original Message:
Sent: 04-23-2026 02:34
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

Phil - This is what Kevin is talking about: https://communityhub.sage.com/us/sage100/f/business-object-interface/259602/tablacus-script-host-timeout-error-during-button-script-execution

I've been involved with this beyond the Sage community post.

On Adv and Prem 64-bit the "Tablacus" error isn't seen but something else less obvious happens. On Standard,64-bit  the Tablacus error is seen. In short, if the button can take longer than 10 seconds to finish, this issue can happen and the ScriptTimeout values you put in SOTA.INI are ignored.

It is now fixed in 2025.2 and 2024.4. So just install the PU if possible. Another way to fix is take the SWCOCX from a v2026 install and on 2025 64-bit or 2024 64-bit, place it on the server's \mas90\SOA and on every PC / Terminal Server where Workstation Setup was run in that \mas90\SOA folder. It is safe to do this (per Sage) and I had a highly affected client do just that. You still need to set the ScriptTimeout=90000 for example (90 secs) in server's SOTA.INI. The user should close their Launcher and restart Sage for it to take effect.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 04-22-2026 19:41
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

Phil - Good question. Let me recap the scripting fixes I know:

• The timeout issue in on 64-bit Sage only as described above. It does NOT apply to any 32-bit Sage versions.
• Error 88 hotfix for v2024 PU0 - PU1. Required a call to Sage support (or your friends) to get hotfix. Fixed since 2024.2. For 64-bit and 32-bit. Fixes the pvxocx32.dll and pvxocx64.dll files in \mas90\Home. 
• Error 88 hotfix for v2023 is for PU0 to PU4. Required a call to Sage support (or your friends) to get. Fixed since 2023.5. For 64-bit and 32-bit. Fixes the pvxocx32.dll and pvxocx64.dll files in \mas90\Home 

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 04-23-2026 10:05
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

@Alnoor Cassim - Does this apply to 32-bit as well?  

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-23-2026 02:34
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

Phil - This is what Kevin is talking about: https://communityhub.sage.com/us/sage100/f/business-object-interface/259602/tablacus-script-host-timeout-error-during-button-script-execution

I've been involved with this beyond the Sage community post.

On Adv and Prem 64-bit the "Tablacus" error isn't seen but something else less obvious happens. On Standard,64-bit  the Tablacus error is seen. In short, if the button can take longer than 10 seconds to finish, this issue can happen and the ScriptTimeout values you put in SOTA.INI are ignored.

It is now fixed in 2025.2 and 2024.4. So just install the PU if possible. Another way to fix is take the SWCOCX from a v2026 install and on 2025 64-bit or 2024 64-bit, place it on the server's \mas90\SOA and on every PC / Terminal Server where Workstation Setup was run in that \mas90\SOA folder. It is safe to do this (per Sage) and I had a highly affected client do just that. You still need to set the ScriptTimeout=90000 for example (90 secs) in server's SOTA.INI. The user should close their Launcher and restart Sage for it to take effect.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 04-22-2026 19:41
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

This customer is 32-bit.  Had gotten some error 88s in 2022, the Type V undefined just appeared with the upgrade to 2025.1.

Phil - Good question. Let me recap the scripting fixes I know:

• The timeout issue in on 64-bit Sage only as described above. It does NOT apply to any 32-bit Sage versions.
• Error 88 hotfix for v2024 PU0 - PU1. Required a call to Sage support (or your friends) to get hotfix. Fixed since 2024.2. For 64-bit and 32-bit. Fixes the pvxocx32.dll and pvxocx64.dll files in \mas90\Home. 
• Error 88 hotfix for v2023 is for PU0 to PU4. Required a call to Sage support (or your friends) to get. Fixed since 2023.5. For 64-bit and 32-bit. Fixes the pvxocx32.dll and pvxocx64.dll files in \mas90\Home 

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 04-23-2026 10:05
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

@Alnoor Cassim - Does this apply to 32-bit as well?  

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-23-2026 02:34
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

Phil - This is what Kevin is talking about: https://communityhub.sage.com/us/sage100/f/business-object-interface/259602/tablacus-script-host-timeout-error-during-button-script-execution

I've been involved with this beyond the Sage community post.

On Adv and Prem 64-bit the "Tablacus" error isn't seen but something else less obvious happens. On Standard,64-bit  the Tablacus error is seen. In short, if the button can take longer than 10 seconds to finish, this issue can happen and the ScriptTimeout values you put in SOTA.INI are ignored.

It is now fixed in 2025.2 and 2024.4. So just install the PU if possible. Another way to fix is take the SWCOCX from a v2026 install and on 2025 64-bit or 2024 64-bit, place it on the server's \mas90\SOA and on every PC / Terminal Server where Workstation Setup was run in that \mas90\SOA folder. It is safe to do this (per Sage) and I had a highly affected client do just that. You still need to set the ScriptTimeout=90000 for example (90 secs) in server's SOTA.INI. The user should close their Launcher and restart Sage for it to take effect.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)


Original Message:
Sent: 04-22-2026 19:41
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

It writes to a separate SQL database that syncs with another app.

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 17:24
From: Kevin Moyes
Subject: Sage 100 2025.1 custom office button script error

Is it the timeout issue?  Does the script take any time to process anything on the server? 

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-22-2026 17:12
From: Phil McIntosh
Subject: Sage 100 2025.1 custom office button script error

The only variable being passed is SalesOrderNo.  This button gets clicked over 100 times per day and gives the error 2 or 3 times.  Going back into the order and clicking again it works...Could this be the 2025.1 manifestation of the the error 88 we would occasionally get on previous versions?

------------------------------
Phil McIntosh
Friendly Systems


Original Message:
Sent: 04-22-2026 15:24
From: Alnoor Cassim
Subject: Sage 100 2025.1 custom office button script error

I know the answer to the less important question. It's falling into a generic error trap in a section of code that was created when Custom Office only supported button scripts before event scripts were created. IOW this old code block doesn't know "V" means VBScript which is why it says "undefined".

So, speaking of old stuff, is it possible in your button properties in the Link Settings tab, off to the right, on the "Select Variables to be passed" button that you have something not set right?  Maybe just create a new button with the same script and see if it works.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)

I compiled this information for our content library - Resolving "Tablacus Script Host" and "Type V Undefined" Timeout Errors in Sage 100

LMK if you think anything should be added to changed to the above document. This is a great example of why we need to maintain our own content library of knowledge. I do not believe there was any one place that contained the full resolution and workaround. Sage does not seem to have anyone working full time on maintaining their KB. 

@Alnoor Cassim - Any chance this issue is related to the paperless office issue where the PDF being created cannot be opened.

Direct Deposit - unable to password protect .pdf document (and slowness) | Sage 100

I compiled this information for our content library - Resolving "Tablacus Script Host" and "Type V Undefined" Timeout Errors in Sage 100

LMK if you think anything should be added to changed to the above document. This is a great example of why we need to maintain our own content library of knowledge. I do not believe there was any one place that contained the full resolution and workaround. Sage does not seem to have anyone working full time on maintaining their KB. 

Jeff - Unlikely it's related to that Paperless P/R Direct Deposit PDF stub printing issue.

@Alnoor Cassim - Any chance this issue is related to the paperless office issue where the PDF being created cannot be opened.

Direct Deposit - unable to password protect .pdf document (and slowness) | Sage 100

I compiled this information for our content library - Resolving "Tablacus Script Host" and "Type V Undefined" Timeout Errors in Sage 100

LMK if you think anything should be added to changed to the above document. This is a great example of why we need to maintain our own content library of knowledge. I do not believe there was any one place that contained the full resolution and workaround. Sage does not seem to have anyone working full time on maintaining their KB.