-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Match Now gives a database error. #8
Comments
(NB - I get the same via a job: "Finished execution of Mutual Aid with result: Failure, Error message: Matching failed: DB Error: unknown error") |
Yes, I had my suspicions, and I found this in the log:
I'll fix that... |
@bjendres that didn't seem to fix it – after install I got the error below in-screen, and 'match now' gives the same error as before.
|
@vingle: that's weird. Could you maybe get the full error message from the CiviCR log? It should be around here:
|
It's
) and
|
That sounds weird, but if you can reproduce that again, please create another ticket... @vingle does that mean it's working and you're happy now? Should we close the ticket...? |
@bjendres - it's working in a clean install so I guess? The error Or if you can suggest specific tables/fields that this error might be referencing I can compare them between my two installs to try and debug further. |
You're right, that is weird. I my opinion, this could only happen if somebody changed the enabled help types while the matcher was running... @vingle maybe open a new ticket for that after all...? |
Have submitted a request for, and offer of, help – both records appear in the dbse with the correct custom fields. But when I click Match Now get the following error (am using Mutual Aid 1.1-alpha1, OCM 1.7-beta3 , Google Mapping/Geocoding):
The text was updated successfully, but these errors were encountered: