Update re McAfee and PoisonIvy-micha
Quote:
Originally Posted by
ispycookies
Thanks for the reply.
I have restarted sddt and it ran through everything fine, EXCEPT that McAfee is still finding a "virus" on the same test:
Code:
(i) 11/3/2008 10:28 AM Testing now: SDDT-PoisonIvy-micha.sbi...
(i) 11/3/2008 10:28 AM Downloading next: SDDT-PoisonIvy-micha.sbi
(i) 11/3/2008 10:28 AM File received.
(i) 11/3/2008 10:28 AM Wrote configuration file.
(!) 11/3/2008 10:28 AM The log file that should have been created (logs\4082.xml) was not found!
(!) 11/3/2008 10:28 AM Damn, could not upload results, will try again later!
(i) 11/3/2008 10:28 AM Failed, need to retest!
Code:
(Service stopped successfully.)
(Service started successfully.)
(i) 11/3/2008 10:38 AM
(i) 11/3/2008 10:38 AM Queued tests:
(i) 11/3/2008 10:38 AM SDDT-PoisonIvy-micha.sbi 4082 2008-10-24 14:13:48
(i) 11/3/2008 10:38 AM Testing now: SDDT-PoisonIvy-micha.sbi...
(i) 11/3/2008 10:38 AM Downloading next: SDDT-PoisonIvy-micha.sbi
(i) 11/3/2008 10:38 AM File received.
(i) 11/3/2008 10:38 AM Wrote configuration file.
(!) 11/3/2008 10:38 AM The log file that should have been created (logs\4082.xml) was not found!
(!) 11/3/2008 10:38 AM Damn, could not upload results, will try again later!
(i) 11/3/2008 10:38 AM Failed, need to retest!
And McAfee snatches up and quarantine's the ini for the above test, same as before.
But at least all of the other tests ran successfully. :)
Hopefully a update to McAfee in the near future will fix this; otherwise that test is never going to complete! :sad:
sddt had been running well and without any McAfee warnings since maybe a week after my last post (which was the beginning of November). However, the recent PoisonIvy-micha test is again triggering McAfee the same as before, only this time when McAfee quarantine's the ini file it causes sddt to crash, but sddt stays at 50% CPU usage until I click on the window that tells Windows whether or not to send an error report. Below is the info from the log:
Quote:
(i) 12/9/2008 2:20 PM Testing now: SDDT-Win32.PoisonIvy.j-micha.sbi...
(i) 12/9/2008 2:20 PM Downloading next: SDDT-Win32.PoisonIvy.j-micha.sbi
(i) 12/9/2008 2:20 PM File received.
(i) 12/9/2008 2:20 PM Wrote configuration file.
(i) 12/9/2008 2:22 PM Exception EFOpenError in module sbsdscan.exe at 0001FD03.
(i) 12/9/2008 2:22 PM Cannot open file "C:\Program Files\SDistTest\sbsdscan.ini". Access is denied.
(i) 12/9/2008 2:22 PM
(!) 12/9/2008 2:22 PM The log file that should have been created (logs\4452.xml) was not found!
(!) 12/9/2008 2:22 PM Damn, could not upload results, will try again later!
(i) 12/9/2008 2:22 PM Failed, need to retest!
Unfortunately I do not have the time right now to do any troubleshooting, but I wanted to at least pass on this information which I hope will be helpful. I'll need to disable sddt for the time being. :sad: But I'll try it periodically over the next weeks/months to see if the issue has somehow gotten resolve either on McAfee's end or with sddt.
:)
SDDT-Sec-Test.gen-Buster.sbi
I got a problem on this detection it's been running for more than 4 day without result...
Got any advise to start the next one?
SDDT-Sec-Test.gen-Buster.sbi
Updated to new version it's working fine now...