Products | Versions |
---|---|
TIBCO BusinessWorks Collaborator | - |
Not Applicable | - |
Description:
Workflow server fails to start IC Processes such as IcWorker, IcDispatcher and IcNotifier and any of these processes goes into a defunct state. Workflow
server could not start successfully.
Symptoms:
The following error will be seen in the IC debug log.
****
14:58:53 (disp) 15259 t001: debug: logServerShutdownEvent - event.log failed -- <Error, Client, 21000>: Invalid Event Type
****
And following error in IC status log
****
2003 Aug 06 09:02:24:000 GMT -0400 WorkflowServer Info IC Status Log Header V4.0
2013 May 08 14:54:47:000 GMT +0200 WorkflowServer Error 3 1 14000 15259 2 77 77 0 Dispatcher User Does Not Exist.
2013 May 08 14:54:47:000 GMT +0200 WorkflowServer Error 3 1 14000 15264 2 55 55 0 Event/Action Daemon User Does Not Exist.
2013 May 08 14:54:47:000 GMT +0200 WorkflowServer Error 3 1 21000 15264 2 55 55 0 Event/Action Daemon Invalid Event Type
****
Cause:
The cause is updating the SERVER_NUMBER or
INIT_DB_VERSION in SERVER_NAMES table. Any time you change the
SERVER_NUMBER or INIT_DB_VERSION from the ORIGINAL value used when the
database was initialized you invalidate the database. The reason for
this is all object ids created are based on the seed of the
SERVER_NUMBER and INIT_DB_VERSION. Changing the values causes the
server to lose essential system objects such as Permanent Job,
EMPTY_POOL and icdba.