You are correct Lat9 I did not edit the log, that was part of the session key and I thought it was odd too. I'll make the change you've suggested CarlWhat and see if that will at least curb the activity. When the error does happen it usually generates 100+ logs at a time, but it only happens very sporadically, so I suspected it was some sort of attack, but looking at server logs, I could never really match it up.
Thank you for your assistance! Hopefully this will help others and perhaps those function changes should be permanently implemented in a future release.
Bookmarks