Hello! We have encountered the following error many times when importing patrols using SMART Mobile Data Import from the Data Processing Queue: “Error linking incidents to patrol: org.hibernate.exception.LockAcquisitionException: could not execute query”.
After clicking OK, it continues the import without further errors. However, I am concerned that a patrol feature could have been corrupted or be missing.
Has anyone encountered this error and/or know the cause and fix? Most importantly, does this error imply there has been data loss?
Sorry for the delay in response to your original message.
It looks to me like there’s likely no data loss. It appears SMART is trying to associate incident data with patrol data. So the error is suggesting that the software is attempting to generate a relationship between a patrol and an incident which is not completing.
Just a couple of follow up questions:
What version of SMART desktop / connect are you running?
Do you teams often collect Independent Incident data (i.e. from a different model through the “incident” function) while on patrol?
Thanks for your reply. I’m running SMART Desktop 7.5.9. Our teams never collect Independent Incident data. I’ve disabled that option in the patrol projects they use. I thought maybe the issue was related to the Data Model attributes being renamed after the last export of the patrol package, but it seems to give the error even on recent projects. It’s great to hear that there’s likely no data loss - that is definitely comforting!
Thanks for the additional info. I assume the Connect version aligns.
Yeah, the error doesn’t suggest data loss to me but you may want to desk test it. Collect a patrol, see if the error occurs and check the data after import to make sure everything is there as expected.
We should have SMART 8 released soon and hopefully after upgrading this error message will go away.