ConfigManager.updateWsDimensions() failed

Question

Hi all,
Anyone got the following error:
[08.27.12 09:16:29] SEVERE: Utility 'emgr_update_set_post_forge_dims' failed. Re
fer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
Occurred while executing line 42 of valid BeanShell script:
39| if (ConfigManager.isWebStudioEnabled()) {
40| ConfigManager.cleanDirs();
41| Forge.getPostForgeDimensions();
42| ConfigManager.updateWsDimensions();
43| }
44|
45| // archive state files, index
[08.27.12 09:16:29] SEVERE: Caught an exception while invoking method 'run' on o
bject '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_pos
t_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host
ITLHost.
from the logs in the [ENDECA_CONF]/logs/shell, it said:
ERROR: Failed to set app config. Make sure you can connect to http://DEMO-002:8006.
ERROR: Failed to set resources for Endeca instance "ContentAssemblerRef": Failed to delete file C:\Endeca\Workbench\workspace\state\emanager\instances\ContentAssemblerRef\resources\FORGEOUTDIMS.xml.gz
it seems the FORGEOUTDIMS.xml.gz file is locked by Endeca Tools Service and I cannot delete it.
So how can i run baseline_update.bat?
Thank you.

Answer 1

Kaido,
I have investigated the issue more in detail. And this is what we found :
If we run the script without the credssp parameter then we recieve a random access denied.
If we run the script with the credssp parameter then the session gets in a broken state because the powershell.exe crashed right at the time we use new-cmsitesystemserver.
At the same time we see in the app log the powershell.exe crash
Just to make it more confusing : if you precreate the new site system using the sccm console and you rerun the script ( with the credssp parameter ) then the crash does not happen and you recieve a nice message stating that the object allready exists.
If we run the new-cmsiteserversystem on the primary site server , started from the console then we have the same issue ( powershell crashes ). Can anyone confirm the issue when running the new-cmsitesystemserver directly on the PSS ? ( using CU2 )