"Sequence Number Caching" in TIBCO iProcess Engine Administrator's Guide for more information about REQIDs.
WARNING: Only Num kilobytes free in
VolumeNames's volume, at least
MinFreeKB are needed
The Process Sentinels regularly check that the system has sufficient disk space for iProcess to operate. The SWDIR\etc\fs_part file defines the list of file systems that are used by iProcess and checked by the Process Sentinels.
“Administering Process Attributes” in TIBCO iProcess Engine Administrator's Guide for more information about the following process attributes:
•
|
CHECKFREQ defines the number of processing loops that the Process Sentinels cycle through before checking that the system has sufficient available disk space. The default value is 50.
|
•
|
MINFREEKB defines the minimum free disk space required (in KB) for a BG process to run. The default value is 10000.
|
•
|
PROCESS_SLEEP defines the amount of time (in seconds) the Process Sentinels will sleep for. The default value is 5.
|
•
|
1 (Critical), if the process is one that runs continuously, such as SPO, WQS or WIS,
|
|
Background (BG) processes can be stopped and restarted without affecting foreground processes. Restarting SPO, WQS or WIS processes will affect client users.
|
“Administering iProcess Engine Server Processes” in TIBCO iProcess Engine Administrator's Guide for more information about how to stop and start iProcess processes.
Possible infinite loop in Procedure:<ProcName > Case:
CaseNum... Sending Step <
StepName >
exceeded max send/withdraw actions per workflow transaction (process attribute BG_MAX_ACTIONS_PER_TRANS =
Value).
“Administering Process Attributes” in TIBCO iProcess Engine Administrator's Guide for more information about the BG_MAX_ACTIONS_PER_TRANS process attribute.
A Background (BG) process received an invalid
FieldName-
FieldValue assignment - for example, a number, date or time may not have been in the correct format.
For the affected CaseNum case, you can issue an event to set the correct field value (for example, by using the
SWDIR\bin\swutil or
SWDIR\util\swbatch utilities, or TIBCO iProcess™ Objects\TIBCO iProcess™ Server Objects). However, the affected field may have been used in other calculated fields or in conditions in the procedure. The application developers will need to investigate further to determine the scope of the problem and what needs to be done to rectify it.
Refer the problem to the application developers responsible for procedure ProcName so that they can investigate where the erroneous
FieldName is coming from. For example, the
FieldName may have been deleted from the procedure.
For the affected CaseNum case, if:
•
|
the indicated FieldName should not be assigned, no further action is required.
|
A Background process (BG) needs to find a value for field
FieldName, but it cannot find a field definition for the field in the
ProcName procedure.
The indicated StepName has been defined to wait on the
WaitedForStep, but the
WaitedForStep does not exist in the
ProcName procedure.
iProcess cannot start a case of procedure ProcName. This could be because the iProcess Engine still has a demonstration license rather than a full license. When the iProcess Engine is initially installed, it is set up with a demonstration license that allows you to create a maximum of 4 steps per procedure, and to start a maximum of 20 cases per procedure.
The appropriate TIBCO iProcess Engine Installation Guide, for more information about how to obtain and implement a full license.
User UserName has attempted to administer a case of the
ProcName procedure (using the
Case Administration tool in Work Queue manager), but is not allowed to do so. This is because
Case Administration access to this procedure has been restricted (using the
Procedure >
Access >
Case Admin option in the TIBCO iProcess Modeler).
User UserName has attempted to start a case of the
ProcName procedure, but is not allowed to do so. This is because
Case Start access to this procedure has been restricted (using the
Procedure >
Access >
Case Start option in the TIBCO iProcess Modeler).
A SWDIR\bin\swutil command tried to access the procedure definition database records for the
ProcName procedure, but was unable to do so.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
3.
|
Send the resulting SWDIR\logs\pstaffifc01.log log file to TIBCO Support for further investigation.
|
A SWDIR\bin\swutil command tried to access the iProcess user tables, but was unable to do so.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
3.
|
Send the resulting SWDIR\logs\pstaffifc01.log log file to TIBCO Support for further investigation.
|
User 'UserName' is not a valid user
The specified operating system UserName is not an iProcess user, but attempted to run a
SWDIR\bin\swutil command that can only be run by iProcess users - for example,
SWDIR\bin\swutil AUDIT.
•
|
Re-run the SWDIR\bin\swutil command that failed as an appropriate iProcess user.
|
•
|
Make the UserName user an iProcess user, and then re-run the SWDIR\bin\swutil command that failed.
|
A SWDIR\bin\swutil command tried to access a procedure that does not exist on the system.
If the specified ProcName is incorrect, re-run the command using the correct
ProcName.
If the specified ProcName is correct, import the procedure to the system, then re-run the command.
Work item 'ReqID:HostName' in queue '
QueueName' unlocked.
The specified StepName cannot be delivered because it has no addressee. The work item is instead sent to user
swadmin’s
Undelivered work queue.
This error can occur if the StepName uses a field addressee, but the field has not been initialized when the step is sent out.
2.
|
To repair the affected CaseNum, log in to the TIBCO iProcess Workspace as user swadmin, and forward the StepName work item from the Undelivered work queue to the intended recipient.
|
A Background (BG) process cannot access the list of procedures after receiving a
SWDIR\bin\swutil RESEND command.
•
|
the TIBCO iProcess swutil and swbatch Reference Guide, for more information about the swutil RESEND command.
|
A Background (BG) process cannot find a procedure that it needs after receiving a
SWDIR\bin\swutil RESEND command.
•
|
the TIBCO iProcess swutil and swbatch Reference Guide, for more information about the swutil RESEND command.
|
A Background (BG) process cannot access the case information for a case of the
ProcName procedure after receiving a
SWDIR\bin\swutil RESEND command.
•
|
the TIBCO iProcess swutil and swbatch Reference Guide, for more information about the swutil RESEND command.
|
A Background (BG) process cannot access the procedure definition for the
ProcName procedure that it needs after receiving a
SWDIR\bin\swutil RESEND command.
•
|
the TIBCO iProcess swutil and swbatch Reference Guide, for more information about the swutil RESEND command.
|
•
|
the TIBCO iProcess Expressions and Functions Reference Guide, for details of the SETSTEPSTATUS function syntax.
|
•
|
the TIBCO iProcess Modeler - Basic Design Guide, for information about how to use the SETSTEPSTATUS function to control Waits in loops or conditions.
|
•
|
the TIBCO iProcess Expressions and Functions Reference Guide, for details of the SETSTEPSTATUS function syntax.
|
•
|
the TIBCO iProcess Modeler - Basic Design guide, for information about how to use the SETSTEPSTATUS function to control Waits in loops or conditions.
|
•
|
the TIBCO iProcess Expressions and Functions Reference Guide, for details of the SETSTEPSTATUS function syntax.
|
•
|
the TIBCO iProcess Modeler - Basic Design guide, for information about how to use the SETSTEPSTATUS function to control Waits in loops or conditions.
|
•
|
the TIBCO iProcess Expressions and Functions Reference Guide, for details of the SETSTEPSTATUS function syntax.
|
•
|
the TIBCO iProcess Modeler - Basic Design guide, for information about how to use the SETSTEPSTATUS function to control Waits in loops or conditions.
|
•
|
the TIBCO iProcess Expressions and Functions Reference Guide, for details of the SETSTEPSTATUS function syntax.
|
•
|
the TIBCO iProcess Modeler - Basic Design guide, for information about how to use the SETSTEPSTATUS function to control Waits in loops or conditions.
|
A Background process (BG) failed to start a case of a sub-procedure because the system’s maximum sub-procedure nesting depth has been reached.
•
|
Check the specified ProcName and StepName to see if there is a problem in the procedure logic. For example, a sub-procedure that calls itself, a group of procedures that call each other in a loop, or a condition in which the exit criteria are not being met, thus creating an infinite loop.
|
•
|
If this is not the case, use the SWDIR\util\swadm command to increase the value of the MAX_SUB_PROCEDURE_DEPTH process attribute, which defines the system’s maximum sub-procedure nesting depth.
|
“Administering Process Attributes”, in TIBCO iProcess Engine Administrator's Guide, for more information about the
SWDIR\util\swadm command.
RELEASED procedure (ParentProcName-
CallingStepName-
CaseNum) started case of UNRELEASED procedure
SubProcName.
The specified CaseNum of released procedure
ParentProcName started a sub-case of unreleased procedure
SubProcName, because no released version of
SubProcName was available.
The TIBCO iProcess Modeler - Advanced Design guide, for more information about how to define and use sub-procedures.
Check the specified SubProcCallStepName and make sure that it is calling a sub-procedure and not a main procedure.
The TIBCO iProcess Modeler - Advanced Design guide, for more information about how to define and use sub-procedures.
Directory <DirName> does not exist. Not adding to the partition list cache.
The DirName directory does not exist, so iProcess cannot monitor the space available in that directory.
The SWDIR\etc\fs_part file defines the directories that iProcess monitors for available space.
DirName is listed in that file.
The WISMBD process may also terminate when this error occurs.
2.
|
To repair the affected CaseNum, log in to the SPC as user swadmin, and forward the work item from the Undelivered work queue to the intended recipient.
|
“Purging Cases”, in the TIBCO iProcess swutil and swbatch Reference Guide, for more information about how to purge a case using
SWDIR\bin\swutil.
Note the ErrCode and contact TIBCO Support for further assistance.
“Administering Process Attributes”, in the TIBCO iProcess Engine Administrator's Guide, for more information about the “MBSET_” process attributes.
The specified MboxSetID could not be loaded, or there are no Mboxes in this Mbox set.
“Administering Message Queues and Mbox Sets”, in the TIBCO iProcess Engine Administrator's Guide, for more information about Mboxes and Mbox sets.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
Use the SWDIR\util\swadm update_queue command to correct the physical queue description
QueueDesc for the queue
QueueID.
•
|
“iql_queue”, in the appropriate TIBCO iProcess Engine (Database) Administrator’s Guide for your database, for more information about the required format of the physical queue description.
|
Examine the SWDIR\logs\sw_warn file for a message produced by the
BG process prior to this message. That message provides additional information about this error and how to resolve it.
A BG process has encountered an error while attempting to dequeue a message from an Mbox set. The following table lists the possible
ErrText values.
•
|
1 (Critical), if MBox sets have been incorrectly configured. (For example, if the WIS processes do not have an MBSET_WRITE_BG attribute set no work items can be released.)
|
“Administering Message Queues and Mbox Sets”, in the TIBCO iProcess Engine Administrator's Guide, for more information about how to administer Mbox sets, message queues and the physical database tables that support them.
2.
|
Use the SWDIR\util\sweaireg LIST command to list the existing EAI Plug-in entries. Search this list for EAIType to ensure that the plug-in is correctly registered . Note that Java-related EAI types (such as the TIBCO iProcess BusinessWorks Plug-in) will not be listed separately.
|
•
|
“IQL_RETRY_COUNT”, in TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
|
•
|
The appropriate TIBCO iProcess Engine Installation Guide, for more information about shared library path requirements.
|
'EAIType' EAI Run-Time Plug-In failed to initialise, error
ErrMsg
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
The interface function 'FuncName' (required for interface version
VerNum) is not available in EAI Run-Time Plug-In '
EAIType'.
The EAIType EAI Server Plug-in claims to conform to the specified version of the EAI Server Plug-in interface, but does not meet the requirements of that interface
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName@HostName EAI Step:
StepName Case:
CaseNum EAI plug-in EAIRun_Call() failed, error:
ErrMsg
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
SWDIR\logs\sw_error or
SWDIR\logs\sw_warn
•
|
1 (Critical), if a required system process fails to start up. (For example, if the BGPREDICT process fails to start, it is only critical if you actually use prediction in your procedures.)
|
The 'EAIType' EAI Run-Time Plug-In does not support any interface specification version that the background server supports.
The BG process does not support any of the EAI run-time plug-in interface versions that are provided by the EAI Server Plug-in. The BG process and EAI Server Plug-in cannot communicate with each other.
The BG process will continue to run normally. However, transactions that attempt processing of EAI step types handled by the
EAIType EAI Server Plug-in will be aborted and rolled back.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
'EAIType' EAI Run-Time Plug-In's '
FunctionName' function provided an invalid value for '
ExpectedData'.
The EAIType EAI Server Plug-in has returned an unexpected value for the specified item of data. (
ExpectedData is a description of the expected data for which the value in question is invalid.)
•
|
while the plug-in is being initialized, the BG process will continue to run normally. However, transactions that attempt processing of EAI step types handled by the EAIType EAI Server Plug-in will be aborted and rolled back.
|
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName EAI Step:
StepName Case:
CaseNum failed. Could not run the EAI call-out - the run-time plug-in for this EAI step type (
EAIType) is either not registered or failed to load and initialise correctly.
The BG process has attempted to process an EAI step of the given
EAIType, but the
EAIType EAI Server Plug-in is either not installed or has failed to initialize correctly.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
1.
|
Check that the EAIType EAI Server Plug-in has been installed correctly.
|
2.
|
Check both the SWDIR\logs\sw_warn and sw_error files for any initialization errors for the EAIType EAI Server Plug-in.
|
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName EAI Step:
StepName Case:
CaseNum failed. Could not withdraw the delayed release EAI step - the run-time plug-in for this EAI step type (
EAIType) is either not registered or failed to load and initialise correctly.
The BG process has attempted to process a withdraw of an EAI step of the given
EAIType, but the
EAIType EAI Server Plug-in is either not installed or has failed to initialize correctly.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
1.
|
Check that the EAIType EAI Server Plug-in has been installed correctly.
|
2.
|
Check both the SWDIR\logs\sw_warn and sw_error files for any initialization errors for the EAIType EAI Server Plug-in.
|
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName@HostName Case:
CaseNum failed. The run-time plug-in for EAI Type '
EAIType', is using 'asynchronous with reply' call-out methods but has not provided an EAIRun_GetReply () function.
The EAIType EAI Server Plug-in is not self-consistent in terms of its communication protocol with the
BG process.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName@HostName EAI Step:
EAIStepName Case:
CaseNum failed. The EAI step failed to withdraw, error:
ErrMsg.
The BG process has attempted to withdraw the specified
EAIStepName as part of a transaction, but has received the specified
ErrMsg from the EAI Server Plug-in.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
Procedure:ProcName@HostName Case:
CaseNum EAI plug-in type '
EAIType' EAIRun_GetReply() failed, error:
ErrMsg
The BG process has attempted to process the specified
EAIStepName as part of a transaction, but has received the specified
ErrMsg from the EAI Server Plug-in.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
The specified Oracle OCIError has occurred while attempting to subscribe to, unsubscribe from or publish an event using Oracle AQ.
If OCIError is “
User does not exist”, and the process named in the message header is
swsvrmgr or
spo, this means that the process cannot use the iProcess event management system, which is provided by Oracle AQ. Possible causes for this are:
Procedure:ProcName@HostName EAI Step:
EAIStepName Case:
CaseNum - Invalid Delayed Release condition expression defined.
The BG process has attempted to process the specified
EAIStepName, but has encountered an invalid expression in the
EAIStepName’s delayed release condition. This can happen if the expression has become invalid since it was defined - for example, if a data field that the expression references has subsequently been deleted.
The BG process rolls back the transaction being processed at the time of failure and continues processing other transactions.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
1.
|
Make sure that ProcName’s hierarchy of parent processes are already running.
|
The PMType (either
Worker or
Watcher) process sentinel cannot create a TCP/IP socket connection to its peer process, because of a socket Errno. This means that the
PMType process sentinel will be unable to restart its peer process, if the latter fails.
2.
|
In the UNIX /etc/services (or Windows %systemroot%\system32\drivers\etc\services) file, make sure that the TCP/IP port numbers assigned to the nodename_watcher and nodename_worker processes are unique (system-wide).
|
TIBCO iProcess Engine Installation Guide, for more information about allocating TCP/IP port numbers to the watcher/worker processes.
1.
|
Make sure that ProcName’s hierarchy of child processes are already stopped.
|
The child process on port number PortNum has reported a socket Errno. It cannot create a server-side socket because the port number it has been given by the worker process sentinel is still in use.
•
|
One of the worker process sentinel’s child processes (for example, a BG process) is using a specified port number and fails. The process is automatically restarted by the worker process sentinel and attempts to create a new socket connection on the same port number as before, but for some reason the operating system has not yet marked that port as unused.
|
•
|
The child ProcessName fails after it is created, but before the worker process sentinel attempts to connect to it. Consequently, there is no server-side socket for the worker process sentinel to connect to.
|
•
|
1 (Critical), if the specified ProcessName is critical to the system’s operation and the process sentinels have been unable to automatically restart it,
|
•
|
2 (Severe), if the specified ProcessName is not critical to the system’s operation but the process sentinels have been unable to automatically restart it,
|
1.
|
Check to see if the specified ProcessInstance of ProcessName is running (and that there is only one copy of it). If it has been marked as suspended, manually restart it and check that the error does not happen again.
|
“Administering iProcess Engine Server Processes”, in the TIBCO iProcess Engine: Administrator's Guide, for more information about how to monitor and restart processes.
2.
|
If the failed ProcessName is the SPO server ( SPO), change the value of the POOLCONNTIMEOUT parameter, in the DBPOOL section of the file, from 600 to 86400.
|
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
A SWDIR\util\swsvrmgr START command has attempted to start the specified
ProcessInstance of
ProcessName, but has failed because that instance is already running.
“Administering iProcess Engine Server Processes”, in the TIBCO iProcess Engine: Administrator's Guide, for more information about how to monitor and start processes.
In the UNIX /etc/services (or Windows
%systemroot%\system32\drivers\etc\services) file, add entries to assign unique (system-wide) TCP/IP port numbers for the worker and watcher process sentinels.
'EAIType' EAI Run-Time called EAI call-back function '
FuncName' with an invalid '
DataItem' parameter value.
The EAIType EAI server plug-in
FuncName function has returned an unexpected value for the specified
DataItem. The
BG process will roll back the affected transaction and continue processing other transactions.
“IQL_RETRY_COUNT”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
Possible infinite loop in Procedure:<ProcName > Case:
CaseNum... Withdrawing Step <
StepName> exceeded max send/withdraw actions per workflow transaction (process attribute BG_MAX_ACTIONS_PER_TRANS =
Value).
Investigate the ProcName procedure to see if there is a loop in the procedure that is causing too many steps to be sent.
“BG_MAX_ACTIONS_PER_TRAN”, in the TIBCO iProcess Engine: Administrator's Guide, for a detailed description of this process attribute.
•
|
subscription, a user tried to run the specified program when they do not have the necessary privileges in Microsoft Windows to subscribe to events that iProcess requires.
|
•
|
publish, an error occurred publishing the event.
|
The BG process cannot read the definition of the
StepName dynamic sub-procedure call step in the
ProcName procedure.
2.
|
Send the .xfr file to TIBCO Support for further analysis and investigation.
|
“Export a Procedure”, in the TIBCO iProcess swutil and swbatch Reference Guide, for more information about how to export a procedure definition.
Invalid sub-procedure 'CaseNum, Proc:
ProcName, Step:
StepName' specified in sub-proc name array field '
SubProcName' ().
SWDIR\logs\sw_error or
SWDIR\logs\sw_warn
If the specified ProcName is incorrect, correct the application so that the dynamic sub-procedure call step calls the correct
ProcName.
Worker(PortNumber) and watcher(
PortNumber) port numbers must be unique in /etc/services.
1.
|
In the UNIX /etc/services (or Windows %systemroot%\system32\drivers\etc\services) file, make sure that the TCP/IP port numbers assigned to the nodename_watcher and nodename_worker processes are unique (system-wide).
|
SWDIR\logs\sw_error or
SWDIR\logs\sw_warn
An attempt by user UserName to lock the specified file timed out, where
FileName is one of the following:
•
|
SWDIR\util\swldap (which holds the current connection information, search parameters, attribute mappings and X500_DIT flag setting used by the SWDIR\util\ldapconf.exe utility)
|
DD/
MM/
YYYY HH:MM (
ServerFil-<
UserName>)Caching of NT permissions for process '
<ProcessName>' succeeded after
Num seconds and
Num retries
The ProcessName process encountered difficulties loading the file permissions definitions on Microsoft Windows, but did succeed in doing so after
Num retries.
The specified StepName is a graft step or dynamic sub-procedure call step, and has called the
SubProcName sub-procedure. However,
StepName and
SubProcName are associated with different sub‑procedure parameter templates, and so cannot map parameters between each other.
The specified StepName is a graft step or dynamic sub-procedure call step, and has called the
SubProcName sub-procedure. However,
StepName and
SubProcName are associated with different versions of the same sub‑procedure parameter template, and so cannot map parameters between each other.
Make sure that both StepName and
SubProcName use the same version of the same sub‑procedure parameter template.
Error(Num) finding main case number for case
CaseNum of procedure
ProcName
An error Num has occurred while attempting to find the top level parent case for a sub-procedure call tree, where
Num is one of the following:
•
|
-1, if the parent case of a sub-procedure cannot be found.
|
•
|
-4, if a sub-case does not contain a SW_PARENTREF field, or if the procedure named in the field does not exist.
|
The specified StepName is a graft step or dynamic sub-procedure call step, and has called the
SubProcName sub-procedure. However,
StepName and
SubProcName are associated with different versions of the same sub‑procedure parameter template, and so cannot map parameters between each other.
Make sure that both StepName and
SubProcName use the same version of the same sub‑procedure parameter template.
|
On UNIX rpcinfo is a system command. On Windows it can be found in SWDIR \rpc.
|
|
Use rpcinfo -t to check if a process is listening on an RPC port. If there is no response, you can use rpcinfo -d to delete the port.
|
A SWDIR\bin\swutil QINFO command has been used to import updated CDQP configuration data to the iProcess Engine, but an error has occurred while attempting to delete the existing CDQP definitions.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
A SWDIR\bin\swutil QINFO command has been used to import updated CDQP configuration data to the iProcess Engine, but an error has occurred while attempting to add a new CDQP definition.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
A SWDIR\bin\swutil QINFO command has been used to import updated CDQP configuration data to the iProcess Engine, but an error has occurred while attempting to initialize access to, or load up the existing CDQP configuration.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
A SWDIR\bin\swutil QINFO command has been used to import updated CDQP configuration data to the iProcess Engine, but an error has occurred while attempting to add a new CDQP configuration setting.
1.
|
Enable debugging on the staffifc.exe (on Windows) or Pstaffifc (on UNIX) process, using the following debug string:
|
A SWDIR\bin\swutil QINFO command has been used to import new or updated CDQP configuration data to the iProcess Engine. However, the command could not open the specified
FileName, which is either:
•
|
the SWDIR\logs\qinfoimp.log log file, in which case no log information will be available for the command.
|
“Set a Process Attribute”, in the TIBCO iProcess Engine: Administrator's Guide, for more information about the
SWDIR\util\swadm command.
2.
|
Use the SWDIR\util\swadm set_attribute command to reset WQS_WIS_USER_COUNT to a value that is less than or equal to your calculated maximum value.
|
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
2.
|
Use the SWDIR\util\swadm set_attribute command to reset WQS_WIS_USER_COUNT to a value that is less than or equal to your calculated maximum value.
|
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
SW_WISINST=WISInstance for queue:
QueueName is too big (max=
MaxWISInstance) - ignored
The specified WISInstance value for queue
QueueName is greater than the highest value WIS instance
MaxWISInstance that is currently defined. SW_WISINST has therefore been ignored, and
QueueName is being dynamically allocated to a WIS process.
“Controlling the Assignment of Queues to WIS Processes” in the TIBCO iProcess Engine: Administrator's Guide, for information about different methods of assigning queues to WIS processes (including how to specifically assign queues using the SW_WISINST queue attribute).
SW_WISINST=WISInstance for queue:
QueueName is assigned to a disabled WIS - ignored
“Controlling the Assignment of Queues to WIS Processes” in the TIBCO iProcess Engine: Administrator's Guide, for information about different methods of assigning queues to WIS processes (including how to specifically assign queues using the SW_WISINST queue attribute).
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
Other Wxxx: messages may provide further information about the cause of the problem.
“Administering iProcess Engine Server Processes”, in the TIBCO iProcess Engine: Administrator's Guide, for information about how to restart the WQS process.
The WQS process has failed to start because of a shared memory conflict. This can happen if, for example, the iProcess Engine is restarted and another application allocates to itself the shared memory key that iProcess expects to use when it restarts.
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
QueueName:SW_WISINST = '
WISInstance' - Value is invalid
“Controlling the Assignment of Queues to WIS Processes” in the TIBCO iProcess Engine: Administrator's Guide, for information about different methods of assigning queues to WIS processes (including how to specifically assign queues using the SW_WISINST queue attribute).
The WQS process failed to register its address with the RPC listener process (
RPC_TCP_LI or
RPC_UDP_LI). Other iProcess processes therefore cannot communicate with the
WQS process and hence cannot access work queues.
•
|
A process was using the RPC port that the WQS process is trying to use. That process has died or been killed, but the RPC port has not been released. The port must therefore be deleted before it can be registered by the WQS process.
|
|
On UNIX rpcinfo is a system command. On Windows it can be found in SWDIR \rpc. Use rpcinfo -t to check if a process is listening on an RPC port. If there is no response, you can use rpcinfo -d to delete the port.
|
“Administering iProcess Engine Server Processes”, in the TIBCO iProcess Engine: Administrator's Guide, for information about how to restart the RPC listener processes.
(Value):SW_WISINST value (
Value) doesn't match already allocated WIS (
WISInstance)
This message is generated by the WQS process when there is a mismatch between the
WISIntance that is currently handling a queue and the
Value of the SW_WISINST attribute. The SW_WISNST attribute is used to specify a
WISinstance that a work queue is to be handled by. On a MOVESYSINFO the value of SW_WISINST is checked for all queues. For existing queues that are already being handled by a
WIS process, any mismatch between the value of the SW_WISINST attribute and the
WIS process handling it, is logged.
“Controlling the Assignment of Queues to WIS Processes” in the TIBCO iProcess Engine: Administrator's Guide, for information about different methods of assigning queues to WIS processes.
•
|
ReturnCode is an internal return code from the software.
|
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java . jar files you should specify.
|
−
|
01 = Failed to initialize sender. This means that the IAPJMS process failed to initialize.
|
−
|
02 = Mismatched message. This means that your JMS delivery method is synchronous and you have received a receipt message for the wrong message.
|
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java . jar files you should specify.
|
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java . jar files you should specify.
|
This error is generated when the swutil EXPMONITOR command is run and if there is an error with the XML. The error means that the XML cannot be validated where:
•
|
Reason is the error message that describes why the XML is not valid.
|
•
|
FileName is the full pathname of the file that contains the error.
|
See "Exporting Activity Monitoring Configuration" in the TIBCO iProcess swutil and swbatch: Reference Guide for more information about the
swutil EXPMONITOR command.
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
•
|
Reason is the error message that describes why the XML is not caused an exception.
|
•
|
FileName is the full pathname of the file that contains the error.
|
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
The queue (QueueName) is currently being cached by the WIS. The
MsgName message will be forwarded later (casenum=
CaseNum reqid=
ReqID).
The WISMBD process has tried to forward the
MsgName message from a
BG process to the
WIS process handling the
QueueName queue. However, the
WIS process was caching the
QueueName queue and so returned an ER_CACHING response to the
WISMBD process, indicating that it could not accept the message.
MsgName is the name of the message that is being forwarded (for example, REQUEST or PURGE).
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
The IAPJMS process failed to find activity monitoring configuration for a case of a procedure where:
•
|
CaseNum is the unique ID of the case.
|
•
|
ReturnCode is an internal return code from the software.
|
7.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java . jar files you should specify.
|
•
|
FileName is the full pathname of the file that contains the error.
|
•
|
ReturnCode is an internal return code from the software.
|
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
•
|
Activity is the name of the activity being monitored.
|
•
|
FieldName is the name of the field being monitored.
|
•
|
ReturnCode is an internal return code from the software.
|
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
•
|
Activity is the name of the activity being monitored.
|
•
|
StepName is the name of the step being monitored.
|
•
|
ReturnCode is an internal return code from the software.
|
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
“Understanding the Activity Monitoring Schemas”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about the activity monitoring schemas.
“Configuring Activity Monitoring”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about configuring activity monitoring.
“Configuring Activity Monitoring”, in the TIBCO iProcess Modeler - Integration Techniques Guide, for information about configuring activity monitoring.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
The IAPJMS process failed to initialize where
ReturnCode is an internal return code from the software.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
The IAPJMS process failed to send a message where
ReturnCode is an internal return code from the software.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
The IAPJMS process failed to start due to an environment issue where
ReturnCode is an internal return code from the software.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
The IAPJMS process failed to start due to a JVM error, where
Code is an internal error code from the software and
Reason is the error message that describes the failure.
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
’EAIType’
EAI Validation-Time Plug-in failed to initialize
2.
|
Use the SWDIR\util\sweaireg utility to check that the plug-in is correctly registered.
|
“Managing EAI Step Server Plug-ins”, in the TIBCO iProcess Engine Administrator's Guide, for information about how to use the
SWDIR\util\sweaireg utility.
If the Message indicates that a server has gone offline, investigate the reason and ensure that it remains available whenever possible.
PROCMGR: No (value) entry has been found in /etc/services file. Using default port (
port). See installation guide.
The procmgr process has not found a port defined for (
value). It is therefor e using a default port.
In the UNIX /etc/services (or Windows
%systemroot%\system32\drivers\etc\services) file, add entries to assign unique (system-wide) TCP/IP port numbers for the affected processes.
The appropriate TIBCO iProcess Engine Installation Guide, for more information about
/etc/services.
The IAPJMS process failed to process a message because
6.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about activity monitoring.
The IAPJMS process failed to send a Work Queue Delta message for the specified case, where
ReasonCode is an internal return code from the software.
5.
|
Check the Java .jar files are specified correctly in the CLASSPATH variable. Look in the IAPJMS.classpath file to see which Java .jar files you should specify.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about publishing Work Queue Deltas via JMS.
The process attributes for the IAPJMS_PORTNO and the
WQDJMS_PORTNO have identical values. If the server continued, this would cause incorrect JMS message routing.
1.
|
Using swadm, change one of the two values to be a unique port number.
|
“Monitoring Activities”, in the TIBCO iProcess Engine: Administrator's Guide, for information about publishing Work Queue Deltas via JMS.
1.
|
Check the ReasonCode for further information.
|
2.
|
Check the SWDIR\logs\sw_error file for any related database errors that may have caused the problem.
|
“Monitoring Activities” in TIBCO iProcess Engine: Administrator's Guide, for information about publishing Work Queue Deltas via JMS.
The WIS process was restarted . However, outstanding subscriptions could not be flagged as invalid on restart. This means that there may be applications expecting Work Queue Deltas that have not been informed that the current subscription is now invalid.
“Monitoring Activities” in TIBCO iProcess Engine Administrator's Guide, for information about publishing Work Queue Deltas via JMS.