Symptom:
My laptop was recently disabled by multiple instances of nilm.exe.
The computer became sluggish and eventually could only be shutdown by removing the battery.
The task manager reported that the amount of memory being using was over 1 Gig and growing. Task manager processes showed pages of nilm.exe, presumably zombies.
And of course the critial error pop-up - "nilm.exe could not initialize." that was always in top and could not be cleared.
Extreme measure taken:
Because of the sluggish performance I could not get to the service menu to shutdown the parent NI service. Instead I renamed the file nilm.exe to killnilm.exe thus inhibiting spawning yet another copy of nilm.exe.
At this point I re-booted and set the parent NI license management service to start manually.
Complaint:
The NI knowledge base lists this as a known problem and that only one copy of nilm.exe should be running. The knowledge base also states the root cause is that TCP/IP is incorrectly configured. I do not agree this root cause statement. The root cause is poor programming practice that allows the lack of a computer resource (TCP/IP sockets connection) to completely crash a computer.