Slow Printing Performance on Server 2016 and 2019 with StarShip installed
There is a pesky bug that just appeared on the Sage KB. While we have not taken reports of this yet, you may want to make note of the issue if you use Sage 100 alongside the popular V-Technologies Starship shipping software.
According to this Sage KB, once Starship is installed on Microsoft Windows Server 2016 or 2019, and users begin printing anything, whether Sage 100 related or outside of Sage 100, they may notice explorer.exe is creating individual threads for each user at login under different PID’s, and then consuming 100% CPU between all these threads.
*This appears to occur around 15 – 30 minutes after 4+ users log in and begin working. Even if all the explorer.exe processes are killed, the issue re-occurs within 15 – 45 mins
Sage believes that the issue is related to StarShip using FabulaTech for print job port redirections and the performance issue is believed to be caused by FabulaTech’s ftusbprint.dll
*Note – Only Server 2016 and 2019 seem to be affected. Server 2012 does not appear to be affected
Sage Engineering is currently aware of the issue. Both Starship and FabulaTech have also been made aware of the problem and are expected to address the issue.