<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Log isn’t going to help here if named is crashing. Getting a backtrace or anything that closely resembles one would help. Running debug build under MSVS would help. Or doing git bisect and pinpoint the breakage to a commit or at least Merge commit would help.<br><br>This is part of the problem - debugging on Windows is extremely painful and requires expertise with extremely high learning curve.<br><br><div dir="ltr"><div>--</div>Ondřej Surý — ISC (He/Him)<div><br></div><div>My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.</div></div><div dir="ltr"><br><blockquote type="cite">On 17. 2. 2022, at 15:08, Jakob Bohm via bind-users <bind-users@lists.isc.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>On 2022-02-12 01:06, Richard T.A. Neal wrote:<br>
</p>
<blockquote type="cite" cite="mid:LO2P123MB4110E9F9588EBA54A593F6E5B3319@LO2P123MB4110.GBRP123.PROD.OUTLOOK.COM">
<pre wrap="">I run BIND on Windows as well but I've been unable to upgrade to 9.16.25 - I get an error stating "Error Validating Account. Unable to install service using this account.". So I'm presently running 9.16.21.
What are the last few things in the Application Event Log (Source: named) before it terminates?
Richard.
-----Original Message-----
From: bind-users <a class="moz-txt-link-rfc2396E" href="mailto:bind-users-bounces@lists.isc.org"><bind-users-bounces@lists.isc.org></a> On Behalf Of Jakob Bohm via bind-users
Sent: 11 February 2022 12:19 pm
To: bind-users <a class="moz-txt-link-rfc2396E" href="mailto:bind-users@lists.isc.org"><bind-users@lists.isc.org></a>
Subject: Windows 9.16.25 fails to start (1067 Terminated unexpectedly)
Dear list,
When recently trying to upgrade some secondary-only authoritative servers running on Windows machines, I found that Bind 9.16.25 (x86_64) binaries from isc.org failed to completely startup, causing Windows to report that "1067 The process terminated unexpectedly.", with 0 process exit code. Attempting to up the debug level all the way to "-d 100"
failed to log a reason, but downgrading to the 9.16.21 binaries resumed operation.
Is there a known issue and workaround for this, or is there any additional information to extract?
<snip>
</pre>
</blockquote>
The latest in the log (I directed it to a file, as the Event Viewer
wrapping in the port was badly done) were the mentioned fetch of
./NS etc. interspersed with zone loading messages for default zones
(I temporarily commented out the real zones to shorten the config,
but it still failed).<br>
<br>
<pre class="moz-signature" cols="72">Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. <a class="moz-txt-link-freetext" href="https://www.wisemo.com">https://www.wisemo.com</a>
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded</pre>
<span>-- </span><br><span>Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list</span><br><span></span><br><span>ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.</span><br><span></span><br><span></span><br><span>bind-users mailing list</span><br><span>bind-users@lists.isc.org</span><br><span>https://lists.isc.org/mailman/listinfo/bind-users</span><br></div></blockquote></body></html>