I was looking at a Login Failure Audit Report when I noticed unusual activity. Several days a week I get login failures for a couple of users at 1AM, plus a minute or two. No one is in the facilities at that time. These people do not have remote access (outside the firewall). I do not have a task agent schedule set for 1AM.
One of these users is sysagent. That is how I found the problem. The other instances are users associated with production or cycle counting. Some log into EpicorMES.
Intermittent, non repeating stuff I love.
Scott
Any Schedules for 12 AM, that might have been affected by DST?
Thanks Calvin, but nothing is set for 12 or 2AM.
Multiple App Servers triples the research time. There is some sort of IIS Worker request to recycle App Pools. Maybe I need to collect some more data and do a little testing to see if it really is a system thing.
This appears to be tied to a task set up on our 2 appservers for a stop and start on the pools. If a user has not signed out, this error is a result. Scott
2 Likes
For completeness of info about the issue … is the time shown the failure log, the time when the pool is recycled?
Correct Calvin
At least for 90% of the instances that stand out.
This was how I found the possible problem. It did not matter if I had a process open or not, I was still getting the error.
I don’t know enough to dig deeper into what is actually happening.
Scott