We are receiving below error code while opening one project in 14.3 Clarity:
We have found the root cause of the error.
The "Request Status" of one of the Team Member had "Rejected" value. This value is not available in OWB - request status lookup values.
So, it threw error "not in enumerated list".
That looks like a problem with a static LOOKUP ; does the data for your problem project contain any values in any static lookup fields for which there are not values in the relevant lookup (obviously this should not happen, but could happen if you have ever been messing about with lookup definitions via XOG or on the database)
I will check all the project fields which uses lookup and see values are valid. One more user has got below message for the same project:
Can this be related to same lookup issue?
No idea - sorry.
(I've only guessed at it being a LOOKUP issue because "enumeration" is the term the application uses to describe the structure of a numeric lookup ; when OWB opens a plan it tends to pull in all the data associated with any static lookups so that you can change values in OWB (for dynamic lookups it doesn't bother so these are readonly in OWB). I'm just guessing that there is some mismatch between the lookup definition (values and enumeration) and the project's data)
I am trying to enable OWB trace in my system but its not working. Below are the environment variables I have added after referring the KB document of it:
Is anything else I have to do to enable trace?
Also, our clarity version is 14.3 and OWB pack available in PPM is x86 type. Does this work in 64-bit system?
Regarding the second error
a server error occurred during login %s - string index out of range: -1
suggests two things to check in
Error While opening project in OWB 2.1.1 from Clarity v13.3
Regarding the first error one reason for that is expected to be fixed as it occurred in 7.5.3 and the KB article TEC439766 is now retired.
However, bugs seem to have incarnations.
Are you using non US setting is OWB and do you have mixed booking?
KB ID: 8416.00000
Doc Type [BUG]
Last Reviewed 07/20/2007
Subject: OWB: German\French regional settings only: mixed booking status causes - Unable to open project XXXXX. Invalid Value - not in enumerated list:.
Keywords: b96957, invalid value, mixed booking, french, german
Initial Product: Clarity 7.5.3
Did this article
help solve your issue?
OWB 7.5.3 and 8.0.x
BUG #96957 - OWB: German\French only booking status causes - Unable to open project XXXXX. Invalid Value - not in enumerated list:.
Projects containing team members with mixed booking status will not open in OWB when the workstation regional settings are set to French or German.
The following line is missing in the pr.team_fr.xml and pr.team_de.xml files:
<ExtendedPropertyData key="10" valueClass="com.abtcorp.core.ABTString" valueString="Mixed"/>
<PropertyData name="Booking" caption="Statut de rÃ©servation">
<ExtendedPropertyData key="0" valueClass="com.abtcorp.core.ABTString" valueString="Inconnu"/>
<ExtendedPropertyData key="5" valueClass="com.abtcorp.core.ABTString" valueString="Optionnel"/>
<ExtendedPropertyData key="15" valueClass="com.abtcorp.core.ABTString" valueString="Ferme"/>
1. Install OWB using the French or German option.
2. In Clarity go to Admin Tools > Project management > Settings
3. Select Mixed Booking and click Save
4. Create a project, add a resource with mixed booking
5. Open the project in OWB
Expected: the project to open without error
Actual: you get the following error: Unable to open project XXXXX. Invalid Value - not in enumerated list:
Extract the pm.team_fr.xml\pm.team_dr.xml file from the RuleBase.jar file (located in the workstation folder C:\Program Files\Open Workbench\lib) to the folder C:\Program Files\Open Workbench\lib\RULEBASE.
Open the pr.team_fr.xml\pm.team_dr.xml file with notepad and insert the missing line. Save the file.
The bug is in development being reviewed.
Ung???ltiger Wert - nicht in aufgez???hlter Liste
Valeur invalide - ne figure pas dans la liste Ã¯Â¿ÂƒÃ¯Â¾Â©numÃ¯Â¿ÂƒÃ¯Â¾Â©rÃ¯Â¿ÂƒÃ¯Â¾Â©e
English version of the error:ABTError:
Invalid Value - not in enumerated list
New ABTException:Invalid Value - not in enumerated list
com.abtcorp.core.ABTException: Invalid Value - not in enumerated list
at com.abtcorp.io.repostream.populators.Populator.setPropertyValues(Unknown Source)
at com.abtcorp.io.repostream.populators.TeamPopulator.populate(Unknown Source)
at com.abtcorp.io.repostream.populators.ObjectPopulator.createTeam(Unknown Source)
at com.abtcorp.io.repostream.populators.ObjectPopulator.processDataPackage(Unknown Source)
at com.abtcorp.io.repostream.populators.ObjectPopulator.populateProject(Unknown Source)
at com.abtcorp.io.repostream.RepoStreamWorker.populate(Unknown Source)
at com.abtcorp.io.repostream.StreamDriver.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Site: update ChargeCodes property
back from actual driver call
Really useful when TEC articles vanish isn't it.
Google revealed another vanished (v7.5.3) TEC article with a similar message; http://webcache.googleusercontent.com/search?q=cache:8TD8h00n_b0J:customerconnect.ca.com/cc/kbtech%3Fdocid%3D438852%26se… (not sure if that link will work) - it is/was TEC438852 and says that the problem is
"The SRM_PROJECTS.CREATED_BY and\or SRM_PROJECTS.LAST_UPDATED_BY field contains reference to an ID that is not in the CMN_SEC_USERS TABLE."
Thank you everyone for the suggestions.
I have checked, we use mixed bookings but other projects with mixed bookings are opening fine. Only this project have the issue.
Also, enabled OWB logging but no error is coming in the log file. Only data read from Clarity is stopped while extracting TEAM records.
How to check the error in OWB console?
More GUESSes : Check all your PRTEAM entries have matching ODF_CA_TEAM entries (should be 1 to 1), check all the LOOKUPs you have on TEAM (as per earlier), check the other ref data on TEAM (the created by and so on).
As for "tracing OWB" - I have only ever followed the TEC articles and it worked for me - but I've never tried in 14.3,
We have checked almost all the fields and data of this project but could not find the reason.
The same project when xogged into another environment is opening fine in OWB.
Can anyone let me know about OWB console ? to check the exact error threw by the OWB.
Have you copied OWB console to a PC and launched it before launching OWB?
The OWB Console window should contain all the messages generated.
Where will I get the OWB console? I have just heard about it and know that we can see all the errors thrown by the OWB. But, don't know how to use it.
Typically you would get OWB console from support with instructions when you have opened a case.
We have already raised a case to CA support two days back but still waiting for some solution from their side.
This issue is now very urgent for us and need to fix it asap.
Please, suggest something.
Try to get the issue moving with support by using the chat and request OWB console while they are working on the problem.
Just wondering when does the error occur
1 - when the project data is read or
2 - when it is placed in a view
If it is 1 then there is not much you can do in OWB.
If it is 2 then you could try to work around it and open it in another view than the default eg like just the project name, no task data and no resource data.
Should it open then you could try to isolate the problem field. That used to work with custom field.
XOG read the project and inspect the file to see if you can detect anything suspicious.
Don't really have any good ideas, support and the gurus who used to be in support like Nick, Nika, Connie, Kathryn, etc do have better understanding and knowledge of the products.
Retrieving data ...