May 2008 - Posts

• MOSS build 12.0000.6315.5000 Prime Update will be available publicly in June

  Hey Community, Just to make you all aware that the Prime Rollup update is now available on request for Premier customers if required now, taking you to build 12.0000.6315.5000 and publicly available in June 2008. This hotfix come in the standard way of a WSS fix [KB Article Number(s): 942489, 952698] and a MOSS fix [KB Article Number(s): 942489, 952704]. There are a lot of fixes within this prime rollup from a publishing perspective [CMS]. Issue: With regards to applying this build 12.0000.6315.5000 once you have applied the fixes that there is an slight issue starting the "SPAdmin Service". The timeout period for this service is to short and you will get an error in the Event Logs showing an error of  "The service process could not connect to the service controller". If you try to manually start this service this is not possible. To successfully start the SPAdmin service you have to modify/add two registry values: 1. HKLM\SYSTEM\CurrentControlSet\Control     ->         add/modify DWORD value ServicesPipeTimeout to 60000 (60 seconds) [Make sure the base type is decimal] 2. HKLM\SYSTEM\CurrentControlSet\Control     ->         add/modify STRING value WaitToKillServiceTimeout to 120000 (120 seconds) [Make sure the base type is decimal] 3. Reboot the server 4. Manually start the SPAdmin service using: net start spadmin   Posted May 27 2008, 12:51 PM by bobbyhabib with 1 comment(s) Filed under: MOSS, SharePoint Services Objects, MOSS Version

• Getting the correct MOSS / WSS version for each server in the farm

  I have seen a few blogs recently talking about how to get the correct version of MOSS from your server's in your server farm. Sound easy enough. What I have seen; are articles telling you to go to the web sites properties of your site collection in IIS and then to select the HTTP Headers tab, here you will see a "Custom HTTP headers" text box which displays a version number of MOSS. GREAT! or Go to "Add/Remove Programs" within control panel select "Microsoft Office SharePoint Server 2007" and click "Click here for support information". On the dialog you will see a version number indicating MOSS version. Suppose to be good!  If you think this is correct then read on! This method of getting the version number for MOSS is not correct. What you will see in the HTTP header tab in IIS is the build version of MOSS at the time when the Virtual Directory [Web Application] was created, if you patch the server with a Service Pack, Hot Fix or a Roll up Fix, the HTTP header tab is not updated with new build version number on existing sites, which can confuse a lot of people.  If you create a Web Application [Virtual Directory] after you have patched the server you will get the Build Version number of MOSS, at the time the site is created. I bet most SharePoint veterans must have wondered why one HTTP header on there site collections may have been different to another site collection on the same server. It proberbly because you have created both site collections at different times with different patches applied to your farm. I noticed that the "Add/Remove Program" method too did not update. The correct way to get this information is to open up "Central Admin", click on "Operations" and then click on "Servers in Farm". in this administration page you will see the Database Schema Version in the top of the screen and a list of servers with the version numbers listed in the relevant column against each server in the farm. You can also see the database schema version in "Site Settings", "Modify All Site Settings" in the Site Information section. The other alternative is to look at the MOSS configuration database [SQL Server] of your site collection and open the Versions table, there will be entires in this table with the versions that have been applied to in your farm and the date when the Service Pack, hot Fix or Rollup was applied. I have listed below the version numbers for MOSS; MOSS 2007 or WSS 3.0 Hotfix (KB953484 - KB953473 - KB953471)   12.0.0.6317.500 MOSS 2007 or WSS 3.0 Hotfix (KB953138 - KB953137)   12.0.0.6316.500 MOSS 2007 or WSS 3.0 Hotfix (KB952704)                     12.0.0.6315.500 MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB952294)       12.0.0.6314.500 [In SSP admin you will get a new Search Administration option, which brings the Search Server features to MOSS.] MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB948945)       12.0.0.6303 MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941274)       12.0.0.6301 MOSS 2007 or WSS 3.0 post-SP1 hotfix (KB941422)       12.0.0.6300 MOSS 2007 or WSS 3.0 SP1                                         12.0.0.6219 MOSS 2007 or WSS 3.0 October public update                12.0.0.6039 MOSS 2007 or WSS 3.0 August 24, 2007 hotfix package  12.0.0.6036 MOSS 2007 or WSS 3.0 RTM                                         12.0.0.4518 MOSS 2007 or WSS 3.0 Beta 2 TR:                                12.0.0.4407 MOSS 2007 or WSS 3.0 Beta 2:                                     12.0.0.4017 Posted May 16 2008, 06:01 PM by bobbyhabib with 5 comment(s) Filed under: MOSS Version, Fam Version

• Troubleshooting SPSite/SPWeb leaks in WSS v3 and MOSS 2007

  Just wanted to make the community aware of a new blog just written by Stefan Gobner (EE Engineer at Microsoft and also a colleague of mine). He explain very well the steps that can be taken by SharePoint Administrators to isolate if a site that contains custom code, which does not properly dispose objects correctly and also how you can isolate components that are leaking these objects. http://blogs.technet.com/stefan_gossner/archive/2008/05/07/troubleshooting-spsite-spweb-leaks-in-wss-v3-and-moss-2007.aspx  Keep up the great work Stefan your a living legend. Posted May 15 2008, 02:41 AM by bobbyhabib with 1 comment(s) Filed under: Custom Objects, SPWeb, SPSite, Leaks, Dispose