Travis 2 Report post Posted February 29, 2020 I receive "Error creating scheduled scan. An unknown error has occurred." when I try to scheduled a scan. This happens no matted what type of scan day/week/month or full/flash/custom. I have tried to Run as Administrator, reboot, check for and update. Scan now works fine. Immunet version 7.0.2.11454. 1 Quote Share this post Link to post Share on other sites
ritchie58 442 Report post Posted February 29, 2020 I just tried to create a new Scheduled Scan with the same results as you can see by my screen grab Travis! You can see I have a Daily Flash Scan scheduled but that was a setting that was transferred over from the last build to 7.0.2 when I upgraded. I'll contact the Admin. Rob. Turner regarding this bug right away! Thanks much for observing & reporting this issue! Best wishes, Ritchie... Edit: A Private Message to Rob has been sent. Quote Share this post Link to post Share on other sites
Travis 2 Report post Posted March 1, 2020 Well this morning it decided to work. The last scan button was yellow (for not doing a scan within 24 hours?) so I did a flash scan.After that was complete I tried to schedule a scan again and it let me. 1 Quote Share this post Link to post Share on other sites
ritchie58 442 Report post Posted March 1, 2020 Hello again Travis, "Ok, that's really weird!" I decided to try it myself just to check it out and was able to schedule a Custom Scan of my C:\ drive with absolutely no problem this time! I still would like to know why that happened and why it was a (thankfully) temporary issue. That's something an Admin or Dev would have to explain to us. This is just an extrapolation on my part but it could have been a temporary issue with iptray.exe (the process that's responsible for the UI) not communicating properly with Immunet's main process sfc.exe for some reason. A temporary server issue perhaps? Cheers, Ritchie... Quote Share this post Link to post Share on other sites
Rob.T 57 Report post Posted March 3, 2020 Am working on reproducing this but No luck yet. Quote Share this post Link to post Share on other sites
ritchie58 442 Report post Posted March 4, 2020 Hey Rob, If you find out anything new about this seemingly temporary issue please enlighten us. "That would be much appreciated!" Regards, Ritchie... Quote Share this post Link to post Share on other sites
Rob.T 57 Report post Posted March 9, 2020 sorry, no luck reproducing the Travis's bug, Still trying though. At best I suspect I reproduced what happened when Richie intermittently reproduced the bug. If you just accept the defaults and attempt go to create a scheduled scan the default "scan type" in the Immunet interface is a "custom scan" with a blank path to the file to scan. If you click through it quickly an error message pops up saying "invalid scan path," since custom scans must have a path to the file/directory their supposed to scan. I've done that a few times now thinking I reproduced Travis's original bug until I carefully went to compare his screenshots to what I had done and realized I forgot to fill out the custom scan path. Thanks, RobT Quote Share this post Link to post Share on other sites
ritchie58 442 Report post Posted March 10, 2020 Blank file path? If you look again at my screenshot I attempted to create a custom scan of my "entire" C:\ drive. That's not a "blank file path" as you stated. I also never got an invalid scan path error message. I am now able to create a custom scan of the entire C:\ drive with no problems, at that time I wasn't able to. I hope that clarifies things as far as what I encountered including Travis. "I'm just glad that whatever it was that caused this was just a temporary thing!" Best wishes, Ritchie... Quote Share this post Link to post Share on other sites
