Tag Archive: iis 7.0


So the search service that comes with SBS 2008 is not installed by default. Desktop Search is, but not Server Search, which lets you index shared files and the like. Out of the box, WSS Search SHOULD work. In all three of my SBS set-ups, it has not worked, and this has plagued me for ages, so I finally set about fixing it today. I can’t tell you the exact reason that it is broken for me, but it is most likely caused by an update, service pack, hardware change, or just plain old incorrect permissions or WSS set-up.

First thing I did was install Windows Search Service.
Open up Server Manager, and select File System. Click Add Services on the right.
Click to check Windows Search Service.

Windows Search Service

Windows Search Service

This took about 15 minutes, and at the end an error was displayed. Closing the windows, I noticed that Windows Search Service was installed and running, and the service was also running under the Services Console.

Hrmmph. At this point I go into Sharepoint Central Administration, and Search still will not work. So now I set about making two new accounts to run the search.

I created WSS_Search, set a password, and added it to the group Administrators.

I then created WSS_Content, and added it to two groups:

SQL Accounts

SQL Accounts

These two accounts might differ from what you have. What we need is an account that has READ access to the Sharepoint Content Database. It can not be an administrator account, or a system account, though I believe it can be Local Service.

Now I tried my search and it still would not work. As a matter of fact, I could not start the search service at all now. So I go to Services Console, scrolls down to Windows Search Service. Right click it and select Properties. Make sure Local System is selected under the Log On tab. Exit out, and go to Windows Sharepoint Services Search. For this Log On, select This Account: and enter the information you used for the WSS_Search account. Change type to automatic, and click apply and start.

Log On Properties

Log On Properties

You will receive a message about the account being granted run as a service privileges.

So far all is well, though Sharepoint still wont Search. Open up Sharepoint Central Administration 3.0 under Administrative Tools.

Click Operations Tab, and then Services on Server.

Services on Server

Services on Server

Click on Windows Sharepoint Services Search.

Now fill in the fields.

  • Service account is WSS_Search, and password.
  • Content Access Account is WSS_Content and password.
  • Database server is grayed out, but should me by default np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
  • Database name is grayed out, but it will be your Search database, such as WSS_Search_WIN-EUGSO7LO7PY
  • Authentication is whatever method you use. Default, it is Windows Authentication. This must be left alone for Microsoft##SSEE. If your database is different, configure the login that would be used to access the database.
  • You can change the time if you wish, I set mine to default every 5 minutes, as we do not have a ton of content on the server.
Search

Search

Click ok. Close all browsers.

Open a command prompt and type iisreset.

Restart both Windows Search and Sharepoint Search Services. Good to go- your site should now be searchable.

The process cannot access the file because it is being used by another process (HRESULT: 0x80070020).

CentralAdmin Error

CentralAdmin Error

This is a simple file in use, except with ports- Windows cannot start centraladmin on port 4721 because it is already using that port. Your options include binding centraladmin to a different port, and restarting IIS, or finding out what is on that port, and fixing it.

Without doing anything, open a command prompt by clicking Start>Run> and typing cmd.

In the black box, type netstat -ano > C:\netstat.txt

Hit Enter.

Navigate to your C:\ drive. Double click the text file named netstat.

Scroll down the list untill you see the port 4721 on the end of an IP address in the second column. It will look something like this:

  TCP    0.0.0.0:4721           0.0.0.0:0              LISTENING       4612

The last number is the Process ID.

Now pres Crtl-Shift-Esc.

Click on the Services tab.

Scroll down until you find the PID that matches the one from our Netstat.

Task Manager

Task Manager

As you can see from my example,. it is Microsoft Exchange Mailbox Assistant. This “Performs background processing of mailboxes in the Exchange store”. I know from past experience that this is not a super critical process, like the Transport Service, though it will supply errors if turned off.

So we won’t turn it off, but lets pause it. This is in hopes that CentralAdmin will take the port back, and then MS Exchange will assign a new dynamic port to the mailbox assistant.

Open Services MMC under Administrative Tools. Find the Mailbox Assistant. Right click it and select Stop.

Go back to your command prompt window and type iisreset.

Now check on CentralAdmin, either by trying to navigate to it or opening IIS Manager. It is started. Now go back to Services, and restart the Mailbox Assistant. It started without trouble.

Let’s double check that the mailbox assistant is assigned a new port.

I check the PID, and cross reference it against a new netstat output and see:

  TCP    0.0.0.0:44824          0.0.0.0:0              LISTENING       5424

Exchange dynamically assigned the port of 44824- much better.

This process can be done with nearly anything. Often times you will install new software and it will take the port of some existing site- this is the process to correct it. Skype is a known culprit. Just make sure you research the  service you are stopping before cutting it off. Stopping SQL (SBSMONITORING) would probably be a bad thing, as would stopping some of the more important Exchange services or any system processes. In those cases, it might be better to change the site binding port.

%d bloggers like this: