Skip to Content

After clicking on "Edit query Specification" option in Lumira Designer 2.0 SP02 it displays an error

HI Experts,

Environment details,

BI 4.2 SP04

Lumira Designer 2.0 SP02

Steps to reproduce the issue:

  1. login to Lumira designer.
  2. Create new Analysis applications. Choose data source for e.g. Universe (UNX),
  3. Click "Edit query Specification" option. It displays an below error.
  4. "Failed to create CMS session (See error log for details)"

Did a hosts file entries of the BO Server on the client machine but still the same issue.

Did IP binding on the BO Server but still issue persists.

Has any one faced this issue?

Log files is attached.desinger-error-log.txt

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 18, 2017 at 05:25 AM

    I had a similar issue after I updated from 2.0 to 2.0 sp2.I tried repairing but didn't helped.I uninstalled add-on and reinstalled fresh 2.0 sp2 full build and there was no problem.still don't know what is the root cause.

    Add comment
    10|10000 characters needed characters exceeded

  • Best Answer
    Sep 18, 2017 at 12:47 PM

    Yes, please see this SAP Note: https://launchpad.support.sap.com/#/notes/2521113

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 11, 2017 at 06:55 PM

    HI Vishnu/Tammy,

    We have been Facing similar Issue, where we Installed Lumira 2.0 SP2 on BI (4.2 SP3).

    we have uninstalled Lumira 1.0 and Did fresh Installation of Lumira 2.0 SP02. when we are trying to edit query specification in designer(related to universe) we are getting "Failed to Initialize Query Panel".

    Tried to do re-install Lumira 2.0 SP02 but no luck, can you suggest on this.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jawahar,

      thank you for reply.

      proxy settings like no proxy option is not there in Lumira Designer, SAP relapsed note for same error . where they mentioned to restart connection server32. after doing that to issue did not resolved.