My version will crash whenever the website requires a re-login, maybe once a month. I've also been getting an odd crash error on imports when an expected index of an array is off. I'll trying running my code in debug mode to catch the reason. For me it's not a big deal as long as I can catch the crash within 5 days allotted to me by the server.
Mine was the same it was only crashing now once in a bluemoon down from almost crashing everyday what did I do to make it more stable ahhhh nothing.. LOL Windows update I guess. Anyhow running it as service for quiet a few days now and no issues at all. So far so good with running it as service as I believe if it crashes running as service than probably service restarts it regardless.
Let's say I use Fix Entry and I accidently entered the wrong plate # and checked off Auto-Update All and now when I try to correct it again I get this error...
Let's say I use Fix Entry and I accidently entered the wrong plate # and checked off Auto-Update All and now when I try to correct it again I get this error...
Anyhow running it as service for quiet a few days now and no issues at all. So far so good with running it as service as I believe if it crashes running as service than probably service restarts it regardless.
Crash logs are attached for those they make more sense to than me.
Also how are people doing black lists where the Viewer does not yet have a record of a plate? I've got a couple of reads on my neighbours letterbox that I "correct" to the plate I want alerted on.
I am not seeing any errors in event viewer.. But again it is random Anyhow Atleast the good news is with the NSSM even if it is crashing it probalby is starting again all by itself so nothing is being missed at this point.. So it is pretty solid with this combo at-least so far running it more than a week almost now no problem I even implimented this for one of my friend and he has not reported anything else either..
I am not seeing any errors in event viewer.. But again it is random Anyhow Atleast the good news is with the NSSM even if it is crashing it probalby is starting again all by itself so nothing is being missed at this point.. So it is pretty solid with this combo at-least so far running it more than a week almost now no problem I even implimented this for one of my friend and he has not reported anything else either..
I've got auto update off on my BI box because I don't want it restarting at an inopportune time. After your post I did a winver and realised how long it had been since I updated windows.
I usually stay on Bleeding edge when I should only stay @ leading edge. So take 20H2 With a grain of salt .. Since Each hardware can be different depending on your hardware driver and how it handles it. Definitely you can try first with 2004. And then 20h2.
Highly recommend backup as this is always a good idea before you do anything..
My version will crash whenever the website requires a re-login, maybe once a month. I've also been getting an odd crash error on imports when an expected index of an array is off. I'll trying running my code in debug mode to catch the reason. For me it's not a big deal as long as I can catch the crash within 5 days allotted to me by the server.
Mine did this for a little while after ALPR changed their login page.
Here's the updated code I use (it was the login button that had to be changed, I believe)
wb_OpenALPR.Document.GetElementById("username").SetAttribute("value", Constants.alprUser);
wb_OpenALPR.Document.GetElementById("password").SetAttribute("value", Constants.alprPassword);
/Updated 2020.10.14 to handle new login method.
wb_OpenALPR.Document.GetElementById("login-btn").InvokeMember("click");
Updating "Auto Plate Corrections" should now work without error - also wrapped it in error handling (into event log) just in case...
Moved some of the logic for the "Plate Detail" grid to hopefully prevent errors when the viewer is started and there are no records for the period it defaults to.
Modified sp_LPR_AllPlates slightly - decreased load time on my system for the "Plate Details" section - which is refreshed every time you click on a plate in the main grid. (1.2 seconds -> 0.5 seconds). You'll want to run this file manually.
Hi Gymratz, Thank you again for the tweaks / improvements. Just to confirm For viewer we need to run this file now dated "2020.12.27 - sp_LPR_AllPlates Update" as a new query ?
Update - I did run it as new query seems like that is how it was.. Everything is up and running. Thank you so much once again!!
I'm not sure if this has been addressed in the new update or not, but hide all doesn't always seem to work. The "plates" I hide are still showing up and this is what comes up when I try to hide it again.
I'm not sure if this has been addressed in the new update or not, but hide all doesn't always seem to work. The "plates" I hide are still showing up and this is what comes up when I try to hide it again. View attachment 78074
I updated the "Auto Correct" to remove and re-add when you want to change it - to account for duplicate keys.
But I didn't touch the Hide All code.
Can you clarify for me what you mean by "doesn't always seem to work?" - The code for which plates to show is in SQL. So either:
1. I need to review that code
2. (And this is what I'm hoping) - I'm just not refresh the grid after you hide one. But, if you were to switch days and go back - or do anything else to refresh the grid, they'd be gone and never visible again.
Slight Edit
The update I made to the SP in the last update will show hidden plates if searched for. For example, if UHAUL was one you hid and you're just looking at "Today" - it won't show up. But, if you search for "UHAUL" today, it will show up.
Wasn't intentional, but not sure if that's a bad thing or not.
I just ran the update, I think that may have fixed it.
Previously the plates I marked as hide all would still show up on the list and when I would try to hide it again I would get the error in the screenshot above.
I think it's a good idea to keep the hidden items searchable. Thank you for the update and keeping up with the project!
Yes. Definitely check out the thread that @tech101 created - he has a very thorough walkthrough on how to set it up. It's not a "install it and walk away" program. It's something I created for myself and then worked with DLONG to improve and make it reusable by others. But, you'll still need Visual Studio, SQL Server, and either a bit of knowledge on how to use them (or diligent at following instructions between what I put in the original post or tech101's guide).
