Unable to start as file is in a protected read/execute area you are attempting to write in.
Working Yesterday before i exited. I had imported a list of servers but it worked yesterday.
program to start.
select a non-protected area like in \Users\
bugreport.txt
download
I just resubmitted a version which should not have that portable.lock file shipped in the appx installer. I already did that several times but I recall I did that in the same "submission" as the one which initially had this file, accidentally. This time I created a submission no. 4 and hope it gets updated at all, since the version 10.2 has not changed yet.
Thanks.
Jay
On Wed, Jul 3, 2019 at 5:41 PM, Ansgar Beckernotifications@github.com wrote:
I just resubmitted a version which should not have that portable.lock file shipped in the appx installer. I already did that several times but I recall I did that in the same "submission" in the store administration. This time I created a submission no. 4 and hope it gets updated at all, since the version 10.2 has not changed yet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
@ansgarbecker Just tried it now, the portable_settings.txt file is still preventing the app from launching.
Can confirm I also get this using version that was updated from Store an hour ago - version 10.2.0.5599
Ok, then my submission from yesterday passed the certification already.
Just for the records: I removed that portable.lock file 2 weeks ago, and resubmitted the package already 3 or 4 times. It seems to me Microsoft caches these packages in some way.
Could you please uninstall and reinstall HeidiSQL from the store, to see if that works?
Checked for updates, there was no update.
Uninstalled and installed back again - same thing.
On error report, same app version as before is shown: 10.2.0.5599
One of our users had the same issue with the portable_settings file this morning. Reading the comments here, I uninstalled, downloaded a fresh copy of the 64bit version (from the Heidi website) and installed that. When it runs, I comes up with the "Session Manager" dialog. I copied the details from my PC and got the following error; I also exported the settings from my PC, imported those and got the same error.
Error: Library seems unusable. Please select a different one. Internal error 126: The specified module could not be found.
@Vire5cent you are using the latest build - be aware these can contain bugs.
The error message is brand new, and caused by non-existing libmysql.dll and/or libmariadb.dll in your HeidiSQL directory. Please check if one of these files exist there. But please post feedback in #677 as that's the right ticket for that library loader.
I have been having the same issue.
I just downloaded HeidiSQL_10.2_64_Portable and the program started without any errors. Then downloaded the installer and HeidiSQL started without errors.
Having the same issue, tried resetting, repairing and reinstalling, but neither worked.
I've submitted a bug report via the crash reporter
I have been having the same issue.
I just downloaded HeidiSQL_10.2_64_Portable and the program started without any errors. Then downloaded the installer and HeidiSQL started without errors.
Yes, downloading the installer from heidisql.com worked for me too. It's just HeidiSQL through the Microsoft Store that is still showing the error. Tried uninstalling and reinstalling several times to no avail. Proceeding with the downloaded installer only.
I uploaded an update to the Windows Store last Friday. The package is still in the certification process. Normally this takes only one day or two, but with the weekend in mind probably one more day.
Is there any update on this yet? I'm still getting the portable_settings error when trying to launch the Heidi app on my desktop. I want to try and avoid downloading again and having to set up multiple connections from scratch.
Today at 12 o'clock I got the message "Your app HeidiSQL submission has been processed." from the Microsoft Store. So, you could watch out if you already get an update for HeidiSQL in the store. If yes, and the problem persists in the new version, I recommend uninstalling and reinstalling. That should remove one offending file from your HeidiSQL directory.
Thanks dude. New release seems to have fixed the issue. It did cause a plink error when trying to open a connection, but fixed by downloading plink.exe again. Back in the game :)
That's great news!
Most helpful comment
I uploaded an update to the Windows Store last Friday. The package is still in the certification process. Normally this takes only one day or two, but with the weekend in mind probably one more day.