AntiVirus

In this post I will refer to a matter which usually slips out of people's minds when they are installing a SharePoint farm, and that is the Antivirus.

Anti-Viruses that use File-Level Scanning basically scan everything that is being used by the OS or apps, that's good for protecting from viruses but what about SharePoint in this deal?

SharePoint loses Performance on this matter if you don't exclude some folders.

Microsoft has indicated in a KB article exactly what is to be excluded, keep in mind to the changes in OS and 64 VS 32 bit servers.

The main folders are:

C: \Program Files\Common Files\Microsoft Shared\Web Service Extensions

C: Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

C:\Program Files\Microsoft Office Servers

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files (on 64 Bit Servers)

C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config C:\Windows\Temp\WebTempDir

C:\WINDOWS\system32\LogFiles 

C:\Windows\Syswow64\LogFiles (on 2008 Servers) 

For reference here is the KB article link.

Office Search Service stuck on 'Stopping'

Today i faced a pretty persistent problem, the Office Search Service was stuck on "stopping" as you can see in the next picture :

What i did was to change the Permissions on the Office Search Service to "LOCAL SYSTEM" (By going to Services.msc), then i disabled the service. the next step i took is the following STSADM command :
stsadm -o osearch -action -start
Which still isn't good enough. now we have to give the office search service the right permissions again.
It should be the Search user you have in the farm.
After the permissions are in order enable the service and run the STSADM command we tried before and that should do it for you :

 If the Exact way that i described the stages doesn't work for you try doing the same stuff i did just in different order because i did them so many time i might be confusing the order of the operations :-)

Sharepoint Versions

Sometimes we come across a Sharepoint farm with an unrecognized Build number.

Fortunatly some one has put in the effort  all ready and wrote all the versions down :

The list for Sharepoint 2007 can be found here.

And the list for Sharepoint 2010 can be found here.

Cause you don't want to get the Wrong Build Number....

unrecognized HTTP status

Hello citizens of the Sharepoint World.

Today i found myself facing a problem from a new kind, the kind that involves Crawling in a Proxy environment.

I encountered the following error message : 

To make a long story short - here is the answer.

The solution in a nutshell :

If you are behind a Proxy and want to crawl content Outside of your LAN, you should Disable the Proxy settings inside  Internet Explorer:

And set the Proxy settings inside the SSP Search Settings :

 And that Should do it for you.

Enable \ Disable Sharepoint alerts

Hello Everyone 

Today i found out a cool way to Disable or Enable alerts in sharepoint.

Why is this so cool you ask ? because instead of canceling all the email features (such as Workflows) i can disable just the alerts. 

this is the way to do it : 

Disable Alerts 
stsadm -o setproperty -propertyname alerts-enabled -propertyvalue false -url http://Web_App-URL

Enable Alerts 
stsadm -o setproperty -propertyname alerts-enabled -propertyvalue true -url http://Web_App-URL

And if you want this to happen right away you should Restart the timer services by going to RUN > Services.msc and restarting a service called  " Windows Sharepoint Services timer"

after which this command should follow :
stsadm -o execadmsvcjobs
that it :-)

Event ID 5783

Some day this week (i can't remember which day was it) i checked my Event viewer for no reason and i saw a bunch of 5783 Errors.

So i turned to Google and found out that the issue is that there are a couple of DB's that are not Synchronized For some reason. the following rows will tell you guys the rest :

Stsadm -o sync -listolddatabases 1 > this will give you a list of the DB's that aren't synced at a period days Represented by the Number you entered.

Stsadm -o sync -deleteolddatabases 1 > i know this command looks scary but it won't delete your DB, it will Only delete the record of it being synced.

In order for us to make sure the Sync occurs now we need to Restart the Windows SharePoint Timer Service By going to RUN > services.msc > and restarting the service 

After which this command should follow in order to start all the executive jobs : 

Stsadm -o execadmsvcjobs

And....that should do it.

Configuration Databse

A couple of days ago i encountered the following error message :

The reason for that is that one of the SQL servers has restarted during the night but although the server is on the Farm doesn't realizes it. so i restarted all the server in the farm and walla - now everything works just fine.

Event id 8214

Hi everyone,

Today i encountered a strange error and when i searched Google - nothing came up.

The error began when i created a n Web Application and tried browsing it VIA  browser.

What i got was "Site does not exist", so i turned to the IIS and clicked "Browse" from there and i got the same error. so i turned to the Event viewer and and i saw that Error 8214 was logged.

From earlier exprience i know IIS 6 has sometimes problems if the IP Address is set to "All Unassigned"

So what i did was change it from the default value to the server's IP address.

I know what you are thinking - what the hell does that got to do with the problem at hand...well try it and see for yourself. It solved my problem :-)