Endeca - Enable rollup counts

App.config

line 400

    --spl
      --dym
      --whymatch
      --back_compat
      510
      --xquery_path
      ./data/dgraphs/local_xquery
  
   --threads
      2
      --stat-abins

Endeca - Debug spelling information

The --spell_msg flag generates useful spelling debugging information displayed to the MDEX Engine stderr, both on startup and on a per-query basis.

      --spl

      --dym

      --spell_msg

      --whymatch

      --back_compat

      510

      --xquery_path

      ./data/dgraphs/local_xquery

Endeca - Baseline Error: Too many *.esp files

ERROR: Too many *.esp files in directory C:/Endeca/apps/xxx/data/complete_index_config

Solution: Remove the abundant .esp file from the folder C:\Endeca\apps\nfm\config\pipeline and reload the files.

SEVERE: Utility 'emgr_update_set_instance_config_from_dir_C-Endeca-apps-xxx-data-complete-index-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.

Occurred while executing line 39 of valid BeanShell script:

[[

36|        ConfigManager.cleanDirs();

37|        Forge.getPostForgeDimensions();

38|        ConfigManager.updateWsDimensions();

39|       ConfigManager.updateWsConfig();

40|       

41|        // archive state files, index

42|        Forge.archiveState();

]]

[08.31.11 08:34:25] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.

Caused by java.lang.reflect.InvocationTargetException

sun.reflect.NativeMethodAccessorImpl invoke0 - null

Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException

com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing valid BeanShell script.

Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException

com.endeca.soleng.eac.toolkit.utility.Utility run - Utility 'emgr_update_set_instance_config_from_dir_C-Endeca-apps-nfm-data-complete-index-config' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.

ERROR: on file nfm.emgr_update_set_instance_config_from_dir_C-Endeca-apps-xxx-data-complete-index-config.log

Endeca - FATAL ERROR

Solution: Delete the file autogen_dimensions.xml.gz and copy the one from autogen_dimensions.xml.external.gz and rename to autogen_dimensions.xml.gz.

 FATAL     08/29/11 19:00:41.205 UTC   FORGE           {config}: Unable to open C:\Endeca\apps\xxx\data\state\autogen_dimensions.xml.gz for input: I/O Exception: compression format exception:            

ERROR          08/29/11 19:00:41.221 UTC   FORGE           {config}: Forge failed with 1 error and 0 warnings. 

Endeca - Solution for cleanDir_processing failed

Solution is removing the file processing from folder E:\Endeca\apps\xxx2011\data and recreate folder E:\Endeca\apps\xxx2011\data\processing and then re-run baseline update.

INFO: [ITLHost] Starting shell utility 'cleanDir_processing'.

Aug 5, 2011 9:43:10 AM com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript

SEVERE: Utility 'cleanDir_processing' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.

Occurred while executing line 17 of valid BeanShell script:

[[

14|        }

15|       

16|        // clean directories

17|        Forge.cleanDirs();

18|        PartialForge.cleanCumulativePartials();

19|        Dgidx.cleanDirs();

20|       

]]

Aug 5, 2011 9:43:10 AM com.endeca.soleng.eac.toolkit.Controller execute

SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.

SharePoint - Create pages with left navigaion

There are plenty of internet pages that teach you how to add left navigation while you create a site page by using SharePoint designer, however, this is definitely not necessary. Any pages changed by SharePoint designer will turned to ungosted and not good for program package. A straight way is locating the correct entry to create page. Here follows steps.
1. Site Action - Manage Content and Structure
2. Click the small right triangle beside folder "Pages" from the left navigation menu. Click New - Page.
3. Name the title, URL and choose page layout. I tried the Blank Web Part page.

It works great for me.