Skip to Content
Webi.png Arrow.png WebiReports.png Arrow.png CheckClientTools.png

To exclude any application incompatibilities, test and compare the product behavior on different client machines.

This easy troubleshooting test is recommended every time, when you are experiencing functional errors or miss-behavior in the BI Launchpad or the Webi Rich Client.

Function problems in your client machine can be caused by an upgrade of the Windows environment, database driver/application/browser/Java version changes, new application installation or even some small configuration changes: e.g. select/view/edit Webi document, functions and buttons became not clickable etc.


When should you do this check?


E.g. Login to BI Launchpad and select HTML mode.

Now you want to create a Webi document based on a universe, but you cannot select any available universe from the universe list. The universe list acts as an image, and the cursor is shown as a cross:

  • Test the same steps on other client machines.
  • In case the same steps are working on the other machine, compare e.g. the installed operating system, the language locale, the installed applications, the browser and Java version etc.
  • Please, contact your IT Administrator Team, to detect and fix the changes in your environment.

E.g. You want to use the BI Launch pad in Java Applet mode.

When you are opening the Webi document, the process is significantly slower e.g. takes 2 minutes.

  • Test the same steps on other client machines.
  • In case the same steps are working on the other machine, compare e.g. the installed BI Client tool version, the browser and Java version, Java configuration, the CPU settings etc.
  • Please, contact your IT Administrator Team, to detect and fix the changes in your environment.

E.g. You want to refresh a Webi document in Webi Rich Client 3-tier mode, but you are getting error 10901.

    • Test the same steps on other client machines.
    • In case the same steps are working on the other machine, compare e.g. the installed BI Client tool version, the installed database middleware etc.
    • Please, contact your IT Administrator Team, to detect and fix the changes in your environment.

1. Login with your user profile to another client machine. (If possible, do it on 1-3 different machines.)

2. Test the same steps.

    1. a. In case the same steps are working on the other machines, compare the possible differences like the operating system (OS) version, language locale, installed applications, internet browser version and configuration, Java version and configuration, installed middleware, BI client tool version etc. Please, contact you IT Administrator Team, to detect and fix the changes in your environment.
    2. b. In case the you are getting the same product behavior, further troubleshooting steps will be needed like test with BI administrator rights and Enterprise authentication, or test with cleared browser and Java cache, test in different browser version etc.

How to become more professional?

See also:

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Jonathan Brown

    These are some good ideas Timo.  This type of troubleshooting will undoubtedly help narrow down the area to focus on when trying to fix an issue.  Good stuff!

    (0) 

Leave a Reply