I understood that it was not eBusiness but the limitation of the timeout is with the webengine by ProvideX not anything due to Sage 100 eBusiness. If you could put it there, at least for testing purposes, that would tell you that it would work but we have to reduce the time it takes to communicate. If it doesn't want to work local there may be other issues then a communication delay.
If it is working on the local, you can attempt to eliminate any application or hardware device between the connection of the two machines. firewall, antivirus, switches, etc.
If it is not working local, then you might need to have them look at the application and what it is doing. Maybe there is somewhere in the process they could reduce the time it takes so it will not timeout. Once it is working on the server locally, then you can test on the other server but it could still require speeding up the connection between the two machines.
Original Message:
Sent: 03-27-2024 16:53
From: Dana Young
Subject: Sage Web Engine
They are not using the eBusiness Manager module. This is with Ascent & Automated Service utilizing the Web Engine for service techs in the field. They don't want this on the Sage server for security reasons.
------------------------------
Dana Young
Lehman Wesley
Lansing, MI
------------------------------
Original Message:
Sent: 03-19-2024 02:42
From: Alnoor Cassim
Subject: Sage Web Engine
@Dana Young - When I was with Sage, during the early days of eBusiness Manager I ran into this as well twice and it was exactly what @Todd Martin mentioned:
- Error 86s and timeouts were appearing in the Web Error Log (under eBusiness Manager / Main)
- The Web Engine machine and Sage machine were separate albeit on the same LAN. I had them initially disable network scanning from AV then later disabled AV entirely, temporarily, but it didn't make a difference.
- In both cases I told them they didn't create enough categories and category trees to lessen the load.
- Customer 1 refused to change that so as an experiment, I installed Web Engine on the Sage server and made sure in the \WebEng\... in the webhide.ini (if I remember the name right), the path to \mas90 was a local drive path not a UNC path. This worked and and they ended up running that way permanently. They were careful to properly whitelist their corporate firewall for the Web Engine ports.
- Customer 2 had even larger categories and trees and it caused an additional problem of the web browser tab itself running out of memory and hanging when the Products & Services eBiz B2C page tried to load over 30,000 items for a single category. I tried to tell them hey seriously how many capacitors and resistors do you need to show at one time and the answer was "well all of them". I said well it's time spend $100k on your website and then they finally relented.
Overall I'm saying you're probably going to have to at least as an experiment install the Web Engine on same server as Sage 100.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Original Message:
Sent: 03-18-2024 12:04
From: Todd Martin
Subject: Sage Web Engine
Are you able to install the web engine on the same server and see if this issue continues to happen? With EBM we saw issues like this for users with extremely large categories/trees when the web user would search and it had to go through the list, it would time out with errors like this. Once we put the web engine on the same server the timeouts stopped. The two servers were both on the same network sitting next to each other but going through the network and even with antivirus/firewall disabled it had an issue.
One thing to note about the web engine, it has a hard coded 90 second timeout.
------------------------------
Todd Martin
MBA Business Software
https://www.mbabsi.com
Original Message:
Sent: 03-18-2024 10:01
From: Dana Young
Subject: Sage Web Engine
No, they are on separate servers.
The errors are in the WebEngine logs. I am not seeing these errors in Sage 100 Activity Log. Sage 100 users are not reporting drops or lost connections, errors, etc.
We feel it is due to a timeout. Both servers are running way too high utilization so we have some monitoring going on right now to watch ping times & any drops. Also feel it could be AV getting in the way while trying to scan, even with IT adamant that's not an issue.
------------------------------
Dana Young
Lehman Wesley & Associates
Lansing, MI
Original Message:
Sent: 03-05-2024 18:02
From: Todd Martin
Subject: Sage Web Engine
Is the Web Engine on the same server as the Sage 100 Data? Where are you seeing the errors? Is in in the Sage 100 error log or in the WebEngine Logs or something specific to OSP? It could be a timeout and not a drop. It could be due to traffic/bandwidth or an application/process that was inspecting the transmission.
------------------------------
Todd Martin
MBA Business Software
https://www.mbabsi.com
Original Message:
Sent: 03-04-2024 10:45
From: Dana Young
Subject: Sage Web Engine
Standard users working in Sage 100 are not receiving these errors.
This is isolated to the OSP server connection for Ascent's Automated Service.
------------------------------
Dana Young
Lehman Wesley
Lansing, MI
Original Message:
Sent: 03-04-2024 10:39
From: Wayne Schulz
Subject: Sage Web Engine
Are these error messages limited to the Sage Web Engine? Are regular users of Sage 100 coming in via the standard Sage 100 interface receiving any messages?
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT