Error while loading webi application

Java Plug-in 11.25.2.18
Using JRE version 1.8.0_25-b18 Java HotSpot(TM) Client VM
User home directory = C:\Users\Arjun
—————————————————-
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
—————————————————-

Resolution: 

Java.1.8.0_25 was uninstalled.

And Java1.7.0_67 was installed.

Advertisements

How to pass value of Input control to other tabs

Courtesy of David Lai:

Selected States:

=If( Pos(ReportFilterSummary(“Summary”);”State In List { “) > 0)
Then Substr(ReportFilterSummary(“Summary”);Pos(ReportFilterSummary(“Summary”);”State In List { “) + Length(“State In List { “);999)
Else “”

vVariable:
=If(Match([Selected States];[State]+”*”) Or Match([Selected States];”*, “+[State]+”*”) Or [Selected States]=””) Then 1 Else 0

One of the major limitations in Web Intelligence is the ability to use 1 input control to control filter selection for “All” tabs.

For example, if I had 5 tabs and wanted to have a country input control that is applied to all 5 tabs, I would need to create a separate input control for each tab.

In addition, if users want to filter on a particular country during runtime, they must REMEMBER to click through each andEVERY tab which is a huge hassle!

I’m not sure why SAP hasn’t provided an option to apply an input control to the whole document, but for now there’s a workaround that we can use.

Heres how to apply the workaround on a multiple selection input control.

In our example we will create a simple report that contains 3 tabs and 1 input control. We will filter on the country dimension with our input control.

Step 1

Since we can’t have the same input control repeat on multiple tabs, what I usually do is create a Summary tab that acts as a cover page as well as the control center for input controls.

Image link

Step 2

Create a variable that grabs the items the user has selected. To do this we do a simple substring using the appropriate positioning. The first part of the “IF” statement tells us that the user has selected items from the input control, therefore we do a substring. Otherwise “” means that the user wants to see everything.

=If( Pos(ReportFilterSummary(“Summary”);”Country In List { “) > 0)
Then Substr(ReportFilterSummary(“Summary”);Pos(ReportFilterSummary(“Summary”);”Country In List { “) + Length(“Country In List { “);999)
Else “”

Step 3

Create a filter that will filter the report elements based on what input control items are selected.

Every row whose country is in the selected variable will be marked as 1.

=If(Match([Selected Countries];[Country]+”*”) Or Match([Selected Countries];”*, “+[Country]+”*”) Or [Selected Countries]=””) Then 1 Else 0

You may be wondering why we have the 2 match statements in the beginning of the If statement. The reason is that the first match takes into account when an item is in the front of the list and the second match takes into when an item is not in the front.

One might ask why can’t we just have 1 match statement that says Match([Selected Countries]; “*”+[Country]+”*”). The reason is that words that have subset words will show up when they shouldn’t

For example “Democratic Republic of Congo” and “Republic of Congo” are 2 countries where the words in “Republic of Congo” are a subset of “Democratic Republic of Congo”. If we were to select “Republic of Congo” in our input control, it would also match “Democratic Republic of Congo” as a match because the * in front of [Country] would include the “Democratic” portion.

Step 4

On each of the report tabs, click on the analysis tab and then on the filter icon.

Drag the filter object on the panel and filter on values that are 1.

Image link

Image linkNow every time you make an input control selection, the 2 report tabs will filter on your selection appropriately.
[/img]

JavaScript error while calling onChangeDocID

com.sap.webi.client.toolkit.exception.WIException: JavaScript error while calling “onChangeDocID”
at com.sap.webi.client.toolkit.exception.WIExceptionFactory.create(WIExceptionFactory.java:18)
at com.sap.webi.ui.jrp.JRPUtil.callJSOnEDT(JRPUtil.java:183)
at com.sap.webi.ui.jrp.JRPUtil.callJS(JRPUtil.java:154)
at com.sap.webi.ui.jrp.JRPUtil.onChangeDocID(JRPUtil.java:54)
at com.sap.webi.ui.context.managers.DocumentManager.openDoc(DocumentManager.java:167)
at com.sap.webi.ui.tasks.workflows.NewDocumentWorkflow.openDocument(NewDocumentWorkflow.java:399)
at com.sap.webi.ui.tasks.workflows.NewDocumentWorkflow.getNextTask(NewDocumentWorkflow.java:378)
at com.sap.webi.ui.tasks.workflows.DocumentWorkflow.getNextTask(DocumentWorkflow.java:163)
at com.sap.webi.toolkit.ui.tasks.TaskWorkflow.startNextTask(TaskWorkflow.java:63)
at com.sap.webi.toolkit.ui.tasks.TaskWorkflow.propertyChange(TaskWorkflow.java:90)
at java.beans.PropertyChangeSupport.fire(Unknown Source)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at com.sap.webi.toolkit.ui.tasks.WebITask.firePropertyChange(WebITask.java:66)
at com.sap.webi.toolkit.ui.tasks.WebITaskManager$TaskPCL.propertyChange(WebITaskManager.java:275)
at java.beans.PropertyChangeSupport.fire(Unknown Source)
at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.SwingWorker$SwingWorkerPropertyChangeSupport.firePropertyChange(Unknown Source)
at javax.swing.SwingWorker$SwingWorkerPropertyChangeSupport$1.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
at sun.swing.AccumulativeRunnable.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: netscape.javascript.JSException: JavaScript error while calling “onChangeDocID”
at sun.plugin2.main.client.MessagePassingJSObject.newJSException(Unknown Source)
at sun.plugin2.main.client.MessagePassingJSObject.waitForReply(Unknown Source)
at sun.plugin2.main.client.MessagePassingJSObject.call(Unknown Source)
at com.sap.webi.ui.jrp.JRPUtil.callJSOnEDT(JRPUtil.java:178)
… 35 more

Account information not recognized: Could not reach CMS ‘:6400’.

Error: Account information not recognized: Could not reach CMS ‘<machine name>:6400’. Specify the correct host and port and check for network issues. (FWM 20030)

Resolution: Restart the SIA

[repo_proxy 49] SessionFacade::checkLicenses – the current user hasn’t got the rights to use this application

[repo_proxy 49] SessionFacade::checkLicenses – the current user hasn’t got the rights to use this application

Reason : License Expired

Untitled

The root server reported an error Initialization Failure. (Reason: CMS system database is overloaded, please try again.

Error:

The root server reported an error Initialization Failure. (Reason: CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027)CMS system database is overloaded, please try again. If the problem persists, please contact the system administrator(FWB 00027)

Cause

Timeout while waiting for database resources.

Resolution

  1. On the server machine, navigate to Central Configuration Manager (CCM).
  2. Stop the Server Intelligence Agent (SIA).
  3. Go to the properties of the SIA.
  4. Navigate to ‘Startup’ tab.
  5. In the ‘Local CMS’ section, double click on the Central Management Server, a ‘Server Properties’ dialog box would appear.
  6. Add the switch -ndbqthreads 10 -maxobjectsincache 100000 at the end of the command line.
  7. Start the SIA.

1339944 – How to delete an unused Node that is listed in the Central Management Console

SAP NOTE:

Symptom

l You need to remove an unused Node from the Server List in the CMC, e.g.:
¡ Node of another deployment after migrating one environment to the other, or
¡ Node associated with a Server Intelligence Agent that no longer exists or is no longer available
l Note: If the Server Intelligence Agent still exists, delete it from within the Central Configuration Manager to unregister it the proper way. These instructions are for those situations where there is no SIA, but an entry in CMC is still seen.
Environment
l SAP BusinessObjects Enterprise XI 3.1
l SAP Business Intelligence Platform 4.0
Reproducing the Issue
1. Having two separate deployments A and B, Create a BIAR file using Import Wizard from deployment A: export all servers and server groups
2. Import the BIAR into deployment B using Import Wizard
3. Stop all services in Deployment A
4. Logon to CMC in Deployment B and navigate to Servers > Nodes:
– a Node pertaining to deployment A is displayed in the Nodes list
– there are no options to delete such node
Resolution
Please note: the below procedure will not delete the Servers associated to the SIA Node that you will deleted.
Hence, delete the services inside the SIA/NODE manually from CMC first. Then move on to the below steps.
NOTE: Before making any changes to the CMS database, it is highly advised to take a full backup of the CMS DB and Filestore.
1. Logon to the Central Management Console
2. Navigate to Servers > Nodes
3. Locate the Node you want to delete and select it
4. Go to the Properties page for the selected Node
5. Take note of the CUID of the SIA
6. Logoff from the CMC
7. Stop all BO Services
8. Make a backup copy of the CMS System Database
9. With the proprietary database client (e.g., SQL Plus for Oracle), connect to the CMS System Database
10. Execute the SQL statement:
¡ BOE XI 3.1: ‘DELETE FROM CMS_INFOOBJECTS6 where SI_CUID = ‘CUID name from step 5’
¡ BO BI 4.X: ‘DELETE FROM CMS_INFOOBJECTS7 where SI_CUID = ‘CUID name from step 5’
11. If the Database Engine requires it, commit the changes
12. Start the BO Services.