That can also happen if you have a communications module listed in the I/O tree, with nothing connected to it in the I/O tree. The usual culprit here is the Ethernet module. There is no reason to list it in the I/O tree unless you are using it for remote I/O or produced/consumed tags.
If it is listed, with no partner, it will give the blinky I/O light warning.