myspace views counter
Skip to main content

Adnan Ahmed (SharePoint Architect)

Go Search
Home
Adnan Ahmed
Project Server Gurus
KANAV
Mohammed MOSS2007
Ajaz
skamuju
Pathik's SharePoint Blog
Sanjay's SharePoint World
Sankar Adapa
Sharepoint With Amit
Need a blog here!
  

Microsoft Office SharePoint Server 2007 Gurus > Adnan Ahmed (SharePoint Architect) > Categories
Deployment Roadmap for WSS 3.0 and MOSS 2007 Updates

How to determine which version of  WSS 3.0 / Microsoft Office SharePoint Server 2007 you are using

 

Microsoft has also added a new section on the Microsoft TechNet web site http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx to help with identifying current required SharePoint patch levels. The latest SharePoint 2007 path level is released on 27th April, 2010. The latest SharePoint 2007 patch level is called April 2010 cumulative update (CU).

 

WSS 3.0/MOSS 2007 Patch Level

Microsoft KB Number

Version Number

Release Date

MOSS 2007 or WSS 3.0 April 2010 Cumulative Update

981042 / 981043

12.0.6535.5000

27th April, 2010

MOSS 2007 or WSS 3.0 April 2010 Cumulative Update

978395 / 978396

12.0000.6529.5000

23rd February, 2010

MOSS 2007 or WSS 3.0 December 2009 Cumulative Update

977026 / 977027

12.0.6524.5001

15th December, 2009

MOSS 2007 or WSS 3.0 October 2009 Cumulative Update

974988 / 974989

12.0.6520.5000

27th October, 2009

MOSS 2007 or WSS 3.0 August 2009 Cumulative Update

973399 / 973400

12.0.6514.5000

25 August 2009

MOSS 2007 or WSS 3.0 June 2009 Cumulative Update

971537 / KB 971538

12.0.6510.5000

15th July, 2009

MOSS 2007 or WSS 3.0 April 2009 Cumulative Update

968851 / 968850

12.0.6504.5000

30th April, 2009

MOSS 2007 or WSS 3.0 SP2

953334 / 953338

12.0.0.6421

28th April, 2009

MOSS 2007 or WSS 3.0 Infrastructure Update

951695 / 951297

 

 

12.0.0.6318

15th July, 2009

MOSS 2007 or WSS 3.0 SP1

936984 / 936988

 

 

 

12.0.0.6219

8th December 2007

 

 

 

 

SharePoint 2007 configuration wizard failed (Cannot connect to database server or database server does not exist)

Last week, I was building a SharePoint Integration environment on 64-bit VMware machines, which are hosted on VMware ESXi Server. All VMware machines in my environment are built on Windows Server 2008 operating system. The database server virtual machine is using SQL Server 2008 Sp1 (64 bit). After installing the SharePoint 2007 on one of my virtual machine, I have started the SharePoint Configuration Wizard. On Step 2 of configuration wizard, I have got an unusual error message that SharePoint cannot connect to my database server or database server name does not exist. I have seen similar type of messages during configuration wizard in the past and most of the time; the issue was to do with network connectivity.

My first thought was to ping the DB server from my SharePoint WFE virtual machine. Surprisingly, I was able to ping my DB Server by either DB Server Name or IP address. I have defined SQL Server aliases for my SQL Server, so I thought may be SharePoint does not like SQL Server alias name on windows 2008 server platform. I decided to connect SQL Server 2008 machine by creating an ODBC connection from SharePoint box. Surprisingly, I have found out that I could not be able to successfully connect SQL Server 2008 machine from SharePoint box by using ODBC connection. This means that SharePoint was not causing any issue in connecting the database server. After spending quite a bit of time on internet, trying to figure out this issue, I have found out that in windows 2008 server, windows firewall is enabled by default and it disabled all ports except Port 80. I tried to disable Windows 2008 firewall on SQL Server 2008 box and hurrah, I was able to create an ODBC connection successfully from the SharePoint server. I knew that Network Administrators don't like to disable Windows firewall completely. After further investigation, I have found out that you need to add SQL Server default port i.e. 1433 or whatever port number that you are using to communicate with SQL Server must be added in the exception list in the Windows firewall. Once you exclude SQL Server Port e.g. 1433 in the windows firewall, you can successfully pass the step 2 of SharePoint configuration wizard. Screen shot below describes how to exclude SQL Server Port in the windows firewall.

 

Content Deployment Error “Failed to read package file”.

When you run the incremental content deployment, you get the following exception during import operation.

Failed to read package file. at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request) at Microsoft.SharePoint.Deployment.SPImport.Run() *** Inner exception: Failure writing to target file at Microsoft.SharePoint.Library.SPRequest.ExtractFilesFromCabinet(String bstrTempDirectory, String bstrCabFileLocation) at Microsoft.SharePoint.Deployment.ImportDataFileManager.<>c__DisplayClass2.<Uncompress>b__0() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.SharePoint.Deployment.ImportDataFileManager.Uncompress(SPRequest request)

Reason: Insufficient disk space in the content deployment temporary location path on the destination server farm.

How to fix this problem: Delete files from the Content deployment temporary location and start the incremental crawl again. The problem will be resolved.

The Cab files are not always deleted and remain in the Content Deployment Folder location e.g. C:\Windows\ContentDeploymet\. To permanently resolve this issue, you must delete these temporary files by creating a scheduled job. Files older than 1 or 2 days can safely be deleted.

 

 

How to Configure PDF iFilter 9.0 for 64-bit operating system on MOSS 2007 Server Farm

Before the release of PDF iFilter 9.0, you have to install windows desktop search, PDF reader and iFilter 8.0 to configure PDF iFilter on MOSS 2007 environment. Now, Adobe has released PDF iFilter 9.0 for 64bit operating system, so configure of PDF iFilter is lot easier than before.

Steps required to configure PDF iFilter 9.0 on 64-bit OS running MOSS 2007 Server Farm

  1. Steps required on MOSS 2007 Server running as Indexing Server

a)    Install PDF iFilter 9.0 on MOSS 2007 Server running as Index Server in the farm. PDF iFilter 9.0 can be downloaded from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025

For 32-bit operating system, install Acrobat Reader 9.1 from http://get.adobe.com/reader/

b)    Verify that PDF has the correct settings in a registry location.

Run Regedit by browsing to c:\Windows\system32\regedt32.exe and double-clicking it.

Within left-side tree, browse to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf

Replace the {4C904448-74A9-11D0-AF6E-00C04FD8DC02} with new GUID i.e. {E8978DA6-047F-4E3D-9C78-CDBE46041603}

 

  1. Steps required on all MOSS 2007 Web Front End Servers

a)    Configure PDF icon for Document Library.

a.    Download pdf16.gif file and copy at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES  location.

b.    Add the following entry in docIcon.xml file, which can be found at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML

<Mapping Key="pdf" Value="pdf16.gif" />

c.    Add PDF File Type under Manage File Types link which can be found in SSP Admin, Search Settings page.

d.    Repeat steps 2.1,b,c on all front-end web servers

  1. Restart SharePoint Search Service

a)    Stop SharePoint Service

Launch the DOS command prompt and type: net stop osearch

b)    Start SharePoint Service

On the command prompt, type: net start osearch

  1. Perform full crawl on SharePoint Search

 

How to Configure SharePoint Treasure (Synonym) In MOSS 2007

The concept of treasures in SharePoint world is not new. It was also used in SharePoint 2003. Treasures are like synonym or similar words that you specify in SharePoint for keywords search.

 

The thesaurus permits you to type a phrase in a search query and to receive results for words that are related to the phrase that you typed. For Example, If user search for word "House", so you also would like to search for "Home", "Flat", "Apartment" etc. The concept of SharePoint Treasures is different than SharePoint Best Bets keywords. In SharePoint Best Bets keyword search, the result returned will be shown in the Best Bets web Part, so Best bets do not influence the ranking of Search Result. The down side in this approach is that you have to manage Best Bets URLs as time goes. So, if you add new page in the web site and you would like to show this page in the Best Bets Web Part, then you have to manually add this new URL in the Site Collection.

 

In the case of Treasures, you don't need to make any change in the configuration and new pages will automatically take effect immediately. You have to update the treasures from time to time, if you want to add more synonymous.

 

Follow the steps below to configure Treasures in SharePoint 2007:

 

1.    Find the SSP ADMIN Site GUID

  • Save the following commands in MS Notepad file as .VBS extension and run. It will display the SSP Admin Site GUID. Make note of GUID Information.

Set objGatherAdmin = WScript.CreateObject("oSearch.GatherMgr.1")

For Each objApplication in objGatherAdmin.GatherApplications

      WScript.echo "SSP: " & objApplication.DisplayName & " Application GUID: " & objApplication.Name

Next

2.    Locate Tsneu.xml FILE

The thesaurus files contain inactive sample content. The neutral Tsneu.xml thesaurus file is applied to queries that do not have a thesaurus file that is associated with the query language. The neutral thesaurus file is always applied to queries, even when there is a specific thesaurus file that is associated with the query language. So, we will only update the Tsenu.xml file for Treasures to work in SharePoint 2007 environment.

      Thesaurus files for SharePoint Server 2007 are located to the following folder:

Drive:\Program Files\Microsoft Office Servers\12.0\Data\Applications\[SSP Admin Site GUID]\Config\tsneu.xml

Note: Always look for drive where you have configured SharePoint 2007 Indexing. So, if SharePoint 2007 Indexing is configured on S:\Search\ drive, then the complete path will be as follows:

S:\Search\Program Files\Microsoft Office Servers\12.0\Data\Applications\[SSP Admin Site GUID]\Config\tsneu.xml

3.    Update Tsneu.xml file

Thesaurus files contain two types of thesaurus entries. These types are replacement sets and expansion sets. Thesaurus files also permit you to configure the word weighting and word stemming options in a replacement set or an expansion set. More details can be found at Microsoft KB 837847 article

§  Open the Tsneu.xml file in Notepad.

§  Remove the following comment lines that appear at the beginning and the end of the file:

o    <!---Commented out--->

§     Add the treasures or synonymous inside an <expansion> tag. In the expansion tag, you specify one or more substitutions that are enclosed by a <sub> tag. For the example that is described earlier, add the following lines:

§  <expansion>

§  <sub> House</sub>

§  <sub> Home</sub>

§  <sub> Apartment</sub>

§  <sub>Flat </sub>

§  <expansion>

§     Save the XML file. Must save the file in Unicode format.

4.    Re-start the SharePoint Search Service

Run the following command on command line:

NET Stop oSearch

NET Start oSearch

 

Things to Remember:

  You do not need to run Full Crawl or do IISRESET or Reset the Index in order for Treasure to work

  Expansion Tag in the Tsneu.XML must not be repeated. Treasures will stop working immediately. An error is also logged in the Event Viewer.

For Example, following <expansion> tags will generate error:

<expansion>

                <sub>Allowance</sub>

                <sub>Increase</sub>

</expansion>

<expansion>

                <sub>Income</sub>

                <sub>Profit</sub>

</expansion>

<expansion>

                <sub>Allowance</sub>

                <sub>Increase</sub>

</expansion>

 

<expansion>

                <sub>Guarantee</sub>

                <sub> Agreement</sub>

</expansion>

  The value of <Sub> tag must not be repeated in any other <expansion> tag entries. For example, the following statement will also generate error in the event viewer.

<expansion>

                <sub>Allowance</sub>

                <sub>Increase</sub>

</expansion>

<expansion>

                <sub>Asset Register</sub>

                <sub>Allowance</sub>

                <sub>Assets Register</sub>

</expansion>

§    When you try to open the Tsneu.xml file in Internet Explorer or any other XML Editor, you get the following error:

o    Error opening input file: 'tsSchema.xml'. Incorrect definition for the root element in schema. Error processing resource '...

o    Ignore this error as this XML validation will not affect treasure to work properly.

§     When you open the txneu.xml in Notepad, Make sure to save this file as Unicode.

Important Resources:

§    http://support.microsoft.com/default.aspx?scid=kb;en-us;837847

§    http://jopx.blogspot.com/2004/11/sharepoint-multilinguage-features.html

§    http://www.jjfblog.com/2007/10/adventures-in-office-sharepoint-2007.html

§    http://blogs.officezealot.com/mauro/archive/2008/07/24/21123.aspx

§    http://social.technet.microsoft.com/forums/en-US/sharepointsearch/thread/e8fd629e-89b9-43e1-83d8-6870795b4ac6/

 

Steps Required Installing MOSS 2007 with SP 1 on Medium Server Farm on Windows Server 2008 64-bit platform (IPV-6 enabled)

We all have done number of MOSS 2007 deployment on Medium Server Farm for our clients. This article only discusses the issues that you may encounter during MOSS 2007 installation on Windows Server 2008 on 64-bit system.

SharePoint Server 2007 RTM or WSS 3.0 will not install on Windows Server 2008.  It requires SP1.  Thus these bits simplify and reduce confusion resulting from users trying to install WSS 3.0 or SharePoint Server RTM versions directly on Windows Server 2008.  Previously, steps were required to add SP1 to the update folder.” (Extracted from msdn blog)

Different Approaches:

There are two approaches to deploy MOSS 2007 along with SP1 on a 64-bit Windows Server 2008.

1.    Gradual Installation of MOSS 2007 64-bit Windows Server 2008

a.    Install MOSS 2007 (Standard/Enterprise) Edition on 64-bit Windows Server 2008

b.    Configure farm including enabling services, creation of SSP Admin Site, MySite etc, Configure Search etc

c.    Install MOSS 2007 SP1 on all Web Front-End and Application Servers

2.    Install slipstream version also known as the Microsoft Office SharePoint Server 2007 with SP1. The slipstream version of MOSS 2007 with SP1 can downloaded from Microsoft Web Site

(32 bit) http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831&displaylang=en

 

(64 bit) http://www.microsoft.com/downloads/details.aspx?FamilyId=3015FDE4-85F6-4CBC-812D-55701FBFB563&displaylang=en

Note: Make sure to download OfficeServerwithSP1.exe from the URL above.

 

Steps Involved in using slipstream version of MOSS 2007 with SP1

As you notice above, obviously we should use slipstream version MOSS 2007 with SP1 to install SharePoint on Windows Server 2008 operating system.

Let’s take an example of a Medium Server Farm, which consist of four servers. One Web Front-end Server (WEB1), one Application Server (APP1) running SharePoint Services such as MS Excel service, Index, Search Query etc and one DB Server (DB1) running SQL Server 2008.

Points to Remember:

  • You must install MOSS on a clean installation of Windows Server 2008. If you uninstall and then reinstall MOSS may fail to create the config DBs. This article does not deal with the steps required to fix this issue.
  • You must use the Complete installation option on all servers you want to use as index, query or Excel services.
  • Setup installs Central Administration site on the first server on which you run setup. Ideally, you should not install Central Admin site on any other server. Make sure that you start your setup from application server, so you don’t have to deploy Central Admin Site on any of the Web Server that you will add in the same farm
  • You must install MOSS 2007 on the same drive on all load balanced front end web server computers
  • Follow Office SharePoint Server security account requirements to create service accounts for MOSS 2007.

Steps required installing MOSS 2007 with SP1 on Medium Server Farm:

Step 1: Build DB1 Server as Database Server

a.    Install SQL Server 2008 Standard Edition on DB1 Server

b.    Add SharePoint Setup Service Account (Domain user account) as:

o   Member of the Administrators group on each server on which Setup is run.

o   SQL Server login on the computer running SQL Server.

o   Member of the following SQL Server security roles:

§  securityadmin fixed server role

§  dbcreator fixed server role

Step 2: Build APP1 Server as SharePoint Application Server (APP1)

a.    Install .NET Framework 3.5. .NET Framework 3.5 can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

b.    Install MOSS 2007 with SP1 and make sure to select “Complete” as Server Type

c.    Run SharePoint Configuration Wizard to create new server farm.

Step 3: Build WEB1 Server as Front-end Web Server (WEB1)

a.    Install .NET Framework 3.5. .NET Framework 3.5 can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

b.    Install MOSS 2007 with SP1 and make sure to select “Web Front End” as Server Type

c.    Run SharePoint Configuration Wizard to connect to the existing server farm.

Step 4: Configure SharePoint Farm

a.    Configure following services on application server (APP1)

                              I.        Stop Windows SharePoint Services Web Application Service.

Note: APP1 server will not host any web application.

                            II.        Start Office SharePoint Search Service. Make sure to select “Use all web front end computers for crawling” for web front-end and crawling option. Otherwise SharePoint Search crawl will not work. This issue is discussed in detail here http://blogs.msdn.com/jmacleod/archive/2008/06/25/iis7-sharepoint-2007-fails-with-503-service-unavailable-errors.aspx  

Step 5: Create Host Header Names for SSP Admin, MySite and Web Application (Optional)

Create Host header names for SSPAdmin, MySite and Web application sites e.g.

  • SSPAdmin
  • MySite
  • DMS

Step 6: Create Portal Site and Run full crawl to index documents