Today at a client, we stumbled upon a problem when updating MOSS2007 SP2 with .Net Framework 3.5 SP1. Everything seemed to work fine, but Search & indexing was not working anymore. The error log showed the following: EventID 6482 - Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration. SearchServiceInstance
Indexing and serving search queries is handled by diffetent servers in the clients environment.
After a bit of googling and bingging we foud this exelent post by Andera Glaser that decribes the problem and the solution to the problem.
http://andreasglaser.net/post/2009/09/13/SharePoint-2007-and-EventID-6482-Application-Server-Administration-job-failed-for-service-instance-MicrosoftOfficeServerSearchAdministrationSearchServiceInstance.aspx
More info about how to fix the problem:
http://support.microsoft.com/kb/962928
f78c92b6-b907-43d5-a6d2-e1f45e8bfa0c|0|.0

Together with 3 colleagues from QNH Business Integration I am currently finishing implementing a already NEN 2082 certified project based on SharePoint 2010.
When SharePoint 2010 hits RTM there will be another audit for this version of SharePoint, because currently the pre release version has been certified.
NEN 2082 is a Dutch standard which is similar the DoD5015 and MoReq standards.
This project was done for the Gemeente Nieuwegein, which is a Dutch local Government.
For this project we have also been nominated for the “Innovation of the year” award:
More information (Dutch)
My colleagues at QNH:
f2d18032-456f-434b-9528-02dbc0d23c4c|1|5.0

Last week, I removed my VS2010 beta installation and installed VS2010 RC. The RC is much more stable, and as a bonus renaming a feature in a SP2010 project now works.
We have been building lots of features lately, and I was very pleasantly surprised to see this bug already fixed.
9ec0c185-6803-4a62-9790-44df71fb014c|0|.0