I've really stayed out of this thread, but let me add my two cents worth
here.
The above is true except for the "up&running" part. DependOnService
allows you to specicy a service dependencies. IOW, if this service
isn't running, RadiusNT will not start. If you stop that service,
RadiusNT will also be stopped. It does allow you to organize the
startup order, but thats it. SQL Server returns a "yes I have started"
to the Service Control manager about 3 secs after its asked. If it
went done dirty (which is typically the issue here) then it could take
several minutes to clean up and be ready for requests. In the mean
time,
the service manager has already started RadiusNT, and its going through
its login requests. The problem is that SQL Server is returning
"Unknown table Servers", etc to RadiusNT because it hasn't fully
initialized.
I will try to add some code to RadiusNT to allow it to correctly
handle that error as well. The only error control currently in there
is login failure.
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com-RadiusNT Mailing list (radiusnt@iea.com)