Menu
▾
▴
openvpn-users
|
From: Ralf H. <Ral...@ch...> - 2013-12-05 09:08:10
|
Serveral of my users somehow managed to botch their openvpn installations. Upon starting the OpenVPN GUI, one particular user is getting a window: ---------------- OpenVPN GUI CreateProcess failed, exe='C:\Users\Acer\Documents\Wichtige Dokumente\Charite\OpenVPN\bin\openvpn.exe' cmdline='openvpn --version' dir='C:\Users\Acer\Documents\Wichtige Dokumente\Charite\OpenVPN\bin' and an OK button on the bottom right. ---------------- Problem: Even upon reinstallation with correct (default) paths, the error message above tends to stick. Where is that path stored? How can I fix this? -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ral...@ch... Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 |
|
From: Gert D. <ge...@gr...> - 2013-12-05 09:32:50
|
Hi,
On Thu, Dec 05, 2013 at 09:52:08AM +0100, Ralf Hildebrandt wrote:
> Problem: Even upon reinstallation with correct (default) paths, the
> error message above tends to stick.
>
> Where is that path stored? How can I fix this?
As far as I understand, it's stored at installation time in the registry,
and *should* be deleted upon deinstall. Samuli, Heiko?
Ralf, which version of the windows installer did they install? (We have
multiple installer versions all based on 2.3.2, and more recent ones have
seen enhancements specifically in registry key handling, IIRC)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany ge...@gr...
fax: +49-89-35655025 ge...@ne...
|
|
From: Ralf H. <Ral...@ch...> - 2013-12-05 10:02:12
|
* Gert Doering <ge...@gr...>: > Hi, > > On Thu, Dec 05, 2013 at 09:52:08AM +0100, Ralf Hildebrandt wrote: > > Problem: Even upon reinstallation with correct (default) paths, the > > error message above tends to stick. > > > > Where is that path stored? How can I fix this? > > As far as I understand, it's stored at installation time in the registry, > and *should* be deleted upon deinstall. Samuli, Heiko? Of course I cannot trust my users, but at some time one user came around and deinstallation DID NOT delete the values. > Ralf, which version of the windows installer did they install? (We have > multiple installer versions all based on 2.3.2, and more recent ones have > seen enhancements specifically in registry key handling, IIRC) Ugh. I encoutered that problem with the most recent vewrson from http://openvpn.net/index.php/open-source/downloads.html "openvpn-install-2.3.2-I003-i686.exe" -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ral...@ch... Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 |
|
From: Samuli S. <sa...@op...> - 2013-12-06 13:30:51
|
> * Gert Doering <ge...@gr...>:
>> Hi,
>>
>> On Thu, Dec 05, 2013 at 09:52:08AM +0100, Ralf Hildebrandt wrote:
>>> Problem: Even upon reinstallation with correct (default) paths, the
>>> error message above tends to stick.
>>>
>>> Where is that path stored? How can I fix this?
>> As far as I understand, it's stored at installation time in the registry,
>> and *should* be deleted upon deinstall. Samuli, Heiko?
> Of course I cannot trust my users, but at some time one user came
> around and deinstallation DID NOT delete the values.
The 2.3.2 installer does not delete any OpenVPN-GUI registry keys when
OpenVPN is uninstalled - only the GUI executable and the desktop icon:
!ifdef USE_OPENVPN_GUI
Delete "$INSTDIR\bin\openvpn-gui.exe"
Delete "$DESKTOP\${PACKAGE_NAME} GUI.lnk"
!endif
When OpenVPN-GUI is launched the first time (as admin) it creates the
registry keys it needs, which include the location of the OpenVPN
executable. Moreover, it does not update the registry keys if OpenVPN is
relocated, e.g. by reinstalling it. Afaik the only way to fix this
situation is to manually remove the entire OpenVPN-GUI registry entry
entirely and then start OpenVPN-GUI as admin. This way correct registry
keys will be regenerated.
I fixed this problem along with some others by creating a separate NSIS
installer for OpenVPN-GUI. This installer is not, however, included in
2.3.x, and probably never will, because it might cause other issues
which we don't want in stable releases. It will be bundled with the
upcoming OpenVPN 2.4 installers, though.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
|
|
From: Ralf H. <Ral...@ch...> - 2013-12-06 14:28:26
|
> The 2.3.2 installer does not delete any OpenVPN-GUI registry keys when > OpenVPN is uninstalled - only the GUI executable and the desktop icon: OK > When OpenVPN-GUI is launched the first time (as admin) it creates the > registry keys it needs, which include the location of the OpenVPN > executable. Seemingly, this is - in my particular case - a bit "off" > Moreover, it does not update the registry keys if OpenVPN is relocated, > e.g. by reinstalling it. OK, so one would have to delete the keys. Which keys? > Afaik the only way to fix this situation is to manually remove the > entire OpenVPN-GUI registry entry entirely and then start OpenVPN-GUI > as admin. This way correct registry keys will be regenerated. Great, where do I find those? > I fixed this problem along with some others by creating a separate NSIS > installer for OpenVPN-GUI. This installer is not, however, included in > 2.3.x, and probably never will, because it might cause other issues > which we don't want in stable releases. It will be bundled with the > upcoming OpenVPN 2.4 installers, though. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ral...@ch... Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 |
|
From: Gert D. <ge...@gr...> - 2013-12-06 14:32:45
|
Hi,
On Fri, Dec 06, 2013 at 03:28:14PM +0100, Ralf Hildebrandt wrote:
> OK, so one would have to delete the keys. Which keys?
> Great, where do I find those?
Sorry for the omission :-) - Heiko mentioned them yesterday, but only
on the IRC channel
13:10 <@d12fk> cron2: HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI is the place the
exe path is stored
(And yeah, we really need to clean this up for 2.4 :-))
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany ge...@gr...
fax: +49-89-35655025 ge...@ne...
|
|
From: Ralf H. <Ral...@ch...> - 2013-12-06 14:56:04
|
* Gert Doering <ge...@gr...>: > Hi, > > On Fri, Dec 06, 2013 at 03:28:14PM +0100, Ralf Hildebrandt wrote: > > OK, so one would have to delete the keys. Which keys? > > Great, where do I find those? > > Sorry for the omission :-) - Heiko mentioned them yesterday, but only > on the IRC channel > > 13:10 <@d12fk> cron2: HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI is the place the > exe path is stored > > (And yeah, we really need to clean this up for 2.4 :-)) Definitely. Littering the registry is never a good thing. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ral...@ch... Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 |
|
From: Samuli S. <sa...@op...> - 2013-12-09 07:31:27
|
> Hi, > > On Fri, Dec 06, 2013 at 03:28:14PM +0100, Ralf Hildebrandt wrote: >> OK, so one would have to delete the keys. Which keys? >> Great, where do I find those? > Sorry for the omission :-) - Heiko mentioned them yesterday, but only > on the IRC channel > > 13:10 <@d12fk> cron2: HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN-GUI is the place the > exe path is stored > > (And yeah, we really need to clean this up for 2.4 :-)) > > gert The openvpn-gui.nsi installer/uinstaller script is functional, but needs some real-life testing in the 2.4 alphas. Integration with openvpn-build buildsystem is still missing, but fairly easy to add. Samuli |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X