A VI Job from Batch file run via Windows Server Scheduler is suddenly creating Sage ghost tasks after running for years.
Windows Server Scheduler shows task as complete, but Master Console shows enter which cannot be killed.
With hourly scheduling, It creating Sage ghost tasks that eat up user licenses.
Odd, worked for years on Sage100Premium 2016, then 3 months fine on Sage100Premium 2020.1
Anyone seen this?
Lee
------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------