• Article Type: General
• Product: Aleph
• Product Version: 17.01

Description:
We have encountered a couple of issues in using their Connexion client that don't prevent cataloguing, but probably are cause for concern. We have reported these to OCLC support, but wonder if they have anything to do with our Aleph set-up.

1) Whenever we perform an action (e.g. search or update holdings) that requires connection with the OCLC server, we get a "Transaction failed. Your host connection may have been lost" error message. On the second try, the transaction always works.

2) Whenever we export a record from OCLC to Aleph, we get a message that "An error has occured with your last action" followed by an explanation "Attempted to read or write protected memory. This is often an indication that other memory is corrupt..." (See attached screen shot) The export is always successful anyway.

Resolution:
This turned out to be a problem with a setting in OCLC Connexion, not with Aleph. OCLC tech support correctly indicated that both problems may be due to a "persistent connection" setting. I don't know why I had to fiddle with the settings -- "persisent" just sounded good, I guess -- but everything works fine, now that I've turned it off.

• Article last edited: 10/8/2013