distal-attribute
distal-attribute
distal-attribute
distal-attribute

Conflict Problem?

User, date Message
Written by jamsession
7 months ago
Category: General
120 posts since Sat, 22 Dec 07
I suspect that my HeidiSQL is conflicting with my AVAST! virus scanner.

I can't update HeidiSQL. During the update proceedure, HeidiSQL "failed" to make something.

I can't update my overnight builds.

Under Avast!'s settings>activate protection>file system shield>exclusions, I listed:

i) C:\Program Files\HeidiSQL\*

ii) C:\Program Files (x86)\HeidiSQL\*

Yet, during sql database export, a message error says:

Cannot create file "C:\Program Files (x86)\HeidiSQL\Backups\December 18, 2013_temp.sql"
Access is denied.

Any advice?

- j unhappy
Written by ansgar
7 months ago
4940 posts since Fri, 07 Apr 06
The updater itself is extracted to your temp directory and then executed. Maybe you need to also whitelist that file. On my Win7 32 bit it's in C:\Users\<MyUserName>\AppData\Local\Temp\ and its filename is HeidiSQL_updater.exe .
Written by kalvaro
7 months ago
587 posts since Thu, 29 Nov 07
As far as I know, HeidiSQL does not create any database backup when you update it. (Why should it?) So I guess you're asking two different things.

If you run a database export manually and choose the program folder as destination you won't have permission to write there (as expected in any properly configured Windows computer). I guess that HeidiSQL doesn't prompt for elevation and I'm not sure why Windows doesn't use virtual storage to "fake" writing on the folder but you shouldn't save your user data in system folders in the first place.

Written by jamsession
7 months ago
120 posts since Sat, 22 Dec 07
1. Sorry, for my ambiguity, kalvaro!

I meant to say that HeidiSQL encounters the problem when I manually try to export my database.

I have HeidiSQL set to export to:

C:\Program Files (x86)\HeidiSQL\Backups\December 18, 2013.zip

where I change the file date over to the current date.


2. My HeidiSQL just updated to 8.2.0.4675.

When I was updating the overnight build, however, an error message said:

failed to create backup file...

So, now, my HeidiSQL won't update to .4680.

When I manually attempted to export my database, an error message said:

Cannot create file "D:\Program Files (x86)\HeidiSQL\Backups\December 19, 2013_temp.sql".
Access is denied.

Incidentally, I did not have this problem prior to installing Avast!.

Any comments?

- j
Written by dchow
7 months ago
8 posts since Tue, 04 Sep 12
Hi ansgar,

I have a similar problem running the updater tool in HeidiSQL. It proceeds to download the update file. When the downloaded file runs, I get a similar "cannot create backup" error message and the whole thing quits. I have to manually restart HeidiSQL to get back in. This is also after I've installed 8.2 and all subsequent updates have failed to update this way. Unfortunately the message is so brief that I can't even get a screenshot of it.

Please advise. Thanks.
Written by ansgar
7 months ago
4940 posts since Fri, 07 Apr 06
Privilege problems with the updater should be fixed in r4680. I never knew that 64bit Windows needs a requireAdministrator flag in the manifest of a software updater, other than Windows 32bit which also looks for filenames like "updater" or whatever. See issue #3474. Thanks to geki007 for creative solution tips.
Written by jamsession
7 months ago
120 posts since Sat, 22 Dec 07
os = 7

I got my HeidiSQL to update and export by running it as administrator. In other words, I right clicked on the HeidiSQL and then clicked "run as administrator". After that, everything worked.

Thanks for the idea, ansgar! smile

- j
Written by ansgar
7 months ago
4940 posts since Fri, 07 Apr 06
Starting with r4680, I guess and hope you never see that problem again, as the updater is now forced to request administrator privileges.
Written by jamsession
7 months ago
120 posts since Sat, 22 Dec 07
Excellent!

Thanks! smile

- j
Written by dchow
7 months ago
8 posts since Tue, 04 Sep 12
Hi ansgar,

I've updated my HeidiSQL with the updater tool in r4680 to r4681 and it all works as expected. I can confirm that everything works for me again. Thanks for getting this problem fixed so quickly.
 

Please login to leave a reply, or register at first.