Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Problems with workflow indexing (GetUserById involved)
Jordi_Masip_(azertiaadmin_-_(deleted))
Errors during indexing step related with workflows appeared in our production environment (Livelink 9.0.0.1 with April patch under SUN/Solaris). We can read thinks like next in trace log file:Log[7] : ExportToIPool:AddOrReplace:WorkId=960766&SubWorkID=960766&permType=WFLog[3] : GetMetaData: UAPI.GetUserById failed. Specified user couldn't be located.It appears several times (for different subworkflows).Does anyone know why it happens?We investigated and we realized that UAPI.GetUserById function is waiting for a user name and it is receiving a group name in these cases. Could it explain this problem?If we don't find how to solve this question, we are thinking to deactivate workflow indexing. What does it mean in Livelink behaviour? Any negative points?
Find more posts tagged with
Comments
eLink User
Message from Eidson Matthew W Contr AFFTC/ITASC <<A HREF="mailto:Matthew.Eidson@edwards.af.mil">Matthew.Eidson@edwards.af.mil> via eLink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
eLink
I've had this same problem.
If you find out the problem please let me know.
Thanks,
Matt
-----Original Message-----
From:
eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent:
Wednesday, June 12, 2002 6:51 AM
To:
eLink Recipient
Subject:
Problems with workflow indexing (GetUserById involved)
Problems with workflow indexing (GetUserById involved)
Posted by
CentrisaAdmin
(Masip, Jordi) on 06/12/2002 09:46 AM
Errors during indexing step related with workflows appeared in our production environment (Livelink 9.0.0.1 with April patch under SUN/Solaris). We can read thinks like next in trace log file:
Log[7] : ExportToIPool:
AddOrReplace:WorkId=960766&SubWorkID=960766&permType=WF
Log[3] : GetMetaData: UAPI.GetUserById failed. Specified user couldn't be located.
It appears several times (for different subworkflows).
Does anyone know why it happens?
We investigated and we realized that UAPI.GetUserById function is waiting for a user name and it is receiving a group name in these cases. Could it explain this problem?
If we don't find how to solve this question, we are thinking to deactivate workflow indexing. What does it mean in Livelink behaviour? Any negative points?
Susan_Lee_(chironuser3_-_(deleted))
Any findings on this issue?
