Daylight Saving Time

Hello Everyone,

This post is mostly aimed to my Israeli crowd (because this problem concerns them the most).
It's about the Daylight saving time issue in MOSS and Sharepoint 2010 in the year 2011.

Sharepoint (or moss) dosen't look at the OS date as regarding to Daylight Saving time, it looks at an XML file located in : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Config\TIMEZONE.xml.

This years Changes include the following changes :

<.Bias>-120<./Bias>

<.StandardTime>
<.Bias>0<./Bias>
<.Date>
<.Month>9<./Month>
<.Day>2<./Day>
<.Hour>2<./Hour>
<./Date>
<./StandardTime>
<.DaylightTime>
<.Bias>-60<./Bias>
<.Date>
<.Month>4<./Month>
<.Day>1<./Day>
<.Hour>2<./Hour>
<.DayOfWeek>6<./DayOfWeek>
<./Date>
<./DaylightTime>
<./TimeZone>

That's because the change is due on the night between Thursday and Friday at 2 AM in the date 4.1.2011.

There is also a little bug that a co worker of mine showed me, you can view it in his Blog.

For those of you who dosen't understand Hebrew i'll reveal the bug here.

Israel resides in the GMT+2 Time Line, which means we are -120 minutes away from the Grinich line.

Therefore the data -120 <.Bias>-120<./Bias>

Month being the month the clock changes to daylight saving time  <.Month>4<./Month>

Hour representing Hour <.Hour>2<./Hour>

DayOfTheWeek representing the day of the week it will change. <.DayOfWeek>6<./DayOfWeek>

And get this : DAY representing the week the change will occur (yes the week not the day) <.Day>1<./Day>


The changes to the XML file needs to be done on all the servers in the farm, and don't forget to backup your old XML files just in case.


Here is what Microsoft have to say about the Issue.

Happy transition to the year 2011 DST :-)

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 :-)