Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error in defaulttrace log from Guided Procedures

After implementing Guided Procedures for test purposes, it was decided that it was not needed. The configuration was removed. However every few minutes an error message is produced.

#1.# 00144F482363002300000712000005BE00045789876BB369#1222148100961 #com.sap.workflow#sap.com/irj#com.

sap.workflow#Guest#0##n/a## 896cb70087fa11dda66900144f482363 #ThreadThreadPool.Worker10,5,SAPEngine_A

pplication_Threadimpl:3_Group##0#0#Error#1#/Applications/Workflow/Engine#Plain###WFMS.processEven

t#

#1.# 00144F482363002300000713000005BE00045789876BBC03#1222148100963 #com.sap.workflow#sap.com/irj#com.

sap.workflow.#Guest#0##n/a## 896cb70087fa11dda66900144f482363 #Thread"["ThreadPool.Worker10,5,SAPEngine_

Application_Threadimpl:3_Group##0#0#Error##Plain###com.sap.workflow.eventsender.WFEventException:

USER_AUTH_FAILED: User account for logonid "user_id" not found!

at com.sap.workflow.engine.WorkflowRuntime.continueExecution(WorkflowRuntime.java:220)

at com.sap.workflow.engine.WFMS.processEventEx(WFMS.java:827)

at com.sap.workflow.engine.WFMS.processEvent(WFMS.java:703)

at com.sap.workflow.engine.WFMS.processEvent(WFMS.java:692)

at com.sap.workflow.engine.BPRuntime.continueExecution(BPRuntime.java:22)

at com.sap.workflow.engine.BPMS.processBPEvent(BPMS.java:98)

at com.sap.workflow.engine.ejb.EWorkflowDirectBean.processEvent(EWorkflowDirectBean.java:39)

at com.sap.workflow.engine.ejb._EWorkflowDirectBean__EJBProxy.processEvent(_EWorkflowDirectB

ean__EJBProxy.java:212)

at com.sap.workflow.eventsender.WFDirectEventSender.sendWFEvent(WFDirectEventSender.java:24)

at com.sap.workflow.es.scheduler.TaskSchedulerDeadline.run(TaskSchedulerDeadline.java:91)

at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:174)

at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:108)

at java.lang.Thread.run(Thread.java:534)

All information (we think has been removed from the portal), we have also looked in the SAP backend and cannot see in the logs were this error is coming from.

Does anyone know where this error is coming from and how it can be stopped?

Thanks

Not what you were looking for? View more on this topic or Ask a question