Class not registered.
Seems innocuous enough.
I recently started a project to upgrade our Windows SharePoint Services v2 sites to v3. I set up some test servers, ran a test upgrade against backups of the production databases – all was smooth.
Until I tried the same thing in production.
Our web front ends are Windows Server 2003 R2 x64 boxes. So, I set ASP.NET to run in x64 mode, and installed WSS v3. I also set up a virtual Windows Server 2003 R2 x86 box running WSS v2 so that I could run the actual upgrade, as our v2 server is an x64 box running ASP.NET 2.0 in 32-bit mode, so I can’t do the upgrade there.
Seems all good.
The x86 box does the upgrade, and does it well. The search service on the x86 box starts fine, creates the database on the SQL 2005 backend, and all is good.
Until I configure the search service on the x64 box.
And get the dreaded, "Class not registered."
The long and short of it is that after a call with Microsoft, I found out that the domain user I was using did not have the permissions to insert the information for the search service into the registry. I haven’t tracked down the exact keys yet, but on the x64 box, the search service user needed to be an administrator on the box to set up search. Not so on the x86 box.
The document Microsoft sent me details which users need which permissions, and looks like it was grafted out of the WSS v3 installation and configuration instructions, although I haven’t located exactly where yet.
More when I know the answer to which keys. Until then, I hope this helps someone!