"Thread was being aborted" while enabling Full-text indexing

If you, due to problems, disable the WSS full-text indexing component, it might be possible that you receive an error when you try to enable the component again:
-------------------------
Error:

Thread was being aborted
-------------------------

This can be solved by performing the following steps (source: WSS Administration Guide):
- Stop Microsoft Search service
- Stop MSSQLServer service
- Start MSSQLServer service
- Start Microsoft Search service
- Open the SQL Query Analyzer
- For each content database run:
exec proc_DisableFullTextSearch
exec proc_EnableFullTextSearch
This enables the FTS outside of Sharepoint. After these steps are performed, Sharepoint must still be configured to show the search box.
To do this, check the enable full-text indexing component in the central admin.

If the error still occures, increase the time-out value for the Central Admin site.
This can be done by increasing the "executionTimeout" value (default 600 seconds) in the web.config in
C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\ADMIN\1033
(<httpRuntime executionTimeout="600">)

Error "<!-- #RENDER FAILED -->" when doc.lib. contains more documents than the Item Limit

When a view of a document library is sorted by "Created" or "Modified" and an Item Limit is set, it is possible the error message "<!-- #RENDER FAILED -->" is displayed when you click the "Next" button. Somehow WSS has difficulties displaying batches of documents when they are sorted on a date field. To solve this, just don't sort by Created or Modified, or don't use an Item Limit and everything will work fine!!

Webcast Sharepoint Portal Server 2007

Microsoft has placed a webcast about Sharepoint Portal Server 2007 on their site. In this webcast all new features in Sharepoint 2007 are discussed.