This one actually hurt. I still don’t know why I had this error –but after installing Infrastructure Update on a fresh install I went to the SSP to ensure search was configured and happy. To my amazement, I was presented with the error:
The resource object with key ‘S2SearchAdminDashboard_Title’ was not found”
There wasn’t a lot on the WEB, but I was able to piece together a few BLOG entries to get it fixed. It turns out that a 5 files did not get updated for the SSP’s virtual directory. To fix the problem you have to:
Go to the default Virtual Directory for a working SharePoint WEB App and copy the following files:
App_GlobalResources\searchadmin.en-us.resx
App_GlobalResources\SearchAdmin.resx
App_GlobalResources\sps.en-US.resx
App_GlobalResources\sps.resx
Place those files in the same directory in the SSP’s Virtual Directory. Next, copy the following file from the default Virtual Directory:
_app_bin\layouts.sitemap
To the same directory in the SSP’s Virtual Directory. Lastly – a good-old IISRESET /NOFORCE to finish things off.
Note: It’s always a great idea to make a copy of the files that you are overwriting in the event you want to roll back. Just don’t place them in a subdirectory of the current directory and keep them named the same. This causes a conflict.
Note 2: Why did the infrastructure Update not work? Not sure. It may have had to do with a service account mismatch. But I have no desire to go back and try to recreate it!
Tags: SharePoint, Troubleshooting
I had the same problem… Your fix works. Thanks a lot for saving me the headache!
My pleasure! Glad my pain helped someone else.
The infrastructure update caused problems for me but for another reason: a newly added server didn’t match perfectly to the other WFE in terms of it’s configuration and basically, that was all she wrote. Had to remove that server from farm, rebuild and now all is well.
We had this problem too. Didn’t realize it until we started configuring the search in production (did not have the same problem in development and stage environments), but this resolution saved us SOOOO much time. Thanks!!
[...] some Googling turned up this article by Jeff DeVerter. After I screwed up by copying two of the wrong files in his article [...]
Thanks for the great post! Solved our problem, too.