Sage 100

Customer is on 2017 Advanced, 47 users. Through the years, it's never been enforced to log out of Sage at night. So now we have many users in data entry tasks every night. I've been kicking them out as I have to do things, but trying to get across to IT and Mgmt that this is not good, could result in data corruption, etc. Suggested sending out an email daily for a couple of weeks and then start publishing a 'wall of shame' every day. They seem resistant to the idea. IT keeps thinking we can do an auto logoff through Windows and that's fine for those at a Launcher but do we have any resolution for users in data entry tasks at the end of the day?

Just tonight we put in a batch file and scheduled task manager to run it at 11. The batch file will stop and start the sage service. This customer knows the risks but believes that his users sit on empty entry screens. The reason they do it is to have the system auto update batches in sages task scheduler prior to midnight. We have the posting date set to the system date so this is important on last day of month. If you're interested, I can get you the batch file tomorrow. Roberta

That would be wonderful Roberta, While still not ideal, it does get them out. Do you know if having all these windows open affect the backup process? I'm trying to use SOX requirements and security concerns, leaving PC's in the accounting software (unified login) to get mgmt. to become concerned.

I have the same issue. The customers remaining on 100/100c tend now to be larger number of users which typically means maintenance (UDF, rebuilds, customized panels) happen overnight. Almost every site has 1-5 users who seem to remain logged in. I hate to kick them out because I often don't know if they're in the middle of doing actual work. I have one or two where we reboot the server overnight however that's usually 1 am and I'm not offering to work the 2 am shift...

Ditto. I drag up the story about my one client who had a salesperson in Customer Maintenance over night and the next day the controller needed to rebuild AR files and selected Reinit by mistake - and then found out their backup doesn't backup files in use. Even that doesn't scare some folks. ARGH!

Customer is on V2017 on port 9540. We created a Microsoft Task Scheduler task to kick this off at 11pm. Here's the contents of the batch file we put in place: no echo net stop Sage 100 Advanced 2017 (9540) net start Sage 100 Advanced 2017 (9540) exit

Thanks Roberta!