Sage 100

Import Jobs chained together suddenly stopped working today. Client has 3 import jobs, first one is kicked off with a .BAT file. the second two are chained together. These jobs were created about 6 months ago and have been working flawlessly; however, today only the first job runs. the two chained jobs **intermittently** don't run. He tells me they mostly don't run but a couple of times today they did run. He already tried blanking out the chain to field and saving the job and then putting it back on (that did not work). He looked at the activity log and can see the first job running but does not see anything listed for he second or third jobs. intermittent problems are always the toughest to troubleshoot so I'm wondering if anyone has any thoughts or if anyone has seen anything like this.

Just to follow up; I had the client rename the 4 ""key"" files in Sage: SY_Workstation, SY_Console, Locate.pvk, and Sessions.pvk and it seems to have resolved the problem so far today. I neglected to mention that this was happening in version 4.1. When I told their IT guy to rename those files, he said the often has to rename SY_Workstation whenever it ""gets too large"". Then he checked the file and told me it was currently at 4GB. I completely forgot that file used to have an issue with tracking every new login as a different workstation back in 4.1. We are upgrading them to 2018 but they have been ""testing"" 2018 for about 4-5 months now. (sigh)

David, I recently had an issue with chained the odd jobs that have been working perfectly for some period of time and then all the sudden had issues. Long story, short....it ended up being an issue with the antivirus. I read that you had resolved your issue but thought I'd but that thought out for you in case you experience it as well.

thank you! as of about noon today it was working, but if it happens again I'll have them look into anti-virus.