Help, BIND9 initialization error on Windows 2000!

[Stefan Puiu]

Just my two cents: I've seen an error like this on Windows, and it was
related to upgrading an app, which would remove a service and then
install a replacement (with the same name). Sometimes the old service
couldn't be removed and you'd see something like this when trying to
run the service.

At least that's what I understand from your posts, since you say you
are able to run named from the command line just fine. You can try
getting the srvinstw.exe tool for Windows 2000 (look for it using
google, should be on the MS site), remove the "ISC BIND" service (I
think it has the same name for BIND 8) and then reinstall BIND 9.

On 7/8/05, Shi Jingnian <shijn at tjpc.org> wrote:
> Gregory Hicks wrote:
> >Then, if you DO NOT have these "not found" events, one of
> >two things is happening:
> >1.  The named.conf you think is in the right place is not
> >    the one that BIND is actually reading
> >or
> >2.  The log file you are looking at is not the one to which
> >    BIND is logging.
>=20
> impossible. i searched and found no other named.conf files
> in the machine except my backup. even now i deleted the
> backup, the service still cannot be started. if you've read
> the messages from the very beginning of the thread, you would
> have known the error happened before reading named.conf, of
> course no logs created, named.exe had even no chance to write
> events before failed.
> "named -g" from DOS box runs well, so i guess my service
> manager has something wrong to initial and invoke named.exe.
>=20
> Shi.
>=20
>=20
>