CMDBuild Forum

Can't access administration module

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:
 
Resource interpreted as Script but transferred with MIME type text/plain: "http://xxx/cmdbuild/services/json/utils/gettranslationobject". administration.jsp:23
  1. Uncaught TypeError: Cannot read property 'children' of undefined CMLookupAccordion.js:21
    1. Ext.define.buildTreeStructureCMLookupAccordion.js:21
    2. Ext.define.updateStoreCMBaseAccordion.js:53
    3. CMDBuild.ServiceProxy.lookup.readAllTypes.successadministration.js:205
    4. (anonymous function)ext-all.js:21
    5. Ext.apply.callbackext-all.js:21
    6. CMDBuild.Ajax.Ext.data.Connection.unmaskAndCheckSuccessAjax.js:61
    7. (anonymous function)ext-all.js:21
    8. Ext.apply.callbackext-all.js:21
    9. Ext.define.onCompleteext-all.js:21
    10. Ext.define.onStateChangeext-all.js:21
    11. (anonymous function)ext-all.js:21

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,
 
I managed to find out that this request is not responding (timeout): http://.../cmdbuild/services/json/schema/modclass/getallclasses?_dc=1364979580782&active=true
 
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,
 
I managed to find out that this request is not responding (timeout): http://.../cmdbuild/services/json/schema/modclass/getallclasses?_dc=1364979580782&active=true
 
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