This counter tracks how many Update packets received by this license server were erroneous, such as arriving with no receive data. Administrators watch it as an early sign of trouble in the license update exchange between server and clients that could eventually cause inaccurate license accounting. For example, a spike in Update errors right after adding a new client to the shared license pool would prompt checking that new client's configuration.