Page Not Found errors in WQS in Alfresco 4.0.b

[aussen2]

I just did a fresh install of 3.4.b (Installer package on 64bit Ubuntu Linux Server) and get a PageNotFoundException when trying to access the Web Quick Start web app. This error appears any content I try to access (content of type ws:article, ws:indexPage or ws:image). Images can be accessed when using the URLs in the format /wcmqs/asset/GUID/filename.suffix. So I assume this has something to do with the section lookup mechanism. All the content is the out-of-the-box data imported by the WQS Share dashlet (i.e. ws:webasset, wsarentSections and ws:ancestorSections are all present where needed). Any idea what could cause that error?

[dmihelj]

I just did a fresh install of 3.4.b (Installer package on 64bit Ubuntu Linux Server) and get a PageNotFoundException when trying to access the Web Quick Start web app. This error appears any content I try to access (content of type ws:article, ws:indexPage or ws:image). Images can be accessed when using the URLs in the format /wcmqs/asset/GUID/filename.suffix. So I assume this has something to do with the section lookup mechanism. All the content is the out-of-the-box data imported by the WQS Share dashlet (i.e. ws:webasset, wsarentSections and ws:ancestorSections are all present where needed). Any idea what could cause that error?

Same with my two installations - on Ubuntu 64bit and Windows Vista 32bit.

[bremmington]

Yes, we're having some problems with the migration of search to Solr. Very sorry for the inconvenience and delay, but they're proving a little awkward to track down and resolve.

We believe that WQS is working as it should when using Lucene as the search engine instead of Solr. It is possible to switch over to use Lucene by setting this property value in your Alfresco properties file:

index.subsystem.name=lucene‍

(by default it is set to "solr" in 4.0)

If you decide to do that then you will have to carry out a full reindex when you first restart Alfresco. This can be done by setting this property:

index.recovery.mode=FULL‍

We will sort this out as quickly as we can, but temporarily switching over to Lucene should get you up and running again.

[dmihelj]

Thanks. Now it works OK.