Sage 100

We have a script in sales order that creates PM work tickets and then creates work tickets for any sub assemblies that it finds and even goes down into the sub assemblies  - sub assemblies and creates work tickets for those.  That said we are running into a timeout issue for scripting it appears.  "The script was aborted because execution exceeded the specified timeout period"

I read I could change that timeout setting by adding:
ScriptTimeout = 45000
to the SOTA.ini file on the server in the mas90 launcher directory.  That doesn't seem to change anything, it always throws this error around 10 seconds of running, adding the line to SOTA.ini or not (resetting the service after making the change, restarting the workstation etc...doesn't seem to make a difference.

Anyone ever fought this before and actually changed the timeout setting?

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------

Chris - I've used it several times and advised several people too. So it's been working. I also just checked the code and it's still in there. It could be:

1. You might have a space before or after the = sign. Don't do that. Make it say ScriptTimeout=45000
This would make the property read as "ScriptTimeout " (with a space) which would fail.
After you make the change, close and restart Sage for it to take effect.
(If it works, you can join my movement called Spaces are the Root of All Evil.)

2. You didn't add it to the [Config] section of the SOTA.INI. It's specifically looking for it there.

3. I don't think so but if you're on Advanced or Premium, you might need to place the change on the client-side SOTA.INI as well. One way to test is to run the script Mas90 Style, that is as Standard. There are also some commands to find out which INI file is in play but it's probably No 1.

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

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

Alnoor,

Thanks for the information!

1. Spaces are the Root of All Evil
2. Seems to work if I run advanced in MAS90 mode but if I run it from the advanced workstation (with both server and local workstation SOTA.ini having the scripttimeout=45000) it's throwing up the timeout period message.

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------

Original Message:
Sent: 10-11-2021 20:15
From: Alnoor Cassim
Subject: Scripting Timeout Issue

Chris - I've used it several times and advised several people too. So it's been working. I also just checked the code and it's still in there. It could be:

1. You might have a space before or after the = sign. Don't do that. Make it say ScriptTimeout=45000
This would make the property read as "ScriptTimeout " (with a space) which would fail.
After you make the change, close and restart Sage for it to take effect.
(If it works, you can join my movement called Spaces are the Root of All Evil.)

2. You didn't add it to the [Config] section of the SOTA.INI. It's specifically looking for it there.

3. I don't think so but if you're on Advanced or Premium, you might need to place the change on the client-side SOTA.INI as well. One way to test is to run the script Mas90 Style, that is as Standard. There are also some commands to find out which INI file is in play but it's probably No 1.

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

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

So Alnoor led me to a great idea that solved my issue without having to chase down these timeout settings.  In my case it was a big query loop checking each component for its potential for having a BOM.  By adding the oUI.ProgressBar into the script and "update" the progress bar on each query it performed it no longer timed out because it was interacting with Sage as it processed thru the queries.  Gives the user something to look at to know it's working on something and it stopped my timeout issue.  

Thank you Alnoor for helping me look at it differently!!

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------

Original Message:
Sent: 10-12-2021 11:46
From: Chris Mengerink
Subject: Scripting Timeout Issue

Alnoor,

Thanks for the information!

1. Spaces are the Root of All Evil
2. Seems to work if I run advanced in MAS90 mode but if I run it from the advanced workstation (with both server and local workstation SOTA.ini having the scripttimeout=45000) it's throwing up the timeout period message.

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------


Original Message:
Sent: 10-11-2021 20:15
From: Alnoor Cassim
Subject: Scripting Timeout Issue

Chris - I've used it several times and advised several people too. So it's been working. I also just checked the code and it's still in there. It could be:

1. You might have a space before or after the = sign. Don't do that. Make it say ScriptTimeout=45000
This would make the property read as "ScriptTimeout " (with a space) which would fail.
After you make the change, close and restart Sage for it to take effect.
(If it works, you can join my movement called Spaces are the Root of All Evil.)

2. You didn't add it to the [Config] section of the SOTA.INI. It's specifically looking for it there.

3. I don't think so but if you're on Advanced or Premium, you might need to place the change on the client-side SOTA.INI as well. One way to test is to run the script Mas90 Style, that is as Standard. There are also some commands to find out which INI file is in play but it's probably No 1.

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

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA

I never would have thought of the progress bar. Great suggestion Alnoor!

I have a couple of long running processes where I can use that to give the user a little comfort that it is performing correctly.

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
https://www.firstmatellc.com/
------------------------------

Original Message:
Sent: 10-12-2021 18:28
From: Chris Mengerink
Subject: Scripting Timeout Issue

So Alnoor led me to a great idea that solved my issue without having to chase down these timeout settings.  In my case it was a big query loop checking each component for its potential for having a BOM.  By adding the oUI.ProgressBar into the script and "update" the progress bar on each query it performed it no longer timed out because it was interacting with Sage as it processed thru the queries.  Gives the user something to look at to know it's working on something and it stopped my timeout issue.

Thank you Alnoor for helping me look at it differently!!

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653
------------------------------


Original Message:
Sent: 10-12-2021 11:46
From: Chris Mengerink
Subject: Scripting Timeout Issue

Alnoor,

Thanks for the information!

1. Spaces are the Root of All Evil
2. Seems to work if I run advanced in MAS90 mode but if I run it from the advanced workstation (with both server and local workstation SOTA.ini having the scripttimeout=45000) it's throwing up the timeout period message.

------------------------------
Chris Mengerink
Director
DWD Technology Group
Fort Wayne IN
260-399-8653


Original Message:
Sent: 10-11-2021 20:15
From: Alnoor Cassim
Subject: Scripting Timeout Issue

Chris - I've used it several times and advised several people too. So it's been working. I also just checked the code and it's still in there. It could be:

1. You might have a space before or after the = sign. Don't do that. Make it say ScriptTimeout=45000
This would make the property read as "ScriptTimeout " (with a space) which would fail.
After you make the change, close and restart Sage for it to take effect.
(If it works, you can join my movement called Spaces are the Root of All Evil.)

2. You didn't add it to the [Config] section of the SOTA.INI. It's specifically looking for it there.

3. I don't think so but if you're on Advanced or Premium, you might need to place the change on the client-side SOTA.INI as well. One way to test is to run the script Mas90 Style, that is as Standard. There are also some commands to find out which INI file is in play but it's probably No 1.

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

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA