The Dashboards application crashes when we try to launch Dashboard Designer on a machine where secured web access or proxy settings are applied.

/wp-content/uploads/2014/07/error_491915.png

    

When the Dashboards application is launched, the startup page of the designer connects to the internet ( www.sap.com, www.businessobjects.com etc) . This causes Designer to crash when security for web access is applied or due to proxy settings.

Dashboards_startuppage1.JPG

     We can disable this security access manually.

     Following are the steps which restrict the designer to access the web.

  1. Go the following folder Dashboards Installation dir\Program files\SAP BusinessObjects\Xcelsius 4.0\assets\startPage\en\js
  2. Open the javascript file start_function.js
  3. Search for the function onInitialize()
  4. Comment line : InitializeResourcesTag()

Start_function.JPG

   5. Save the file.

   6. Re-launch Dashboard designer.

Dashboards_startuppage2.JPG

To report this post you need to login first.

5 Comments

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

  1. Amit Anant Kulkarni

    Thanks Noopur for sharing this information.

    This is really helpful in troubleshooting the issues in which we are sure that the Dashboards is installed by following all the best practices however still we get the error.

    (0) 
        1. Amit Anant Kulkarni

          Hi Ahmed,

          Go to SAP Dashboards assets folder (By default
          “C:\Program Files (x86)\SAP BusinessObjects\Xcelsius 4.0\assets”)

          Rename folder “startPage” to another name like
          “startPage_change”

          Launch SAP Dashboards again. kill orphan Excel.exe
          process beforehand if needed.

          Let me know how you did resolve the issue.

          Regards,

          Amit

          (0) 
  2. Stephen Tarrant

    I found that the line RefreshMRUTables has to be uncommented.  Once I did that it worked OK.  It does mean the MRU list won’t be displayed.

    If someone can work it out, it would probably be a problem with the place the MRU list is expected to be found has changed in Windows.

    (0) 

Leave a Reply