Showing posts with label Livelink Logs. Show all posts
Showing posts with label Livelink Logs. Show all posts

Tuesday, March 16, 2010

Enabling Full Livelink Logging to Capture LAPI Problems

0 comments
In trying to troubleshoot the 101107 LAPI error and 0-byte size documents, I learned there are some specific settings in the OT.ini file (not the actual name btw) to allow for LAPI logging.

In the file:
[general]
debug=2
 
[options]
WantLogs=TRUE
WantLAPILogs=TRUE
WantTimings=TRUE
WantVerbose=TRUE
 
Restart services, replicate the issue as many times as you want, and start comparing GB's worth of logs!
Have fun!

Tuesday, March 9, 2010

Error: Unique constraint on dtree, LAPI add object, 101107

0 comments
Environment: Livelink 9.7.1, .NET 3.5, Oracle 10, ADN module, heavy category/attributes
Problem: Multithreaded LAPI app loads several documents into Livelink and creates new folder structures, permissions, RM Classifications, and categories. Once in a while, we run into this error on the Livelink server side: Oracle error: (1) --> ORA-00001: unique constraint (LINK_OWNER.ADNIDS_INDEX1) violated

The LAPI error is CreateObjectEx Failed. Message=Error adding categories to node errMsg=Error saving generated number. Status=101107 (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
LapiException: CreateObjectEx Failed. Message=Error adding categories to node errMsg=Error saving generated number. Status=101107

Theories:
  • ADN is blowing up again. 
  • The LAPI port is getting overloaded.
  • LAPI sucks.
  • The database is being overwhelmed by multiple transactions from multiple users (adding one object to Livelink is usually about 100-200 various transactions, so do the math if there are 100+ users).

Wednesday, March 3, 2010

Error: The provider already exists in this session

0 comments
I've been trying to troubleshoot a LAPI error and perused through the Livelink connect logs. This one error kept showing up.

"The provider already exists in this session"

Looks like you can ignore this one. It is a warning message that is to be expected. It is saying that the EFS required has already been identified. It is common and can be ignored.

Link to the discussion thread here.