Purpose

This page describes the procedure customers should follow when experiencing issues with Lumira Designer.

Basic Checks

	Check whether you have installed the newest Lumira Designer release according to SAP Note 2465894.
	Read the release limitations notes related to your Lumira Designer version: Lumira Designer 2.4: SAP Note 2810656 Lumira Designer 2.4 Patch 5: SAP Note 3145626 Lumira Designer 2.4 Patch 5 and compatibility with BIP releases: SAP Note 3251932
	If the error occurs only when connected to BI Platform (and not in local mode), read SAP Note 1894504 in addition.
	If the error occurs only when connected to SAP NetWeaver (and not in local mode), read SAP Note 1894594 in addition.
	If the error occurs only when connected to SAP HANA (and not in local mode), read SAP Note 2154859 in addition.
	Read the Administrator Guide: SAP Lumira, especially the configuration and troubleshooting sections.

Designer Version in DS_Support.zip

Troubleshooting

X.509 Configuration on BIP

In case you get such errors in the Designer when authenticating with BIP through X.509 certificates:

Caused by: com.businessobjects.dsws.session.DSWSException: The syntax for the specified CMS name is invalid
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

then apply the following steps on the server:

1. Configuring the axis2.xml File
2. Generating a Shared Secret Value
3. Configuring web.xml File

Download BIP Lumx and run in local mode

These images explain how to download a LUMX from BIP so that it runs in local Designer mode i.e. without any login to BIP. This is important in support in order to avoid any influence of BIP settings (be it user specific, or connection specific stuff) on the scenario.

1. Run the Designer logged into BIP and export the app(s) from the LUMX via a Support ZIP
   
   
   
2. Open the Support ZIP and copy the LUMX into the Lumira Documents folder
   
   
   
   
   
3. Restart your Designer and skip the logon to BIP. Open the app from the Local Documents folder NOT from (Offline) BI Platform...
   Map all BIP connection to SAPLOGON / Designer Hana connections like so:
   
   
   

Starting the GA template via Execute Locally with Parameters

To reproduce issues in the Designer it is sometimes necessary to start a Generic Analysis template with its parameters specifying the data source properties:

XSYSTEM, XQUERY, XTYPE

On BIP the XSYSTEM has this syntax  cuid:<cuid>

But executing locally in LUMX mode it works the following way:

At first add your connection to the LUMX document. Then go to the On-Startup handler e.g., and add a DS_1.assignDataSource. Press Ctrl-Space to get the completion dialog and chose the connection chooser. Then select the newly added connection.

Finally you will see an index in this example "2" which represents this connection.

Then choose Execute Locally and append the following to this URL:

&XSYSTEM=2&XTYPE=BW&XQUERY=<my-query-name>

Test Web Service and Restful Service

In case you face issue with login (Lumira Designer is using Web Service) or creating LUMX document (Lumira Designer is using Restful WS) you can easily test the 2 URLs in Chrome. The results should look like this: Use Chrome to achieve the same output.

The restful URL must show this kind of XML when correctly configured:

And the web service URL must show this message if correctly configured:

Create Fiddler of Designer WebService and Restful WebService calls

Open your SapLumiraDesigner.ini and add the 4 +2 bold lines at the same position:

 jre/bin/SapLumiraDesignerVM.exe
-aadProxyHost
localhost
-aadProxyPort
8888
-vmargs
-XX:+HeapDumpOnOutOfMemoryError
...
-Dsun.net.client.defaultConnectTimeout=88000
-Dhttp.proxyHost=localhost
-Dhttp.proxyPort=8888
-Xmx4g
...

Then start Fiddler and afterward the Lumira Designer. Be aware that the password is part of the Fiddler. You can just delete the items recorded during login in Fiddler or search for the Password and delete all matching lines.

The final Fiddler should contain:

A) Web Service URLs

http://host:port/dswsbobje/services/BIPlatform

B) Restful Web Service URLs 

http://host:port/biprws/lumxserver/v1/document

IMPORTANT: read chapter Fiddler Tunnel Requests

Failed to create remote document (404)

com.sap.ip.bi.zen.connectivity.ConnectivityException: Failed to create remote document "test_lumira"
...
Caused by: com.sap.ip.bi.zen.connectivity.ConnectivityException: org.apache.http.client.ClientProtocolException: Unexpected response status: 404
    at com.sap.ip.bi.zen.backends.lumx.DocumentServer.createDocument(DocumentServer.java:1510)
    at com.sap.ip.bi.zen.backends.lumx.LumxSystem.createDocument(LumxSystem.java:1263)
Caused by: org.apache.http.client.ClientProtocolException: Unexpected response status: 404
    at com.sap.ip.bi.zen.backends.lumx.RestfulWsHelper.uploadLumxDocument(RestfulWsHelper.java:94)
    at com.sap.ip.bi.zen.backends.lumx.DocumentServer.createDocument(DocumentServer.java:1507)

Verify that in CMC that the "Restful web service" application's host name is the Lumira server host

Fix Layout after Migration to SAPUI5 m Mode

https://blogs.sap.com/2017/11/03/design-studio-fix-layout-after-migration-to-sapui5-m-mode/

You are missing members when using context menu

The No. 1 candidate is the new setting of the context menu that came with 1.6 SP x.

Be aware that there is a known bug that returns MaxNumber - 1 members only, e.g., 99 instead of default 100.

Design Tool Installation - SAPSetup Guide

The design tool installation is done with the SAPSetup Wizard. For more information, see chapter "Installation" in the Administrator Guide: SAP Lumira.

For more information about the SAPSetup Wizard, see the SAPSetup Guide:

Start the design tool installer with the following parameter:

SapDsSetup64.exe /extract:.\extractFolder

The SAPSetup Guide is available in the extractFolder.

Problems During Startup

• If the Lumira Designer client does not start, perform the following steps:
  1. Uninstall the Lumira Designer client and delete the whole installation directory in case there is something left: C:\Program Files\SAP Lumira\Lumira Designer
  2. Rename the following two folders:

     • C:\Users\xxx\LumiraDesigner-config

     • C:\Users\xxx\LumiraDesigner-workspace

  3. Reinstall the Design Studio client.
• If you encounter problems during startup, switch off the Antivirus temporarily, then test with an administrator user. If this works, you can find missing rights with the help of the SysInternals AccessChk tool:
  

  accesschk -s <yourUser> "C:\Program Files\SAP Lumira\Lumira Designer"

  or
  

  accesschk -s <yourUser> "C:\Program Files\SAP Lumira\Lumira Designer" 

  Make sure that for all files and folders you have at least read permissions. Additionally, you can use the -n option to "Show only objects that have no access". Please compare the output of a working user and a non-working user. 

• If Lumira Designer shows the splashscreen for a short time, but the application does not come up (or the application comes up with a completely broken user interface), and the error log contains an entry like the following:

  java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.UnsatisfiedLinkError: <some path...>\sapjco3.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform   

  then a conflicting sapjco3.dll exists on your system, which took precedence over the Lumira Designer packaged DLL. The solution is to append the following line to SapLumiraDesigner.ini:

  
  -Djava.library.path= 

  
  followed by a line break. This sets the java.library.path system property to the empty String, eliminating external effects caused by the Windows PATH variable.

• If during startup a popup with "Failed to create Java Virtual Machine" appears, your VM might have run out of memory.

Try to reduce the memory settings step by step:

• • Change the parameter -Xmx in the file SapLumiraDesigner.ini in the Lumira Designer installation directory, e.g., from "-Xmx1024m" to "-Xmx768m".
  • Restart LumiraDesigner.

This value had to be increased with Design Studio 1.2 SP01 from 512 to 1024 (Xms from 128 to 256, MaxPermSize from 384 to 512). Consider switching to a 64 Bit OS in case of insufficient memory.

• If the design tool displays a "Collecting Garbage" error message, then a reduction of the two memory values mentioned above can also help.

SSLException creating document (DS >= 2.0)

In case you face an error
Caused by javax.net.ssl.SSLException: hostname in certificate didn't match: ....

Solution: please verify your WACS URL in the CMC.

Instantiating Data Sources

If you encounter errors instantiating data sources, please check your etc./services file on the server or desktop (local mode).

Hints in the trace file are:

service '?'

Connect to message server host failed.

SAP HANA Hierarchies

You have issues / crashes with a hierarchy defined in SAP HANA Studio: Note that not all HANA hierarchy features are supported in Design Studio. For more information, see SAP Note 2038663.

SAP HANA HTTP Connections (Design Studio 1.5)

You use Design Studio 1.5 and consuming SAP HANA HTTP data sources gives the following error message: SQL Error : insufficient privilege: Not authorized at ptime/query/checker/query_check.cc:3290. This indicates that there are additional privileges required for the SAP HANA user. For more information, see SAP Note 2141541. 

You use Design Studio 1.5 and consuming SAP HANA HTTP data sources causes HTTP error 404 or 403. Make sure that the Info Access Service is imported on your SAP HANA server. For more information, see Importing the Info Access Service.  

To create HTTP Traces of the INA protocol with Fiddler (Note 3278768) change the following preferences in the Design Studio client:

Note: If Fiddler does not show any traces with Lumira then you can add the 2 proxy lines the Designer's or Discovery's INI file after this existing line:

-XX:+HeapDumpOnOutOfMemoryError

-Dhttp.proxyPort=8888
-Dhttp.proxyHost=localhost

If you are not allowed to change the INI because you are not administrator, then you do the following.

Make a copy of Designer or Discovery INI file which from the installation folder into a directory where you are allowed to edit it, e.g. Desktop.
Then add the above lines at the end of the INI file and save.

Finally create shortcut to Designer or Discovery Executable and add this parameter in the properties:

--launcher.ini "C:\Users\USFAOSSupt03\Desktop\MyFiddlerCopy.ini"

IMPORTANT: you have to use Execute Locally to use the INA client implementation in the Designer firing the HTTP requests to the server through Fiddler. If you run the application on BIP then the BIP Lumira Addon will fire the HTTP requests and you will not record them on the client.

Now start at first Fiddler (otherwise nothing works) and then the new shortcut.

In Fiddler you can filter for /ina/ requests like this:

Then your recording should look like this:

Fiddler Tunnel Requests

In case Fiddler does not show any requests or only Tunnel requests containing /ina/ in the URL and your INA connection you are using HTTPS, then try the following:

In case all these efforts do not help, and you still have tunnel requests, a look into the Fiddler log might reveal the root cause. So, if you are an expert with HTTPS, you might know a workaround. In case not you have to enable HTTP temporarily and gather the Fiddler traces with HTTP.

Retrieve Connection Properties via Query Builder

When you analyze the HTTP communication of the Designer with Fiddler via INI parameter:

-aadProxyHost
localhost
-aadProxyPort
8888

you can figure out the SELECT queries that are sent to the platform for retrieving all connection properties.

In case of problems this can be done with the Query Builder as well.

Be aware that the Design Studio Designer fetches all connections immediately after login with 1 HTTP request, but Lumira Designer fetches them when you open the Add Connection dialog, i.e., when they are shown to the end user. Another difference with Lumira is that it fetches only the connections for the current selected folder (for performance reason).

Fiddler will show the SELECT statements and they will look like this (in this example Lumira Designer 2.1):

Then start the query build tool (For details about the tool https://blogs.sap.com/2013/06/17/businessobjects-query-builder-basics/)

http://myhost:portAdminTools/querybuilder/ie.jsp

Now copy/paste the SELECT statement from the above XML and submit it.

The CUID in the statement is the CUID of the folder where the problematic OLAP connection resides in. You can look up each CUID in BI launchpad.

The query in this example is:

SELECT STATIC FROM CI_APPOBJECTS WHERE SI_PARENT_CUID='AfxsOYKlrXhBorv5WlhhOh4' AND (SI_KIND='Folder' OR SI_KIND='CommonConnection')

The result looks like this:

If you are looking for the properties of a specific OLAP connection, you can look up the CUID of the connection and then fire this statement replacing the CUID with yours:

SELECT STATIC FROM CI_APPOBJECTS WHERE SI_CUID='AdicTrWD9tVHsc_ZDjVSVxs'

No Local Connections Available

If no local connections are shown in the Design Studio client, this can be caused by not finding the saplogon.ini file. If the INI file is stored in a "non-standard" location or is stored in a virtual application, you can specify the location by adding these two lines to SapDesignStudio.ini:

-aadSaplogoniniPath
<path to your ini file copy>

IMPORTANT: Add them directly before the -vmargs line. Note that there must be a line break separating the argument from its value. If the path denotes a folder, the file name inside that folder must be "saplogon.ini". The path can also directly point to a file. In this case, you can choose the file name individually.

For trouble shooting please analyze the Debug logs like this:

Single Sign-On (SSO) Problems

If you have issues with SSO using SNC with the design tool, read chapter "Authentication and Single Sign-On in Local Mode" in the Administrator Guide: SAP BusinessObjects Design Studio.

For Kerberos configuration please also read these notes / KBAs:

1992282 - How to setup Windows AD SSO into Design Studio using the BI Platform add-in

1769179 - How to configure KERBEROS login on Business Intelligence Platform (with Java test program)

SSO to BW in Designer fails as of Designer 2.2

This issue is caused by the combination of SNC setting for a BW system in CMC and the usage of SSO for an OLAP connection to the same system.

Workaround 1: switch off temporarily SSO and use a hardcoded user password
Workaround 2: switch off SNC for this system

Solution: 2701524 - SSO-configured OLAP connections do not work in Lumira Designer 2.2

HTTPS / SSL

Read the following notes

1807142 - How to enable HTTPS/SSL Designer against BIP

2154860 - Troubleshooting HTTPS / SSL issues with Design Studio

Codepage Issues

If you have codepage issues in applications on BI platform and SAP NetWeaver at runtime (wrong characters being displayed at runtime, filters on members with non-ASCII characters in their name not working), see SAP Note 2216929.

BIAL Script Validation Errors

If you encounter BIAL Script validation errors, read SAP Note 2079054.

"No More Handles" Error Analysis

If you get the error "SWTError: No more handles", proceed as follows:

1. Start your task manager and click on the Processes tab.
2. Choose menu item View/Select Columns.
3. In the Select Process Page Columns dialog box, select Handles, User Objects and GDI Objects and click OK.
   • 

4. Sort the process list by Image name and select the design tool process SapDesignStudio.exe (with Design Studio >= 1.4 observe the corresponding javaw.exe process).

5. Work with your design tool for a while and execute at least each step once. Then write down the handles number and observe whether you can find steps after which the handles always grow with a significant amount.
   Normally handles are allocated and after finishing a certain step e.g., by closing of windows, dialogs, applications they are released again with a short delay. But if the number grows when repeating a step 5-10 times always in more or less the same magnitude, then this might indicate an error. 

JavaScript Errors

1. Start Internet Explorer, press Alt-X and choose Internet Options.
2. In the Internet Options dialog box, deselect the following two JavaScript settings and check the Display notification setting.

   • 

3. Close the design tool and all Internet Explorer processes.
4. Re-start the design tool and check whether a Javascript error is shown.

Issues With Preview and/or Execute Locally

If the preview in the design tool and "Execute locally" do not show any analysis application but instead an empty page or errors like "This page can't be displayed", proceed as follows:

1. Disable Antivirus and Firewall temporarily.
   We had already issues with antivirus tools blocking the loading of all Javascript files only inside Design Studio client.
2. Choose Execute locally and copy/paste the URL into a different Web browser like Chrome or Firefox and test the application with this browser.
3. Install a VM with a new Windows OS and design tool installation and compare this with the non-working system.
4. Try different ports: You can configure them in the design tool on the Preferences page under Embedded Web Server.
5. Analyze the ports of the design tool:

For example, you can use the Sysinternals TCPView to look at the local ports that are used by the internal Web Server (jetty) inside the design tool.

Here is the port used by the design tool (can be changed on the Preferences page):

And here TCPView shows that the design tool is LISTENING on port 7777.

Furthermore make sure that your IE is configured in a way that it does run in IE mode 11:

As the preview inside the Designer is also an IE control it can have the same limitations as the standalone Internet Explorer. Choose execute locally and run the application in IE and the press F12 and verify the mode. Important you have to use the localhost URL to achieve the same scenario as in the preview.

The Enterprise Mode feature might cause issues here:

https://docs.microsoft.com/en-us/internet-explorer/ie11-deploy-guide/what-is-enterprise-mode

Analysis Applications with MIME Objects

Depending on which platform and release version you use, note the following:

Design Studio >= 1.3 in BI Platform Mode

• For CSS and images, use the Open CSS or Open Image dialog of the design tool's property sheet.
• For other MIME types like TTF, use the Open CSS dialog:

1. Click the Upload Local CSS button.
2. In the file selector, enter e.g., *.ttf after the file name and select your MIME object.

Note: Other extensions than CSS will not appear at all in the Open CSS dialog. MIMES without path used in a CSS must be uploaded to the same folder as the CSS.

Design Studio <= 1.5 in SAP NetWeaver Mode

You need to upload all MIME objects manually in the ABAP Workbench of the BW system.

Note: MIME objects without path used in a CSS must be uploaded to the same folder as the CSS.

For more information, see "Uploading Images to the MIME Repository" in the Administrator Guide. SAP BusinessObjects Design Studio based on SAP NetWeaver at http://help.sap.com/boall > English > all products: Design Studio.

Design Studio >= 1.5 in SAP NetWeaver Mode

Depending on the SAP NetWeaver release version, there are different ways to upload the images:

• You upload the images in the design tool.

  For more information, see chapters "Image" or "Button" in the Application Designer Guide: Designing Analysis Applications, under Help > Help Contents in the design tool.

For more information about the required SAP NetWeaver release versions for direct upload in the design tool, see SAP Note 2111546.

• You upload the images in the ABAP Workbench of the BW system. For more information, see "Uploading Images to the MIME Repository" in the Administrator Guide. SAP BusinessObjects Design Studio based on SAP NetWeaver at http://help.sap.com/boall > English > all products: Design Studio.

Design Studio <= 1.5: How to Find Out Which MIME Objects Are Used In Your Application:

1. Create your analysis application in local mode.
2. Choose Application > Open Repository Folder.
3. Open the XML file content.biapp in your application folder with a text editor.
4. Search the file for CSS and images.
5. Check if the CSS files reference other MIME objects like fonts.

For example, NEW_DESIGN_FONT.css used in the templates of the design tool references SAP-icons.ttf and SAP-icons.eot.

Design Studio >= 1.5: How To Find Out Which MIME Objects Are Used In Your Application:

With Design Studio >= 1.5, when exporting analysis applications in the Export Application dialog box, the system analyzes the selected application and auto-detects all MIME objects referenced by the application (including MIME objects referenced by script coding). For more information, see chapter "Exporting Analysis Applications" under "Advanced Design Tasks" in the Application Designer Guide: Designing Analysis Applications, under Help > Help Contents in the design tool.

SDK component is not updated in the Designer or Platform

Make sure that you are using a version number with a "qualifier" as the last part of the number, e.g.

1.0.0.qualifier

This guarantees, that Eclipse during generation process replaces the qualifier place holder with an increasing version number.

This can be found in the feature.xml as well as in the manifest.mf.

Further info can be found in the SDK docu:

https://help.sap.com/doc/businessobject_product_guides_aad16_en_ds_16sp01_dev_guide_en_pdf/1.6.1.0/en-US/ds_16SP01_dev_guide_en.pdf

Known Issues

Non-sticky Load balancer leads to 401/500

In case you are using a load balancer between your Designer and your Tomcat/web server, then you must make sure that all requests from the Designer go to the same Tomcat. Otherwise, you might face this kind of error:

com.sap.ip.bi.zen.connectivity.ConnectivityException: org.apache.http.client.ClientProtocolException: Failed to obtain RESTful WebServices logon token, response status: 500, reason:
Caused by: org.apache.http.client.ClientProtocolException: Failed to obtain RESTful WebServices logon token, response status: 500, reason:
at com.sap.ip.bi.zen.backends.lumx.RestfulWsHelper.retrieveRestFulWebServicesToken(RestfulWsHelper.java:125)
at com.sap.ip.bi.zen.backends.lumx.RestfulWsHelper.uploadLumxDocument(RestfulWsHelper.java:55)
at com.sap.ip.bi.zen.backends.lumx.DocumentServer.uploadDocumentInternal(DocumentServer.java:1530)

Saving LUMX document leads to 401 error

 Caused by: org.apache.http.client.ClientProtocolException: Unexpected response status: 401
at com.sap.ip.bi.zen.backends.lumx.RestfulWsHelper.uploadLumxDocument(RestfulWsHelper.java:94)
at com.sap.ip.bi.zen.backends.lumx.DocumentServer.uploadDocumentInternal(DocumentServer.java:1534)

The root cause is a bug in the Lumira software caused by special chars in the LUMX document name like '%' or '&'

Workaround: use only alphanumerical chars for a test (a-z, 0-9,)

Designer is slow

Symptom: an extremely slow startup.

 Please check whether your task manager Details tab show similar heavy load on Windows Defender MsMpEng.exe process:

If the majority of CPU consumption is SapDesignStudioVm.exe then please do the following tests:

1. disable temporarily Antivirus and Firewall
   Restart the Designer and verify whether it has an effect. If this has an effect, contact your Antivirus or Firewall vendor.
2.  If not, install a new Windows on a VM e.g., and before installing any other software install the Designer and test again This worked fine inside SAP network.
3. If this works fine, then add additional software like security products one by one and test after each installation again.

Others

• If your data source has an initial view configured, and changes to the data source in the backend (BW or HANA system) are not reflected in your application or even make the application crash at runtime, read SAP Note 2154750.
• BI Platform mode only: If after the import of an application containing Universe-based data sources the data source fails to initialize even though you mapped the Universe in the import wizard correctly, read SAP Note 2286208.
• If you have performance related issues, read SAP Note 1931691.
• If the design tool crashes, read SAP Note 2021164.
• As of Design Studio 1.4, there is an issue with SAP JVM and Kerberos. For more information, see SAP Note 1769179.
• In case of 60s timeouts against Hana data sources of see Support for SAP HANA System
• In case of timeouts (com.sap.ip.bi.zen.connectivity.ConnectivityException: Read timed out) against BIP in the Designer read note 2125471
  

Related SAP Notes

SAP Note 1773751: Design Studio - Support Note for Client

__________________________________________________________________________________________________________

Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.