|
Written by Administrator
|
|
Tuesday, 15 September 2009 11:17 |
|
Full procedure can be found detailed @ Microsoft's site here but to synthesize I would consider the following:
Important: If you know what and how, i reccomend you article about minimal downtime patching: Patch with minimal downtime
1. Back up the server farm before you start the software update installation. Create a backup of search and all databases. Have on mind that configuration DB and Admin DB cannot be restored in case of need, see: http://support.microsoft.com/kb/948725/en-us
To backup Configuration of your farm you have to do following:
2. Check the status of Timer Jobs. When you first installed Office SharePoint Server 2007 on your server farm, if you used an upgrade method — either in-place or gradual — and upgrade jobs remain in progress, the software update installation might fail. You must verify that none of the upgrade processes are running. Go to the SharePoint Central Administration site, click Operations, and in the Global Configuration section click Timer job status. If any upgrade jobs are listed, you must allow the upgrade to complete before you install the software update.
3. Check If there are orphaned objects in the content databases — orphans are items that do not have any parent or child relationships — the software update installation fails. To ensure that the installation succeeds, you must either fix the relationship of objects or drop the orphans before you begin the software update installation.
- To detect orphaned items, use the following syntax:
stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item>
- To delete orphaned items, use the following syntax:
stsadm -o databaserepair -url http://<URL_of_WindowsSharePointServices_Site> -databasename <name of database that contains the orphan item that is to be deleted> -deletecorruption
4. If you customized a predefined site template by directly modifying the site template files — an action that Microsoft does not recommend — the software update installation might overwrite some of the files that you modified, and your customizations in those files will be lost. You must reapply any site-template customizations after you install the software update.
So this was an easy part, just preparation for your patching, lets continue bellow with actual patching, where somehting can actually happen.
|
|
Read more... [How to patch MOSS 2007 - summary]
|
|
|
Written by KbNk
|
|
Monday, 14 September 2009 07:24 |
When you for some reason (or reason that is mentioned bellow) have to remove "Office sharepoint server search server" role from farm topology and for some reason it remain in stopping state following could help you.
Stop "Windows SharePoint Services Search" in computer management, or by typing net stop oSearch in command line on the Indexing server.
Then on affected server type stsadm -o execadmsvcjobs this will force all jobs that are hanging to complete. And after that you should be able to see that this role is Stopped.
After this, you can readd the role if you need and then start oSeatch service on index server by typing net start oSearch.
Possible reasons then this can happen.
You may face issue that index remain in propagating status and following errors appears on almost all servers:
|
|
Read more... [Office sharepoint server search server - Stopping]
|
|
Written by KbNk
|
|
Monday, 14 September 2009 13:00 |
Complete guide for gradual migration from SPS to MOSS including studying, planing, installing, migrating and best practicies.
If you think i am going to write complete guide that is already written milion times on internet, you are wrong i will post here links for good - already written - articles. Steps reccommendations and so on. Everything in one place, so you can get pretty good overview about installation and configuration.
So here are steps
1. Before you event start, and you have no knowledge about MOSS, or just very few. Read this perfect book about MOSS and WSS3.0
Beginning SharePoint 2007 Administration: Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007
by Göran Husman
ISBN: 978-0-470-12529-8; Paperback; June 2007; 600 pages
2. After you read this book :) i reccommend at least have a look on planning
|
|
Read more... [Complete guide for gradual migration from SPS to MOSS including studying, planing, installing, migrating and best practicies.]
|
|
Written by KbNk
|
|
Wednesday, 19 August 2009 13:44 |
|
Recently I had to upgrade my MOSS farm with Aprils CU. So I confirmed downtime, prepared myself to patch 6 servers and during nice saturday morning, started to patch.
I have doubleclicked installation exe file downloaded from microsoft.com and after 10 seconds following message appeared:
The detection failed, this can be due to a corrupted installation database
Basicaly that means that your installed database is not in good shape and process has difficulties to read required informations from it. So patching could not continue.
As this happened on all servers in the farm, initial talks about reinstalling whole MOSS 2007 were proscribed. Because of importancy, there was no time and opportunity to play and google, MS call had to be logged.
Actually.. I was pretty much surprised how fast it was sorted out and how proffesional two engineers were.
So you have two options how to solve this. (well basicaly three - you can remove all information about MOSS with Windows Installer CleanUp Utility -
http://support.microsoft.com/kb/290301 to remove all references to MOSS, delete all folders and install it again :-) But definetelty we dont want to go with this way )
1.there are many articles about this how to solve it just with regedit.exe. They are all similar to next few words:
|
|
Read more... [Solved: The detection failed, this can be due to a corrupted installation database]
|
|
Written by KbNk
|
|
Monday, 13 July 2009 17:55 |
Error 401.1 appears when you localy browse a Web site that uses Integrated Authentication in IIS 6.0 - issues you should be aware when applying workaround.
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or IIS 6, you receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address. You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
There is workaround that might be used and is recommended (by MS) you don't have to restart your server when applying this one (just IISRESET is reccomeneded).
READ bellow to see possible issues that can occur if you apply this hotfix !!
|
|
Read more... [Error 401.1 when browsing localy Sharepoint]
|
|
Written by KbNk
|
|
Monday, 06 July 2009 20:23 |
Here are some point I want to share with you I have learned during my last upgrade SPS2MOSS
Stsadm is commandline tool provided with WSS 3.0 actualy it was part of first software from Microsoft - SharePoint Team Services - therefor the STS.
Via the STSADM you are allowed to do almost all operations you are able to do via Sharepoint Central Administrator (SCA) and even more.
The best it you can use scripts to do anoying operational tasks for you.
Unfortunately not everything is included in basic package of stsadm and you cannot use it for everything from begining. But Microsoft finaly understood that not just they have programming skills but also few others on the planet.
You are able to write your own extensions for STSADM as it is "pluginable" now in the version 3.0.
Let say you have to migrate several hundreads of sites from WSS2.0 to WSS 3.0 using gradual approach and you want to migrate several sites per day/night. So you consider using scripts and STSADM, but it won't allow you to migrate just like that, as set of commands for it are not inlcuded for now..
First you need to install and deploy great and MUST set of extensions from Gary Lapointe.
|
|
Read more... [STSADM extensions for migration using script]
|
|
|
|
|
|
|
Page 3 of 4 |
| 
| 
| 
| 
