Hello, Has anyone applied Security Patch MS10--039 for MOSS 2007? This security patch was released on the 8th of June and I wanted some feedback in regards to any issues that are not documented. My enviornment uses CAC authentication with Kerberos and ADFS, therefore; it's easy to break. Thanks, Dennis

Original question is just asking for feedback since 983444 and SharePoint v3 is having some issues. Unable to connect to configuration database after installing KB983444: http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/c054514a-4c1d-47d5-a2bc-d8c3c7a6870d To Dennis I've not yet seen anyone report issues with MOSS but I'm not sure they've updated yet.

We are having issues in our test lab after installing this patch. Running "psconfig -cmd upgrade -inplace b2b -force -wait" that Didn't fix the problem either. I am getting the below error and in the Upgrade log it keeps saying ReflexiveUpgrade [SPServer Name=SPdf Parent=SPFarmsacc Name=SP_Config] failed. [SPManager] [ERROR] [6/24/2010 3:16:04 PM]: The access control list on C:\Inetpub\wwwroot\wss\VirtualDirectories\80\wpresources\web.config could not be modified because the path could not be located in the file system. I see a web config file @ C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\layouts\web.config and @C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config I dont see whats causing the patch to look for web config file in C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN> psconfig -cmd upgrade -inplace b2b -force -wait SharePoint Products and Technologies Configuration Wizard version 12.0.6500.5000 Copyright (C) Microsoft Corporation 2005. All rights reserved. Performing configuration task 1 of 4 Initializing SharePoint Products and Technologies upgrade... Successfully initialized SharePoint Products and Technologies upgrade. Performing configuration task 2 of 4 Initiating the upgrade sequence... Successfully initiated the upgrade sequence. Performing configuration task 3 of 4 Upgrading SharePoint Products and Technologies... Failed to upgrade SharePoint Products and Technologies. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Upgrade completed with errors. Review the u pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se rver Extensions\12\Logs\Upgrade.log. The number of errors and warnings is liste d at the end of the upgrade log file. Total number of configuration settings run: 3 Total number of successful configuration settings: 2 Total number of unsuccessful configuration settings: 1 Successfully stopped the configuration of SharePoint Products and Technologies. Configuration of SharePoint Products and Technologies failed. Configuration mus t be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at C:\Program Files\Common Files\Micros oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_6_24_2010_15_15_54_98_36 9751619.log and the application event log.

There is a good article from Joel Oleson on this patch at http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=353 Also, the MS SharePoint team blog published this: http://blogs.msdn.com/b/sharepoint/archive/2010/06/22/installing-kb938444.aspx According to the MS article it should only affect customers with WSS 3.0 standalone installations. The key message from MS is that is is a recommended security patch and it should be installed ASAP. As with all security patches, it should be fully regression tested in a test environment prior to rolling it out. HTH.Benjamin Athawes - Twitter: @benjaminathawes - Blog: http://mossblogger.blogspot.com - Email: mail at bathawes.com

http://blogs.technet.com/b/sbs/archive/2010/06/18/companyweb-and-sharepoint-central-admin-not-accessible-after-installing-kb983444.aspx Solution: For most issues the resolution will be to be to forcefully finish phase two and complete the provisioning of the databases. To do this, follow these steps: Open the Services snap-in and Restart the Windows Internal Database service. Run the following command from an elevated command prompt (if the command fails, note the error and run the command again, in some occasions due to some timing considerations, it might have to be run multiple times before it works, we would suggest trying it 2 or 3 times). C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force The command may take a long time to run. If it completes successfully, SharePoint Central Admin and Companyweb should work (confirm IIS services are running, bindings are correct, etc.) After the psconfig completes, check the following: If SharePoint Central Admin works but Companyweb does not, check the bindings for the web site in IIS, we’ve seen some cases where they are missing. The previous steps take care of most of the issues, on a few others we’ve seen issues with abnormally configured custom accounts for the Search Service causing problems. Here is a quick workaround to get you through the issue back to a working CompanyWeb if you are indeed hitting this issue. To verify that the Local Service account is being used for SharePoint Search, do the following: Click on Start > Run and type services.msc Right-click on the Windows SharePoint Services Search service and choose Properties Click on the Log On tab. If the account is anything other than Local Service, proceed with the following steps. To fix this, use stsadm to unprovision the search service so you can finish psconfig. After that, you should be able to access Sharepoint Central Administration to fix the login account and restore the functionality of SPSearch: Open an elevated cmd prompt and run the following command: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>STSADM.EXE -o provisionservice -action stop -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search,Version=12.0.0.0,Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename spsearch Complete Steps 1-3 from the previous section. Once they complete and you have a working SharePoint Central Administrator and CompanyWeb sites, proceed to the next set of steps. Change the login account for SPsearch to Local Service. Open Sharepoint Central Administration > Operations > Services on Server Click on Windows SharePoint Services Search Select Local Service under predefined for service account and content access account, then click OK Use stsadmin to reprovision the spsearch service: From an elevated cmd prompt, run the following command: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>STSADM.EXE -o provisionservice -action start -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search,Version=12.0.0.0,Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename spsearch You will not see any search results in SharePoint until a full crawl has been initiated and is successfully indexing the content. To trigger this, use stsadm: From an elevated cmd prompt, run the following command: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>STSADM.EXE -o spsearch –action fullcrawlstart Important: If you are receiving event 2436 for Windows SharePoint Services 3 Search after initiating the full crawl, then you need to follow the steps that are documented in the following blogpost: Event 2436 for SharePoint Services 3 Search. In fact, we have seen the occurrence of this issue become the reason why many customers change the login account for spsearch as an attempted workaround.Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog