What specific URL?

We get exactly the same error message via the Firefox connector as Sangoli posted above.

I would be happy to provide one...do you need the url from Primo?

we're not able to get the metadata from your primo catalog (PNX in technical terms). If you're a patron, talk to your library. If you're a librarian, talk to Exlibris.

URL: http://primoapac02.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=ABS#

Hi Adam,

We are also having this same problem.

We have noticed recently that Zotero no longer works for Ex Libris Primo sites that are still running on the 'classic' UI. When trying to save a record we get the following message:

An error occurred while saving this item. See Troubleshooting Translator Issues for more information.

Or sometimes:
An error occurred saving with Primo. Attempting to save using Embedded Metadata instead.

See for example:

http://virtuose.uqam.ca/
https://primo.tug-libraries.on.ca/primo_library/libweb/action/search.do?vid=WATERLOO
http://decouverte.uquebec.ca/primo_library/libweb/action/search.do?vid=UQTR
http://primo-standard-lb.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=UOTTAWA

Searching for records on these sites and then attempting to save via Zotero results in an error (using up to date versions of Chrome or Firefox).

Curiously, for the University of Vienna, Zotero still works with their classic interface:
http://usearch.univie.ac.at/

Using the Chrome network inspector we can see that both urls have status 200 for Vienna:
https://usearch.univie.ac.at/primo_library/libweb/showPNX.jsp?id=TN_doaj_soai_doaj_org_article_47f5128d766d48f78d1765125b3e7d70
https://usearch.univie.ac.at/primo_library/libweb/showPNX.jsp?id=2

In the non-functionning sites, there is only one URL, using the docID rather than the session ID, and it gets a 404 or 500 error:
https://primo.tug-libraries.on.ca/primo_library/libweb/showPNX.jsp?id=vtug2256046 (404)
http://primo-standard-lb.hosted.exlibrisgroup.com/primo_library/libweb/showPNX.jsp?id=TN_jstor_archive_1341886962 (404)
http://virtuose.uqam.ca/primo_library/libweb/showPNX.jsp?id=UQAM_BIB001313503 (500)

There was a recent update to the Zotero Connector :
Version 5.0.41, Updated September 4, 2018

This may or may not be relevant but it seems the problems started around this time.

Is there a way to diagnose and fix this problem? I do not think the source of the problem is with Primo, since this problem is occuring in both our test and production environments, and those are running on different versions (test is on the most recent August 2018 release, while production lags behind on the August 2017 release. Zotero previously worked properly in both environments).

Please let me know if any additional information is necessary.

Thanks,
Sacha

Ottawa is hosted, I'm not sure about TUG, but the UQ and UQAM sites are both local. I have opened a ticket in Salesforce with Ex Libris and am waiting for a response. I'll follow up here when I get a reply.

Same problem here. It was working fine in Zotero version 5.0.52, but when I upgraded to 5.0.55 the problem started. Got the message that it couldn't save and it's only saving the book record as a web page.

It works "better" on the new UI because the new UI includes COinS metadata [1] for results, and Zotero is using the COinS translator instead of the Primo PNX translator. I'm not how the COinS metadata is getting built, so I don't know if it's comparable in quantity or quality to the PNX metadata retrieved by the Primo translator.

As to why the Primo translator has broken, it appears to be related to showPNX.jsp. TUG was returning 404 for showPNX.jsp because at some point it got removed (maybe in a Primo upgrade?). After we re-added it, based on the version available in the Developer's Network [2], now we're seeing 500, and the output doesn't look like showPNX.jsp is getting called at all, but rather that the regular Primo page generator is getting called with parameters it doesn't understand and is failing. Maybe some Tomcat configuration was required on the FEs to get that URL to be loaded directly?

[1] https://en.wikipedia.org/wiki/COinS
[2] https://developers.exlibrisgroup.com/blog/showPNX_Revisited

@bwuhlman no, the new Primo instances are still working via PNX, not via COinS (there's a link to PNX embedded in the search results and item displays); but as you diagnose correctly, the issue is indeed with the showPNX not working correctly for the older versions -- as this used to work, I'm pretty sure the issue is on ExLibris side and there's very little we can do in Zotero without getting PNX in Primo.