| Event Id | 10045 |
| Source | Windows SharePoint Services 3 Search |
| Description | Successfully imported the application configuration snapshot into the registry. |
| Event Information | This information from some newsgroups may help you: I restarted the SharePoint Services Search, but still got the same error. So I looked up what I needed to check to verify my Indexer settings and found the following: "To start it, you have to visit your content database in Central Admin Application Management. In the SharePoint Web Application Management section, click on Content Databases. This should expose your content database for the farm." So I did just that. I went to Application Management on the Central Administration site and clicked on Content Databases. I saw my database; WSS_Content and clicked on it to view the settings. Sure enough, the Search Server (Indexer) was not selected. I chose my index server (my only SP server) and clicked OK. I retried the Search: This Site, and got a message that there were no results to be found!!!No error message!!! I stopped and restarted my Content Crawls by going to Shared Services Admin>Shared Services>Search Settings (under Search)>Content sources and crawl schedules. I have 3 sources; the SP server and sites, a shared folders directory, and the Exchange Public Folders directory. I stopped and started the crawl on all 3 and then tried the Search: This Site once again...... Success!!!! I am getting search results now. |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.