While starting AEM author, it gives the following error:
WARN [FelixStartLevel] org.apache.jackrabbit.core.util.RepositoryLock Existing lock file C:\CQ5\AEM-author\crx-quickstart\repository.lock detected. Repository was not shut down properly.
Please help me to fix this issue.
You didn't indicate which version of AEM you are using but I think the CRX 2.3 troubleshooting info at https://docs.adobe.com/docs/en/crx/2-3/administering/repository_lock.html is valid for all versions that run on CRX.
Stop your instance, In your C:\CQ5\AEM-author\crx-quickstart\ search for all .lock files and delete them and restart.
Related
I tried internet search on this issue and it is very common with many suggestions. The problem started with an update to VS2019 in which I paused because my projects in VSCode were breaking.I did a system restore and when I tried to start VSCode I got a message saying my installation was corrupt. So I reinstalled to the latest version and now get this error.
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found...
I found 3 extensions that needed updating so I do so but did not fix this problem. Do not know if I need to update the .Net Core since it looks like a version mismatch. It seems these updates are wreckless since they always cause thing to go wrong.s
If you are facing this problem, it means you are using Windows.
This official microsoft live share github page explains how to fix the issue: https://github.com/MicrosoftDocs/live-share/issues/102
Especially, check out this comment: https://github.com/MicrosoftDocs/live-share/issues/102#issuecomment-366509735
make vscode is up to date
uninstall live share from vscode
close vscode completely
restart vscode as administrator
reinstall live share
I should add:
close completely vscode and restart it
I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.
I have been following the instructions on
https://docs.adobe.com/docs/en/aem/6-1/deploy/upgrade.html
I reached "Once the upgrade is finished, the AEM homepage will be shown."
However, all I get is "an HTTP 503 status for all requests except for those under http:///system/console", exactly as described at the NOTE under this step.
The problem is that I always get this error, not only during the upgrade, but also after the upgrade is finished!
The error.log states:
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
11.11.2015 12:38:29.888 *ERROR* [qtp231586654-77] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.
Any help is highly appreciated.
We've encountered this once:
There were issues with diskspace (the disk was simply full), make sure you have an adequate amount of space available.
There could be two possible reasons:
Some of the bundles are not active.
Lucene is corrupt and hence not able to start
Possible fix is:
Bring your bundles back to active, if it is not active.
Stop your instance. go to crx-quickstart\repository\index and delete index folder.
Restart the instance (This will regenerate Lucene indexes fully).
Quick fix:
Stop the AEM instance.
Go to folder crx-quickstart\repository\ remove folder index
Start the AEM.
Everything should working fine. (It's working for me)
Check the permissions under crx-quickstart\repository\ after you deleted the index.
For me it had nothing to do with the segmentstore or the index or any unsatisfied bundles. Instead, it was the datastore.
The permissions for the datastore directory didn’t allow the user running aem to access it. The datastore directory is configured in org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.
This error really should reveal its root cause a little bit more easily. I’m sure it was somewhere in the logs, though…
We are trying to upgrade to AEM 6.1 from 6.0sp2. As Adobe suggested that we have to upgrade the Dispatcher to 4.1.9 (as mentioned here https://docs.adobe.com/docs/en/aem/6-1/release-notes.html )
On Publish instance, we did the following:
Downloaded the new dispatcher file from https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/dispatcher/_jcr_content/top/download_37/file.res/dispatcher-apache2.2-windows-x86-4.1.9.zip
Replaced the "disp_apache2.2" file in C:\Apache2\modules. We did not change any settings "dispatcher.any" as we wanted all of them to work as they were working.
Restarted Apache, then AEM.
But the site is not loading, not even localhost http://localhost:4503 (Publish instance)
We can see the following errors in "startup" log file:
27.07.2015 14:39:37.890 *ERROR* [main] ERROR: Unable to re-install slinginstall:E:\aem\publish2\crx-quickstart\launchpad\startup\1\org.apache.sling.fragment.ws-1.0.2.jar(java.lang.IndexOutOfBoundsException: Index: 0, Size: 0)java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
The path "E:\aem\publish2.." did not exist. The one we had was "E:\aem\publish.."
Did anyone come across similar? Or are we missing any step?
We found the issue is not related to Dispatcher upgrade, but is related to AEM not able to connect to an external device where the content is being stored.
After we resolved the issues, the upgrade went on smoothly.
I am developing a plugin in moodle, I have uploaded the plugin but in Manage activities I see the ' Missing from disk' error and a related Section error! in the settings. Why I am getting such an error?
I had problems with the "videofile" Moodle plugin (version 1.5).
When I was upgrading to the Moodle 3.0 version, a message "missing from disk error" was showing, and it was unable to continue with the installation.
The file "version.php" from "/mod/videofile" had the command "$module" in several lines. I replaced with "$plugin" and that solved the problem.
Hope this help someone with the same problem.
Check the directory permissions for the plugin directory - if your webserver cannot read the directory, then you are likely to get this error.
I had this same issue when upgrading Moodle and had to move some custom plugins from the old install to the new.
But for me it was the file ownership that was the problem (I'm on a Linux server).
Changing the ownership (chown) fixed the issue for me.