Problem with "cannot set property into main storage"

Hello All,

I restarted my computer recently, and since re-boot, my avast icon has a little red O on it and the on- access scanner is not running.

I see this when starting the program.

http://img110.imageshack.us/img110/9291/avastscreenshot6qv.png

My version of Avast is the most current available 4.7.844 I think. My system runs Win 98.

I looked at the FAQ, but it said it’s directions do not apply to my version. Any help would be appreciated, I’m hoping this is a known problem. I considered re-installing, but I do not want to go to the hassle unless completely necessary.

Thanks in avance for replies.

There is little hassle involved in reinstalling avast, other than the fact it could be that what caused this is still present.

Try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow. You need to be on-line to do this.
If that doesn’t work try, uninstall, reboot, install, reboot.

Since version 4.7.807 a new data storage called SQLT is used by avast!
Which version are you using?

Maybe the Jet drivers (MDAC package) of Microsoft could help (http://www.microsoft.com/data).
There’s also an MDAC/Jet repair tool: http://www.macropool.com/en/download/mdac.html#Repair

Is this the same issue as discussed by leomalev here: http://forum.avast.com/index.php?topic=21429.msg179203#msg179203 ?
I.e. do you see the same entries in your error.log file?

Thanks
Vlk

Hi Vlk

Yes, I see exactly the same message!

Leonardo

Yes, it’s nearly identical to Leonardo’s problem. It worked fine until a re-start, but the odd thing is, I had done a re-start after the update (As Avast requested) and nothing happened then.

I also have to resort to Task Manager to get into the main program, which once I’m in, seems to work normally. My on- access, active protection is disabled, and will not respond.

Thanks, I’m going to do a little searching, I’ll report back what I find.

Here are a few lines from my Error.log file. There is a whole page of these,all similar, but some of them have slightly different messages.

06/07/2006 3:02:33 PM 1149710553 4294759171 Storage query “INSERT INTO LocalProperties (Object, Property, Val) VALUES (1145138800, ‘ScanAreas’, ‘QuickStartupMem’);” failed. Error description: “database is locked”.
06/07/2006 3:05:08 PM 1149710708 4294268193 Storage query “INSERT INTO LocalProperties (Object, Property, Val) VALUES (1145138800, ‘ScanAreas’, ‘QuickStartupMem’);” failed. Error description: “database is locked”.
06/07/2006 3:09:24 PM 1149710964 4294190797 Storage query “INSERT INTO LocalProperties (Object, Property, Val) VALUES (1354780464, ‘Report’, ‘None’);” failed. Error description: “database is locked”.

I just got done un-installing, re-installing, and updating Avast. It took about 50 minutes and I still have my problem. NO on- acess protection.

I’m off to try Tech’s links…

Yeah, 4 in a row, your getting tired of me bumping the thread…

Thanks Tech, turns out I needed Microsoft Data Access Components (MDAC) 2.8 SP1. Once installed and a re-boot, Avast on- access reactivated. It seems to be working fine now.

Thanks everyone for the assistance. :slight_smile:

Glad that we could be useful in some way 8)

Thanks Tech, turns out I needed Microsoft Data Access Components (MDAC) 2.8 SP1. Once installed and a re-boot, Avast on- access reactivated. It seems to be working fine now.

WHAT??? :o
Are you positive this was the case?

Because the new storage system has NOTHING to do with MDAC/Jet whatsoever. So it’s really very unlikely it would help…

Thanks
Vlk

Hi

I guess Vlk has a point, because I also installed MDAC 2.8 SP1, but to no avail… I still can’t get past the splash screen…

Anyway, resident protection is still working flawlessly… :slight_smile:

Leonardo

All I know is after I downloaded and installed the MDAC, upon re-boot, the little “O” or “inactive” symbol on my taskbar icon came off, and it is working now. ??? I can’t explain it, just glad it’s working.

If it cannot be explained, just blame it on Win 98. ::slight_smile: