This content has been marked as final. Show 11 replies
Please login to your workbeanch and see if there are some file lock (Application Setting --> Resource Locks)
it says No resources are locked at this time.
Can you check Workbench is running on the host and port specified in your AppConfig.xml file's ConfigManager component definition? The default Workbench port is 8006.
yes its on the same port.
thanks for the quick reply.
What do the [ENDECA_CONF]/logs/shell show? Generally this error occurs when the configs cannot connect to the workbench instance for some reason.
It has only one line saying ERROR: Could not open acquire_lock.status.
eaccmd.bat remove-all-flags -app <your application>
This should remove any locks held by the application. If this fails, it generally points to an issue in file/dir ownership and what user is running the scripts.
Usually this happens when a under privileged user tries to access particular service, or folders.
1) Grant user access to the service account (since it is windows) if current user is not local administrator.
2) Check out folder permissions
3) Check your system path
We had faced similar problems of ‘Releasing locks’ where some changes were made by "root" user and the service was expecting "endeca" user(On Linux system). The solution that worked for us was to taking ownership of the entire endeca installation directory to "endeca" user.
The user which was using installation has the ownership of file system(C:\Endeca and C:\apps) as well. The only abberation is thats its not the "endeca" users are recommanded in installation docs.
I was able to avoid this one by not integrationg my applicaiton with WorkBench.
There is some issue with the work bench interation which was gating this to work.
I had the same problem recently, after I transferred files over to my new laptop. What I found is that the set_templates.bat file on my machine had an incorrect hostname. After fixing that, the problem went away.