Hi @ikehoe,
You’ve probably already seen this similar thread – not sure it’s any help, but linking it here anyway just for completeness’ sake.
@Dulip_Withanage is our expert on all things ORCiD, so I’ll tag him here.
Meanwhile, I’d suggest checking your log file for a message that appeared at the time the user received that message. There should be a message there that indicates more detail about the problem. For OJS 3.1.2, the ORCiD plugin kept its own log file called “orcid.log” in the files directory of the installation.
We technically don’t support OJS 3.1.x, and are shortly going to drop support for 3.2.x as well, so I do suggest prioritizing an upgrade to 3.3.0 LTS! LTS is Long-Term Support, a new release strategy we introduced last year to suit organizations that didn’t want to plan regular upgrades. More details about that here. And I promise, once you get to 3.3.0 or newer, upgrades will become a lot easier.
Regards,
Alec Smecher
Public Knowledge Project Team