openvpnserv2 crash

[lstipakov]

Reported here.

Installing alpha2 without GUI on the current Windows Canary in Virtualbox.
Disabled everything except service and DCO.
Interactive service had started while OpenVPNService failed.

Event Viewer shows in System time out events 7009 and 7000, and in Application :

Event 1026
Application: openvpnserv2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.SecurityException
at System.Diagnostics.EventLog.FindSourceRegistration(System.String, System.String, Boolean, Boolean)
at System.Diagnostics.EventLog.SourceExists(System.String, System.String, Boolean)
at System.Diagnostics.EventLog.SourceExists(System.String)
at OpenVpn.OpenVpnService..ctor()
at OpenVpn.Program.Main(System.String[])

Event 1000
Faulting application name: openvpnserv2.exe, version: 2.0.0.0, time stamp: 0x67d2d744
Faulting module name: KERNELBASE.dll, version: 10.0.27881.1000, time stamp: 0x392e7c44
Exception code: 0xe0434352
Fault offset: 0x00179554
Faulting process id: 0xD14
Faulting application start time: 0x1DBE4637FBEF3DF
Faulting application path: C:\Program Files\OpenVPN\bin\openvpnserv2.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

OpenVPNService would not start as neither Network nor Local service, only as System.

[lstipakov]

Before installing OpenVPN, could you run this powershell script as an admin:

$source = "OpenVPNService"
$logName = "Application"

if (-not [System.Diagnostics.EventLog]::SourceExists($source)) {
    [System.Diagnostics.EventLog]::CreateEventSource($source, $logName)
    Write-Host "Event source '$source' created under log '$logName'."
} else {
    Write-Host "Event source '$source' already exists."
}

[lstipakov]

Reproduced by deleting event source from the registry - probably a leftover from the previous service. The fix is underway.

[irwir]

The script repored existence when installed and right after uninstall.
After reboot:

Exception calling "CreateEventSource" with "2" argument(s): "Must specify value for source."
At line:2 char:5
[System.Diagnostics.EventLog]::CreateEventSource($source, $logNam ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : NotSpecified: (:) [], MethodInvocationException
FullyQualifiedErrorId : ArgumentException

Event source '' created under log ''.

On the subject of leftover. There were quite a few upgrades: Virtualbox, Canary versions, and also OpenVPN.
But the result is the same even when there were no legacy or other OpenVPN services in the list, and all registry entiries related to "OpenVPN" string had been deleted manually before installing.

It might be mentioned that on Windows Server 2019 similar installation was successful, but the service commonly fails on reboot and requires a manual start. Maybe this was yet another issue; let's see how it will behave after the fix.

[irwir]

Additional note. When cleaning the registry, I also deleted the driver, because ovpn-dco.inf remained in the driver store.
Should the driver(s) be purged automatically?

[lstipakov]

May I ask you to try this installer? It creates the possibly missing event source during installation.

[lstipakov]

Regarding driver presence in the driver store - yes, this is known behavior, also true for tap-windows6 and 2.6 releases. We could probably improve it but this is not related to the service crash.

[irwir]

The new installer worked properly in Canary.

Testing on Windows Server 2019 will be tried later, and it might be having a different issue.
Alpha2 was giving this error on reboot:

The description for Event ID 0 from source openvpnserv cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

openvpnserv error:
DeleteNrptRules: could not open NRPT base key (2)

As said above, manually started service worked well.

Driver store cleanup.
Should I create an issue in openvpn-build?

[lstipakov]

@irwir Yes, please create the issue about driver store cleanup.

Regarding NRPT error - this is from interactive service - yet another component which is responsible for privileged operations. The error you observing should not be related to openvpnserv2 startup error. Could you check if following registry keys exist?

HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows NT\\DNSClient\\DnsPolicyConfig
HKLM\\SYSTEM\\CurrentControlSet\\Services\\Dnscache\\Parameters\\DnsPolicyConfig

The error you are getting is supposed to happen when both of those keys are missing, which is somewhat unexpected.

Anyway, the openvpnserv2 service startup issue appears to be resolved, right?

[irwir]

Service crash issue looks fixed.
Driver store cleaning suggestion has been added (openvpn-build).

There are no these keys in the registry.
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient...
HKLM\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters\DnsPolicyConfig
This server does not have domain services installed. Maybe rare, but such possibility should be taken into account, should it not?

Thank you!

[lstipakov]

The fix will be part of alpha2-I002 or alpha3. I've created a separate ticket for NRPT issue.

Thank you @irwir for helping us make OpenVPN better.