There are times when you need to find out what version of SharePoint Foundation you are currently running. The easiest way to do this is to look in SharePoint Central Administration via the following procedure:

 

 

On the SharePoint Foundation Server select Start | Microsoft SharePoint 2010 Products | SharePoint 2010 Central Administration.

 

 

When the SharePoint Central Administration appears select Manage Servers in Farm from under the System Settings in the top right.

 

 

In the middle of the page locate Configuration database version and compare the number you find here with:

 

http://todd-carter.com/sharepoint-versions/

 

You’ll then know whether you are running the latest version.

In the previous post I showed how to recreate a Windows SharePoint Search Database that had become unusable. There is of course some troubleshooting you can do before recreating an SQL database. This is generally to check and repair the database using the SQL command DBCC CHECKDB like so.

 

 

For arguments sake, let’s say that the database WSS_SEARCH_SERVERF is corrupt. Firstly login to the Microsoft SQL Server Management Studio Express and expand the Database folder so you can see each database.

 

The first step will be to put the database into single user mode so that only SQL can work on it exclusively while it is being repaired. Single user mode means that only a single program will be able to use the database. If another process is using the database now and we put the database into single user mode that process will typically grab the database and not allow us to work on it. Thus, you should stop anything else that is currently access the database so SQL Management can gain exclusive access.

 

Because this is a SharePoint Search database we know that the only thing that should be accessing this is the SharePoint Search Service.

 

 

Therefore go into the Windows Services console and locate the appropriate SharePoint Search Service. In this case it is Windows SharePoint Search Service since the source system is WSS v3. Right mouse click on the service and select Stop from the menu that appears. You may also want to actually Disable the service to prevent it from re-running itself. If you are checking a SharePoint Search Database then this would be recommended as SharePoint Search will reactive on a regular basis and grab the database.

 

After a few moments the SharePoint Search Service will show nothing in the Status column indicating it is not running.

 

 

Return to the SQL Management console, right mouse click on the database in question and select Properties from the menu that appears.

 

In the dialog that appears select Options on the left and then scroll down on the right until you locate the State section at the bottom. There you will see a line Restrict Access. Change this to SINGLE_USER and press the Ok button to continue.

 

You will be prompted about closing connections to this database. Press OK to proceed.

 

 

When you are returned to the main SQL Management console you should see a small person icon over the database and the name of the database should have (Single User) displayed after it.

 

 

If you now select the New Query button (just under the File menu in the top left of the screen), it will open a blank area on the right. Into here type:

 

dbcc checkdb (‘’);

 

in this case:

 

dbcc checkdb (‘wss_search_serverf’);

 

then press the Execute button just above. This will simply examine the database for issues and report back the results.

 

The window below will show the output from this check process. Examine the log to determine the issues that may be evident.

 

Prior to actually completing a repair of the suspect database it is recommended that you have some form of backup.

 

To proceed with the rebuild and repair change the query to:

 

dbcc checkdb (‘’, repair_rebuild);

 

in this case:

 

dbcc checkdb (‘wss_search_serverf’, repair_rebuild’);

 

You may need to run this command a few time to complete all the repairs. Check the output of the repair for the results.

 

Hopefully, the database has successfully been repaired and now you can put it back to MULTI_USER mode by reversing the process detailed earlier via Properties | Options | Restrict Access.

 

 

With the database now back in multi-user mode you should be able to start the dependent services and everything should now work as expected. Don’t forget to change the mode of any dependent services from disabled in the Windows Services management console if you disabled them earlier.

In the rare even that the search database for Windows SharePoint Services 3.0 becomes corrupt or unusable here is how to create a new one. The SharePoint search Database simply contains index information about the SharePoint site and can be recreated at any time.

 

 

If you go into the SQL Server Management Studio Express you should be able to identify the search database that you are having an issue with. In this case we can see that it is WSS_SEARCH_SERVERF.

 

 

Open the SharePoint Central Administration. Select the Operations tab and then select Services on Server from under the Topology and Services heading.

 

 

Locate the line Windows SharePoint Services Search and press the Stop hyperlink to the right.

 

 

You will then receive a message like shown above telling you that the index files will be deleted. Press OK to continue.

 

 

After a few moments you should see that the Status changes to Stopped. Now select the hyperlink Windows SharePoint Services Search on the left or the Start button on the right.

 

 

Complete the details for the Service Account. This is account that the SharePoint Search Service runs as. Best practice is to have a dedicated account with a password that doesn’t expire and NOT use the Local service. This account will automatically be given full read only rights to all SharePoint data. Scroll down.

 

 

Now select a Content Access Account. This account will be used to crawl (read) all the SharePoint data and index it. again, best practice is that it should be a dedicated account with a password that doesn’t expire and NOT the Local Service.

 

In the Search Database fields you will see the Database Server name and the Search database (here WSS_SEARCH_SERVERF).

 

 

Enter a new name for the SharePoint Search database (here WSS_NEW_SEARCH_DB) and leave the other settings as is.

 

Press the OK button to create the Search database and start the SharePoint Search Service.

 

 

You will have to wait a few minutes while the Search Service is configured and started.

 

 

You should see that the Windows SharePoint Services Search is now started.

 

 

If you refresh the databases view you should now see the new Search database you created that is now operating with SharePoint. You can detach and remove the old database to avoid confusion.

 

 

Depending on how much database you have on your site it might take a while to completely reindex the search results. You can of course always do a full crawl manually if you want. Beware that the first crawl (whether automatic or forced) will be a major crawl (since it is new empty search database) and will thus be a very intensive process that may impact the performance of the server.

 

The last thing you should do is run a search from the SharePoint site to ensure everything is now working as expected.

This was going to be a post about the fact that I managed to get Search working on SharePoint Foundation 2013, and I did have it working. Honest. The initial issue I experienced seemed to either be the fact that I had accidentally installed SharePoint Foundation 2013 on the member server as a local (rather than a domain) administrator or that the times on the workstation and the server were too different. Whatever it was I did have it working.

 

That was until I powered up the machines (server and members server) to get some screen shots of it all working. Problem is now it does again! I also noticed the the SharePoint machine was really, really slow and when I took a look at the resources I saw:

 

 

 

From this you can see how much memory and processing is being consumed by SharePoint Search alone! Wow. You are doing to need more hardware grunt of you are planning to implement SharePoint Foundation 2013 from what I can see.

 

Now admittedly  I am only running this on a virtual machine for testing purposes but I can tell you I didn’t have these issues with SharePoint Foundation 2010! The more I work with Foundation 2013 the more I am beginning to dislike it. Don’t get me wrong, I love SharePoint 2013 but getting this blighter to work is proving very, very difficult. I certainly hope others aren’t seeing these issues. Another reason to focus on Office 365 in my books.

 

The positive thing, when I did get SharePoint search working, was that SharePoint Foundation 2013 now incorporates all the features of Search Server Express (obviously the reason why there is no more stand alone Search Server Express product). It also includes the ability to index PDF documents WITHOUT the need to install separate iFilters.

 

Now, if I could only show you that actually working but as I said, when I booted the machines backup SharePoint search no longer worked on Foundation 2013. Back to the drawing board yet again.