RS01240: TABLEAU REPORTS DO NOT OPEN WHEN SCENARIO'S CULTURE HAS BEEN CHANGED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When an LNP scenario's culture has been changed, existing
    Tableau reports fail to open properly.  This happens because the
     custom report tables and default Tableau reports remain in the
    same language that the scenario was originally created in.  An
    error message similar to the following will be displayed:
    
    There was a problem connecting to the data source "Customer
    Sums Report":
    
    SQL Server database error 0x80040E37: Invalid object name
    'dbo.CustDetailCustomerSumsRpt'.
    The table "[dbo].[CustDetailCustomerSumsRpt]" does not exist.
    Unable to connect to the server
    "\\.\pipe\DAB8C487-6F-4D-40\tsql\query".  Check that the server
    is
    running and that you have access prvileges to the requested
    database.
    
    Would you like to edit the connection information?
    
    Yes | No
    
    Also, this error can be found in the application log (this
    example was taken from a Japanese OS):
    
    Tableau.exe application error occurs, 6100.11.724.1830 version,
    faulting module ntdll.dll, version 5.1.2600.6055, address
    0x00010a19 error occurs
    
    Steps to Reproduce:
    This example assumes that the original model was created using
    English as the User Interface Language.
     1. Open LNP and select a non-English language (Application
    button > Options > User Interface Language).
     2. Open an existing project with Tableau reports.
     3. Click Yes for version conversion if asked.
     4. Click Yes for culture conversion if asked.
     5. Open the Custom Reports dialog.
     6. Open the Customer Details report.
    
    What's wrong?  An error message is displayed.
    

Local fix

  • * If the scenario went through a version conversion and a
    culture conversion, you need to open the Custom Reports
    Management dialog (in the ribbon select Solution > Custom
    Reports), select File, and "Restore Default Reports."
     * If the scenario only went through a culture conversion, then
    you need to rerun the solver with "Generate Custom Report"
    checked in Optimization Parameters form.  Then, after the solver
    has finished running, you need to open the Custom Reports
    Management dialog, select File, and "Restore Default Reports."
    

Problem summary

  • This issue has been resolved and the fix will be available in
    IBM ILOG LogicNet Plus XE 7.2.24.30.
    

Problem conclusion

  • The fix is now available on FixCentral.
    

Temporary fix

Comments

APAR Information

  • APAR number

    RS01240

  • Reported component name

    LOGICNET PLUS X

  • Reported component ID

    5725A0200

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-18

  • Closed date

    2013-04-04

  • Last modified date

    2013-04-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LOGICNET PLUS X

  • Fixed component ID

    5725A0200

Applicable component levels

  • R720 PSY

       UP

  • R710 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM ILOG LogicNet

Software version:

720

Reference #:

RS01240

Modified date:

2013-04-04

Translate my page

Machine Translation

Content navigation