GetEvents error / "Events: subscription 8000ffff"

J C

J C

n3wb
Dec 13, 2023
15
9
GA
Hello Experts

I started getting this error today on all 5 cameras...anyone know why?? Something to do with DST maybe? I did change the time in each cameras' setting but still getting the error.
Onvif triggering is not working on 3 cameras.

Thank you
 

Attachments

  • error2.JPG
    error2.JPG
    65 KB · Views: 74
  • error1.JPG
    error1.JPG
    23.4 KB · Views: 65
Yep, I had the same error this morning, but only on one camera. ONVIF app, showed the same error on that one camera, and showed it was something to do with time.
But the only solution was to do as @wittaj described above.
 
It is an issue where the camera and BI are having "handshake" issues and thinks that there is a problem, when there isn't (usually). It is an annoying issue, but not causing any issues other than we don't like seeing that error message LOL.

We usually see this come up when someone updates BI and it was fine on a previous version but has issues on a newer version.

And sometimes they just pop up, usually if a camera rebooted or temporarily lost connection with BI.
 
  • Like
Reactions: J C
I had many "Events: Request 8000ffff" at 3am also, on many cameras, but all have onvif authenticator: OFF (but I do have "get Onvif trigger events" checked ON as I do use the camera's IVS). Recordings were not impacted.
 
From what I remember about this issue it had to do with a mismatch between the authentication request time and what the camera evaluated time was taking into account time zone settings.

I also had a similar issue way back when and disabled authentication in the cam itself as my cams are on their own separate network.
 
wittaj said:
In the camera GUI, Under Network > Access Platform, turn onvif authenticator off.
Click to expand...

This is obviously Camera brand specific, as there's nothing for auth with ReoLink.

Will flag to Ken/BI Support.

Meanwhile, I have Disabled "Auto Refresh" within Onvif commands within the BI GUI, just in case. Hoping itll get the commands one time, and not keep hammering it as such to cause the error.
 
Last edited:
Auto Refresh did nothing, so I checked my logs. Found the date the problem started, which was around 3rd March.

Have gone back to 5.8.7.5, a version from Mid Feb, to see if that helps.
 
Vini said:
Auto Refresh did nothing, so I checked my logs. Found the date the problem started, which was around 3rd March.

Have gone back to 5.8.7.5, a version from Mid Feb, to see if that helps.
Click to expand...
My problem started Mar 3 after 2AM the same time as the DST time change when we set the clock 1 hour ahead. Coincidence???
 
I mean, it’s an observation. But our clocks didn’t change in the UK though…
 
Rolling back hasn’t seem to have helped… :(

Will have to wait for Support to get back to me.
 
You must log in or register to reply here.
Top Bottom