by Martin
24. marts 2010 12:46
I've now moved on to the testing state of SharePoint 2010. This requires, between many other things, to configure your Search Service Application. But what good does this do you, when you cannot create an Search Service Application?? I got an error when trying to create the Search Service Application:
Errors were encountered during the configuration of the Search Service Application. Requested registry access is not allowed.
[More gibberish in form of stacktrace, but the stacktrace didn't help at ALL, it didn't tell me which key in the registry that were inaccessible]
So I got the input to use the Process Monitor from Microsoft (formerly RegMon by SysInternals). Using this, I was able to pinpoint the key in error: "HKLM\SOFTWARE\Microsoft\Shared Tools\Web server extensions\14.0\Secure\FarmAdmin" and the user that didn't have access (my App Pool identity, strange...). Using regedit to navigate to the key in question, I could now add the permissions to the user (app pool identity).
After doing this it worked :) :
Hope this can help someone out there.
As the used environment is only for testing purposes, I don't care about the real impact of just adding permissions directly on a registry key. In the real world you might consider other ways around (in short: do it right from the start ;) )
Abonnér