Hi Mary,

This is a Sage 300 function and is only available in Sage 2023 version.

Has anyone worked out a way around this? The Sage feature is not available to us, so we are looking for another way to achieve the same effect.

The issue is that a job starts running and then when it gets to the Sage connector it fails because there is no lanpak available.  We need to be sure that the automation jobs can always run.  The client bought extra Lanpaks but of course their users don't always log off Sage properly. 

In the UI if one windows user runs Sage twice on the same workstation, using the same windows user and the same Sage300 login, Sage current users shows a single license to open 2 companies (as documented for Sage).  So on the IMan server, I logged in as windows user IMan, Sage user IMan and opened a company.  Then I scheduled an IMan job which runs services and IIS as windows user IMan, and logs into Sage as sage user IMan but this time it shows two licenses allocated to user IMan.  Sage must see the 2 ways of logging into Sage as different users.

I also tried restricting Sage users' permitted logon times in the hope that it would force off any users that remained logged on after hours, but it doesn't seem to do that - it only prevents them from logging into Sage after hours.