Sharepoint 2010 - Health Analyzer alerts

Microsoft has come up with a new tool in Sharepoint 2010 - Health Analyzer. Its helps us diagnose and resolve issues related to configuration , performance and usage .

we can check the Environment health using the feature .

To get to the health analyzer we need to go to the central admin

1. first check whether the account that we are using is a member of the Farm Administrators group.
2. Click monitoring
3. under Monitoring you will find Health Analyzer section
4. Under which you can click on Review problems and solutions
5. On the Review problem and resolve page click on the Alert that you want to resolve
6. Follow the steps given in the Remedy section of the Review problems and solutions
7. After you have followed all the steps given .
    Click Reanalyze Now to confirm that the issue is resolved.
8. If the issue is resolved, the alert status changes to 4-Success.

This is a Best Automated tool which Analyzes the server farm and comes up with some good solutions on its own . you can try this at regular Intervals .

Cannot load the site / Site takes a long time to load

Today i Came across a issue where in the site did not load up .

We checked and found that we are able to get to every other page and site .

we then tried going to the web part maintainence page and checked there were some content editor webparts and as we know in IE there are major issues with the content editor webpart we tried opening the site in Chrome .

And to my surprise it opened up fine with some junk characters in the webpart

we then tried modifying the webpart and found that under the location of the file there was a excel file url given .

we removed the url and exited the editing on the page and then checked in a New IE browser and we were able to browse the site without any issues .

Note : This might not be the only cause of the issue . there are mutiple things which can affect the loading of the site . do contact me in such cases so that I can check and come back with some good Resolution.

Unable to save .pdf files from Adobe Acrobat Reader to the SharepointDocument Lib

Unable to save .pdf files from Adobe Acrobat Reader to the Sharepoint Document Library.  As per http://support.microsoft.com/kb/265867/en-us this is a known issue and the workaround is mentioned in the Microsoft KB article.  During troubleshooting it is discovered there is another way this can be done.

For this we first need to ensure that WebDav is enabled in Web Service Extensions in the IIS.  Also make sure that the WebClient service is running in the Services.msc in Windows Server 2003.  Once we have this done, we add a network place using the UNC path.  For instance, if your document library url is http://sharepoint/documents then type in the path as \\sharepoint\documents and this would ask for your valid credentials.  Once you enter your credentials, a network share folder would be created in your My Network Places.  Now you can open your favorite .pdf files in the Adobe Acrobar Reader and save a copy of it directly into the Sharepoint Document Library using the netwrok share in My Network Places.

Note:  The above procedure can be used only to create network shares for folder in the Sharepoint site running on port 80 only.  This is because Web Folders are created for other port numbers and as per the above quoted Microsoft KB article, it is a known issue that .pdf files cannot be saved.  This applies to all non Office applications like .jpg, .rtf etc…

No Adobe PDF documents are returned in the search results when yousearch a Windows SharePoint Services 3.0 Web site

To resolve this issue, make sure that the Windows SharePoint Services Search service is configured to crawl PDF documents on each server on which the Adobe PDF IFilter is installed. To install the Adobe PDF IFilter and to configure the Windows SharePoint Services Search service, follow these steps:

1. Download and then install the Adobe PDF IFilter from the following Adobe Web site:
   
   http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611 (http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611)
   
   Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


2. Add the following registry entry, and then set the registry entry value to pdf:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\<GUID>\Gather\Search\Extensions\ExtensionList\38
   
   To do this, follow these steps:
   
   
   
   1. Click Start, click Run, type regedit, and then click OK.
   
   
   2. Locate and then click the following registry subkey:
      
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\GUID\Gather\Search\Extensions\ExtensionList
   
   
   3. On the Edit menu, point to New, and then click String Value.
   
   
   4. Type 38, and then press ENTER.
   
   
   5. Right-click the registry entry that you created, and then click Modify.
   
   
   6. In the Value data box, type pdf, and then click OK.


3. Verify that the following two registry subkeys are present and that they contain the appropriate values.Note These registry subkeys and the values that they contain are created when you installed the Adobe PDF IFilter on the server.
   
   
   
   • 
     
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf
     
     This registry subkey must contain the following registry entry:
     
     
     
     • Name: Default
       Type: REG_MULTI_SZ
       Data: {4C904448-74A9-11D0-AF6E-00C04FD8DC02}
   
   
   • 
     
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\Filters\.pdf
     
     This registry subkey must contain the following registry entries:
     
     
     
     • Name: Default
       Type: REG_SZ
       Data: (value not set)
     
     
     • Name: Extension
       Type: REG_SZ
       Data: pdf
     
     
     • Name: FileTypeBucket
       Type: REG_DWORD
       Data: 0x00000001 (1)
     
     
     • Name: MimeTypes
       Type: REG_SZ
       Data: application/pdf


4. Upload the PDF documents to the Windows SharePoint Services 3.0 Web site.


5. Stop and then start the Windows SharePoint Services Search service. To do this, follow these steps:
   
   
   
   1. Click Start, click Run, type cmd, and then click OK.
   
   
   2. Stop the Windows SharePoint Services Search service. To do this, type net stop spsearch at the command prompt, and then press ENTER.
   
   
   3. Start the Windows SharePoint Services Search service. To do this, type net start spsearch at the command prompt, and then press ENTER.
   
   
   4. Type exit to exit the command prompt.

Note If the Windows SharePoint Services 3.0 Web site already had PDF documents before you installed the Adobe PDF IFilter on the server, you may have to perform an additional step. After you install and configure the Adobe PDF IFilter on the server, modify a property of the existing PDF documents on the server. For example, modify a metadata property such as the title, or upload the PDF documents to the Windows SharePoint Services Web site again. When you do this, the Windows SharePoint Services Search service crawls the existing PDF documents again.

Alerts do not work after upgrading WSS 2.0 to WSS 3.0

RESOLUTION:
===========
1.Take the stsadm backup of the WSS 3.0 site where alerts are not working
2.Delete the web application and the WSS 3.0 site without deleting the content database (Not deleting the content database just to ensure the original database exists)
3.Create a new web application and the site collection
4.Restore the earlier taken stsadm backup on to the newly created WSS 3.0 site

Command syntax for stsadm backup is

"stsadm -o backup -url <http://sitename> -filename <file location>
Command syntax for stsadm restore is

"stsadm -o restore -url <http://sitename> -filename <file location> -overwrite

WSS 3.0 - Server Error in '/' Application

After upgrading from Windows SharePoint Services 2003 to 2007 we are getting errors
accessing the website

Server Error in '/' Application
An application error occurred on the server. The current custom error settings for
this appplication prevent the details of the application error from being viewed
remotely

Event ID 1309

CAUSE:    The application pool for SharePoint was running as Network Service and that account
did not have rights it needed on the server to run a WSS 3.0 website

Resolution :

Once we gave the Network Service account write access to
'C:\WINNT\Microosft.NET\Framework\v2.0.50727\Temporary ASP.NET Files' the problem
was resolved

Getting event IDs 6398, 7076, 6482, 7080, 7888, 6481, 5554 in WindowsServer 2008

After installing MOSS or WSS in windows Server 2008 when you go to Event Viewer, you will find that you are getting event ids 6398, 7076, 6482, 7080, 7888, 6481, 5554 on a continues interval

SYMPTOMS:
—————–
–your sites will open very slowly
–you will be prompted for user credential repeatedly
–performance of the site will be affected

ERROR

 ————————–
–6398, 7076, 6482, 7080, 7888, 6481, 5554 event ids in event viewer under “Application”

CAUSE:
———–
–you have installed WSS and MOSS both on the Windows Server 2008
–service pack installation for either WSS or MOSS is not done
–Difference in encryption like 32-bit(x86 or i386) or 64-bit
–SQL server installation is incorrect or two version of SQL is installed
–Take the backup of SharePoint Farm, sharepoint site and SQL databases
–Uninstall MOSS
–Uninstall WSS
–Restart the server
–install the Slipstream version of MOSS or WSS

{Note- Regarding SQL server installation, if you are making a “STANDALONE” installation nothing else to perform or change.
If you have SQL server on the same different box or event on the same box them make “COMPLETE” installation and specify the SQL server name when running the SharePoint Products and Technology wizard}

–check the event viewer and you should not get any event ids

ENVIRONMENT:
———————–
Windows Server 2008 Enterprise (64-bit)
MOSS 2007 with SP1 {Slipstream} (64-bit)
WSS 3.0 with SP1 {Slipstream} (64-bit)
SQL Server (64-bit)

Site not browse able with host header – 401.1 error

ISSUE DESCRIPTION
===================

>SharePoint site is browse able from the client machine with the host header.
>When browsing from the server, it prompts for credentials three times and then we get 401.1 Unauthorized error.
>On server, we can browse the SharePoint site with server name(In some cases even with server name, the site doesn’t come up)

RESOLUTION
===================

>Remove the security update KB963027 for Internet Explorer 7.0 and then reboot the server.
>If that didn’t work try with http://support.microsoft.com/kb/896861

WSS 3.0: When trying to search on sharepoint site, Getting message “Noresults matching your search were found.”

1. Symptom –
=============

–>When you are trying to perform search on your SharePoint site  on your sharepoint server, you are getting following error message:

No results matching your search were found.
Check your spelling. Are the words in your query spelled correctly?
Try using synonyms. Maybe what you’re looking for uses slightly different words.
Make your search more general. Try more general terms in place of specific ones.
Try your search in a different scope. Different scopes can have different results.

–>Windows SharePoint help search is working fine and it gave results when we searched for “SharePoint”

–>Unable to get results on the SharePoint site

2. Cause –
==========

–>Issue due to windows Updates

3. Resolution –
================

–>We created a registry entry in the following location

HKLM\System\CurrentControlSet\Control\Lsa

–>Created a new DWORD key named “DisableLoopbackCheck” and modified the value to 1

–>We performed Full Crawl by the command

stsadm -o spsearch -action fullcrawlstart

–>We performed Search and it worked successfully

Getting prompted enter username and password when trying to get into the SSP area

1. Symptom –

–>You are trying to access your shared services page URL https://sharepoint/ssp/admin, but it prompts for password thrice and if the password is supplied for the system account you get IIS error

“HTTP Error 401.1 – Unauthorized: Access is denied due to invalid credentials.”

–>You are unable to get into the SharedServices1 site

2. Cause –>Security setting in Windows Server 2003
3. Resolution –> went to registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

–>Create a DWORD Key “DisableLoopbackCheck” and modified the value to 1

–>Performed IISRESET

–>Browsed the SharedServices site and it opened successfully

4. More Information –

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6

http://support.microsoft.com/kb/896861

User profile import for newly added users in the domain is not happening

Cause : User profile sync account was not present in the 'Pre-Windows 2000 Compatibility Access' group.

Resolution :  Added the User profile sync account to the 'Pre-Windows 2000 Compatibility Access' group. Started incremental profile import. It completed successfully. Started full people crawl. It completed successfully. People search results were pulled up.

February 2011 Cumulative Update for WSS V3 and MOSS 2007

Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package): February 22, 2011

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2475886

Office SharePoint Server 2007 Cumulative Update Server Hotfix Package (MOSS server-package): February 22, 2011

http://support.microsoft.com/default.aspx?scid=kb;EN-US;2475885

Note : After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm

February 2011 CU for SharePoint 2010

Download SharePoint Foundation 2010 February 2011 CU

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475880

Download SharePoint Server 2010 February 2011 CU

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475878

Download SharePoint Server 2010 with Project Server February 2011 CU

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbln=en-us&kbnum=2475879

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

According to some blogs it says

For the 2010 Server Products it is sufficient to install the SharePoint Server 2010 package as it includes the SharePoint Foundation package.

However i would suggest to go ahead and try to install both MSF and SP 2010

Cannot connect to the configuration database after installing SP2

*** Problem Description ***
BEHAVIOR/SYMPTOMS:
====================

PSConfigUI failing after installing WSS 3.0 SP2

Environment:

===============

Wss 3.0 on a stand alone system

Customer is using the windows internal database

Issue :

After the installation of the sp2 which is included as a critical update in the windows update we face connection issues with Sql

 Error message :

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

Access to table dbo.spt_values is blocked because the signature is not valid.

 When we run the psconfig

Symptoms:

======

It will start creating n number of sharepoint_config databases without any tables

We will not be able to access the dbo.versions when we try checking the version of the database

We might be able to check for the version of the config database

Resolution :

Download management studio express
Set SQL express to allow tcp/ip and named pipes

Open the connection with the following address

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Backup all the databases from the sql server management studio .

Check with the customization as it will be lost

Tak e a screen shot of

Solution management
AAM
Topology
Databases in the Sql server management studio
Uninstall windows internal database from the add remove programs

Uninstall SharePoint and reboot the server

Install back SharePoint with windows internal database (standalone installation )

Restore all the databases

Attach the database back to the farm

The server should be up and running

How to find out the ID of a site collection .

1. Open the Central Administration


2. Application Management


3. SharePoint Site Management


4. site collection quotas and locks

Select the appropriate site collection  and you will get the ID of that specific site collection



How to find out the ID of a subsite:

1. Save the current site as site template[.STP extension]


2. Save it to disk somewhere.


3. Now, navigate to that location and rename the file to .CAB extension.


4. Extract the CAB file and find the manifest.xml file.


5. Now, in the file check for the site ID/TemplateID string and get the value.


6. Navigate to end of this post for the TemplateID to Name mapping.

How to find out the List ID:

1. Navigate to the SharePoint list using the browser.


2. Select the Settings + List Settings menu command.


3. Copy the URL from the browser address bar into Notepad. It will look something like:

https://personal.collaborationtools.consumer.citigroup.net/personal/ag14178/_layouts/listedit.aspx?List=%7B47F2F5E2%2D6474%2D4929%2DB986%2D64BBE801C97A%7D



Delete everying before and including “List=”.

Change “%7B” to “{”

Change all “%2D” to “-“

Chnage “%7D” to “}”

You are now left with the Id:



{47F2F5E2-6474-4929-B986-64BBE801C97A}

Your client does not support opening this list with Windows Explorer

we are very much familiar with this error message and know what exactly needs to be done if such issue occurs. But this issue varies if operating system changes from XP to Windows Vista.

 FYI- This is a known issue with windows vista OS and we have a Microsoft KB for this: http://support.microsoft.com/kb/841215

 Before we can go ahead and conclude on to above mentioned KB, make sure to check the following points:

 1)    Web client service should be started

2)    You can also get the error if the URL to the document library is 100 characters long

3)    If you are using Internet Explorer 6 you will get the error. You know it’s time to upgrade

 It would be a good question as What exactly this KB suggest ?

 Please refer the following info:

         Click Start

        type regedit.exe in the Start Search box

        Locate and expand the list and navigate to the following location

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameter

        Locate the value BasicAuthLevel

• Right click the value and choose Modify.


• In the Value data box, type 2, and then click OK.

        Exit Registry Editor, and then restart the computer.

 Note: We will not do any kind of changes inside the registry so this should be done with the help of Desktop Support Team

 If it’s a Windows Server 2008 OS then please check the following:

        Open up the Windows Server Manager.

        Click Features in the left hand menu

        Click Add Features, in the main window.

        Select the Desktop Experience feature, and then click Next.

        Click Install.

        Click Close when the Add Features wizard is done.

        Choose to reboot when done.

 If it’s a Windows Server 2003 OS then please check the following:

 Download and install the Microsoft Hotfix

Windows Office needs a Web Client update to work properly with WebDAV.

SharePoint: Unable to start “Excel Calculation Services”

ISSUE:
=======

–When trying to start “Excel Calculation Services” under central administration–Services on Server, getting error message

“Unknown Error”

Or

“Failed to resolve the site ID for ‘Office Server Web Services’.”

–When we check the Event Viewer–Application Logs, getting following event ID 7034
Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          7/30/2009 9:04:35 AM
Event ID:      7034
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <SharePoint Server Name>
Description:
An attempt to start/stop instance  of service Excel Calculation Services on server <SharePoint Server Name> did not succeed.  Re-run the action via UI or command line on the specified server. Additional information is below.

Cannot open database “SharedServices1_DB” requested by the login. The login failed.
Login failed for user ‘Domain Name\<SharePoint Server Name>$’.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event“>
<System>
<Provider Name=”Windows SharePoint Services 3″ />
<EventID Qualifiers=”0″>7034</EventID>
<Level>2</Level>
<Task>807</Task>
<Keywords>0×80000000000000</Keywords>
<TimeCreated SystemTime=”2009-07-30T16:04:35.000Z” />
<EventRecordID>15441</EventRecordID>
<Channel>Application</Channel>
<Computer><SharePoint Server Name></Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>Excel Calculation Services</Data>
<Data><SharePoint Server Name></Data>
<Data>Cannot open database “SharedServices1_DB” requested by the login. The login failed.
Login failed for user ‘Domain Name\<SharePoint Server Name>$’.</Data>
</EventData>
</Event>

Resolution:
===========
1. Find the command prompt under the start menu, right click on it and choose ‘Run as Administrator’.

2. Change directories to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin.

3. Run the following command:

STSADM.EXE -o provisionservice -action start -servicetype “Microsoft.Office.Excel.Server.ExcelServerSharedWebService, Microsoft.Office.Excel.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”

You try to attach a word document in Sharepoint and error get an Error "Ambiguous name detected: tmp.dde"

Resolution:

·         Research on the above error and found that if we rename normal.dot and reopen the word it will recreate it.

·         Close all the word document and rename NORMAL.DOT

·         You will find that under :

·         C:\Documents and Settings\<your SoeID>\Application Data\Microsoft\Templates

·         Open a blank word document and close it.

·         Check the location again, you will find that normal.dot will be created.

·         Ask the user to open the word document from the Sharepoint site and it should work fine

Found that it is Documented In Microsoft KB articles

http://support.microsoft.com/kb/165860

There are 2 methods mentioned in the Kb

 Method 1: Delete the Tmpdde Macro

Method 2: Rename Normal.dot

Not able to map a SharePoint site as a Mapped drive

OS -  XP SP2  

Error : The format of the specified network name is invalid

Cause = Webclient is diabled on the cleint machine

 Steps to Enable webclient

 Start => run

In the run box type services.msc

 we will find webclient service right click and open the properties and change it from disabled to automatic or manual and start the service apply the changes 

Now we can then map the drive 

However one more thing to add is we had to specify the url as \\sitename\sites\sitecollectionname

List of MOSS 2007 Template ID Information

0 - GLOBAL (SetupPath=global) - "Global template"

1 - STS - "windows SharePoint Services Site", "Team Site", "Blank Site", "Document Workspace"

2 - MPS - "Basic Meeting Workspace", "Blank Meeting Workspace", "Decision Meeting Workspace", "Social Meeting Workspace", "Multipage Meeting Workspace"

3 - CENTRALADMIN - "Central Admin Site"

4 - WIKI - "Wiki Site"

7 - BDR - "Document Center"

9 - BLOG - "Blog"

20 - SPS (OBSOLETE) - "SharePoint Portal Server Site"

21 - SPSPERS - "SharePoint Portal Server Personal Space"

22 - SPSMSITE - "Personalization Site"

30 - SPSTOC (OBSOLETE) - "Contents area Template"

31 - SPSTOPIC (OBSOLETE) - "Topic area template"

32 - SPSNEWS (OBSOLETE) - "News area template"

33 - SPSNHOME (SubWebOnly) - "News Home template"

34 - SPSSITES - "Site Directory area template"

36 - SPSCOMMU (OBSOLETE) - "Community area template"

38 - SPSREPORTCENTER - "Report Center Site"

39 - CMSPUBLISHING (SetupPath=SiteTemplates\PUBLISHING) - "Publishing and Team Collaboration Site"

40 - OSRV (SetupPath=SiteTemplates\OSRV) - "Shared Services Administration Site"

47 - SPSPORTAL - "Corporate Intranet Site"

50 - SRCHCEN - "Search Center"

51 - PROFILES - "Profiles"

52 - BLANKINTERNETCONTAINER - "Internet Presence Web Site"

53 - BLANKINTERNET - "Publishing Site", "Press Releases Site", "Publishing Site"

54 - SPSMSITEHOST - "My Site Host"

90 - SRCHCENTERLITE (SetupPath=SiteTemplates\SRCHCENTERLITE) - "Search Center Lite"

6221 - PWA (SetupPath=SiteTemplates\PWA) - "Project Web Access Site"

6215 - PWS (SetupPath=SiteTemplates\PWS) - "Project Workspace"

14483 - OFFILE - "Records Repository", "Records Repository"

Wss 3.0 / Moss 2007 Build Versions

WSS 3.0				MOSS 2007
Release	Version	KB		Release	Version	KB
RTM	12.0.4518.1016	n/a		RTM	12.0.4518.1016	n/a
Public DST	12.0.6039.5000	934525		Public DST	12.0.6034.5000	937832
SP1	12.0.6219.1000	936988		SP1	12.0.6219.1000	936984
Post SP1 (Jan) (Global)	12.0.6300.5000	941422		Post SP1 (Jan) (Global)	12.0.6300.5000	942819
Post SP1 (Jan)	12.0.6300.5000	941653		Post SP1 (Jan) (Global)	12.0.6301.5000	945089
Post SP1 (Feb)	12.0.6303.5000	948945		Post SP1 (Jan) (Global)	12.0.6301.5000	941274
Post SP1 (Feb) (Global)	12.0.6304.5000	949399		Post SP1 (Feb) (Global)	12.0.6303.5000	948947
Post SP1 (Mar) (Global)	12.0.6305.5000	949749		Post SP1 (Feb) (Global)	12.0.6304.5000	949402
Post SP1 (Mar) (Global)	12.0.6306.5000	949956		Post SP1 (Mar) (Global)	12.0.6306.5000	949955
Post SP1 (Mar) (Global)	12.0.6307.5000	950279		Post SP1 (Mar) (Global)	12.0.6307.5000	950280
Post SP1 (Mar) (Global)	12.0.6308.5000	950484		Post SP1 (Mar) (Global)	12.0.6307.5000	950292
Post SP1 (May) (Global)	12.0.6314.5000	952288		Post SP1 (Mar) (Global)	12.0.6308.5000	950487
Post SP1 (May)	12.0.6314.5000	952292		Post SP1 (May) (Global)	12.0.6314.5000	952294
Post SP1 (May) (Global)	12.0.6315.5000	952698		Post SP1 (May) (Global)	12.0.6315.5000	952704
Post SP1 (May) (Global)	12.0.6316.5000	953137		Post SP1 (May) (Global)	12.0.6316.5000	953138
Post SP1 (June) (Global)	12.0.6317.5000	953473		Post SP1 (June) (Global)	12.0.6317.5000	953471
Post SP1 (June)	12.0.6317.5000	953484		Infra Update (Global)	12.0.6318.5000	951297
Infra Update (Global)	12.0.6318.5000	951695		Post SP1 (July) (Global)	12.0.6324.5000	955593
Post SP1 (July)	12.0.6324.5000	955594		Post SP1 (July)	12.0.6324.5000	955586
Post SP1 (AAM)	12.0.6324.5001	956248		Exel Security fix (Global)	12.0.6317.5000	953397
Aug CU (Global)	12.0.6327.5000	956057		Aug CU (Global)	12.0.6327.5000	956056
Aug CU	12.0.6327.5000	957109		Oct CU	12.0.6331.5000	957693
Oct CU (Global)	12.0.6332.5000	957691		Oct CU	12.0.6331.5000	958569
Dec COD (Global)	12.0.6335.5000	959644		Dec COD (Global)	12.0.6335.5000	959637
Dec CU	12.0.6335.5000	960010		Dec CU	12.0.6335.5000	960011
Dec COD (Global)	12.0.6336.5001	961175		Dec COD	12.0.6336.5001	961176
Feb 2009 CU	12.0.6341.5000	961755		Dec COD	12.0.6336.5002	963022
SP2	12.0.6421.1000	953338		Feb 2009 CU	12.0.6341.5001	961756
April 2009 CU	12.0.6504.5000	968850		SP2	12.0.6421.1000	953334
Jun 2009 CU	12.0.6510.5001	971538		April 2009 CU	12.0.6504.5000	968851
Aug 2009 CU	12.0.6514.5004	973400		Jun 2009 CU	12.0.6510.5003	971537
Oct 2009 CU	12.0.6520.5000	974989		Aug 2009 CU	12.0.6514.5002	973399
Dec 2009 CU	12.0.6524.5000	977027		Oct 2009 CU	12.0.6520.5000	974988
Feb 2010 CU	12.0.6529.5000	978396		Dec 2009 CU	12.0.6524.5001	977026
April 2010 CU	12.0.6535.5002	981043		Feb 2010 CU	12.0.6529.5000	978395
Jun 2010 CU	12.0.6539.5000	983311		April 2010 CU	12.0.6535.5002	981042
Aug 2010 CU	12.0.6545.5001	2276474		Jun 2010 CU	12.0.6539.5000	983310
Oct 2010 CU	12.0.6548.5000	2412268		Aug 2010 CU	12.0.6545.5001	2276472
Dec 2010 CU	12.0.6550.5002	2458606		Oct 2010 CU	12.0.6548.5000	2412267
Feb 2011 CU	12.0.6554.5000	2475886		Dec 2010 CU	12.0.6550.5000	2458605
April 2011 CU	12.0.6557.5000	2512783		Feb 2011 CU	12.0.6554.5000	2475885
June 2011 CU	12.0.6562.5000	2544399		April 2011 CU	12.0.6557.5000	2512782
Aug 2011 CU	12.0.6565.5001	2553022		June 2011 CU	12.0.6562.5000	2544398
SP3	12.0.6608.1000	2526305		Aug 2011 CU	12.0.6565.5000	2553020
Oct 2011 CU	12.0.6654.5000	2596541		SP3	12.0.6608.1000	2526299
Dec 2011 CU	12.0.6656.5000	2596987		Oct 2011 CU	12.0.6654.5002	2596540
Feb 2012 CU	12.0.6658.5000	2597959		Dec 2011 CU	12.0.6656.5001	2596986
April 2012 CU	12.0.6661.5000	2598130		Feb 2012 CU	12.0.6658.5000	2597958
				April 2012 CU	12.0.6661.5000	2598129