Troubleshooting
Problem
User clicks 'Maintain - configuration - Automatic Journals - Control Tables - Allocations', or another new Java based functionality such as 'Maintin - Jobs - Define'. User receives error message #1. Alternatively, user clicks "Maintain - Jobs - Define". User receives Error #2.
Symptom
Error #1
Error
Model not found in context: journalType
Unable to find instance of model of type: journalType, type interface com.ibm.cognos.ccr.journaltype.JournalTypeModel (load=DEFAULT)
exceptionID=ERR.ANY.WEBSERVICECONNECTIONEXCEPTION.CANNOT_EXECUTE_SERVICE, argument(s)=[http://SERVERNAME/cognos8/controllerserver/CCRWS.asmx, 010:b13d7e20-8a9d-11df-b32b-80ef7ef2ebe5:2913536545]
FAIL:!java.lang.StackOverflowError!
[OK]
Error #2
!model not found in context: job!
!unable to find instance of model of type: job, type interface com.ibm.cognos.ccr.job.jobmodel!
exceptionId=ERR.ANY:WESERVICECONNECTIONEXCEPTION.CANNOT_EXECUTE_SERVICE, argument(s)=[http://SERVERNAME/cognos8/controllerserver/CCRWS.asmx, MlsdfjbviKJERTxWENGDOEFOIJEFNVTYP]
FAIL:!java.lang.StackOverflowError!
Cause
NOTE:
- The error 'Model not found in context' is generic - there are a number of different potential causes for this.
- See separate IBM Technotes for examples.
- Similarly, when the 'FAIL' explanation message states 'java.lang.StackOverflowError' there are also several possible causes
This IBM Technote specifically relates to the scenario where the problem is caused by an invalid Extended dimension structure.
- For example, at least one member has itself as parent (causing a loop)
Environment
Note that this error can occur even when Extended Dimensions are not being used (i.e. they are all inactive).
- In this scenario, the member level still needs to be fixed, even though the entire Dimension is not in use.
Diagnosing The Problem
Run a "verify structures" report for each and every extended dimension (for example "ext dim 2" or whatever it is called) and check for errors.
- For example, you may receive the error "The level 0 is valid only for the total"
Steps:
- Launch Controller
- Click "Maintain - Special Utilities - Verify Structures"
- sdf
If the report contains a message similar to "The level 0 is valid only for the total" then you know that you are suffering from this problem in that 'bad' Extended Dimension (e.g. "Extended Dim 4"):
Resolving The Problem
Ensure that all extended dimension structures are valid.
- Remove or correct any invalid dimension members.
Steps:
- Click "Maintain - <BAD_DIMENSION_NAME> Structure - Change Table - Define/run"
- Open up the "Add/Delete" tab
- Enter the relevant code (from the error report - for example "OZ" and "OZDI" in the example above) and fill in the correct setting (e.g. "D" for Operation). TIP: See attached document "Screenprints.pdf" for how to fix an example case.
- Click the 'Run' (Play) button (to start the conversion. After a while the message "Conversion Finished" should appear.
- Afterwards, run the "Verify Structures" report again (against all dimensions, but especially the 'bad' extended dimension). There should be no error now.
- Test (i.e. click "Maintain - Jobs - Define"). TIP: The first time that this menu item is opened, it can take some time to appear. However, there should be no error.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21441171