Search This Blog

SBL-BPR-00158: Cannot execute workflow process definition '%1'.

Applies to:

Product Release: V7 (Professional)
Version: 7.7.2.2 [18356]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

This document was previously published as Siebel SR 38-3008152701.

Symptoms

SBL-UIF-00401, SBL-SCR-00141, SBL-DAT-00215, SBL-DAT-00712, SBL-SVR-01051, SBL-SCM-00022, SBL-SMI-00033, SBL-NET-01023, SBL-BPR-00125, SBL-BPR-00151

Hi,

We are having problems using drag drop functionality on SWE. When you try to save the attached document systems gives the error "Session Warning: The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again." and logs out the user. We have tried the same functionality with dedicated client and it works ok. We also tried the functionality with DB authentication on SWE and had the same error. We are currently using ADSI authentication for production.

The best I have found from SWE logs is as follows.

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] RPC coming in without a user session

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] Failed to obtain a session ID. NOT OK

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] Set Error Response (Session: Error: 00065535 Message: NOT OK)

Your help is appreciated.

Solution

Message 1

For the benefit of other readers,
Customer reported that drag drop attachment functionality on SWE (Web Client) is not working. Further, the following error message was reported while saving the drag & drop attachments from the windows explorer.

"Session Warning: The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again." and finally logs out the user.

Comments:
Initial investigation steps included the following checks and confirmation from the customer:-
-    This behavior was happening on all attachment screens.
-    Drag & drop attachments from the windows explorer onto the “Siebel Application > Attachments Screen” works fine on a Siebel dedicated client. However, the same functionality is not working for the SWE _Web Client, for all the USERS.
-    Even tried attaching a small size file, this did not work either (just to eliminate the size and type of document they were attaching).

Next, we noticed few error messages like
**********************************
ObjMgrLog    Error    1    0    2006-05-09 10:05:26    (init.cpp (232)) SBL-SCR-00141: Siebel eScript runtimefout in procedure 'GetFieldValue' van BusComp [DHB Financial Accounts]:

Error: SiebelError: Deze bewerking is niet toegestaan wanneer geen records worden weergegeven. Voer eerst een query uit die minstens één record retourneert of voeg een nieuwe record toe.(SBL-DAT-00215)

<CONT'D> Resolution 1 of 2........

Message 2

<CONT'D> Resolution 2 of 2........

ObjMgrLog    Error    1    0    2006-05-09 10:05:26    (init.cpp (232)) SBL-SCR-00141: Siebel eScript runtimefout in procedure 'GetFieldValue' van BusComp [DHB Financial Accounts]:*****
********************************
So just to eliminate the possibility of eScript related issue, customer conducted testing by setting "EnableScripting" parameter false and later also setting Application Object parameter "Application Scripting Enabled" to false. However, still the behavior was the same.

Finally, customer confirmed that the root cause of this reported issue was to do with the underscore "_" character which was used for naming their Servers. Basically, the server network name of their production server was "SIEBEL_PROD". That problem occurs because of that underscore "_" character. So when they used the IP address of the actual server instead of the server name (with underscore ‘_’) everything started working as expected.

Additional reference to similar issues which are posted on Support web:
"Service Request #: 38-2936429161 - problem to upload attachment bigger than 1 MG"
Document Enhancement Request 12-IYK4BR has been logged to make sure that this is documented in Siebel Bookshelf.

"Alert 1067: Siebel Server Failures Due to Hyphen Character in Machine Hostname and in the Siebel Server Name"


Thank You,

Siebel Technical Support


Applies to:

Siebel Call Center - Version: 8.1.1 SIA [21111] to 8.1.1 SIA [21111] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 11-Feb-2010***

Symptoms

When attempting to deploy a Workflow Process as a web service (from Siebel Tools), and generate the wsdl, the following errors were reported :-

SBL-BPR-00158: Cannot execute workflow process definition 'UCM My Customer Profile'.

SBL-EAI-04307: No ports were initialized for Web Service named 'UCM My Customer Profile' having namespace value 'http://siebel.com/CustomUI'.

SBL-EAI-50162: WSDL cannot be generated for web service 'UCM My Customer Profile'. The Workflow Process 'UCM My Customer Profile' may not be activated and caused the WSDL generation to fail.

Cause

During the deployment of the Workflow Process as a web service, SQL was generated to check the deployment definition, for example :-

SELECT
T1.CONFLICT_ID,
...
FROM
SIEBEL.S_WFA_DPLOY_DEF T1
WHERE
(T1.TYPE_CD IN ( 'PROCESS' )) AND
(T1.NAME = 'UCM My Customer Profile' AND T1.DEPLOY_STATUS_CD IN ( 'ACTIVE' ) AND (T1.EFF_START_TS < CONVERT(TIMESTAMP, '07/23/2008 05:55:44') OR T1.EFF_START_TS
IS NULL) AND (T1.EFF_END_TS > CONVERT(TIMESTAMP, '07/23/2008 05:55:44') OR T1.EFF_END_TS IS NULL))
ORDER BY
T1.VERSION DESC

If this did not find a row, the generation of the wsdl would fail.  In the customer environment, the SQL returned 0 rows.

Solution

Remove the Expiration Date/Time from the Workflow Process in the Admin - Business Processes > Workflow Deployment > Active Workflow Processes view.

Re-deploy the Workflow Process as a web service from Siebel Tools.

Change request Bug 10547166 has been logged to request that when a new Workflow Process is revised from a version where the Effective End Date is set, that the end date is nulled.


Applies to:

Error Message Area:Business Processes/Workflow - BPR
Version:Siebel 7.7

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00158: Cannot execute workflow process definition '%1'.

Scope

This document is informational and intended for any user.

SBL-BPR-00158: Cannot execute workflow process definition '%1'.

Explanation

1. The workflow may not exist in the database.

2. The workflow process name may not be spelled correctly.

3. The Process Status of the workflow process is not active in the Siebel client.

4. The workflow's Activation Date is later than the time of execution.

5. The workflow's Expiration Date is earlier than the time of execution.

Corrective Action

1. Go to the Business Process Administration > Workflow Deployment view. Query for the workflow definition in the top list applet using the process name given in the error message. If it does not exist, import the workflow.

2. Check the spelling of your workflow process name where it is invoked. Reinvoke your workflow process task with the correct spelling.

3. In Siebel Tools, check that workflow processes have a status of Completed. In the Siebel client, verify that the same workflow processes have a status of Active.
If you have recently activated a workflow process in the Siebel client, stop the workflow process manager component and restart it. Resubmit your job.

4. Change the workflow's Activation Date to be earlier than the time of execution.

5. Change the workflow's Expiration Date to be later than the time of execution.


Applies to:

Siebel System Software - Version: 7.0.4 [14068] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Area(s):ADM - App. Deployment Manager, Siebel EAI
Release(s):V7 (Enterprise), V7 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:Application Deployment Manager, ADM, UDA, EMT

This document was previously published as Siebel Troubleshooting Steps 41.

Purpose

How To Troubleshoot Application Deployment Manager (ADM) in Siebel 7.7.

Last Review Date

05-Jan-2006

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

The information presented in this document is intended to help troubleshoot ADM related problems and the most commonly reported symptoms and error messages while running Application Deployment Manager (ADM). ADM is a new feature in Siebel version 7.7 that helps Siebel administrators easily and quickly automate the migration of key reference data across different Siebel environments, such as between a development and a test environment. This troubleshooting document is a supplement to Siebel Bookshelf version 7.7 > Going Live with Siebel eBusiness Applications > Migrating Customizations Between Applications.
Note: This document may not be fully applicable for Siebel version 8.x due to the new ADM architecture, for more information please review Siebel Application Deployment Manager Guide from version 8.x.
 
 
Contents

Troubleshooting Overview

Table 1 - Deployment Session Status Field Values
Table 2 - Component Events to Enable for ADM Troubleshooting
Figure 1 - Location of Log Files for ADM errors
Table 3 - ADM Session Log.

Architecture

Figure 2 - Siebel Components and Objects Used in ADM

ADM Workflow Processes for Online Deployments
Figure 3 - Workflow Process and Business Services Used for Online Deployment

ADM Business Services for File Deployments
Figure 4 - Business Services Used for File Deployment

Common ADM Error Messages

Table 4 - Common ADM Error Messages and Symptoms
Figure 5 - Hierarchical LOV Deployment with LOVs of the Same LOV Type
Figure 6 - Hierarchical LOV Deployment with LOVs of Different LOV Type
 
 

Troubleshooting Overview

 
Because ADM is designed with standard Siebel Business application components and objects, many tools already exist for troubleshooting the individual Siebel components. The challenge is to understand how the components communicate with each other and the sequence of events. An understanding of the ADM architecture and workflow processes is critical to successful isolating and resolving problems.
 
The general steps for troubleshooting are:
 
  1. Navigate to Site Map > Application Deployment Manager > Deployment Session View View and locate your ADM session’s status. The status will let you know if there is an error. See Table 1 for an explanation of the session statuses and first steps.
 
  1. Check the source and target systems for log files or error messages. The locations where logs can be found are shown in Figure 1. Log file locations for the Siebel server and a dedicated client are shown. If you are performing an online deployment OR a file deployment connected to a thin client, the logs you want to examine will be on the Siebel server. If you are performing a file deployment on the dedicated client, the logs you want to examine will be on the dedicated client.
 
  1. Once you have found the relevant log files, scan the component logs to find the first point of failure. Typical error messages for ADM are listed in this Troubleshooting guide.
 
  1. If the logs do not contain any detail, enable the appropriate component events for each server component. See Table 2 for a list of the component events to enable and which components to enable them on.
 
  1. If you identify the problem to be related to an integration object, business component rules or the EAI Siebel Adapter, then do further testing using export files.
 
Once you have resolved the problem, re-create your ADM session and deploy it again.
 
Table 1 - Deployment Session Status Field Values
 
Status
Description
Diagnostic
New
This is a new deployment session.
Deployment session has not submitted yet.
Submitted
This is a status that you will usually see for HTTP deployments. This means data has been sent successfully sent from the source system to the target system.
On the Source system, you will see the Submitted status until the jobs complete on the Target system.
 
If the status never changes on the source system, check target system for queued or failed server requests (jobs). Typically these requests will be in the WorkFlow Process Manager server component. To find the jobs, navigate to Site Map > Administration - Server Management > Jobs.
 
On the target system, also make sure the Workflow component group is online, and you have synchronized the batch components.
Validation Failed
This status indicates that the source system was unable to validate the environment details (see error SBL-SVC-00232) or log into the target server.
Check the source system log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message.
Deployment Failed
The deployment failed.
Check the source system log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message.
 
If it was an online deployment, also check target system for Workflow or EAI object manager logs for any errors.
Incomplete Deployment
Some items did not deploy successfully. Other items may have been deployed successfully.
Check the source system log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message.
 
If it was an online deployment, also check target system for Workflow or EAI object manager logs for any errors.
Export Completed
This is a status usually for file deployments. It indicates a successful file export.
The ADM data was exported successfully from the source system. Check the specified file directory for the output file.
 
NOTE: this status does not indicate that data was imported into the target system.
Deployment Completed
This status indicates successful data migration from source to target.
The submitted deployment ran successfully on the target system, and an acknowledgement was successfully sent back and received.
 
 
Table 2 - Component Events to Enable for ADM Troubleshooting
 
Component Event Name (Alias)
Level
Description
Components*
ADM Event (ADM Event)
4
Captures events related to ADM, such as errors.
EAIObjMgr, WfProcMgr, the AOM
EAI Siebel Adapter (EAISiebAdpt)
4
Captures EAI Siebel Adapter related events, including integration component and integration component fields accessed, and the values for the fields; business components and business component fields accessed and the values for the fields.
WfProcMgr, the AOM
EAI Transport (EAITransport)
4
Captures EAI Transport related events: including direction (send/receive) and result. For HTTP transport, shows headers and responses. For File Transport, shows the full filename.
EAIObjMgr, WfProcMgr, the AOM
Performance Event (FSMPerformance)
4
Captures events related to the File Systems performance such as time taken to read or write to the file system, and the name of file.
EAIObjMgr, WfProcMgr, the AOM
Event Context (EventContext)
4
Captures applet and method executed, view names, and screen names that the user navigates to.
the AOM
SrmBusSvc Condition (SRMBusSvc)
3
Captures when the Server Requests business service submits a job.
EAIObjMgr, WfProcMgr, the AOM, SRProc, SRBroker
Server Requests Routing Info (SRMRouting)
4
Captures Server Requests routing information, including SRB Session ID and component name.
EAIObjMgr, WfProcMgr, the AOM, SRProc, SRBroker
Object Manager SQL Log (ObjMgrSQLLog)
4
Captures the SQL select, insert, update, and delete statements.
EAIObjMgr, WfProcMgr, the AOM
Session Manager (SessMgr)
3
Captures SISNAPI events related to the Siebel session manager.
WfProcMgr, the AOM
Object Manager Business Service Operation and SetErrorMsg Log (ObjMgrBusServiceLog)
4
Captures Business Service-related events such as when business services are created, deleted, and the methods invoked.
 
EAIObjMgr, WfProcMgr, the AOM
Object Manager Business Component Operation and SetErrorMsg Log (ObjMgrBusCompLog)
4
Captures Business Component-related events: create and delete.
EAIObjMgr, WfProcMgr, the AOM
Workflow Engine Invoked (EngInv)
4
Captures when the workflow process engine is invoked.
EAIObjMgr, WfProcMgr
Workflow Process Execution (PrcExec)
4
Captures workflow process related events, and shows process properties values.
EAIObjMgr, WfProcMgr
Workflow Step Execution (StpExec)
4
Captures the process step events including business services invoked and inputs and outputs of the business services, conditions evaluated, and outcome of the step.
EAIObjMgr, WfProcMgr
XML Conversion (XMLConversion)
4
Captures the conversion of XML documents to property sets steps and vice versa, shows encoding used in the document.
EAIObjMgr, WfProcMgr
 
* AOM refers to your application object manager. If you are connected through the Siebel Web Client, you are using an application object manager, such as CallCenter (SSCObjMgr_enu).
 
You can enable more events than those listed in Table 2. The events listed in Table 2 are intended as a starting point for troubleshooting generic ADM problems. For more information about the component event infrastructure, refer to Siebel Bookshelf version 7.7 > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging.
 
Figure 1 - Location of Log Files for ADM errors
 
 
 
On the source system, the ADM log file in the $SIEB_ROOT/temp directory often contains more information than you will see on the screen. The ADM Session will show a hyperlink to the log file. Even if you do not see a file listed in the ADM Session, check the Siebel server temp directory for a file.

A sample log where a deployment failed and the reason it failed is shown below in Table 3. The filename will be the name of the deployment session with a .log suffix.
 
Table 3 - ADM Session Log. Filename Is 42-4P84F.log
 
Line #
Text
1
[Deployment Session Header]
2
ADM Deployment Session: 42-4P84F
3
ADM Deployment Project: testtest
4
Start Time: 08/01/2004 17:00:00
5
Target Web Address: http://myserver/eai_enu
6
Target User Name: SADMIN
7
 
8
[Transaction: ProdFeature]
9
Status: Data Preparation Completed
10
Session Items: UDA Admin Product Line, UDA Product Feature
11
End Time: 08/01/2004 17:00:07
12
 
13
[Transaction: ProdFeature]
14
Status: Import Failed
15
End Time: 08/01/2004 17:00:17
16
EAI Logs:
17
No inserts are allowed in Integration Component 'Admin Product Line_Internal Product'.
(SBL-EAI-04184)
 
In the sample ADM Session log, you can see the name of the ADM project testtest in line 3, as well as the target server name myserver in line 5. You can also quickly see that the deployment data type, ProdFeature in line 8 and line 13, and the final status Import Failed in line 14.  The Status Data Preparation Completed on line 9 means that the source system was able to successfully query and get information from the Source system. But then the import into the Target system failed as shown by the status in Line 14. The failure error message is in line 17.
 
At this point, you should check the Target system for WfProcMgr logs (workflow process manager tasks) where the EAI Siebel Adapter is used to update or insert the data. In this case, the reason is because the standard Admin Product Line Internal Production integration component does not allow inserts. In order to successfully deploy the Product Feature data, the products associated with the Product Lines must already exist on the target system.
 

Architecture

 
ADM is built on the Server Requests, Workflow Process and Enterprise Application Integration (EAI) infrastructure.
 
Figure 2 presents a logical overview of the different components involved. There are two environments shown, a source and target. Each environment is a distinct Siebel enterprise with its own Siebel database and server(s). The Siebel database for each environment contains tables that store data that is to be migrated (i.e. LOV data), ADM workflow process definitions, job details for the server requests, and entries in the EAI Queue. Each Siebel enterprise has an SRF which contains the ADM integration objects. Each enterprise will also have access to its own Siebel FileSystem, which will temporarily store files used in the ADM session.
 
On the source system, you need to have the Workflow and System Management component groups online. On the target system, you need to have the EAI, Workflow and System component groups online; you also need to setup the Siebel Web Server so that the target system can receive the HTTP requests. (If you are deploying using Export file, you would not use the Siebel server components or the Web Server, but all the other components below the dashed line are still required.)
 
Figure 2 - Siebel Components and Objects Used in ADM
 
 
 
 
 

ADM Workflow Processes for Online Deployments

 
The workflow processes used by ADM and standard integration objects’ names start with the letters UDA (for Universal Deployment Agent). The primary business service used in the UDA workflow process is the UDA Service. The sequence of events, workflow processes and business services for an online ADM session are outlined in Figure 3. Because of differences in the flow and architecture for a deployment using export files, that process is outlined separately in Figure 4.
 
Figure 3 - Workflow Process and Business Services Used for Online Deployment
 
 
 
Figure 3 also illustrates the flow of data in an online deployment. When you click Deploy in the ADM views, the button invokes the UDA Deployment workflow process. The UDA Deployment workflow process runs in the current application object manager you are using. So for example, if you are logged into the Financial Services object manager, it will run in the FinsObjMgr_enu component. The UDA Deployment workflow process then runs a subworkflow process, UDA Environment Verification, to verify that the Target environment is up and its schema versions match those in the Source environment. The UDA Environment Verification workflow processes use HTTP at this point to communicate with the Target system.
 
On the target system, the EAI Object Manager receives the request from the UDA Environment Verification workflow process through the UDA Deploy named subsystem. The UDA Deploy named subsystem dispatches the request to the UDA Service business service and the UDA Service sends a response back to the source system.
 
After verification is complete, on the source system, the UDA Deployment workflow process uses the Server Requests business service to submit an asynchronous workflow process job. The workflow process task invokes the UDA Data Query workflow process. The UDA Data Query workflow process uses the EAI Siebel Adapter and method query to extract data that to be deployed (into a Siebel integration object and then into XML). Once the ADM data is obtained, it is sent from the source to the target system using the UDA HTTP Transport workflow process as a sub workflow process.
 
On the target system, the EAI Object Manager receives the ADM data from the UDA HTTP Transport workflow process through the UDA Deploy named subsystem. This time UDA Deploy named subsystem uses the Server Requests business service to submit an asynchronous workflow process job. A new workflow process manager task runs the UDA Target Workflow workflow process. In the UDA Target Workflow, the EAI Siebel Adapter, with method Upsert (in Siebel version 7.7), is used for the logic of determining if the data will be updated or inserted. Upon successful processing of the ADM Data, the workflow process manager sends a confirmation back to the source using the SISNAPI protocol.
 
On the source system, the confirmation request is received by the same application object manager that originally initiated the deployment. The UDA Acknowledgement workflow process runs to update the ADM Session data with the results from the target system.
 

ADM Business Services for File Deployments

 
Figure 4 illustrates the flow of data in a deployment using export files. Unlike batch or online deployments, when you use export files, you do not need to have a running Siebel server. There are also no explicit workflow processes invoked. The architectural simplification makes the file deployment option ideal for testing ADM.
 
If you encounter an error performing an online deployment, switching your test case to a file deployment is a good way to isolate the root cause of the error. When you test with the file deployment option on a dedicated client, you can enable client-side tracing so you can see more details on what may be happening with the underlying Siebel application layers. You can focus on errors specific to the integration objects, content objects or EAI Siebel Adapter, and not be concerned with Siebel server infrastructure. For steps on how to perform client logging, refer to How Should Client Side Logging Be Set? (Doc ID 475587.1).
 
 
Figure 4 - Business Services Used for File Deployment
 
 
 
In Figure 4, the application object manager represents the object manager engine in a dedicated client or in a zero foot print client. In a file deployment, you need to create an XML file that represents the ADM data first in the source system. The file needs to be saved in a location that is accessible by both the source and the target environments.
 
On the target system, you import the file created from the source system. When the XML file is deployed on the target system, a copy of the XML file is saved in the EAI Queue. When the update or insert is complete on the target system, a broadcast message is displayed on the target system to the position of the user who initiated the import
 
On the source system, you will still need to create an ADM project and a new ADM Session. However, when you click the Deploy button in a File deployment scenario, no workflow processes will be dispatched. Instead, the UDA Service will provide the logic to create an XML file containing the ADM deployment data.  On the target system, you can directly import the XML file using the Menu -> Deploy from File option. You do not need to have the EAIObjmgr running or any deployment session or project created on the target system.
 
The drawback to using file deployment is that you will not have a record showing if an import succeeded or failed on the source or target system. Since there is no HTTP or SISNAPI established between the target and source environment in a file deployment, there is no ADM view that shows if the deployment data was successfully imported. If there is a failure on the target system to import the data, you will see the message in the client GUI. You can also check the EAI Queue (under Application Administration – Integration) for a status and a copy of the XML that you attempted to import.
 
The file deployment mode is also supported via the server manager (srvrmgr) command line which optimizes the import operation. With one srvrmgr command, you can import multiple files.
 

Common ADM Error Messages

 
Below is a list of common ADM error messages. Make sure to search SupportWeb with the error message and check for the latest ADM alerts as well.
 
These error messages may appear on the GUI or in a log file. For a listing of places to check for log files that would contain ADM related errors, see Figure 1.
 
Table 4 - Common ADM Error Messages and Symptoms
 
An error occurred exporting to file. Please make sure the path <path value> points to a valid directory which has enough space and is writable by the application process owner (SBL-SVC-00255)
SBL-SRQ-00103: Unable to find definition of component WfProcMgr
SBL-SVC-00232: The schema and SRF of the source environment and the target environment must be of the same version.
Step '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186)
EAI Queue Entry Always Created During File Import
Unable To Deploy: Target Server Path is a required field. Please enter a value for the field. (SBL-DAT-00498)
Deployment Failed: “[Microsoft][ODBC Driver Manager] Invalid cursor state”
Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System.
SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement'
ObjMgrSRFLog Warning...(objdef.cpp (2192)) SBL-DAT-00144: Could not find 'Import Object' named 'EMT Session'
Multiple matches found for instance of integration component '%1' using search specification '%2' in the business component '%3', based on user key '%4'
LAST_UPD_BY Field Does Not Contain Correct Values
Task Status Completed but Data Not Imported
"There were more rows than could be returned. Please refine your query to bring back fewer rows (SBL-DAT-00500) (SBL-EAI-04376)
View: UDA Project Administration View does not contain applet: EMT Project Form Applet. (SBL-SVC-00254)
LOV Parent-Child Relationship Is Not Established
 
 

An error occurred exporting to file. Please make sure the path <path value> points to a valid directory which has enough space and is writable by the application process owner (SBL-SVC-00255)

 
Symptom or Error Message
 
You received the following error when exporting to a file:
 
An error occurred exporting to file. Please make sure the path <path value> points to a valid directory which has enough space and is writable by the application process owner (SBL-SVC-00255)
 
Cause
 
The export path specified is not a valid directory name or is inaccessible from the machine where the ADM process is running.
 
Diagnostic Steps
 
Verify that the file path given is valid and can be accessed from the machine where the ADM process is running.
 
Solution
 
The export path should be a shared network resource. If deploying to a file using a dedicated client, specify an export path is that is relative to the dedicated client. For example, if you are on your local Windows machine, you can specify d:\temp as your export path.
 
If deploying to a file using a zero footprint client, specify an export path is relative to the Siebel server where the object manager is running.  For example, if you are using the thin client, and connecting to a Siebel server running on Solaris, you need to specify a network path that is valid for the Solaris server, i.e. /tmp.
 
 

SBL-SRQ-00103: Unable to find definition of component WfProcMgr

 
Symptom or Error Message
 
After clicking Deploy and entering the correct password, the deployment session fails. The following error messages shows up in the Siebel component log:
 
SBL-SRQ-00103: Unable to find definition of component WfProcMgr
 
In the ADM log or on the Siebel client, you may see this error message:
 
Error encountered at workflow "<?>", step "<?>"
- No change/update is in effect.(SBL-EAI-04442)
 
Cause
 
The Workflow Process Manager Server component definition has not been synchronized from the Server Manager screen. When you synchronize components, the Siebel server updates information about your Enterprise in the S_SRM_ACTION table.
 
Diagnostic Steps
 
  1. Navigate to Sitemap > Administration - Server Configuration > Enterprises > Synchronize.
 
  1. The middle applet (Batch Component Admin) should contain a list of server components. If the list is empty, synchronization has not been done.
 
Solution
 
In the source and target environments, start a Siebel Client. Then navigate to Sitemap > Administration - Server Configuration > Enterprises > Synchronize, click Synchronize.
 
 

SBL-SVC-00232: The schema and SRF of the source environment and the target environment must be of the same version.

 
Symptom or Error Message
 
The deployment session fails with this error:
 
SBL-SVC-00232: The schema and SRF of the source environment and the target environment must be of the same version.
 
Cause
 
In Siebel versions 7.7 and 7.7.1, ADM checks the Siebel SRF and schema versions of the target environment against that of the source environment. If either the SRF or the custom schema versions are different, you will get the error.
 
Change Request 12-MAR8FT has been logged to address this product defect. It has been fixed in Siebel Fix Pack 7.7.2.1. 
 
The new behavior is that SRF version will not be validated. The custom schema version checking will be skipped but the major, minor and vertical schema versions are still checked. However, if the SRFs between the target and source environments do not have matching integration objects, the deployment would still fail.
 
Solution
 
  1. Contact Siebel Technical Support to request the latest available 7.7.2.x Fix Pack. Install the fix pack on your target and source Siebel application environments.
 
  1. If you are not able to install the fix pack, a manual workaround is available. It is to deploy using Export Files so you can modify the XML attributes. Here is how to modify the XML:
 
    1. Determine the schema and srf versions for the target system.
 
    1. Deploy any file on the target System (you will not need to import this project into any system.) Then open up the file you deployed in notepad and copy out the lines containing the SchemaVersion and SRFVersion. It will look something like this (with different values in double quotes):
 
SchemaVersion="41.57.0.69" SRFVersion="36|1074164158|1087259477"
 
    1. Modify the Export file.
 
    1. Open up the XML file created from your source system. Then cut and paste the Schema and SRF string from the target system’s XML into your source system’s XML file. When you save the source system XML file, make sure you retain the original encoding of the XML document (utf-8).
 
NOTE: Other modifications to the XML content are not recommended unless otherwise directed by Siebel Technical Support.
 
If you require a workaround for online deployments, please contact Siebel Technical Support for assistance with modifying the UDA Deployment workflow process.
 
 

Step '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186)

 
Symptom or Error Message
 
When deploying a session using the command line interface, the status of the deployment session fails with the following errors:
 
We detected an Error which may have occurred for one or more of the following reasons:
Step '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186)
 
You may see this error in the object manager log:
 
SBL-GEN-00000: Unable to load message 0xffff
 
Cause
 
Command line deployment using on-line mode is not supported
 
Solution
 
In order to deploy in command line mode, the session must be configured to export to a file by checking the Export to File flag. Batch deployment using on-line mode is not supported.
 
 

EAI Queue Entry Always Created During File Import

 
Symptom or Error Message
 
An EAI queue entry is always created when performing a file import regardless of the Business Component User Property value.
 
Cause
 
This is an expected behavior for the standard ADM configuration.
 
Solution
 
To stop entry generation in the EAI Queue, set the User Property Use EAI Queue to Never on the EMT Session business component.
 
For more information about the EAI Queue, refer to Siebel Bookshelf version 7.7 > Siebel Connector for SAP R/3.
 
 

Unable To Deploy: Target Server Path is a required field. Please enter a value for the field. (SBL-DAT-00498)

 
Symptom or Error Message
 
You are not able to deploy to a file. When you click Deploy, you may see this message:
 
Target Server Path is a required field. Please enter a value for the field. (SBL-DAT-00498)
 
Cause
 
The Export to File box must be checked to deploy to a file.
 
Solution
 
Check the Export to File box in the ADM Session.
 
If the box is grayed out, you need to recreate a new ADM Project and check the Export to File box for the new ADM Project. Then enable the new ADM Project and redeploy.
 
 

Deployment Failed: “[Microsoft][ODBC Driver Manager] Invalid cursor state”

 
Symptom or Error Message
 
After clicking Deploy, the status changes to Deployment Failed. The following error message shows up in the SRProc.log file:
 
"[Microsoft][ODBC Driver Manager] Invalid cursor state"
 
Cause
 
  1. The database is running out of the cursors.
 
  1. There are too many connected users.
 
Diagnostic Steps
 
Check the number of the cursors in the database and make sure it complies with Siebel system requirements.
 
Solution
 
If the number of cursors is too low, increase the cursor number and run the deployment again.
 
 

Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System.

 
Symptom or Error Message
 
When submitting an online deployment, you receive the following error:
 
Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System. Please verify the connection information. (SBL-SVC-00252)
 
Cause
 
The HTTP session from the source to the target could not be started.
 
Diagnostic Steps
 
  1. Check that you have supplied a valid Siebel URL for the target system.
 
  1. Check that you have typed in a valid username and password for the target system
 
  1. Check that the EAI object manager on the target system is online. You can verify that the EAI object manager on the target system is online by using the statspage with this URL: http://<webserver>:<port>/eai_enu/_stats.swe (substitute <webserver> and <port> with values for your environment). If the stats page comes up, you have verified that you are able to connect to the EAI Object manager and it is online.
 
  1. Check that the source and target environments have network connectivity. For example, make sure you can ping the target webserver from the source Siebel server physical machine.
 
Solution
 
  1. Fix any invalid arguments supplied and recreate the deployment session.
 
  1. Make sure that the EAIObjMgr is online on the target system.
 
  1. If there are network problems, check with your network administrator to resolve the problems (e.g., name resolution problems, firewalls in place).
 
 

SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement'

 
Symptom or Error Message
 
When executing a batch deployment, you get the error:
 
SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement'
 
Cause
 
The workflow process name is not spelled correctly or the workflow process is not activated in the Siebel Client.
 
Diagnostic Steps
 
  1. Check the spelling of your workflow process. In the symptom above, Deployement is misspelled (an extra 'e' between the 'y' and the 'm').
 
  1. In Siebel Tools, check that workflow processes have a status of Completed. In the Siebel client, verify the same workflow processes have a status of Active.
 
Solution
 
  1. Resubmit your workflow process task with the correct spelling.
 
  1. If you have enabled a workflow process in the Siebel client, stop the workflow process manager component and restart it. Resubmit your job.
 
 

ObjMgrSRFLog Warning...(objdef.cpp (2192)) SBL-DAT-00144: Could not find 'Import Object' named 'EMT Session'

 
Symptom or Error Message
 
When you enable component event logging in the Siebel server components, you see messages like these:
 
ObjMgrSRFLog      Warning    ...    (objdef.cpp (2192)) SBL-DAT-00144: Could not find 'Import Object' named 'EMT Session'. This object is inactive or nonexistent.
 
Cause
 
These are warning messages, and they are benign. You can ignore those messages. If the value after the component event is not Warning, then you should investigate if the error is fatal.
 
 

Multiple matches found for instance of integration component '%1' using search specification '%2' in the business component '%3', based on user key '%4'

 
Symptom or Error Message
 
When deploying all the out of the box LOVs, you get this error:
 
Multiple matches found for instance of integration component '%1' using search specification '%2' in the business component '%3', based on user key '%4'.
 
Cause
 
The Siebel seed data has duplicate values for LOVs.
 
Change Request 12-MPWXD3  has been logged to address this product defect.
 
Diagnostic Steps
 
Log into the database and run the following SQL statement to see if you have duplicate seed data:
 
select TYPE, NAME from S_LST_OF_VAL
where type = ‘LOV_TYPE’
group by TYPE, NAME
having count(*) > 1
 
Solution
 
Log on a Siebel Client, and go to the LOV Views. Query for the LOV Types you found running the SQL Query in the diagnostic steps. For each duplicate pair, change the display value for one of the records to make the record unique.
 
 

LAST_UPD_BY Field Does Not Contain Correct Values

 
Symptom or Error Message
 
After migrating data from the source application to the target application with different users, records are always inserted as SADMIN user ID. The LAST_UPD_BY field does not contain correct values.
 
Cause
 
Data is inserted into the target application using the Server Request Broker (SRB) and Server Request Processor components (SRP). The user stamp on the inserted records will be the user name set for the SRB/SRP components (typically SADMIN), not the user name supplied from the source application.
 
Solution
 
Create a new user ID with the same privilege as SADMIN and update the SRB/SRP components to use that new user ID.
 
 

"There were more rows than could be returned. Please refine your query to bring back fewer rows (SBL-DAT-00500) (SBL-EAI-04376)

 
Symptom or Error Message
 
When exporting data to a file, you receive the following error message:
 
We detected an Error which may have occurred for one or more of the following reasons:
Method 'NextRecord' of business component 'Feature Access' (integration component 'Feature Access') returned the following error: "There were more rows than could be returned. Please refine your query to bring back fewer rows (SBL-DAT-00500) (SBL-EAI-04376)
 
Cause
 
There is a 10K limit on the EAI transport.
 
Solution
 
Specify a search specification such as [Name] not like 'A* to reduce the number of records returned to less than 10,000.
 
If you are not in a production environment and would like to bypass the 10K limit, it is possible to do so. However, please bear in mind that there is a potential for large memory usage of the Siebel server component.
 
To bypass the default 10000K limit, set the value for the parameter "DSMaxFetchArraySize" under the "InfraDatasources" named sub-system to the number of records you expect to export. Note that this param is for a given data source and would impact all components that share the same data source so we only advise you set this value immediately prior to your export and reset it to the default after your export.
 
On a dedicated client, you can set the value by setting param MaxFetchArraySize under the individual data source section on the client’s cfg file.
 
 

Task Status Completed but Data Not Imported

 
Symptom or Error Message
 
When deploying sessions using the command line interface, the status of the workflow process task is completed. However the data has not been imported to the target environment.
 
Cause
 
  1. The UDA Batch Import and UDA Batch Deployment workflow processes have not been deployed properly.
 
  1. The FileExportPath and FileImportPath process properties are not valid.
 
Diagnostic Steps
 
  1. In Siebel Tools, check that UDA Batch Import and UDA Batch Deployment workflow processes have a status of Completed. In the Siebel client, verify the same workflow processes have a status of Active.
 
  1. Confirm the workflow processes have the correct FileExportPath and FileImportPath process property values.
 
Solution
 
  1. Deploy the UDA Batch Import and UDA Batch Deployment workflow processes in Siebel Tools. Activate the workflow processes in the Siebel Client.
 
  1. When exporting the file, verify the FileExportPath process property is set correctly for the workflow process UDA Batch Deployment. When importing the file, verify that the FileImportPath for the UDA Batch Import workflow process has a valid value. The values should be the directories which will contain the exported and imported files respectively. Both values can point to the same location.
 
NOTE: For more information about how to deploy using the command line interface, refer to Siebel Bookshelf version 7.7 > Going Live with Siebel eBusiness Applications > Migrating Customizations Between Applications > Deploying Sessions Using Command-Line Interface.
 
For more information about deploying in batch mode (running the workflow process), refer to Siebel Bookshelf version 7.7 > Going Live with Siebel eBusiness Applications > Migrating Customizations Between Applications > Reviewing the ADM Data Migration.
 
 

View: UDA Project Administration View does not contain applet: EMT Project Form Applet. (SBL-SVC-00254)

 
Symptom or Error Message
 
View: UDA Project Administration View does not contain applet: EMT Project Form Applet. (SBL-SVC-00254)
 
Cause
 
The applet might be missing in View: UDA Project Administration View
 
Diagnostic Steps
 
In Siebel Tools, query for the View UDA Project Administration View.
 
Check for all the View Web Template Item applets. Verify if the EMT Project Form Applet is there.
 
Solution
 
In Siebel Tools navigate to View and query for UDA Project Administration View and then add a View with the following information:
 
Web Template Item
Name = "EMT Project Form Applet" applet
Item Identifier = 3 or next number
Applet Value = "EMT Project Form Applet"
Applet Mode = "Edit"
 
 
LOV Parent-Child Relationship Is Not Established
 
Symptom or Error Message
 
When deploying dependent data types, such as hierarchical LOVs with the LOV-HierParent data type, both records are successfully imported in the target system, but the parent-child relationship is not established. For LOVs, after the first deployment, the child LOV does not show the parent LOV. When you redeploy the project a second time, then the parent-child relationship is established.
 
Cause
 
For dependent data types, ADM will deploy the child data type before the parent data type. When ADM deploys the child data, the parent does not yet exist so the EAI Siebel Adapter cannot set the relationship on the child to point to the parent. Hence, after the first deployment, while both data types are successfully deployed, the relationship between the two records is not established.
 
Solution
 
This is the intended behavior of ADM that all hierarchical data must be imported twice. When deploying a child record, ADM will not error out if the parent record does not exist because the picklist validation is disabled.
 
When an LOV record with a reference to a parent Language Independent Code (LIC) value is being inserted, that parent LIC value must already be present in the target system for the reference to be successfully set. However, since the Parent LIC value is in itself another LOV record, the only way to make sure that all the references are successfully established is to import the LOV values using two dependent data types both are LOV data types. Internally this will cause two deployment operations to occur, once per session item. See Figure 5 for a logical description of what happens.
 
Import pass #1 based on the LOV-HierChild session item: all LOVs will be inserted successfully. For the child LOVs that reference a parent LIC, the parent LIC field will be left blank. The UDA List of Values integration component has been configured to ignore errors on self referenced fields which are bounded to a picklist.
 
Import pass #2 based on the LOV-HierParent session item: the same LOVs will be updated. However, now any Parent LIC values referenced in the record being imported is already present in the target DB. So therefore, second import will update the LOV records previously upserted from the first deployment with the correct parent LIC value.
 
In the case where the parent and child LOVs are of different LOV Types, you can deploy the data in one deployment session by using the deployment filter. Since the ADM child data type (LOV-HierChild) is always deployed first, if you set the deployment filter for the child ADM data type to find the record for the parent LOV, the parent LOV can be inserted before the child LOV. Then set the deployment filter for the parent ADM data type (LOV-HierParent) to find the child LOV deployment record. See Figure 6 for the logical description of what happens.
 
NOTE: If you are deploying LOVs where the LOV child and parent are of different LOV types, be sure to review Document 477904.1 for information on how to obtain updated SIFs. Without the updated SIFs compiled into your SRF, you will not be able to deploy LOV data if the LOV Types are different.
 
Figure 5 - Hierarchical LOV Deployment with LOVs of the Same LOV Type
 
 
 
Figure 6 - Hierarchical LOV Deployment with LOVs of Different LOV Type
 
 



Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405] ESN Engy/Oil
Database: Oracle 10.2.0.1
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-3447348216.

Symptoms

SBL-BPR-00158

Hi,

We are work with Siebel Energy version 8.0.We are testing in the standard and we have been a problem, when pressing the button “Verify” in service request form applet on appears the following message of error:

"Cannot execute workflow process definition '0V-17YTZP' (SBL-BPR-00158)

We have consulted supportweb, we have verified that workflow "FS - Verify Entitlement SR" is active in client and status completed in tools.

We attach screenshot with error called error.jpg

Do you could help us?

Thanks and regards

Solution

Message 1

Hello Jorge,

Thank you for using the Siebel SupportWeb.

For the benefit of other readers, an error was being reported when clicking ‘Verify’ from the Service Request form applet :-

Cannot execute workflow process definition '0V-17YTZP' (SBL-BPR-00158)

It was suggested to navigate to the Administration – RunTime Events > Events screen, and query for Object Type=Applet and Object Name=Service Request Detail Applet. Then drill down on the Action Set Name, and check which Workflows are being invoked on this event. A reference was found for a Workflow with ProcessId = '0V-17YTZP'. After deleting this reference, and from the Menu, clicking Reload Runtime Events, the Verify button worked as expected.

Change request 12-1F7X8TN has been logged for the described behavior.


Siebel Technical Support


Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.2 [19219]
Database: Oracle 9.0.1
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP 9000 Series HP-UX

This document was previously published as Siebel SR 38-3028717591.

Symptoms

SBL-BPR-00158

We are migrating from unix to Windows platform and also upgrading Sibel from 7.5 to 7.8.
In 7.8 environment, all server components are up and running except Workflow Monitor component. The component is showing online but it is not processing any triggers. Also We do not see any log files created for this component.
We need to get workflow monitor running in order to test our migration changes in our new windows environment. Please look at this at the earlies.
Thanks

Solution

Message 1

For the benefit of other readers:

Customer has workflow policies which invokes workflow proceses. The Workflow Monitor Agent which invokes the workflow processes was failing. Upon closer investigation, the failure was within the Workflow Process' execution, where the Workflow Process Manager task was failing with the following error message:

GenericLog    GenericError    1    0    2006-05-04 12:51:29    ( (0) err=4300107 sys=32982) SBL-OMS-00107: Object manager error: ([0] Cannot execute workflow process definition 'HRS Reassign Case'.(SBL-BPR-00158) (0x80d6))

Once the Workflow Process Manager task failed with this error, it also returned the error message and error code back to the caller which is Workflow Monitor Agent. Thus, the Workflow Monitor Agent task failed and echoed the same error message.

The next step was inspecting the Workflow Process Manager task log file for the error:

GenericLog    GenericError    1    0    2006-05-04 12:51:29    ( (0) err=4300107 sys=32982) SBL-OMS-00107: Object manager error: ([0] Cannot execute workflow process definition 'HRS Reassign Case'.(SBL-BPR-00158) (0x80d6))

At a high-level, this error message usually indicates that a workflow process being invoked is either not deployed, deployed but not activated, or activated but has an activation date in the future and/or an expiration date in the past, thus making the workflow not active.


[1/6]

Message 2

[2/6]


At a more granular level, the component which invokes a workflow process will also issue certain SQL statements to check for the workflow process with an 'Active' status. If these SQL statements return 0 rows, then the workflow process is not found, and this "Cannot execute workflow process definition" will be returned.

In customer's scenario, their workflow process has been deployed, activated, has no activation nor expiration dates. Thus, the workflow is technically available, but the workflow engine could not retrieve it properly.

Upon inspection of the WfProcMgr log file, the tracing revealed the following sequence of SQL queries being issued:

1. SELECT /*+ ALL_ROWS */
   FROM
       SIEBEL.S_LST_OF_VAL_BU T1,
       SIEBEL.S_LST_OF_VAL T2
   WHERE
      T2.ROW_ID = T1.LST_OF_VAL_ID (+) AND
      (T2.NAME = :1 AND T2.TYPE = :2)
   ORDER BY
      T2.TYPE, T2.ORDER_BY, T2.VAL
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 1: WFA_DPLY_STAT_CD
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 2: LOV_TYPE
ObjMgrSqlLog    Debug    5    0    2006-05-12 10:59:34    User search spec: 'WFA_DPLY_STAT_CD'
AND LOV_TYPE
.....

2. SELECT /*+ ALL_ROWS */
   FROM
       SIEBEL.S_LST_OF_VAL T1
   WHERE
      (T1.LANG_ID = :1 AND T1.TYPE = :2 AND T1.BU_ID IS NULL)
   ORDER BY
      T1.TYPE, T1.ORDER_BY, T1.VAL
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 1: English

......

Message 3

[3/6]


ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 2: WFA_DPLY_STAT_CD
ObjMgrSqlLog    Debug    5    0    2006-05-12 10:59:34    User search spec: English
AND 'WFA_DPLY_STAT_CD'
AND IS NULL
....

3. SELECT *
   FROM
       SIEBEL.S_WFA_DPLOY_DEF T1
   WHERE
      (T1.NAME = :1 AND T1.DEPLOY_STATUS_CD IS NULL AND (T1.EFF_START_TS < TO_DATE(:2,'MM/DD/YYYY HH24:MI:SS') OR T1.EFF_START_TS IS NULL) AND (T1.EFF_END_TS > TO_DATE(:3,'MM/DD/YYYY HH24:MI:SS') OR T1.EFF_END_TS IS NULL))
   ORDER BY
      T1.VERSION DESC
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 1: HRC Create Activity for SR created over Phone
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 2: 05/12/2006 14:59:34
ObjMgrSqlLog    Detail    4    0    2006-05-12 10:59:34    Bind variable 3: 05/12/2006 14:59:34

In the 1st select statement, the Object Manager was querying for all lov values for the lov type WFA_DPLY_STAT_CD, which is for the workflow's status.

In the 2nd select statement, the Object Manager was querying for all the lov values in for the lov type WFA_DPLY_STAT_CD in a certain language. However, note the bind variable 1 uses 'English' as the value, eventhough the column is for S_LST_OF_VAL.LANG_ID column. LANG_ID column should be a 3-character language code. For this query, we should expect the bind variable 1 to be binded to value 'ENU' instead.

......

Message 4

[4/6]


Then, the 3rd query checks for the Active version of the requested workflow process. However, note the 3rd query's where clause says "T1.DEPLOY_STATUS_CD IS NULL". This is not correct. For any activated workflow, it will always have a value being 'Active', 'Outdated', 'Inactive', it will never have NULL as a status. Thus, this where clause having "T1.DEPLOY_STATUS_CD IS NULL" causes the query for the workflow process definition to return 0 rows, and leading up to the "Cannot execute workflow process definition" error message.

The 2nd select statement returns 0 rows when it was querying for LANG_ID = 'English', so no values found for lov type WFA_DPLY_STAT_CD, thus no value passed over to the 3rd select statement for the query on S_WFA_DPLOY_DEF DEPLOY_STATUS_CD column. This is why the 3rd query ended up with where clause DEPLOY_STATUS_CD IS NULL -> this query then returns 0 workflows found.

The source of the problem was in the query against S_LST_OF_VAL for type WFA_DPLY_STAT_CD with LANG_ID = 'English'.

Customer performed the following additional test cases:

a. When customer initiated the workflow using a dedicated client with user login SRIRAJAG, the 2nd query binded LANG_ID = 'ENU', and the workflow was able to execute using this user's login.

.....

Message 5

[5/6]


b. Site Map > Data Administration > Locale > check for one with Locale Code = 'ENU'. Customer has this set to "ENU", which is the correct setting, so this was not the source of the problem.

3. Lastly, we checked the Preferred Language field for each of the user login that was tested, this is the S_CONTACT.PREF_LANG_ID column. This revealed the following information:

SRIRAJAG has PREF_LANG_ID = 'ENU'
HRSIEBELLOGIN and SADMIN have PREF_LANG_ID = 'English'

Customer ran a query against the database and found 118,000+ out of a total of 184,201 records which has PREF_LANG_ID = 'English'.

Thus, the source of the string 'English' was due to the S_CONTACT.PREF_LANG_ID value for certain users in the database. For more information on this "Preferred Language field":

Bookshelf > Global Deployment Guide > Configuring Global Deployments > About Parameters for Language and Locale:

" The setting of the Preferred Language field in the Contacts screen overrides the value of the Language Code parameter for determining the language for multilingual lists of values (MLOVs). This setting is stored in S_CONTACT.PREF_LANG_ID in the Siebel Database. This field does not affect Mobile or Developer Web Client users. "

......

Message 6

[6/6]


To enable the workflow to execute properly, customer has set S_CONTACT.PREF_LANG_ID = 'ENU' for the users which runs the Siebel server components that executes workflow (ie, users HRSIEBELLOGIN and SADMIN). This helped to resolve the "Cannot execute workflow process definition" problem and allowed the workflows to run successfully.

As for why the S_CONTACT.PREF_LANG_ID has 'English' instead of 'ENU', customer did configure the 7.5 Contact Business Component to use the PREF_LANG_ID column to store a language preferemce code which is based on a picklist. This field is then used to determine the language of the survey link that is sent to the users at the resolution of a case. Customer was suggested to review their configurations after the 7.8 upgrade to verify if this configuration for the contact language preferemce code needs to be further corrected or adjusted for the 7.8 upgraded environment.

Thank you,

Siebel Support

Search keywords: workflow, engine, monitor, agent, process, fail, error, not found, S_CONTACT.PREF_LANG_ID, preference, language, code, S_LST_OF_VAL, English, ENU, query, LOV, type, Cannot execute workflow process definition, WFA_DPLY_STAT_CD, S_WFA_DPLOY_DEF, DEPLOY_STATUS_CD

.


Applies to:

Product Release: V7 (Enterprise)
Version: 7.7 [AN 296]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-1531130397.

Symptoms

SBL-BPR-00158

Hi:

We have written Workflow (WF) Policies, Conditions to detect changes in certain objects/tables. Upon WF Policy violation, the WF Policy Action is supposed to invoke a WF Process w/arguments. The WF Process then sends out the IO XML to an External application.

The problem is that the WF Policy Action is not able to invoke our WF Process. We have verified the configuration steps and everything seems to be fine. In fact the same configuration works fine on Siebel 7.5

Attached is our Workflow Monitor Agent log

Please help resolve this issue ASAP. Thank you!

Vitria
408-212-2643

Solution

Message 1

For the benefit of other readers:

The following items were checked:

1. Customer ran the workflow process through simulator, it works fine.
2. Workflow Policy triggers are fine because the record can be seen in the S_ESCL_REQ table.
3. The problem is, the Workflow Process fails to run it correctly on the server.

Customer has a custom workflow program called "Vitria Run Integration Process" that uses "BusIntMgr" component to run the workflow process.

The Business Integration Manager server components are online and fine.

When checking the Siebel Client > Siebel Workflow Deploymet view, the workflow process does show up:

process name = "Vitria Request For Action"
status = completed
version # 0

When checking the Active Workflow Process view, the workflow process does show up as active as well.

When setting additional tracing on the BusIntMgr component and reproduced the error for a BusIntMgr_xxxx.log file, the following was the last query issued by BusIntMgr before the error:

SELECT
      T2.CONFLICT_ID,
      T2.LAST_UPD,
      T2.CREATED,
      T2.LAST_UPD_BY,
      T2.CREATED_BY,
      T2.MODIFICATION_NUM,
      T2.ROW_ID,
      T2.EFF_START_TS,
      T2.EFF_END_TS,
      T2.NAME,
      T2.BUSOBJ_NAME,
      T2.VERSION,
      T2.DEPLOY_STATUS_CD,
      T2.MODE_CD


[1/6]

Message 2

[2/6]


   FROM
       SIEBEL.S_LST_OF_VAL T1,
       SIEBEL.S_WFA_DPLOY_DEF T2
   WHERE
      T2.DEPLOY_STATUS_CD = T1.NAME AND T1.TYPE = 'WFA_DPLY_STAT_CD' AND T1.LANG_ID = :1 AND
      (T2.NAME = :2 AND T1.VAL = :3 AND (T2.EFF_END_TS > TO_DATE(:4,'MM/DD/YYYY HH24:MI:SS') OR T2.EFF_END_TS IS NULL))
   ORDER BY
      T2.VERSION DESC
ObjMgrSqlLog    Detail    4    0    2004-10-04 10:23:30    Bind variable 1: ENU
ObjMgrSqlLog    Detail    4    0    2004-10-04 10:23:30    Bind variable 2: Vitria Request For Action: 0
ObjMgrSqlLog    Detail    4    0    2004-10-04 10:23:30    Bind variable 3: Active
ObjMgrSqlLog    Detail    4    0    2004-10-04 10:23:30    Bind variable 4: 10/04/2004 17:23:30
ObjMgrSqlLog    Detail    4    0    2004-10-04 10:23:30    

ObjMgrBusServiceLog    Error    1    0    2004-10-04 10:23:30    (engine.cpp (2430)) SBL-BPR-00158: Cannot execute workflow process definition 'Vitria Request For Action: 0'.

When the query was ran against the customer's server database with the bind variables substituted, it did not return any rows.

When the customer issued the following query:

select * from S_WFA_DPLOY_DEF;

This returned a few rows, but surprisingly, there was a row with process name = "Vitria Request For Action", and not with Process Name = "Vitria Request For Action: 0".

It appears that the value for workflow process name submitted to the BusIntMgr was not right.

......

Message 3

[3/6]


From further investigation, the Siebel Client > Business Process Administration screen > Workflow Actions > Arguments list and it's picklist values comes from the picklist in the workflow policy program. The program in question here is "Vitria Run Integration Process", it has the following:

Program Name:    Vitria Run Integration Process

Details for 'ProcessName' argument name:

Name:            ProcessName
Picklist:        Completed Workflow Process PickList
Source Field:    Name

The problem is with the program argument "ProcessName" was using Source Field = "Name", which causes the picklist to show the workflow process name concatenated with the version #. The picklist uses:

BusComp:        Repository Workflow Process
Field:        Name
Post Default:    Expr: "[Process Name] + ': ' + [Version]"

This causes the BusIntMgr to issue a query to look for the workflow process name by Process Name + Version #, which can not be found in the S_WFA_DPLOY_DEF.

The correct way should be that this picklist uses Source Field = "Process Name" to select by process name regardless of version #. [Process Name] field is mapped to the S_WFA_DPLOY_DEF.PROC_NAME column. We can not use the process name going by version number, because version number can change as we revise and deploy new versions of the workflow process.

......

Message 4

[4/6]


Customer was able to fix the problem with the custom Workflow Policy Program against the server DB, by updating the Source Field property to "Process Name" for program "Vitria Run Integration Process".

The out-of-box "Run Workflow Process" program does not have this problem as the Source Field is already set to "Process Name".

Customer then restarted the VitriaWorkMon and now the WorkMon is able to execute the action successfully to run the workflow process. Now the custom program and workflow policy is working.

However, Siebel Support still recommended that customer use Workflow Process Manager server component to run workflows in Siebel 7.7. The reason is that the Business Integration Manager server components will be depreciated in future Siebel versions as documented in Siebel Bookshelf > Business Process Administration Guide > For Developers: Understanding How Workflow Processes Are Designed > Invoking Workflow Processes > About Invoking a Workflow Process:


.....

Message 5

[5/6]


NOTE: Starting with Siebel 7.0, Business Integration Manager and Business Integration Batch Manager have been deprecated, so if you were using either one in your business processes you need to replace them with Workflow Process Manager or Workflow Process Batch Manager respectively.

In addition to the above documentation, a documentation change request was also raised to document the changes that should be made for any existing custom workflow policy programs that will be migrated from Siebel 7.0/7.5 to 7.7:

Documentation CR # 10481570:
Abstract:    Document changes required for custom workflow policy programs and action migrated from 7.0/7.5 to 77

The changes recommended for Siebel 7.7 are:

For any Workflow Actions that uses "Run Integration Process" or a custom workflow policy program that is a copy of "Run Integration Process", these programs will run the workflow process using Business Integration Manager server component, which will be deprecated.

......

Message 6

[6/6]


Please convert such programs or workflow actions to use the Workflow Process Manager server component by doing one of the following:

Approach # 1:   Change the custom workflow policy program arguments to use the following:

Name:            Action Type
Default Value:    WfProcMgr

Name:            ProcessName
Source Field:    Process Name

Check the changes into the server database.

Approach # 2:   Create a new workflow policy action which uses the standard "Run Workflow Process" program.

This can be done by navigating to Site Map > Administration - Business Process > Actions, create a new action with Program = "Run Workflow Process".

Search keywords: Cannot execute workflow process definition, workflow, process, error, run workflow process, run intergration process, WfProcMgr, BusIntMgr, workflow policy programs, arguments, Action Type, ProcessName, Source Field, Completed Workflow Process PickList

.


Applies to:

Siebel CRM - Version: 7.8.2.14 SIA[19251] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2000 Advanced Server
Database Server OS: Microsoft Windows 2000 Advanced Server

This document was previously published as Siebel SR 38-3076259561.

Symptoms

hello,
We get the following error when creating order line items.
"Cannot execute workflow process definition 'PSP Driver Workflow Process'.(SBL-BPR-00158)". Enabling it we get errors about other workflows.
We are not using any of the Order managment features all are products are simple products. Please suggest how we can around this workflow errors or if there is a easy way to disable all the OM related workflows?
Thanks

Cause

Setup.

Solution

Message 1

For the benefit of the other readers:

Requirement: How to disable Order Management workflows?

Behavior: The customer is getting the following error when creating Order Line Items: "Cannot execute workflow process definition 'PSP Driver Workflow Process'(SBL-BPR-00158)". However, even enabling this workflow, other Workflows errors are displayed.

The customer is not using any of the Order management features and all products are simple products. In this case, please suggest a workaround this workflow errors or if there is a easy way to disable all the OM related workflows?

Resolution:

Step1: Rename the PSP Driver Workflow process and changing their step process.
Approach:
1. In Tools, “expire” the workflow process
2. In Tools, "revise" the workflow process to include only Start and End steps (creating new, distinct records for each step)
3. In Tools, "deploy" the revised workflow process
4. In the Application view "Administration –> Business Processes –> Workflow Deployment", active the revised workflow process

Step2:

Turn off the 'Product Recommendation Driver Workflow' that also makes a part of the Order Management functionality.

Approach:
1. Navigate to the Administration - Runtime Event screen > Action Sets view
2. In the Actions Sets list, select the record named Product Recommendation.
3. In the child list, in the record named Raise Signal, deselect the Active checkbox.

Please also check the document: "Is it possible to completely disable the order management signals from firing? (Doc ID 875852.1)" for more details about how to disable C/OM signals as well.

Regards.
Oracle Technical Support


Applies to:

Siebel Loyalty Customer Portal - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms



We are currently working on an internal POC on the Loyalty and eLoyalty modules.In the eloyalty application when I am trying to click on "Save Cart" button it gives the following error "Cannot execute workflow process definition '0V-16FKPI'.(SBL-BPR-00158)?".
We have activated all the workflows for Loyalty application. Infact one of SR stated the workflows that needs to be active for Loyalty. we have done that.Also we have also reloaded run time events but it still gives the above error. Please let us know how to resolve the same.

Also when we click on "Check out" button it gives error as "Cannot execute workflow process definition '0V-1CFDMG'.(SBL-BPR-00158)". I have navigated to runtime administration - Event and queried for Action Set Name "Workflow_0V-1CFDP4".I have activated/inactivated the runtime event. Also reloaded the runtime events, but still i get the same error.

Cause


This is produce defect I have raised CR # 10596960 as product defect.

Solution


CR # 10596960 has been raised as a product defect.

Please making any changes please note down all ids and changes. so that you can revert it back.

1) Take the row id of the workflow - ""'LOY eMember - Checkout Process' " , please take from the Workflow deployment view - Acitve workflow tab. take the row id of activated worflow.
2) Goto Runtime event screens - search for RTE based on applet - Quote Form Applet - Current (eSales) and SubEvent 'FrameEventMethodLOYCheckout'
3) now drill down the action set "Workflow_0V-1C0DCJ."
4) Check for the process id in Business context feild below Business Service and Method name , check for the process id "0V-1CFDMG".
5) Replace the process id "0V-1CFDMG" with new row id of workflow "'LOY eMember - Checkout Process".
Reload RTE again. logout.

Its working fine after changing.

Applies to:

Siebel CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Under any opportunity, i go to Quote tab, when i click Auto Quote button, quote does get created, but the following error also thrown as well:
[1] Error invoking service 'ISS PSP Dispatch Service', method 'CalPSPWorkflow' at step 'Dispatch Service'. (SBL-BPR-00162)
[2] Cannot execute workflow process definition 'Basic Pricing Procedure'. (SBL-BPR-00158)

Goal

The Goad is to eradicate the following errors while using Quote > Auto Quote button:
[1] Error invoking service 'ISS PSP Dispatch Service', method 'CallPSPWorkflow' at step 'Dispatch Service'.(SBL-BPR-00162)
[2] Cannot execute workflow process definition 'Basic Pricing Procedure'.(SBL-BPR-00158)

Solution


Please make sure all workflows belonging to the following groups are activated:

[Group] = "Configurator" OR [Group] = "Asset Based Ordering" OR [Group] = "Eligibility & Compatibility" OR [Group] = "eAdvisor" OR [Group] = "eSales" OR [Group] = "Compound Product Validation" OR [Group] = "Product Recommendation" OR [Group] = "Product Promotions" OR [Group] = "Pricer" OR [Group] = "C/OM UI Processes" OR [Group] = "Application Deployment Manager" OR [Group] = "User Registration"

Go to Siebel Tools, revise and deploy all workflows belonging to the above groups then start the Siebel Application and go to Administration Business Process -> Workflow Deployment and activate (by clicking on the Activate button) these workflows.

It may also be necessary to go to Administration -> Runtime Events then to Events and choose Reload Runtime Events from the menu.

Once the above is done please retest the functionality and let us know the results.

Thank you,
r> Oracle|Siebel Product Support.


Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 8.1.7.3
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1248695731.

Symptoms

We migrated our Customizable Products to the QA environment and After customizing the Products in the eConfiguratorand clicking on the Done button results in the following error message

Cannot initiate workflow process definition '1-1RRRK'. Verify that it does exist, has an 'Active' status, is activated and has not expired.(SBL-BPR-00158)"

On further investigation we found a similar SR on the supportweb #: 38-1046712637 , we tried following the same steps but it did not resolve our issue

These are steps we tried
1. Navigate to Business Process Administration > Workflow Processes
    a. Reimport workflow process from DEV, SIS OM Edit Service Order Line Item
2. Navigate to Runtime Events Administration > Events tab
               a. Query for Object Subevent EventMethodPMTConfigure
               b. Drill down on the Action Set Name hyperlink
    c. In the Actions applet, delete all actions
3. Activate the imported workflow process
4.ReLoad Personalization and Restarted the Dedicated client

However as the above did not work we went ahead and created the Action for the Action Set and modified the Business Service Context to match the row id and step ids of the new workflow process and this worked. Though the issue is resolved we thought it would be better to find out if there was a process which would not require the steps we did in the workaround to make it cleaner and easier for the QA administrators to do when the same move happens to Production

Please let me know if you need any more info

Thanks

Solution

Message 1

For the benefit of our customers.

I have taken ownership of your SR. Reimporting runtime events workflow processes into another environment does somethimes cause the Runtime Events Action Set to loose context of the active process id. These are the steps I would recommend when importing a runtime events to another environment where another version of the same process exist.

1. Import your new runtime events process but do not activate this process yet.
2. Deactivate the old process.
3. Navigate to Runtime Events Administration and Reload Personalization.
4. Activate your new process version.
5. Reload personalization
6. Verify that you have the new process Id in your action set.

The key to this whole procedure is to manually perform the deactivation of your old process (do not delete this process after deactivation) then reload personalization before activating and reloading the new workflow process in order to cache the new process id correctly.

The customer confirmed that this suggestion help resolve their issue.

Thanks,

Siebel Technical Support


No comments:

Post a Comment

Subscribe to: Post Comments (Atom)