Why did an old XProtect LPR component stop writing logs after a Log Server upgrade?

Answered by ANPR AI·Sourced

Short answer

A historical authentication change can block older components.

Explanation

The 2018 R3 Log Server changed compatibility with 2018 R2 and earlier LPR components.

Things to check

  • Component releases
  • Server Logs options

What to do

Use the documented compatibility setting only for that legacy combination, or align component versions. Do not apply this historical workaround to unrelated current failures.

Source

Milestone: Managing server logs

Scope and version

Latest guide; historical 2018 R2/R3 compatibility note

Was this answer helpful?

Your vote decides which questions we answer next.

Comments

Add a comment

Share what worked for you, or ask about a detail in this answer.

Comments are reviewed before they appear.

Cloud API

Test plate and vehicle recognition on your own images.

Send a photo or camera frame to our API and get the plate, country, make and model back as JSON. Start free, or run the same models on your own servers.

  • 100 free credits every month, no card
  • Plates for Saudi Arabia, Qatar, Kuwait, Bahrain and Oman
  • Cloud API or on-premise deployment

Related questions

Browse all ANPR questions