cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot find the root of your orgchart in SQl server data connection

Former Member
0 Kudos

Hi All


In nakisa orgchart  we are getting the error " Cannot find the root of your orgchart. The orgchart box may have been deleted or incorrectly specified, or no valid org structure can be found for the selected effective date. Please change the root of the chart or select another effective date "

We are using the nakisa build ( Name OrgChart , Version 3.0 SP1 ,  Build 0701033200 ,SQL server 2008  ) and we successfully fetch the data from SAP and updated in SQL SERVER and tables with data  are created in SQL server succesfully .


We have created  the view and it is published successfully and it give the above error  in org chart view

I have attached the detail  screen shot  for more info , please let me know  how to rectify the issue .


Regards

Abdull Hakkim.K

+919940174346

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Abdull,

Check KBA below which has checks we ask customers to perform when they get this error.

1708773 Cannot find the root of your OrgChart

Best Regards,

Matthew

lukemarson
Active Contributor
0 Kudos

Hi Abdull,

Can you go into the database and verify that the table OrgUnitHierarchy2 exists and that it is populated with data?

What does the cds.log say after extraction?

Is this a new or recent implementation? If so then you should use OrgChart 3.0 SP3 or, if possible, OrgChart 4.0.

Best regards,

Luke

Former Member
0 Kudos

Hi Luke
1) OrgUnitHierarchy2 table is created in SQL server but datas are not there . Other few table in SQL server is having data .
2) Please find the CDS log : got error in line 18 

16:51:10 INFO com.nakisa.Logger - com.nakisa.framework.login.Main : LogIn :
Login process finished successfully
11. 26 Nov 2012 16:51:15 INFO
com.nakisa.Logger - Invoking action:refresh []. For processor
ModuleControlAppProcessor. Against controller ModuleControlCtr
12. 26 Nov
2012 16:51:15 INFO com.nakisa.Logger - refresh on ModuleControlAppProcessor
took: 12ms
13. 26 Nov 2012 16:51:18 INFO com.nakisa.Logger - Invoking
action:refresh []. For processor ModuleControlAppProcessor. Against controller
ModuleControlCtr
14. 26 Nov 2012 16:51:18 INFO com.nakisa.Logger - refresh on
ModuleControlAppProcessor took: 5ms
15. 26 Nov 2012 16:51:18 INFO
com.nakisa.Logger - Invoking action:loadorgchartdirectory []. For processor
ModuleControlAppProcessor. Against controller ModuleControlCtr
16. 26 Nov
2012 16:51:18 INFO com.nakisa.Logger - loadorgchartdirectory on
ModuleControlAppProcessor took: 12ms
17. 26 Nov 2012 16:51:18 INFO
com.nakisa.Logger - Invoking action:refresh []. For processor
OrgChartAppEventProcessor. Against controller OrgChartCtr
18. 26 Nov 2012 16:51:18 ERROR com.nakisa.Logger -
com.nakisa.framework.data.commandProcessor.impl.SqlServerCommandProcessor :
getDataTables : Problem executing query. Data Element Name:
OrgUnitHierarchyDataElement

19. 26 Nov
2012 16:51:18 WARN com.nakisa.Logger - ChartingProcessor : StartChart : Could
not create nodes. Error message returned:Index: 0, Size: 0

20. 26 Nov
2012 16:51:18 INFO com.nakisa.Logger - refresh on OrgChartAppEventProcessor
took: 103ms
21. 26 Nov 2012 16:51:32 INFO com.nakisa.Logger - [Admin console]
admin user 'admin' successfully logged in
22. 26 Nov 2012 16:51:53 INFO
com.nakisa.Logger - ManagerInit: Time took to setup Build: 12802 ms
23. 26
Nov 2012 16:51:55 INFO com.nakisa.Logger - ManagerInit: Time took to load
settingsResources: 125 ms
24. 26 Nov 2012 16:51:58 INFO com.nakisa.Logger -
ManagerInit: Time took to load appResources: 2153 ms
25. 26 Nov 2012 16:51:59
INFO com.nakisa.Logger - ManagerInit: Time took to load extractorSchema: 37
ms
3) We are using live mode in our production system now we are planning to go with stagged mode for better performance .
Regards
Abdull.K








StephenBurr
Active Contributor
0 Kudos

Ok, then for sure you need to be looking at the CDS log for the period when your extract and join occurred as the "OrgUnitHierarchy2" table needs to exist and hold all the OU data for your structure.  This table is used to "draw" the Organisational Structure hierarchy.

If necessary, re-run the extract and join and review the log.

Stephen

lukemarson
Active Contributor
0 Kudos

Hi Abdull,

The problem is that you have no data in OrgUnitHierarchy2 table. In the Log Manager set the logging level to the highest and also select 'Database Tracing' option. Re-run the extract and see if the error(s) appear in the log file. Also check if the data is populated. If not the log might give the errors, although if it doesn't then you might need to run every join statement directly on your database until you find the error.

Also, check that HierarchyTable2 and HierarchyTable has data.

Best regards,

Luke