Hey guys, my Avast dnt open because Error: dbsCreatObject.
What can I do?
Thx
Which is your Windows? 98, Me, XP?
Do you use any other antivirus in your computer?
Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove
Then choose Repair function in the popup window (Repair).
You must be connected to the internet while repairing.
If this does not help, can you uninstall / boot / install / boot again?
Which is your Windows? 98, Me, XP? XP Professional
Do you use any other antivirus in your computer? No
Can you try to repair your installation? Yes, didn´t work
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove
Then choose Repair function in the popup window (Repair).
You must be connected to the internet while repairing. I tried
If this does not help, can you uninstall / boot / install / boot again? I will try!!
Thx
It’s an obvious problem. Change ODBC to XML storage. Search forums for solution.
EDIT:
I’m working on automatic patch fior this common error, so it won’t be such pain in the rear to help people regarding this issue.
Hey guys, my Avast dnt open because Error: dbsCreatObject.
Doesn’t that refer to the jet data base maybe a switch to xml would cure the problem
use the nifty aec programme to do it
Dang it RejZor beat me again ;D ;D ;D ;D ;D ;D ;D
As this is quiet common problem, i decided to make a small fix tool.
Get it here:
http://forum.avast.com/index.php?topic=14208.0
Hello, I just installed avast home edition it is also giving me this type of error, i had another anti virus which i just uninstalled! can any body help me:
Error: dbsCreatObject
Follow this link:
http://forum.avast.com/index.php?topic=14208.0
RejZoR,
Your small fix tool realy works!
Thx a lot!!
I don’t doubt that the tool works in changing the database from odbc to xml, but this really shouldn’t be the first course of action.
Whilst this isn’t a problem for those using the Home version. However, those using the Pro version it has been mentioned it is best to be on odbc for the extra functionality, etc. (not totally certain of the exact reason). For them they should be looking at updating the jet drivers so they continue to use odbc for the database.
So why don’t Alwil guys make a sticky with appropriate instructions? I’m really tired of writing this solution over and over again…
I think there is something in the avast FAQ about it on the web site.
Perhaps that wants to be on the FAQs or a Sticky here - http://www.avast.com/eng/other_questions.html#idt_1406
Q: What should I do when I see this error message: "Unknown error. Program cannot set property into main Storage"?A: This error message is displayed when your ODBC drivers are too old, or damaged, or if they aren´t installed properly. avast! uses these drivers by default. There are two solutions for this problem:
* Install current ODBC drivers provided by Microsoft. You can download them from this page. * Don´t use the ODBC drivers, use XML instead. To make avast! use XML drivers, follow these steps: 1. Open the file avast4.ini located in C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA in Notepad. 2. Find the section [COMMON] 3. In this section, change the line Database=ODBC to Database=XML 4. Save the file 5. Restart your computer</blockquote>
Yeah, but problem is that people DON’T read FAQs and README files.
I know, because i noticed the same for my programs (even though, mine have much smaller Readme files).
There is also one (actually two) solution for this. And it’s not so impossible.
When avast! encounters such error, it should give user web address on which it can obtain latest Jet drivers. Error is way too common so they should do something about it.
Another solution is to add switching option on error dialog for this error, an option to change to XML. At least in Home Edition.
This will do the trick for sure.
I’m agree, reading the avast help file, FAQs, forums search, forum sticky threads and or readme files is obviously lacking as we see from the many posts on these forums; so adding another sticky isn’t going to improve this based on past experience.
However, your idea to offer solutions to this common problem in the error dialogue is excellent. The second option for home users is also very good, perhaps going a step further and have the database=XML on installation of the home version. This however, may be an issue is they subsequently upgrade to the pro version (but that would have been a problem if they switched on you option two).
But great ideas.
Hopefully avast will take it up. Or at least point them to the website FAQ entry for it, so the url link isn’t hard coded into the error dialogue and is easier to maintain a current url on the website.