Search This Blog

SBL-BPR-00131: %1

Applies to:

Siebel Communications, Media and Energy CRM - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Unable to successfully run "VORD CPVE Simple Validation Expression Checker Service" when [Count] = 0

1) Log onto Siebel eCommunications

2) Create a new product called "Network Sample" , check the flag Compound Product and set the Network Element Type to "Network"

3) Create three new products called "Network Node Sample 1", "Network Node Sample 2", "Network Node Sample 3" , do not check the Compound Product Flag and set the Network Element Type to "Network Node"

4) On the "Network Sample" product click on the Product Validation tab and then Validation Services

5) Create two new services
     - VORD CPVE Simple Validation Expression Checker Service
     - VORD CPVE Component Cardinality Checker Service

6) Now click on Product Validation Expression Rules and create a new entry
     - Sequence = 5
     - Search Expression = [Network Element Type] = "Network Node"
     - Aggregate Function = [Count]
     - Group By Fields = [Product Name]
     - Having Expresion = [Count] > 0
     - Active = True
     - Message = TEST (Create this message in "Administration - Order Management > Message Types" where Group is "Simple Expression Rule")

7) Now change to the Cardinality Rules Tab and create the following entries
     - Product = Network Node Sample 1 , Min Qty = 1, Max Qty = 10, Active = True
     - Product = Network Node Sample 2 , Min Qty = 0, Max Qty = 20, Active = True
     - Product = Network Node Sample 3 , Min Qty = 1, Max Qty = 30, Active = True
     - Product = Network Sample , Min Qty = 1, Max Qty = 1, Active = True

8) Create a Sales Order for an account and add the "Network Sample" product to the line items.

9) Navigate to "Sales Order > Line Items > Network Line Item" and highlight the "Network Sample" line item and hit the "Validate" button

10) Pop up appears with the following information

The following problems were found:
Network Sample must have at least 1 Network Sample Node 1
Network Sample must have at least 1 Network Sample Node 3
(SBL-BPR-00131)

11) Navigate to "Sales Order > Line Items > Network Line Item" and add "Network Node Sample 1" line item and hit the "Validate" button

12) Pop up appears with the following information

The following problems were found:
TEST
Network Sample must have at least 1 Network Sample Node 3
(SBL-BPR-00131)

13) Change the Product Validation Expression Rules such that "Having Expression = [Count] = 0 " - ( using '=' and not '>' )

14) Navigate to "Sales Order > Line Items > Network Line Item" and remove the line items so that there is only "Network Sample" line item and hit the "Validate" button

15) Pop up appears with the following information

The following problems were found:
Network Sample must have at least 1 Network Sample Node 1
Network Sample must have at least 1 Network Sample Node 3
(SBL-BPR-00131)

There is no message for the Simple Expression Rule Checker

See recording: Simple_Validation_Expression_Checker_Service.wrf

The above recording requires the webex player application which can be downloaded from www.webex.com



Cause

This functionality is not currently available



Solution

Enhancement Request CR 10599143 has been logged and the issue may be resolved in a future release pending investigation from Engineering Team.

References

BUG:10599143 - UNABLE TO SUCCESSFULLY RUN "VORD CPVE SIMPLE VALIDATION EXPRESSION CHECKER SERVICE" WHEN [COUNT] = 0

Applies to:

Siebel eCommunications - Version: 8.0.0.3 [20416] - Release: V8

Information in this document applies to any platform.

Goal

In TBUI when the task flow reaches an error step the following error is displayed:

[1] An internal error has occured while handling the following exception. The current task has been canceled as a result.(SBL-BPR-00530)
[2] <custom error message>(SBL-BPR-00131)

Can the first error be translated or changed?

Solution


The first error message (SBL-BPR-00530) displayed in a error step is hard coded and can not be changed. The error message passed to the custom error appears in the second error displayed (SBL-BPR-00131).

CR#10560755 has been opened to enhance the product so that the first error message displayed can be changed.


Applies to:

Siebel Campaigns - Version: 7.0.4 [14068] and later   [Release: V7 and later ]
Siebel Marketing - Version: 7.0.4 [14068] and later    [Release: V7 and later]
Information in this document applies to any platform.
""""Checked for relevance on AUGUST 3, 2010 GGONZALEZ """"
---------------------------------------------------------------------
Release(s):V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:Segment, Bridge, error

This document was previously published as Siebel Troubleshooting Steps 51.

Purpose

Siebel Marketing Segmentation Bridge Troubleshooting Guide .

Last Review Date

09-Dec-2004

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

This document describes troubleshooting steps that are specifically related to the Segmentation Bridge solution. In addition, you may encounter setup issues that are relevant to any Siebel 7.7 deployment of Siebel Marketing. For general Siebel 7.7 Marketing troubleshooting solutions, refer to Troubleshooting Steps 43 posted on SupportWeb.

The following sections of Troubleshooting Steps 43 are also relevant to Segmentation Bridge implementations:

  • Marketing Server Installation
  • Marketing Metadata
  • Siebel Enterprise Installation and Setup
  • List Format Design
  • Campaign Load

This document provides a set of tests that can be used to confirm correct system operation during the development phase of your implementation of Siebel Marketing Segmentation Bridge. The topics are organized based on the steps in the installation and configuration process. Make use of keyword searches if you do not see your issue listed under a section. There may be an entry in another topic that relates to the same problem.

Connectivity

Campaign Load / Segment Load

General

Connectivity

Segment Designer Views Display an Analytics Login Page

Symptom or Error Message

A Siebel Analytics login page appears when you navigate to any of the following views:

  • Segment screen tab > Segment Designer
  • Segment screen tab > Segment Tree Designer
  • Administration - Marketing > Marketing 7.7 List Formats
  • Administration - Marketing > Marketing 7.7 Server Administration 7.7

Cause

  • The login and password for the user is not consistent between the Siebel OLTP and the Siebel Analytics Server.

  • The user may not exist at all in the Siebel Analytics repository.

Diagnostic Steps

  1. Launch Siebel Analytics Administration Tool and ensure that the user has been created using the option Manage > Security.

  2. Compare the password of the user in Siebel Marketing and in Siebel Analytics.

  3. Log in Siebel Analytics Answers, and run a simple query. Ensure that data is returned. This indicates that this user can query the databases through Siebel Analytics.

Solution

  1. Create the user in the Siebel Analytics Administration Tool under Manage > Security if it does not already exist

  2. Ensure that the user has a password consistent with the Siebel transactional application.

  3. If you can not run a query in Siebel Answers, the solution may differ depending on the error you encounter. Please first do a search on SupportWeb using the error message you get, and log a service request if you need further assistance. Please log the service request with Siebel Technical Support in the Siebel Analytics area and provide the following information:

  1. The simple query you run

  2. The error message you received


The Error Message, "The Page Can Not Be Displayed," Appears in the Siebel 7.7 Marketing Views

Symptom or Error Message

When trying to connect to any of the following views:

  • Marketing 7.7 Server Administration 7.7
  • Marketing 7.7 List Formats
  • Segment Designer
  • Segment Tree Designer

The following error appears:

The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

Cause

The HTTP Host may have the incorrect Siebel Analytics Web server specified for the SegmentServer hostname parameter.

Diagnostic Steps

  1. Go to Site Map > Integration Administration > Host Administration.

  2. Query for the Virtual Name = SEGMENTSERVER.

  3. Verify that the Name column is set to the Siebel Analytics Web server running the marketing module and that the name is not included in brackets.

  4. Go to Site Map > Integration Administration > Symbolic URL Administration.

  5. Query for any URLs containing *SEGMENTSERVER*. The Host Name should match the name of your Siebel Analytics Web server running the segmentation module.

  6. Try to connect to this URL using http://<host name>/Analytics, where <host name> is the value set in the SEGMENTSERVER host parameter. If the Host parameter is correct but diagnostics step 6 fails, this means that you are not able to connect to the Analytics Web server.

Solution

  1. Navigate to Site Map > Integration Administration > Host Administration

  2. Query for the Virtual Name = SEGMENTSERVER

  3. Update the Name column to the name of the Siebel Analytics Web server running the marketing module.

  4. If you are not able to connect to the Analytics Web Server:

    1. Ensure that you can ping the Analytics Web Server by running the following command line:

      Ping ServerName

      If you cannot ping successfully, refer to your network administrator for the network configuration issue.

    2. Ensure that the Siebel Analytics Web Server is running. If the service does not start, look in the log located in \\SiebelAnalyticsData\Web\log. Find any errors in the log and search on SupportWeb using the error message as a keyword. Log a service request under Siebel Analytics area if you need further assistance and provide the Analytics Web Server log file located in \\SiebelAnalyticsData\Web\log.

    3. Ensure that the Web Server is properly started. If it does not start, refer to your system administrator.


The Marketing Link Does Not Appear in the Analytics Web User Interface

Symptom or Error Message

When a user logs into the Analytics Web environment, the main link for Marketing or the links for the Segment Designer, Segment Tree Designer or List Format Designer cannot be seen.

Cause

  1. The license key file used during the Siebel Analytics installation may not include the marketing module licenses.

  2. The privileges for the user (including the Analytics Web Admin) may not display the new modules.

Diagnostic Steps

  1. Open \\SiebelAnalyticsData\Web\config\analyticsweblicense.xml\

  2. Verify that you have a valid license for the following sections:

    • <WebMessage name="kmsgLicenseListFormats"
    • <WebMessage name="kmsgLicenseSegmentTrees"
    • <WebMessage name="kmsgLicenseSegments"

If this is not the case, you are encountering Cause 1.

  • If the license keys are correct:

    1. Log in to Siebel Analytics web interface as an Administrator.

    2. Select the Admin link.

    3. Select Manage Privilege.

    4. Verify the privileges of the user logged in to Siebel Marketing for the Segmentation and List Formats module. If this is not the case, you are encountering Cause 2.

    Solution

    Cause 1

    1. Make sure that you have installed Siebel Analytics version 7.7.1 or later. Previous versions (including Siebel Analytics version 7.7.0) did not include the marketing segmentation module.

    2. Confirm that a valid license key was used for Siebel Analytics version 7.7.1 including the Marketing Module.

      1. Log in to Siebel Analytics as an Administrator.

      2. A link for Marketing should appear in the top section (in the same area as the links for Dashboards, Answers, Delivers, Admin, and Log Out).

    Cause 2

    1. Log in to Siebel Analytics web interface as an Administrator.

    2. Select the Admin link.

    3. Select Manage Privileges.

    4. Find the entries for the marketing modules and add the user or group to the permission.

      • List Formats

        • Create List Formats
        • Create Headers and Footers
        • Access Options Tab
        • Add/Remove List Format Columns

      • Segmentation

        • Create Segments
        • Create Segment Trees
        • Create/Purge Saved Result Sets
        • Access Segment Advanced Options Tab
        • Access Segment Tree Advanced Options Tab
        • Change Target Levels within Segment Designer

    When Logging In, this Message Occurs: "You are currently not logged into the Siebel Analytics Server... To log back in, click here."

    Symptom or Error Message

    When logging in with a user who exists on Analytics Server, the following message occurs:

    You are currently not logged into the Siebel Analytic Server... To log back in, click here...

    Cause

    Privacy settings in Internet Options of the Internet Explorer browser might be set too high.

    Diagnostic Steps

    1. In the Internet Explorer toolbar, choose Tools > Internet Options. Click the Privacy tab and check the privacy setting indicated by the slider.

    2. Check that the setting on the slider for the Internet zone is set to low.

    Solution

    1. Set the setting to a low value.

    2. If this is an issue, the workaround is to click the Edit button on the bottom section that state Web Sites to override cookie handling. Input the full domain name where the Siebel Analytics Web server resides and click the Allow button.


    No Siebel 7.7 Segments Appear in the Popup Dialog When Adding a Record in the My Segments View

    Symptom or Error Message

    When adding a record in the My Segments View, there is no error message. However, the popup appears and does not show any Siebel 7.7 Segments.

    Cause

    The HTTP Host may have the incorrect setting for Siebel Analytics Web server for SegmentServer Parameter

    Diagnostic Steps

    1. Navigate to Site Map> Integration Administration > Host Administration

    2. Query for the Virtual Name = SEGMENTSERVER

    3. Verify that the Name column is set to the Siebel Analytics Web server running the marketing module.

    4. Try to connect to this URL using http://<host name>/Analytics, where <host name> is the value set in SEGMENTSERVER Host parameter. If the Host parameter is correct but diagnostic step 4 fails, it means that you are not able to connect to the Analytics Web server.

    5. Navigate to Site Map> Integration Administration > Symbolic URL Administration.

    6. Query for any URLs containing *SEGMENTSERVER*. The Host Name should match the name of your Siebel Analytics Web server running the segmentation module.

    Solution

    1. Navigate to Site Map> Integration Administration > Host Administration

    2. Query for the Virtual Name = SEGMENTSERVER

    3. Update the Name column to the name of the Siebel Analytics Web Server running the marketing module.

    4. If you are not able to connect to the Analytics Web Server:

      1. Ensure that you can ping the Analytics Web Server by running the following command line:

        Ping ServerName

        If you cannot ping successfully, refer to your network administrator for the network configuration issue.

      2. Ensure that the Siebel Analytics Web Server is running. If the service does not start, look in the log located SiebelAnalyticsData\Web\log. Look for any errors in the log and search on SupportWeb using the error message as a keyword. Log a service request under the Siebel Analytics area if you need further assistance and provide us the Analytics Web Server log file located in \\SiebelAnalyticsData\Web\log

      3. Ensure that the Web Server is properly started. If it does not start, refer to your system administrator


    Error nQSError: 10017 Appears When Saving a Segment Result Set

    Symptom or Error Message

    When saving a segment saved result set, you get the following error message:

    State: 08003. Code: 10017. [NQODBC] [SQL_STATE: 08003] [nQSError:
    10017] The connect operation failed. [nQSError: 43001]
    Authentication failed for Administrator in repository Star:
    invalid user/password. (08003)

    Cause

    Saving a result set uses the EXECUTE PHYSICAL procedure call. This call must be executed by an administrative user whose login and encrypted password is setup in the \\SiebelAnalyticsData\Web\config\instanceconfig.xml file. The default instanceconfig.xml does not specify an administrative login and password and so the default that is used is Administrator/SADMIN.

    Diagnostic Steps

    1. Open the \\SiebelAnalyticsData\Web\config\instanceconfig.xml file on the Siebel Analytics Web Server that runs the Marketing module.

    2. Verify that the AdministrativeLogin parameter has a valid Siebel Analytics user.

    3. Verify that the AdministrativePassword parameter has an encrypted password.

    4. Ensure that the user set in the instanceconfig.xml file is valid and part of the Administrators group:

      1. Launch Siebel Analytics Administration Tool.

      2. Select Option Manage > Security.

      3. Click on Groups.

      4. Double-click on the Administrators group and ensure that the user is listed.

    Solution

    1. In the file instanceconfig.xml uncomment the AdministrativeLogin and AdministrativePassword section if required.

    2. Connect to the following URL:  http://<ServerName>/analytics/saw.dll?EncryptString.

    3. Log in using the user indicated in the instanceconfig.xml file. A web page appears showing an encrypted string.

    4. Copy and paste this string in the value for AdministrativePassword parameter.

    5. Open the instanceconfig.xml file in Internet Explorer. If you want to double-check that the section is properly uncommented, it should display like the following (comments would appear in grey):

      <AdministrativeLogin>Administrator</AdministrativeLogin>
      <AdministrativePassword>1d0f03a35f062ba39e024b20aabf2bce8a03</AdministrativePassword>

    Campaign Load / Segment Load

    General Troubleshooting Information

    A user can load a campaign or segment using either of the following methods:

    • Using the Load Segment button in the Campaigns > All Campaign Across Organization > Segments/Lists view

    • Selecting the Load Campaign option from the program flow or the program explorer

    During this task, the following steps occur:

    1. A component request is created on the Siebel Server in order to launch the workflow process

      To verify if this component request has been correctly created, go to the Server Administration > Enterprise Operations > Component Requests view. You should see a job with Component Job=Workflow Process Manager and Mode = Asynchronous.

    2. A Workflow Process Manager task is started. It executes the Standalone Campaign Load workflow if you started the Load Segment task on a standalone campaign or the Campaign Load workflow if you are loading a campaign from a program.

      1. You can verify if this task is started in the Server Administration > Tasks view. Look for the latest Workflow Process Manager tasks.

      2. You can increase the log level of the workflow in the view in order to get further information:

        1. Navigate to Server Administration > Components > Component Event Configuration

        2. In the upper list applet, select the component Workflow Process Manager.

        3. In the bottom applet, set to Log Level = 4 the events you want to trace:

          Error Condition 4 Triggered upon reaching an unhandled error or exception
          Component Tracing 4 A trace condition was met (used from LogTrace only)
          SQL Error 4 Trace SQL when error occurs
          Object Manager Business Component Log 4 Object manager business component log event
          EAI Integration Object Validation 4 EAI Integration Object Validation Event Type
          Web Service Outbound 4 Web Service Outbound Run-time Event Type
          Web Service Outbound Argument Tracing 4 Web Service Oubound Run-time Argument Tracing
          Workflow Definition Loading 4 Workflow engine loads a process definition into memory
          Workflow Engine Invoked 4 A workflow engine method was invoked
          Workflow Process Execution 4 Workflow engine executes a process
          Workflow Step Execution 4 Workflow engine executes a step

        This list is only provided as an example. You can use it as a starting point but you may need to activate additional events depending on the behavior encountered.

    3. If the options are correctly setup, the workflow sends a request to execute a job to the Analytics Web Server.

    4. The Analytics Server runs the query to select data based on the Segment criteria.

      1. You can view the log of the Marketing Job in the view Marketing Administration > Marketing 7.7. Server Administration 7.7 > Manage Marketing Job. If you do not see any jobs here, first try to increase the log level (please see below) and if the result is the same, it means that the tasks failed at a previous step.

      2. You can increase the log of the Marketing job by modifying the file instanceconfig.xml in the folder \\SiebelAnalyticsData\Web\Config and add the following parameters:

        LogLevel>6</LogLevel>
        <MarketingJobsLogDetailLevel>5</MarketingJobsLogDetailLevel>

        You can verify if this step is correctly executed by editing the segment in the view Segments > Segment Designer and clicking on the Update Counts button. If the counts are correctly updated, then a different step is the cause of the campaign load error.

    5. The Analytics Server generates an EAI file in the Siebel file system, for which the format is defined in the Campaign Load Format.

      • You can verify if this file is generated in the folder Marketing File System/EAI.

      • The Marketing File System location is setup in the file instanceconfig.xml located in the folder \\SiebelAnalyticsData\Web\Config.

  • The Siebel workflow, "Standalone Campaign Load" or "Campaign Load", imports the EAI file in the Siebel transactional database by launching the Import Marketing Contact workflow. If this step is failing, review the following:

    1. Verify that you are using the correct Campaign Load Format for the segment:

      1. Edit the Segment using the view Segments > Segment Designer.

      2. In the Advanced Tab, verify the Campaign Load File Format field.

    2. Review the Campaign Load Format.

      1. Make sure the Column headers match to Integration Component fields (as specified in the Segmentation Bridge technical note). NOTE: Headers are case sensitive.

      2. Make sure that your contact keys columns are characters. Bring up Properties for the column. Go to Value Format > Check the Override Default Value Format check box. Then select "Plain Text" from the dropdown.

    3. Review the Workflow Process Manager in the Server Administration view.

    4. Review EAI files generated to ensure they include the correct mappings. Also make sure you don't have bad data that the Siebel object manager will not accept.

    5. Test in Workflow Simulator

    6. Review Object Manager Logs in view Server Administration.


    Write List File Job Errored Out on Analytics Server When Loading a Campaign

    Symptom or Error Message

    When trying to load a campaign the following error occurs:

    Object manager error: ([0] Error while loading segment '99-4IV1L'.
    Write List file job errored out on Analytics Server. Please refer to analytics job '1'.(SBL-EXL-00151) (0x6eda))
    Object manager error: ([1] Stack trace:
    Application [Siebel Sales Enterprise].RaiseErrorText(), Built-in function
    Service [Campaign Execution].DoLoadAnalyticsSegment(), Line: 1669
    Service [Campaign Execution].Service_PreInvokeMethod(), Line: 1778 (0x
    Object manager error: ([2] Error invoking service 'Campaign Execution', method 'Load Analytics Segment' at step 'Load Analytics Segment'.(SBL-BPR-00162) (0x80d8))

    Cause

    This is a generic error message that indicates that Siebel Analytics was unable to generate the EAI import file. There can be various causes and it is necessary to review the Analytics logs to identify the exact cause.

    Diagnostic Steps

    1. You need to review the Marketing logs or Analytics logs on the Analytics Server in order to identify the root cause of the error.

    2. Go to the Marketing Administration > Marketing 7.7 Server Administration 7.7. > Marketing Job Management view.

    3. In Background Jobs, drill down on details for the job with the ID indicated in the error message of the Workflow Log:


      Object manager error: ([0] Error while loading segment '99-4IV1L'.

      Write List file job errored out on Analytics Server. Please refer to analytics job '1'.(SBL-EXL-00151) (0x6eda))

    In this example, the marketing job is 1.


  • An XML file is opened. Look for the keywords Exception and Message. If the XML file is opened within Internet Explorer, you can reduce or expand a node in order to make the file easier to read. A minus sign indicates you can collapse the node. A plus sign indicates you can expand the node to get further details:


    In this example Analytics was unable to generate the segment because a physical table was missing on the database.

    Solution

    The solution may differ depending on the error message found in the marketing job. Please search this document and SupportWeb for this error message and contact Technical Support if you require further assistance.

    Error SBL-EXL-00151 (Error Importing EAI File) When Loading a Campaign

    Symptom or Error Message

    When trying to load campaigns the following error appears:

    Error while loading campaign '1-20VBO'.
    Details: Error while loading segment '1-20VBI'.
    Error while importing EAI file. Refer to SRM request '1-188O-EZ' for more details.(SBL-EXL-00151)(SBL-EXL-00151)
    Error invoking service 'Campaign Execution', method 'Load Analytics Campaign' at step 'Load Analytics Campaign'

    Cause

    Siebel Analytics has generated the EAI file but Siebel Marketing is not able to load it into the Siebel OLTP Database. This is a generic error that may have several root causes.

    Diagnostic Steps

    Refer to step 6 of section Campaign Load / Segment Load > General Troubleshooting Information.

    Solution

    1. If the Campaign Load Format is not correct in the segment Advanced Options, select the correct Campaign Load Format, save the segment and try again.

    2. If the Campaign Load Format is not correctly defined, correct it and load the campaign again.


    Error SBL-OMS-00107 and SBL-BPR-0016 When Loading a Campaign

    Symptom or Error Message

    When running the Campaign Load task, no contacts/prospects are associated to the Campaign. The Campaign Load Workflow log file shows the following error:

    SBL-OMS-00107: Object manager error: ([1] Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Update Camp Con'.(SBL-BPR-00162) (0x80d8))

    Cause

    Setup is not able to handle the transactions when there are over 1000 records in the file.

    Diagnostic Steps

    1. Create small segments (1500-2000 records), so that you have at least 1 EAI file with 1000 records (based on current Campaign Load Format settings). Associate this segment to a Campaign, and load campaign.

    2. If this is really a transaction related problem, then this job should error out also.

    Solution

    1. Go to view Administration - Marketing > List Format.

    2. Open you Campaign Load Format, and select the Options table.

    3. Change the Max# Records parameter to 100. The load process will now split files into 100 records each. This will result in smaller transaction being used.

    4. Perform the Campaign Load again, assuming the database can handle these smaller transactions.


    Load Campaign Requires Each Segment to Have an Assigned Campaign Load Format

    Symptom or Error Message

    Object manager error: ([0] Error while loading segment '99-4IYXK'.
    Details: Load Campaign requires each segment (or segment tree) to have an assigned campaign load format. Please review this setting for each each segment (or segment tree) on the Adv
    Object manager error: ([1] Stack trace:
    Application [Siebel Sales Enterprise].RaiseErrorText(), Built-in function
    Service [SAW Interface Service].WriteListFiles(), Line: 1817
    Service [SAW Interface Service].Service_PreInvokeMethod(), Line: 1879
    Service
    Object manager error: ([2] Error invoking service 'Campaign Execution', method 'Load Analytics Segment' at step 'Load Analytics Segment'.(SBL-BPR-00162) (0x80d8))

    Cause

    The segment you have created does not have an associated Campaign Load Format.

    Diagnostic Steps

    1. Go to view Segment > Segment Designer > Advance Options

    2. Select a Campaign Load Format in Campaign Load File Format field and verify that this field is empty.

    Solution

    1. If you have already an available Campaign Load Format:

      1. Go to Marketing Administration > Marketing 7.7 Server Administration 7.7 > Manage Marketing Defaults.

      2. In the "Default Campaign Load File Format" column, click on the browse button for your Target Level and select the Campaign Load Format. Any new segments that are created will be automatically set to this campaign load format.

  • If you do not have an available Campaign Load Format yet:

    1. Go to view Marketing Administration > Marketing 7.7 Lists Formats.

    2. If you see a List Catalog available for the Target Level, drill down on it and create a new Campaign Load Format. For more information, refer to the Segmentation Bridge Technical Note 549 or 548, in the section, Creating a Campaign Load Format for the Segmentation Bridge.

    3. If there is no available List Catalog for this Target Level, you need to define one:

      1. Open Siebel Analytics Administration Tool

      2. Select option Manage > Marketing

      3. Select Marketing Object List Catalogs.

      4. In the right pane of the windows, right-click and select the option, New List Catalog.


    SBL-OMS-00107: Object Manager Error: ([0] Step 'Read Csv File' references non-existent process property '1-29T66'.(SBL-BPR-00182) (0x80ea))

    Symptom or Error Message

    The first workflow reports the error:

    Object manager error: ([0] Error while loading segment '99-4IYXU'.
    Error while importing EAI file. Refer to SRM request '99-8TZ-2' for more details.(SBL-EXL-00151) (0x6eda))

    The Import Marketing Contact workflow reports the error:

    ((0) err=4300107 sys=33002) SBL-OMS-00107: Object manager error: ([0] Step 'Read Csv File' references non-existent process property '1-29T66'.(SBL-BPR-00182) (0x80ea))

    Cause

    The error Step 'Read Csv File' references a non-existent process property '1-29T66';. (SBL-BPR-00182) happened because the input property is defined of type Process property under Business Process but this property is not defined under the WF process Prop.

    Diagnostic Steps

    Not Applicable

    Solution

    1. Ensure that the Siebel Server has the correct Siebel repository file (*.srf). If you are using several languages, verify all languages sub-folder.

    2. Re-import the workflows for the Segmentation Bridge in view Business Process Administration and activate the new workflows.

    3. Re-import Import Marketing Contact Workflow from a working environment

    4. Activate the new version of Import Marketing Contact Workflow.

    5. Revise and activate the workflow Campaign load.

    6. Restart the Siebel Server.


    Error Step 'Copy Contacts?' references non-existent process property '1-29SUS'.(SBL-BPR-00182)

    Symptom or Error Message

    The first workflow reports the error:

    Error Step 'Copy Contacts ?' references non-existent process property '1-29SUS'.(SBL-BPR-00182) -- "Error invoking service 'Campaign Execution', method 'Associate Purchased Lists' at step 'Bridge Associate Purchased Lists'.(SBL-BPR-00162)(SBL-BPR-00131)"

    Cause

    The Campaign Load workflow and the Campaign List Association workflow are not in synch.

    Diagnostic Steps

    Not Applicable

    Solution

    1. Ensure that the Siebel Server has the correct siebel repository file (*.srf). If you are using several languages, verify all languages sub-folder.

    2. Re-import the workflows for the Segmentation Bridge in view Business Process Administration and activate the new workflows.

    3. Re-import Campaign List Association Workflow from a working environment.

    4. Activate the new version of Campaign List Association Workflow.

    5. Revise and activate the Campaign Load workflow.

    6. Restart the Siebel Server.


    Some Contacts Are Not Associated to the Campaign

    Symptom or Error Message

    Some contacts are not associated to the Campaign. The Import Marketing Contact workflow reports the following error for some records:

    Begin: Business Service 'Read CSV File' invoke method: 'CsvToPropSet' c57c998
    (SBL-MKT-00321) The number of fields in the header does not match that in record

    Cause

    The record has not been imported due to incorrect data in the EAI File.

    Diagnostic Steps

    1. Verify the log level of the Workflow Process Manager component:

      1. Go to Server Administration > Components > Component Event Configuration

      2. In the upper list applet, select the component Workflow Process Manager.

      3. In the bottom applet, set the Log Level = 4 for the event "Object Manager Business Component Log".

      4. In the bottom applet, set the Log Level = 4 for the event "Workflow Process Execution ".

    2. Recreate the error and get the new Workflow Log

    3. In the log, look for a row similar to the following:

    4. Input: @0*0*2*0*0*0*11*CsvFileName62*C:\ses752ora\siebfs\Marketing\EAI\ list-23-20041103180325-1.txt10*DeleteFile5*FALSE

    5. Open the EAI file from the Marketing file system and look for incorrect data (comma, quotes, double quotes, etc.). In our example, the EAI file is C:\ses752ora\siebfs\Marketing\EAI\list-23-20041103180325-1.txt

    Solution

    1. If the record includes quote or double quote characters you can use a function in the Campaign Load Format in order to replace them automatically.

    2. If the numeric fields are automatically grouped by quotes or commas, a good solution is to define the field as Varchar in Siebel Analytics Administration Tool.


    General

    Database Cache Entries Are Not Being Deleted from the Database Even Though They Have Been Purged From Manage Marketing

    Symptom or Error Message

    When examining the \\siebelanalytics\data\web\sawlog.log, the following errors appears:

    Odbc driver returned an error (SQLDriverConnect).
    State: 08003.  Code: 10017.  [NQODBC] [SQL_STATE: 08003] [nQSError: 10017] The connect operation failed.
    [nQSError: 43001] Authentication failed for Analytic in repository Star: invalid user/password. (08003)
    ----------------------------------------------------------
    Type: Error, Severity: 42
    Time: Fri Sep 24 14:58:43 2004
    File: project/webconnect/connection.cpp, Line: 286
    Properties:
            ThreadID: 29900
     
    Location:
            saw.threads
            saw.threadPool
            saw.taskScheduler.processJob
            saw.sqlNodeCacheMgr.cleanExpired
            saw.connectionPool.getConnection
    Authentication Failure.
    Odbc driver returned an error (SQLDriverConnect).
    ----------------------------------------------------------
    Type: Error, Severity: 40
    Time: Fri Sep 24 14:58:43 2004
    File: project/webmarketing/cachemgr.cpp, Line: 190
    Properties:
            ThreadID: 29900
     
    Location:
            saw.threads
            saw.threadPool
            saw.taskScheduler.processJob
            saw.sqlNodeCacheMgr.cleanExpired
    ***kmsgErrorInDeletingCache: message text not found ***
    Authentication Failure.

    Cause

    A background thread is responsible for logging in as an administrative user to perform the database cache cleanup. Deleting database cache uses the EXECUTE PHYSICAL procedure call. This call must be run by an administrative user whose login and encrypted password is setup in the \\SiebelAnalyticsData\Web\config\instanceconfig.xml file. The default instanceconfig.xml does not specify an administrative login and password and so the default value that is used is Administrator/SADMIN.

    Diagnostic Steps

    1. Open SiebelAnalyticsData\Web\config\instanceconfig.xml  file on the Siebel Analytics Web Server running the Marketing module.

    2. Verify that AdministrativeLogin parameter has a valid Siebel Analytics user.

    3. Verify that AdministrativePassword parameter has an encrypted password.

    4. Ensure that the user set in the instanceconfig.xml file is valid and part of the Administrators group:

      1. Launch Siebel Analytics Administration Tool.

      2. Select Option Manage > Security.

      3. Click on Groups.

      4. Double-Click on Administrators group and ensure that the user is listed.

    Solution

    1. In the file instanceconfig.xml, uncomment the AdministrativeLogin and AdministrativePassword section if required.

    2. Connect to the following url:  http://<ServerName>/analytics/saw.dll?EncryptString.

    3. Log in using the user you use in the instanceconfig.xml file. A web page appears showing an encrypted string.

    4. Copy and paste this string as the value for the AdministrativePassword parameter.

    5. Open the instanceconfig.xml file in Internet Explorer. To double-check that the XML section is properly uncommented, the file should look like the following example (comments would appear in grey):

      <AdministrativeLogin>Administrator</AdministrativeLogin>
      <AdministrativePassword>1d0f03a35f062ba39e024b20aabf2bce8a03</AdministrativePassword>

    Segment Update Counts Returns the Error, "Cannot obtain number of columns for the query result"

    Symptom or Error Message

    When a user updates counts for a segment or segment tree, the following error appears:


    Error in executing cursor for WorkNode (Id:1)
    Odbc driver returned an error (SQLExecDirect).

    State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 16001] ODBC error state: 37000 code: 8180 message: [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.. [nQSError: 16001] ODBC error state: S0002 code: 208 message: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'M_C_CONTACT'.. [nQSError: 16002] Cannot obtain number of columns for the query result. (S1000)

    SQL Issued: POPULATE M_C_CONTACT MODE (APPEND TABLE CONNECTION POOL "Siebel Data Warehouse"."Data Warehouse Connection Pool") AS SELECT '1c0bcd20-09eb-1000-a784-646464640000', ID FROM ( SELECT "- Contact Profile".ROW_ID AS ID FROM "Customer Profile (mktg)" WHERE "- Contact Profile"."Active Flag" = 'Y' ) DT

    Cause

    The caching tables have not been created in the source database for segmentation.

    Diagnostic Steps

    Caching tables are named M_*.

    1. Get the caching table name that generates the error from the log file. In our example this is M_C_CONTACT'.

    2. Verify that this table has been created in your database.

    Solution

    Create the required Caching Tables. Refer to Siebel 7.7 Bookshelf.in Analytics Server Administration Guide > Configuring Marketing Module Metadata chapter.

    Update Counts for a Segment or Segment Returns Error, "User does not have all the privileges"

    Symptom or Error Message

    User gets the following error message when performing Update Counts for a segment or segment tree:

    Error in executing cursor for WorkNode (Id:9)

    Odbc driver returned an error (SQLExecDirect).

    State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 13006] User does not have all the privileges. (S1000)

    Cause

    This error may be caused by:

    • The user designing the segment or segment tree may not have writeback permissions to allow caching of the segment criteria blocks.

    • Incorrect setup of marketing cache

    Diagnostic Steps

    1. Verify writeback Privileges. Verify that the group or user has writeback permissions for the datasource where segment cache and saved result sets are written.

      1. Login to the Siebel Analytics Administration tool.

      2. From the top menu, select Manage > Security.

      3. Double-click on the appropriate group (such as Segmentation User) or user (such as SADMIN).

      4. Select the Permissions button.

      5. In the \User\Group Permissions dialog, select the Query Limits tab. Locate the entry for the Data Warehouse data source (for example, the data source where cache and saved result sets are written).

      6. Scroll to the right and verify the value of the Populate Privilege column. If the value is not Allow, then writeback privileges are incorrect.

    2. Verify correct setup of the Segment Cache. Verify if any of the criteria blocks for the segment or segment tree are cached in the criteria block properties.

      1. Confirm if caching is causing the issue by deselecting caching for all criteria blocks and nested segments and reissuing the Update Counts. If a segment tree is being used, many of the nodes will automatically be cached by the server, so you may want to run a segment count separately to test this.

      2. If caching a block seems to be causing the error:

        1. Verify that the cache tables exist in the database. Cache Table names are prefixed with M_. Look for such table names in the error and verify if this table exists in the database.

        2. Verify that the caching metadata arguments have been entered correctly for the Target Level in the Analytics Admin Tool.

          1. Go to Manage > Marketing.

          2. Double-click on the Target Level object.

          3. Identify the Primary Qualified List Item (QLI) in the dialog.

          4. In the main Marketing Metadata window, find the Primary QLI in the Qualified List Items list. Double-click on the icon for it.

          5. In the dialog, go to the Cache Information tab and confirm that the parameters and physical SQL statement are correct. For more information, refer to the Siebel Analytics Server Administration Guide > Configuring Marketing Module Metadata.

    Solution

    1. If writeback Privileges are wrong:

      1. Login to the Siebel Analytics Administration tool.

      2. From the top menu, select Manage > Security.

      3. Double-click on the appropriate group (for example, Segmentation User) or user (for example, SADMIN).

      4. Select the Permissions button.

      5. In the User/Group Permissions dialog, select the Query Limits tab. Locate the entry for the Data Warehouse data source (for example, the data source where cache and saved result sets are written).

      6. Scroll to the right and set the Populate Privilege column to "Allow" for that connection pool.

      7. Click OK twice and save your changes.


    2. If a Caching Table is causing the error:

      1. Create the required Caching Tables. Refer to Siebel 7.7 Bookshelf > Analytics Server Administration Guide > Configuring Marketing Module Metadata.

      2. Verify the configuration of Caching Tables in Siebel Analytics Administration Tool, option Manage > Marketing ...> Qualified List Items. Refer to Siebel 7.7 Bookshelf > Configuring Marketing Module Metadata in the Siebel Analytics Server Administration Guide.


    Error nQsError: 59107 When Running a Segment or List Job

    Symptom or Error Message

    When running a segment or list job, you get the error:

    [nQsError: 59107].  Set operation failed due to incompatible sort order.

    Cause

    This error occurs when the Siebel Analytics Server (SAS) and the database use incompatible sorting rules for character data. This can occur for example if SAS does a binary sort on USC2 representation of data and the database does a binary sort on UTF8 representation of data.

    Diagnostic Steps

    1. Ask to your Database Administrator what sorting rule is used by your database.

    2. Launch Siebel Analytics Administration Tool.

    3. In Physical Layer, Double-click on the database.

    4. Go to Features tab.

    5. Verify the value of SORT_ORDER_LOCALE.

    Solution

    1. Launch Siebel Analytics Administration Tool.

    2. In Physical Layer, Double-click on the database.

    3. Go to Features tab. Set SORT_ORDER_LOCALE. Value to "xxx".


    When Selecting a Segment, Error Occurs When Trying To Browse User Folder

    Symptom or Error Message

    When trying to add a segment, an error occurs when trying to browse the user folder:

    SBL-EXL-00151 "SOAP MESSAGE: no children folders found"

    Cause

    The user used for impersonation does not have proper rights to read the Analytics folder.

    Diagnostic Steps

    1. If the error occurred when browsing the user folder, try to browse the Shared folder.

    2. If the error occurred when browsing the Shared folder:

      1. Go to view Segments > Segment Designer.

      2. Ensure that the folder selected has at least one segment or one sub-folder.

    Solution

    1. If the error occurs only for the User folder:

      1. The first workaround is to save segments into the Shared folder instead of the User folder.

      2. A second workaround is to have read permissions on all /users folders ("Read" for Everyone.). It is important to allow the distribution at lower levels.

    2. If the error occurs also for the Shared folder:

      1. Verify that the user used for impersonation has read access to the shared folder.

      2. Ensure that the folder selected has at least one segment or one sub-folder.

    Attachment 477974.1:4


Applies to:

Siebel CRM Integration Pack for Oracle Order Management: Order to Cash - Version: 2.2 and later   [Release: 2 and later ]
Information in this document applies to any platform.
Siebel CRM Integration Pack for Oracle Order Management - Version: 2.2

Symptoms

-- Problem Statement:
In AIA 2.2 - Order to Cash When inquiring the availability
for a line item in an order it fails with error:

[1] Error invoking service 'SWI External Integration Service', method 'checkAndSetError' at step 'Set Err Msg'. (SBL-BPR-00162_
[2] AIA Error (XPathExecutionError)
'XPath expression failed to execute.
Error while processing xpath expression, the expression is
"ora:processXSLT('ATPCheckInterfaceRequestOrders_to_ProcessSalesOrderATPCheckEBM.xsl',bpws:getVariab
leData('CheckATPsalesOrderReqMsg','ATPCheckInterfaceRequestOrders'))", the reason is
file:///a01/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_CheckATPSalesOrderSieb
elReqABCSImpl_1.0_84002e95516f6c8e871c7d8643a2769f.tmp/ATPCheckInterfaceRequestOrders_to_ProcessSale
sOrderATPCheckEBM.xsl<Line 268, Column 130>:XML-22044:(Error) Extension function error:
Error imvoking 'lookupXRef':oracle.tip.xref.exception.ValidationException:Reference Column Name is
Empty for Cross Refrence Table Name "ITEM_ID"
Please ensure Reference Column Name is not-empty'
'
Please verify the xpath query.
(SBL-BPR-00131)

-- Steps To Reproduce:

Login to Siebel
Create an Order
Add an item to the order
Select fulfillment tab
select the line item, and click on the inquiry button

Cause

The lookup function lookupXRef fails because the value for internal_id in bsr_system table (AIA schema) where system_code =  'SEBL_01'  is incorrect

Solution

  1. Identify Enterprise server name of the Siebel instance
  2. Update the internal_id field for the record in bsr_system (AIA schema) where system_code = 'SEBL_01'
  3. Bounce SOA Suite

To Identify Enterprise server name of the Siebel instance:

Easiest way to tell what this should be is to look at the siebel request payload received by any Siebel requestor ABCS. In that the root element of the Siebel message typically displays this. For
eg:
<ListOfSWIOrderIO Language="ENU" Locale="English - United States" MessageId=""
EnterpriseServerName="SBA" xmlns="http://siebel.com/OrderManagement/Order/Data">

In this example the EnterpriseServerName="SBA"

 

To Update the internal_id field for the record in bsr_system (AIA schema) where system_code = 'SEBL_01'

    • Login to AIA Console
    • Click on 'Setup' tab
    • Click on 'System' subtab
    • Update Internal_id field for record where system_code=SEBL_01
    • The correct value base on the example for 1) above is SBA
    • Click on Save


Applies to:

Siebel Marketing - Version: 7.8.2.4 [19224] - Release: V7

Information in this document applies to any platform.

Symptoms


When attempting to Campaign wave launch encounters the error The same values for 'ListExportFileName' already exist. This error is apparent in most of the campaigns.

the following error occurs:
ERROR
-----------------------

GenericLog GenericError 1 0 2009-02-19 14:34:03 Object manager error: ([0] Error invoking service 'Wave Execution', method 'SendOffers' at step 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
--
The same values for 'ListExportFileName' already exist.

If you would like to enter a new record, please ensure that the field values are unique.(SBL-DAT-00382)(SBL-BPR-00131) (WF_ERR_CUSTOM_1))

Cause

In launch a campaign and generate export files,you define this list export format same as you define e.g. a load format, in the list format designer on Analytics side. If you open this format there is an Advanced tab. There you set the file name of the file generated, i.e. which parts this file name consists of (name, data, etc). And if I'm not totally wrong Marketing 'just' picks up the generated file and the name. So if you e.g. removed the timestamp potentially, they have situations where the file name is equal.

To check the file names in the Marketing\Lists folder and may be the table on Siebel side where it tries to write the name to.

Solution

Workaround:

Consider adding an element to the List Format naming convention to make it unique.
For example, you can add Job ID: Standard-@{campaignCode}{}-@{jobID}{0}-@{waveCode}{0}-@{loadNumber}{1}-@{timestamp}{}-@{fileCounter}{1}.dat

I would request you to try the workaround in your test env and let me know if this will work with include "JobID" in all your formats.

The error 'ListExportFileName' already exist when launching a campaign record did not re-occur after we included the JobId in the filename of the output file.



Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.2.214 [16066] Fin Svcs
Database: Oracle 8.1.7.3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: HP-UX 11i

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

Symptoms

SBL-UIF-00299

We currently have a requirement to restrict Administration users, who are responsible for setting up end-user records, from deleting or modifying employee records with system logins (eg SADMIN) required for workflows etc.

Due to the BC Read Only Field not working for Views with Admin Mode Flag = True we are now trying to prohibit the update of particular user records in the User Administration Screen > Employee List View through a runtime event.

Runtime event is as follows:
Object Type: BusComp
Object Name: Employee
Event: PreSetFieldValue
Subevent: Last Name
Action Set : WBC Employee Read Only Fields
Action Step: Stop Update
Type: BusService
Bus Serv: Workflow Process Manager
Bus Serv Method: RunProcess
"ProcessName", "WBC Stop Emp Delete"

The Workflow Process checks whether the [Login Name] of the employee selected is equal to one which we want to protect for update. In our example it is login F123456 but we would also like to protect SADMIN.

When we update the last name of the employee with login F123456, the following error is displayed

[1] Wrong field values or value types detected in field Last Name. Please re-enter your field values. If you need additional assistance, please refer to the documentation.
[2] This is a System Admin employee record and cannot be deleted or modified.

The 2nd error message is the message we wish to display.
Why are we getting the first error message before it? Could you please try to replicate this in your vanilla environment?

Solution

Message 1

For the benefit of other users,

What customer has observed is expected behavior with how errors are returned in Siebel. In this case, the workflow process is run by the "Workflow Process Manager" business service. The errors are returned in a stack (First-In-Last-Out: 1st error is always placed at the bottom and newer errors are on the top. When errors are returned, the last errors are always shown first and the first error is always shown last).

The observed errors are:

[1] Wrong field values or value types detected in field User ID.
Please re-enter your field values. If you need additional assistance, please refer to the documentation. (SBL-UIF-00299)
[2] This is a System Admin employee record and cannot be deleted or modified. (SBL-BPR-00131)

The first error is returned by the Object Manager (OM) as it was not able to update the record with the user's changes and second one is the one returned by the workflow stop step.

Both errors are returned together by the OM to the UI:

a) Object Manager is the one that called the workflow, it got this error first and placed it at the bottom of the error stack.

b) Then, the OM produced the error from the user's failed updated attempt on the UI and this error is placed on the top of the error stack, above the one returned by workflow.

When the error is thrown/returned to the UI, they are popped from the stack from top to bottom, so we ended up with the WF error shown last.

(to be continued...)

Message 2

(Continued...)

The Object Manager is the caller and the WF is callee, the caller gets the error from the callee and appends it to whatever other error is has and displays it to the UI.

It is not possible to suppress the error message from OM. Please refer to Service Request #: 38-1005351951 in supportweb where the workaround is to invoke the WFP from a script, the End step in the Workflow Process can set a Process Property, containing the error message. When the workflow encounters the required condition, the Process Property is set containing the error message.

Change request 12-10D68P1 has been logged to address that the error messages should be enhanced:

1) Make the error messages more descriptive to indicate who/where they are coming from.

2) Change the order in which the errors are thrown to reflect the order in which they actually occurred.


Siebel Technical Support


No comments:

Post a Comment

Subscribe to: Post Comments (Atom)