Error EX4: DBISAM Engine Error #11013

[aarontx]

Has this issue been resolved?

I tried installing the latest stable build and am receiving the database errors.

Win 7 64-bit new build.

[mouser]

I just got a report that someone was experiencing this.. If anyone gets this error on current builds, can you tell me about your setup and OS?
And can you try changing the options on the "Tweaks" tab for where to store the temporary database file?

[mouser]

Ok so I got a follow up email from the other person experiencing this bug -- he tracked it down to the fact that CHS was saving its data to user's document directory, which was on a NETWORK drive.
Solution was to modify the ConfigDir.ini file in the ClipboardHelpAndSpell directory to point to a local drive (in his case CONFIGDIR=%APPDATA%).

[mouser]

For those looking for a summary of the situation and solutions, see my first post on the first page of this thread.

[drgt]

Hi.

I just got this error too for the first time at boot, after 6 month use or so without a problem.
I use version 2.33 on XP SP2 and Avira antivirus.

Error EX4: DBISAM Engine Error #11013

I use the portable edition (did not install the program) which is stored in my D local hard disk which is excluded from Avira's Scan.

[mouser]

have you tried the fixes in the first post?

[drgt]

You mean exclude database directory from Antivirus?

Like I said, the entire drive is excluded.

[mouser]

Can you try changing the Temporary Database Location in the options here:


Try the different options see if any fix it.

[drgt]

Ok. Thanks.

Will monitor and report back.

It is working right now, all I did was terminate by task manager and relaunch D:\....exe.

[mouser]

I wonder if i can check for and handle this condition more gracefully.. It may simply be a case of a temporary file being locked at start of app by a security app but that a second attempt to read it would solve the problem.

In your case terminating and relaunching solved the problem and you didn't have to make any changes in the app or in your antivirus tool, is that correct?

[drgt]

That is correct!

And like I said, this is the first time it happened and it was at boot time.

[HankFriedman]

I finally found a solution that worked for me.

None of the suggestions listed here worked, but since I use WinPatrol, I set a startup delay for CHS to 2 minutes 10 seconds, and now the problem doesn't happen.