Remote installation, binlsvc wont start.

[lefty78]

I have a windows 2000 sever set up as a DC, DHCP server, DNS server, WINS server, and as a RIS server. My problem is the the BINLSVC wont start, this is needed for the RIS clients to connect. When I reboot the computer it tells me a service or device has failed (BINLSVC), when I try to manually start the service I get the following error;

'Microsoft Management Console'
Could not start the Boot Information Negotiation Layer service on local computer.
Error 183: Cannot create a file when that file already exists.


at the same time an event is recorded in the event log as follows;

'System Log'
Source:Service Control Manager
Event ID: 7023
Description: The Boot Information Negotiation Layer service terminated with the following error; Cannot create a file when that file already exists.


Any pointers?

 

[dredoggg]

A Search of the MS web site for:
"Could not start the Boot Information Negotiation Layer"
gave a number of possibles, but this is probably the best hit:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281929

 

[lefty78]

Thanks for the response, but that doesnt seem to be my answer. I have tried that already and it does not change anything.

 

[CaptainMorgan]

Lefty,

I'm not sure this is going to help you but since you seem to have your W2K server also doing duty as a DHCP, DNS, WINS and RIS server, I thought this might point you in the right direction. You'll need to check the Application Log to see if these errors combinations are there. I got this from the following URL:

http://www.eventid.net/displayqueue.asp?eventid=1002

Sorry about the length. When you print it out it'll make more sense. Hope it helps.

Event ID: 1002
Event Source: bvlsvc
Event Type: Error
Event Description: The BINL service cannot initialize its global data. The following error occurred:
1722
Comment: SymptomsWhen you restart your computer, Boot Information Negotiation Layer service (BINL service) in the Remote Installation Services (RIS) may not start.

Also, the following error message may be reported in the system event log:

Service Control Manager event ID 7023:
The Boot Information Negotiation Layer terminated with the following error:
The specified domain either does not exit or could not be contacted.

The Application Log shows BINLSVC 1002 and 1008 error messages when this service is starting up:

Event ID 1002, source BINLSVC
Description:
The BINL service cannot initialize its global data. The following error occurred: 1355

Event ID 1008, source BINLSVC
BINL service is shutting down because of error 1355
However, you are able to start the service manually after a few hours. Then, the Verify Server property in RIS shows no errors.

Cause: This issue is a timing issue, and it can occur if you configured RIS and the DHCP Server service on the same domain controller.

The error message can occur if the server is configured as a WINS client or if a WINS server is not defined for the server. This behavior has not been reported when the server is configured as its own WINS server.

Resolution: To work around this issue, configure the BINL service to be dependent on DHCP Server. To do this, follow these steps:

Start Registry Editor (Regedt32.exe).
Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrrentControlSet\Services\BINLSVC\DependOnService
On the Edit menu, click Add, and then enter the following value: DHCPServer

NOTE: If you remove DHCP Server at a later time, you must remove all of the dependences on DHCP Server as well. If you do not remove the dependencies, the computer locks when you restart it.

Status: Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

More Information: The RIS feature that is included with Windows 2000 Server is designed to install Microsoft Windows 2000 Professional clients.

 

[lefty78]

That is also another route that I have tried. Although I may need some clarity as to what exactly they are telling you to change. If I navigate to that listing in the registry (HKLM\System\CurrentControlSet\Services\BINLSVC\DependOnService) it has a value of TCPIP Lanman

my question, are they asking you to change that value, or to create a new one all together.

I think it is just for the manipulation of the key that is already present, and changing that keys value to DHCPServer does change the dependencies for the BINLSVC, but still does not resolve the problem.

I have a feeling I have a newly discovered issue. I have been working on this for the last two months. HoHum.

 

[CaptainMorgan]

Lefty,

Sorry to hear it's been that much of a pain. From what I've read I'd have to assume (that could be a nasty right there) that it will add the DHCPServer to the string. Never having had to do this, I'm not sure.

Just curious but do you happen to have another DC that you can load RIS onto separately. If it is an issue with timing then having DHCP and/or WINS and RIS loaded independent of each other may solve it for you? If you haven't already tried it, maybe setting them up in that fashion will resolve the issue.

Sorry I can't be much more help than that.

Anybody else have any ideas?

 

[tlcscousin]

also make sure you authorise the ris server in dhcp.

 

[lefty78]

I should have another DC, but there is none. I think the problem would be easier to troubleshoot if there was one set as a RIS specific server. I have tried uninstalling the services and reinstalling them in a number of orders, and all is authorized and configured properly, no fix.

AH, I dont think I mentioned that the tftp is not starting properly either, if this sheds some more light on the situation. Thanks for your responses.