| Brijesh's profileBrijesh's spacePhotosBlogLists | Help |
|
|
October 18 Step by step installation of Service Pack1 for Microsoft Office SharePoint Server 2007 - MOSS 2007 SP1These steps assume following SharePoint topology: 1. SPSRVR1: Query Server and SharePoint Central Administration Site 2. SPSRVR2: Index Server and Dedicated Web Front End server for crawling 3. SPDB: Database Server – SQL Server 2005 Note: We have heterogeneous environment, where SPSRVR1 and SPSRVR2 have Windows Server 2003 Enterprise Edition with SP1-32 bit (x86) and SPDB has Windows Server 2003 Enterprise Edition with SP1-64 bit. We have installed Microsoft Office SharePoint Server 2007 Standard Edition-32 bit (x86) with SQL Server 2005 Standard Edition with SP1-64 bit. SharePoint Topology overview: ExchangeServer2003: SPSRVR1: SPSRVR2: SPDB: Steps to install Service Pack1 for Microsoft Office SharePoint Server 2007: 1. Stop Word Wide Web Publishing Services on SPSRVR1 server. Use following batch file, 2. Stop Word Wide Web Publishing Services on SPSRVR2 server. Use following batch file, 3. Download and Run (double click on .exe file) WSS 3.0 SP1 on SPSRVR1 server. 4. Read the license terms and click “Accept” button. 5. Click “Continue”. 6. At the reminder message click “OK”. 7. At the installation complete message click “OK”. 8. If SharePoint Products and Technologies Configuration wizard starts, CANCEL/CLOSE it. 9. Repeat steps 3-8 for SPSRVR2 server. 10. Download and Run (double click on .exe file) MOSS 2007 SP1 on SPSRVR1 server. 11. Read the license terms and click “Accept” button. 12. Click “Continue”. 13. At the reminder message click “OK”. 14. At the installation complete message click “OK”. 15. At the end of the software update installation, SharePoint Products and Technologies Configuration wizard starts, if it does NOT then go to Start > All Programs > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard to start it manually. 16. On the SharePoint Products and Technologies Configuration wizard welcome screen, click “Next” button. 17. Click “Yes” if it notifies for services might need to be restarted. 18. On completing SharePoint Products and Technologies Configuration wizard, click “Next”. 19. When the dialog box about installation in a server farm appears, do NOT click “OK”. Instead leave each server with the following dialog box displayed. “You must run setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run setup and the configuration wizard on the other servers now, and then return to this server and click “OK” to continue.” 20. Repeat steps 10-19 for SPSRVR2 server. 21. Return to SPSRVR1 server and click “OK” button to finalize the installation. 22. SharePoint Products and Technologies Configuration wizard will go through configuration steps (typically from step1-9). 23. On the configuration successful page, click “Finish”. 24. Verify installation. Open SharePoint Central Administration site, Click Operations > Topologies and Services > Servers in Farm and verify version number next to each server, it should be 12.0.0.6219. You may check log files to review any errors while installing updates (SP1). Log files can be found at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS with the name “Upgrade.log”. 25. Go to SPSRVR2 server and click “OK” button to finalize the installation. 26. Go through steps 22-24 for SPSRVR2 server. 27. After you verify that the installation of Service Pack1 was successful for both the servers – SPSRVR1 and SPSRVR2 servers, start Word Wide Web Publishing Services on SPSRVR2 server and then on SPSRVR1 server. Use following batch files, “C:\ Stop And Start All SharePoint Services\Start SharePoint Services SPSRVR2.bat” “C:\ Stop And Start All SharePoint Services\Start SharePoint Services SPSRVR1.bat” 28. Verify access to SharePoint application – SharePoint sites. It should be available to all (Intranet). Note: It would be a good idea to reboot all the SharePoint servers in the farm after installing Service Pack 1 for Microsoft Office SharePoint Server 2007 – MOSS 2007. Here are the batch files to stop and start all SharePoint services while updating the SharePoint server farm, 1. Stop SharePoint Services SPSRVR1.bat/SPSRVR2.bat:
echo This script will stop all SharePoint and IIS Services. Press any key to continue... pause net stop w3svc pause
2. Start SharePoint Services SPSRVR1.bat/SPSRVR2.bat: echo This script will start all SharePoint and IIS Services. Press any key to continue... pause net start w3svc pause Note: You may stop and start World Wide Web publishing service (w3svc) only while installing Service Pack 1 for your Microsoft Office SharePoint Server 2007 however we decided to stop and start all SharePoint and IIS services. References: October 08 Query Server is not responding and SharePoint Search is brokenThis post is in reference to my previous post regarding SharePoint Search issue. I have tried to add detailed resolution steps for that issue. Issue: Query Server does not respond for content index propagation and SharePoint search does not work for searching new contents. It may work for searching old contents. These steps assume following SharePoint topology: 1. SPSRVR1: Query Server and SharePoint Central Administration Site Note: We have heterogeneous environment, where SPSRVR1 and SPSRVR2 have Windows Server 2003 Enterprise Edition with SP1-32 bit (x86) and SPDB has Windows Server 2003 Enterprise Edition with SP1-64 bit. We have installed Microsoft Office SharePoint Server 2007 Standard Edition-32 bit (x86) with SQL Server 2005 Standard Edition with SP1-64 bit. Create a new folder (e.g. “Applications2”) on SPSRVR1 (Query Server) for content index propagation. There is no need to share it. SharePoint will do it automatically and remove sharing for “Application” folder (original location for content index propagation). It is highly recommended to create a new folder (“Application2”) at the same level as its original folder (“Application”). Run following command on SPSRVR1 (Query Server) Note: Do not move existing content index from old location (“Application”) to a new location (“Application2”) manually. In fact, SharePoint does it automatically once you create a new location for content index propagation and run above command E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications on SPSRVR1 – Query Server (Currently it is 4.84 GB with the items in index = 1271197) E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications on SPSRVR2 – Index Server (Currently it is 12 GB with the items in index = 1271197) Above command should reinitialize Query Server for Shared Service Provider- SSP in your SharePoint Server farm. Check Search Settings from SharePoint Central Administration site. Index Server should start propagating content index to a new location on Query Server with the message stating “Propagating to new Query Server (Name of the Query Server). Once “Indexing Status” and “Propagation Status” are idle, you should start “Full Crawl” to crawl the new contents and update the content index which will be propagated to a new location on Query Server automatically. This should fix your issue and SharePoint search should be working fine for searching new as well as old contents after you finish “Full Crawl”. |
|
|