LAPI Error 107404

Session Status=107404
Error=Error setting the category or attributes for this node. Error saving generated number.
Happening When=Updating multiple documents with latest attribute values.

The "Error saving generated number" points to an Automatic Document Numbering module specific error... but who knows. More research to follow....

LAPI Error 101107

LapiException: CreateObjectEx Failed. Message=Error adding categories to node errMsg=Error saving generated number. Status=101107

Scenario: Bunch of categories need to be applied to a newly created folder structure and sub objects. I was trying to add a document into Livelink via LAPI. If the folder structure for where document goes does not exist, then the LAPI app creates it with the correct categories, attributes, permissions, RM Classifications, etc... However, if the structure exists, even though the category may have been applied incorrectly, then the app will just load the document into the folder structure.

Potential cause: I'm still looking into since there are so many moving parts and factors involved with this enterprise solution.... for loading documents non-natively (if that's a word) into Livelink. (DAMN architects)
What I think is happening is that -

• The category DNE at the expected parent level.
• The attributes were not populated correctly.
• ADN (automatic document numbering) had an issue

I strongly believe it has something to do with ADN because I have found issues with SQL Injections. You attempt to load a document with reserved SQL words like UNION and JOIN and ADN freaks out. Special characters like apostrophe mess it up too. We have patched ADN with a quick fix from the vendor but still run into this 101107 error. It's like Livelink is failing during the database writes into ADN along with the external file store and the attribute tables. WTF....

What a pain in the ass to resolve. Logging on the Livelink is so process intensive.

LAPI Connection Issues

I've been running into sporadic issues with an enterprise app that hits Livelink constantly through LAPI. The following are some articles I found. None of them fixed my issue though because we've actually attempted the resolutions two years ago to fix ANOTHER LAPI connection issue. F%$K!!!

Article Number: 3500936 - Why do I get LAPI connectivity issues intermittently?

• Running massive amounts LAPI transactions result in "Could not access server" error.

Article Number: 15090633 - LAPI - GetObjectAttributesEx Function Executes Increasingly Slowly When Called Repeatedly

• Repetitive usage of the function results in degrading performance.

Article Number: 3496785 - Keep Livelink Socket Backlog In Mind When Creating Multi-Threaded LAPI programs

• LAPI calls randomly fail in Multi-threaded applications if the number of application threads are greater than the number of Livelink server threads

Article Number: 3501616 - Getting sporadic LAPI errors (Pooling LLSession objects)

• There is no apparent advantage to pooling LLSession objects 

Livelink aka Livestink

Well... I don't hate Livelink that much. If it wasn't for the lack of developers and Livelink specialists, then I would be out of a job. There A LOT of great things about the content management system. But there are also, A LOT of nuisances that bring the product quality down. As a Livelink developer, I have been involved on all sides of a Livelink implementation. More to come as I jot down my prior and current experiences with this product.