Tiago Duarte

Today a got a warning from the OS "You are running out of disc space!" What? 160GB is not enough anymore? After removing some stuff, like temporary files, cleaning the disc, and removing unecessary apps and installations, I decided to look for large files above 150MB and turns out there were about 60GB in SharePoint log files. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS) I did find some issues. SharePoint was trying to use Single Sign-On, while SSO wasn't enable on the farm. Well, since I don't really need logs I just stopped and disabled the WSS Tracing Service. At least now I don't have to worry about keeping an eye on that folder every once and a while.

Problem: If an upgrade is started using the stsadm command line tool, you will not able to start another upgrade process from the user interface. If you try to start a second instance of upgrade, the following error message will be displayed: "Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server "X"." http://www.blogger.com/img/blank.gif "X" is the name of the server that initiated the upgrade process. Solution: stsadm -o setproperty -pn command-line-upgrade-running -pv No http://technet.microsoft.com/en-us/library/cc288357%28office.12%29.aspx

[ERROR] [08-04-2011 11:05:54]: Upgrade object too new (build version = 12.0.6539.5000, schema version = 12.0.0.0). Current server (build version = 12.0.6425.1000, schema version = 12.0.0.0). After trying almost everything, I managed to get the command working by changing, the... registry! HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0 Key: BuildVersion Value 12.0.6425.1000 To the actual installed version located in C.A. Operations, Servers in Farm (12.0.6554.5000) then it worked! stsadm –o upgrade –inplace –forceupgrade Latest WSS Cummulative Update (12.0.6554.5000) http://support.microsoft.com/kb/2475886 Latest MOSS Cummulative Update (12.0.6554.5000) http://support.microsoft.com/kb/2475885 WSS/MOSS VERSIONS http://insomniacgeek.com/how-to-determine-the-installed-sharepoint-version/ Source http://vandanarathore.blogspot.com/2009/06/b2b-upgrade-fails-with-error-upgrade.html

Problem: SharePoint Configuration wizard throws Invalid List Template while adding a server to a farm Solution: Check servers for missing XML templates from one another. Make sure all servers have all language folders: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\1033\XML C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\2070\XML http://www.richardawilson.com/2010/09/erors-adding-server-to-farm-invalid.html

using (SPWeb web = (SPWeb)properties.Feature.Parent) don't use SPContext!

WSS 3.0 Error: Cannot make a cache safe URL for "SpellCheckEntirePage.js", file not found. Please verify that the file exists under the layouts directory. Don't know why it has gone missing but here's the solution: Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\ [your_language_LCID] copy SpellCheckEntirePage.js and SpellChecker.js to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033