Troubleshooting
Problem
Symptom
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:515)
at com.ibm.cognos.ccr.core.ui.databinding.widgets.AbstractControllableComposite.createController(AbstractControllableComposite.java:67)
at
<....>
Cause
- For more details, see separate IBM Technote #1600374
- For more details, see separate IBM Technote #1600374
- TIP: For another example, see separate IBM Technote #1618336
- For more details, see separate IBM Technote #481789
- For more details, see separate IBM Technote #1618336
- For more details, see separate IBM Technotes #1441171 & 1691901.
- For more details, see separate IBM Technote #1619686
- For more details, see separate IBM Technote #1636695.
- For more details, see separate IBM Technote #1646879.
- For more details, see separate IBM Technote #6116608 .
Environment
Controller database hosted on Oracle server.
The problem does not occur in all environments. In other words, keeping the default (unmodified) file "ccr-system-properties.properties" will work in most environments.
- By enabling the path in this file, then Controller's Java-based functionality will try to connect using the 'thin' protocol
- If the file/path is unmodified (the default settings), then those components will try to use the 'OCI'
TIP: For another example, see separate IBM Technote #1618336.
Diagnosing The Problem
... 68 more
Caused by: com.ibm.cognos.ccr.common.WebServiceConnectionException: exceptionId=ERR.ANY.WEBSERVICECONNECTIONEXCEPTION.CANNOT_EXECUTE_SERVICE, argument(s)=[FAIL: Message: Automation error
The remote procedure call failed. Source: FrJavaProxyB, http://servername/ibmcognos/controllerserver/CCRWS.asmx, ?]
at com.ibm.cognos.ccr.ccrws.JAXWSClient.executeTask(JAXWSClient.java:107)
Example - Scenario #6
FAIL:!java.lang.StackOverflowError!
Resolving The Problem
Copy database-specific JAR file onto Controller application server
- See separate IBM Technote #1600374.
Scenario #3
Specify the location of the TNSNAMES.ORA file in the ccr-system-properties.properties file in the ...Server\integration folder.
- Logon to the Controller application server as an administrator
- Locate the 'integration' folder. TIP: By default the 'integration' folder is here: C:\Program Files (x86)\ibm\Cognos\C10\Server\integration
- Open the file "ccr-system-properties.properties" inside Notepad
- Edit the file as appropriate.
Scenario #4
Configure System Variable "CCR_JAVA_Home" correctly.- See separate IBM Technote #1615017.
Scenario #5
Modify the file "ccr-system-properties.properties".- See separate IBM Technote #1618615.
Scenario #6
Correct invalid extended dimension structure.- See separate IBM Technote #1441171.
Scenario #7
Correct the Windows username/password used for the service "IBM Cognos Controller Java Proxy" on the application server.
- For more details, see separate IBM Technote #1619686.
Scenario #8
Ensure that either:
- There is no "CCRProxy.options" file
- or the "CCRProxy.options" file contains valid memory settings (e.g. 2Gb RAM or less for 32-bit JAVA)
- or convert the system to use 64-bit JAVA.
Optimise the Controller application server's Java Proxy service memory subsystem.
- For more details, see separate IBM Technote #1646879.
Scenario #10
Upgrade to Controller 10.4.2 IF1 (or later)
- For more details, see separate IBM Technote #6116608 .
Related Information
1600374 - "Could not create the view: !Could not create
481789 - "Could not create the view: !Could not create
1618336 - "Could not create the view: !Could not create
1618615 - "Could not create the view ... FAIL:!oracle/j
1441171 - Error 'Model not found in context: journalTyp
1619686 - "Could not create the view... Automation erro
1636695 - "Could not create the view: !Could not create
1646879 - "Could not create ... Caused by ...FAIL:!java
1691901 - "Could not create the view" when opening "Com
6116608 - "Failed to launch! ... java.lang.NullPointerException" launching Java…
Was this topic helpful?
Document Information
Modified date:
24 March 2020
UID
swg21612000