Hello everybody,
First thanks aevans713 for the publishing. I think that the edition unpublished it and then I forgot to change back the status…
So last week, I finally had the time to work on this issue and to let anybody know, I find out what was the issue! After a lot of re-installation in my local computer of the Alfresco Community Edition 4.2.c, I finally understood why this exception appears in the first place and of course, it wasn't due to my extensions
.
In fact, you can try to do the following and you will get the exact same issue. This was tested in Linux (OEL) and Windows (Windows 7, Windows 8).
1. Install Alfresco Community Edition 4.2.c from the bundle executable/binaries
2. Let all default parameters and once the installation is done, start Alfresco
3. Login to the Alfresco Share UI (http://localhost:8080/share) using the admin account and the password setup during the installation
4. Navigate to the Sites finder (http://localhost:8080/share/page/site-finder)
5. Click on "Search" to display all existing sites (only the default one is present: "Sample: Web Site Design Project")
6. Click on "Delete" to delete the swsdp site
7. Navigate to the Repository (http://localhost:8080/share/page/repository)
8. Remove the "Sites" folder (/Company Home/Sites)
9. Refresh the page and take a look at your logs => You should be able to see a lot of exceptions like the one describe in my first post
You may wonder why somebody would delete the Sites folder… Well… 2 years ago, I was quite new to Alfresco and I wanted to do something "clean" (maybe a little bit too clean). As I didn't need the Sites features, I thought that delete this folder wouldn't hurt Alfresco and in fact except these exceptions in the log files, there was no other issues.
If you don't have a way to restore the Sites folder like it was my case (after 2 years, no backup left), here is what you can do to fix this issue:
- A => The Alfresco Community Edition 4.2.c where the "Sites" folder doesn't exist (was removed)
- B => The Alfresco Community Edition 4.2.c where the "Sites" folder exist
1. Install a new Alfresco Community Edition 4.2.c from the bundle executable/binaries => This is B
2. Start Alfresco and log in to the Alfresco Share UI of B
3. Delete the default site "Sample: Web Site Design Project" (DON'T delete the Sites folder) of B
4. Configure a replication target on B to point to A (doc: http://docs.alfresco.com/4.1/tasks/adminconsole-replication-transfertarget.html)
5. Configure a replication job on B to replicate the "Sites" folder from B to A
6.1. Enable the replication on B by adding the share url into the share-config-custom.xml file (doc: http://docs.alfresco.com/4.1/tasks/adminconsole-replication-lockedcontent.html)
6.2. Enable the replication on B by adding the replication.enabled=true into the alfresco-global.properties file (doc: http://docs.alfresco.com/4.1/tasks/replication-share.html)
6.3. Restart B for Alfresco to take into account the last changes
7. Run the replication job
Once the replication job has run, the exceptions disappear from the log files of A.
To go deeper, I don't know if this new "Sites" folder can be used to create new sites on A but for me it do the job since I don't have the exceptions anymore and since I don't use the sites features.
Have a nice day,
Morgan
First thanks aevans713 for the publishing. I think that the edition unpublished it and then I forgot to change back the status…
So last week, I finally had the time to work on this issue and to let anybody know, I find out what was the issue! After a lot of re-installation in my local computer of the Alfresco Community Edition 4.2.c, I finally understood why this exception appears in the first place and of course, it wasn't due to my extensions
.In fact, you can try to do the following and you will get the exact same issue. This was tested in Linux (OEL) and Windows (Windows 7, Windows 8).
1. Install Alfresco Community Edition 4.2.c from the bundle executable/binaries
2. Let all default parameters and once the installation is done, start Alfresco
3. Login to the Alfresco Share UI (http://localhost:8080/share) using the admin account and the password setup during the installation
4. Navigate to the Sites finder (http://localhost:8080/share/page/site-finder)
5. Click on "Search" to display all existing sites (only the default one is present: "Sample: Web Site Design Project")
6. Click on "Delete" to delete the swsdp site
7. Navigate to the Repository (http://localhost:8080/share/page/repository)
8. Remove the "Sites" folder (/Company Home/Sites)
9. Refresh the page and take a look at your logs => You should be able to see a lot of exceptions like the one describe in my first post
You may wonder why somebody would delete the Sites folder… Well… 2 years ago, I was quite new to Alfresco and I wanted to do something "clean" (maybe a little bit too clean). As I didn't need the Sites features, I thought that delete this folder wouldn't hurt Alfresco and in fact except these exceptions in the log files, there was no other issues.
If you don't have a way to restore the Sites folder like it was my case (after 2 years, no backup left), here is what you can do to fix this issue:
- A => The Alfresco Community Edition 4.2.c where the "Sites" folder doesn't exist (was removed)
- B => The Alfresco Community Edition 4.2.c where the "Sites" folder exist
1. Install a new Alfresco Community Edition 4.2.c from the bundle executable/binaries => This is B
2. Start Alfresco and log in to the Alfresco Share UI of B
3. Delete the default site "Sample: Web Site Design Project" (DON'T delete the Sites folder) of B
4. Configure a replication target on B to point to A (doc: http://docs.alfresco.com/4.1/tasks/adminconsole-replication-transfertarget.html)
5. Configure a replication job on B to replicate the "Sites" folder from B to A
6.1. Enable the replication on B by adding the share url into the share-config-custom.xml file (doc: http://docs.alfresco.com/4.1/tasks/adminconsole-replication-lockedcontent.html)
6.2. Enable the replication on B by adding the replication.enabled=true into the alfresco-global.properties file (doc: http://docs.alfresco.com/4.1/tasks/replication-share.html)
6.3. Restart B for Alfresco to take into account the last changes
7. Run the replication job
Once the replication job has run, the exceptions disappear from the log files of A.
To go deeper, I don't know if this new "Sites" folder can be used to create new sites on A but for me it do the job since I don't have the exceptions anymore and since I don't use the sites features.
Have a nice day,
Morgan
