Hello,
First, I would like to thank all contributors to this very nice piece of software.
I have an issue. I installed it and use it for a week now, but i don't have access to the administration module.
1. I imported some classes from a coworker's installation
2. I "play" with CMDBuild, add cards, importing CSV... everything is okay
3. When i click on "Administration module", i see the splash screen (grey background) and nothing happens.
4. I click elsewhere, i can see the administration module, but with no content (only the header and two empty panes).
Here's javascript console output:
Hello,
The error you describe is a bit 'strange.
The only similar case that we remember was caused by a bad definition of a lookup lists, that for a wrong error management in the source code prevented the access to the Administration Module.
In that case the CMDBuild user created a multi-level lookup list, where a child record was connected to a non-existent father.
Can you check with a SQL select in the database (table "LookUp") if this is the problem ?
CMDBuild team
Hello,
It looks like you are right... I started a fresh instance and reworked carefully the import.
The funny thing is that now i have access to the Administration module, but the Data management module doesn't show any classes!
After waiting 30 seconds watching at the splash screen, i get a cryptic "An error has occurred" popup.
- There are classes in my databases, i imported them though SQL scripts
- I cleaned the cache, restarted the instance
- The only error i get from logs is "[persist ] Inexistent attribute "IdClass" for table "_Dashboards"
Could you give me tips to debug these kinds of UI errors?
BTW, i had another error in the logs "Invalid byte tag in constant pool: 60". I corrected it by updating the icu4j jar after cmdbuild deployment.
Previously Tecnoteca wrote:
Hello,
The error you describe is a bit 'strange.
The only similar case that we remember was caused by a bad definition of a lookup lists, that for a wrong error management in the source code prevented the access to the Administration Module.
In that case the CMDBuild user created a multi-level lookup list, where a child record was connected to a non-existent father.
Can you check with a SQL select in the database (table "LookUp") if this is the problem ?
CMDBuild team
Hello,
Previously Philippe wrote:
Hello,
It looks like you are right... I started a fresh instance and reworked carefully the import.
The funny thing is that now i have access to the Administration module, but the Data management module doesn't show any classes!
After waiting 30 seconds watching at the splash screen, i get a cryptic "An error has occurred" popup.
- There are classes in my databases, i imported them though SQL scripts
- I cleaned the cache, restarted the instance
- The only error i get from logs is "[persist ] Inexistent attribute "IdClass" for table "_Dashboards"
Could you give me tips to debug these kinds of UI errors?
BTW, i had another error in the logs "Invalid byte tag in constant pool: 60". I corrected it by updating the icu4j jar after cmdbuild deployment.
Previously Tecnoteca wrote:
Hello,
The error you describe is a bit 'strange.
The only similar case that we remember was caused by a bad definition of a lookup lists, that for a wrong error management in the source code prevented the access to the Administration Module.
In that case the CMDBuild user created a multi-level lookup list, where a child record was connected to a non-existent father.
Can you check with a SQL select in the database (table "LookUp") if this is the problem ?
CMDBuild team
I forgot to add that everything is fine under 1.5.0, only after an upgrade to 2.0.4
Previously Philippe wrote:
Hello,
Previously Philippe wrote:
Hello,
It looks like you are right... I started a fresh instance and reworked carefully the import.
The funny thing is that now i have access to the Administration module, but the Data management module doesn't show any classes!
After waiting 30 seconds watching at the splash screen, i get a cryptic "An error has occurred" popup.
- There are classes in my databases, i imported them though SQL scripts
- I cleaned the cache, restarted the instance
- The only error i get from logs is "[persist ] Inexistent attribute "IdClass" for table "_Dashboards"
Could you give me tips to debug these kinds of UI errors?
BTW, i had another error in the logs "Invalid byte tag in constant pool: 60". I corrected it by updating the icu4j jar after cmdbuild deployment.
Previously Tecnoteca wrote:
Hello,
The error you describe is a bit 'strange.
The only similar case that we remember was caused by a bad definition of a lookup lists, that for a wrong error management in the source code prevented the access to the Administration Module.
In that case the CMDBuild user created a multi-level lookup list, where a child record was connected to a non-existent father.
Can you check with a SQL select in the database (table "LookUp") if this is the problem ?
CMDBuild team