Gavin’s Sharepoint Blog

Hi All,

Microsoft have just released a hotfix to search DCOM permission post SP1 problem which I wrote about previously.

The hotfix can be found here. http://support.microsoft.com/kb/953137

Hi All,

I’ve just stumbled across a problem post MOSS 2007 SP1.

After applying SP1 to an existing installation and running a full catastrophic backup it fails on the shared search index item with an error regarding UnauthorizedAccessException.  The environment I am experiencing this in is a single virtual machine that is a domain controller, SQL2005 SP2, and multiple domain service accounts for the farm service account, search service, etc.

The error can be seen in the spbackup.log as:-

[5/8/2008 2:59:48 AM]: Error: Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.
    UnauthorizedAccessException: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 80070005.
[5/8/2008 2:59:48 AM]: Debug:    at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
   at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
   at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.get_SearchApi()
   at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPrepareBackup(Object sender, SPBackupInformation args)
   at Microsoft.SharePoint.Administration.Backup.SPBackup.RunPrepareBackup(SPBackupRestoreObject node)

It looks like SP1 is blasting away the permissions on the OSearch DCOM application.

I’d like to thank Jason Medero with his post and /dev/arthur for his post on this issue which lead me to confirm what they had found.

While their posts talk about manually editing the DCOM launch permissions for the OSearch application, Ali Mazaheri on his article has a far simpler solution.

Just run the following command:

stsadm -o osearch -action start

After you run this command you can browse to the permissions of the the OSearch DCOM application and confirm that the sharepoint service accounts and the WSS_ADMIN_WPG and WSS_WPG groups have been granted local launch and local activation permissions.

Note that while I found this error while trying to run a backup, my application event log was full of errors similar to what Ali describes in his article. This just demonstrates that if you have errors in your event log after applying a patch or service pack, something has gone wrong and you need to investigate it.

If any of you are using the Microsoft System Centre Capacity Planner you might like to know about a bug I discovered yesterday.

The bug is that when you edit the model, modify the latency of the site to site connections and then save the model, after you re-open the model the latencies are reset to 10ms.

I posted the bug to the SCCP managed forum and I would like to compliment Jonathan Hardwick from Microsoft on his prompt response. He has confirmed the problem as a bug. So hopefully a patch or release will be available soon to fix the problem.

I just spotted this spreadsheet that Mark Arend has posted.

The Sharepoint 2007 permissions matrix is a great reference of the out of box permissions and how they map to the default groups.

I’ve printed this one in colour and “it’s going straight to the pool room!”

The other great reference is on the sharepoint solutions page. This is a collection of visio diagrams on all sorts of sharepoint topics. Search for the diagram on application security.

Microsoft have just released new templates for sharepoint via the Microsoft download site.

The first is the “SharePoint Templates: Preformatted document libraries for Windows SharePoint Services 3.0 and SharePoint Server 2007“

This download includes stp files for document libraries with sample docx templates. There are 5 examples:-

• Invoices
• Specifications
• Press releases
• Customer site visit reports
• Meeting notes

The second download is for the “Office SharePoint Server 2007 DoD 5015.2 Resource Kit“.  From what I’ve read about this one it looks quite complex and has caveats that you should engage a partner for an actual records management implementation.

Just stumbled across this on a Google search.

Adobe Labs have a pre-release of how to support Adobe Reader v8.1 ifilter on 64bit sharepoint.

I’ll admit that I haven’t tested this yet and it involves a 64bit ‘thunking’ layer. In the past I have seen some instructions on to use this technique to ‘hack’ together a custom 32bit ifilter handler onto a 64bit system.

The main significance of this is that currently the only cleanest way of supporting pdf indexing on sharepoint 64bit platforms is to use foxit pdf ifilter. However this is commercial software that is priced based on the number of CPU cores. (As at 25JAN2008 this was “License cost for each server with up to two CPU cores is $329.99. Each additional CPU core costs $129.99.”) Now with most production servers these days being dual quad core processors (ie 8 processing cores) This would be US$1109.93 for each production server. Congrats does go to foxit for seeing a large hole left in the market by Adobe being so slow to support the 64bit platform and providing a solution.

The other comment worth making is that the foxit 64bit ifilter may be coded natively in 64bit but I’m not sure of this. Whereas the Adobe solution is taking the existing 32bit ifilter in wrapping it into 64bit which does involve a processing cost overhead. If you had a large index with lots pdf documents then going for a native pdf ifilter could bring a significant performance difference.

‘cwhite’ has just posted on the sharepoint ‘from the field’ blog on a hotfix release to fix timer job issues. This has also been known as the ‘timer job shocker’. Initially I read some reports that it might be due to a security update to the .NET framework but it re-appeared for me. This one has been has been a tough one to track down so I’m glad to see that a hotfix has been released.

In the application event log you will see events for 7076, 6398, 6432 and for me I also saw 6482.

I’ll copy and paste the full events from my test server below.

The KB article is here. The anonying thing about this KB article is that it is categorised as only applying to IIS and not sharepoint even though the big driver to fix this seem to have been MOSS related. That means that it would be difficult to find this KB article if you are restricting your KB searches by product.

——————————————–

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer
Event ID:    6398
Date:        11/01/2008
Time:        12:10:08 PM
User:        N/A
Computer:    MOSSTEST
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 9668b02b-5f13-4963-bf0b-181c81272dea) threw an exception. More information is included below.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

——————————————–

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    6482
Date:        11/01/2008
Time:        12:14:07 PM
User:        N/A
Computer:    MOSSTEST
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (5e5393a6-039a-4896-a727-04818d85b326).

Reason: Exception from HRESULT: 0×80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0×80005006): Exception from HRESULT: 0×80005006
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
   at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
   at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
   at Microsoft.SharePoint.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

——————————————–

Event Type:    Error
Event Source:    Office SharePoint Server
Event Category:    Office Server Shared Services
Event ID:    7076
Date:        11/01/2008
Time:        12:14:08 PM
User:        N/A
Computer:    MOSSTEST
Description:
An exception occurred while executing the Application Server Administration job.

Message: Exception from HRESULT: 0×80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0×80005006): Exception from HRESULT: 0×80005006
   at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
   at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
   at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
   at Microsoft.SharePoint.Metabase.ApplicationPool.set_UserName(String value)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider srp)
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

——————————————–

I’m on sharepoint designer training this week and getting up to speed to sharepoint publishing and WCM.

I spotted another bizarre default behaviour in sharepoint yesterday.

If you have a publishing site and you apply individual permissions to pages (also known as fine grained permissions), which is not beyond the realm of possibility on an intranet or similar website by default these pages will not be included in the search results.

Go to the site settings for the site and from the ‘Site Administration’ column select ‘Search Visibility’. You will notice that aspx pages by default are not indexed if they have fine grained permissions.

This just seems to be a bizarre default setting. Given that search results are security trimmed why is the default behaviour not to index all aspx pages?

Anyhow change the setting to ‘Always index all aspx pages on this site’ and they will be indexed.

The nice thing on the screen above is that the sentence above the radio buttons will indicate if your site has fine grained permissions.

Well it’s finally been released, SP1 for MOSS / Sharepoint 2007.

The best place to start is the technet resource centre.

Looks like there a few ‘gotchas’!

Watch out for the known issue of killing the registry settings for the foxit pdf ifilter if you are using that.

Looks like go slow, take care and test, test, test, for applying this SP.

01-DEC-2007, just an update Joel has posted on the official sharepoint team blog a further update on SP1.

————————————————————————

Cezary Aniśko has just posted some notes that look like a high level summary of what will be in Sharepoint 2007 SP1. Unfortunately his post is in Polish, which not a language that I know. However there is still plenty of info that can be gathered from his post.

http://blogs.technet.com/canisko/archive/2007/11/28/service-pack-1-dla-sharepoint-server-2007-i-windows-sharepoint-services-3-0.aspx

I’m also copying it over there just in case it ‘disappears’.

———————————-

Service Pack 1 dla MOSS 2007 i WSS 3.0 wniesie:

· Wsparcie instalacji i pracy MOSS 2007 z SP1 i WSS 3.0 z SP 1 na Windows Server 2008. Ze stron Microsoft będzie można pobrać odpowiednio przygotowane pliki instalacyjne MOSS 2007 i WSS 3.0 zawierające w sobie SP1

· Wsparcie technologii AJAX. Możliwe będzie używanie Microsoft AJAX 1.0 Control toolkit dla Microsoft ASP.NET, AJAX 1.0 Extensions dla ASP.NET

· Remote Blob Storage API w WSS 3.0 (937901). Pozwoli ISVs budować providery do składowania plików na zewnątrz SQL Server. Odpowiednie API zostanie dodane do SDK

· SP 1 będzie zawierać w sobie 60 hotfix’ów (MOSS i WSS)

· Nowe komendy STSAdm:

• Mergecontentdbs – For consolidating or repartitioning site collections across content databases (939035)
• Rename site – renaming host named site collections (939535)

· People Picker ability to scope to an OU (806244)

Najważniejsze hotfixy zawarte w SP1

• Hotfix 926284: List view web part not retained saving template

• Hotfix 938888: Edit document fails/IE Crash side by side Office

• Hotfix 938663: Timer jobs delayed one hour because of DST

• Hotfix 936867: Inherit permissions causes destructive error (lose permissions to site)

• Hotfix 930807: Cannot open WSS alerts in Outlook cached mode

• Hotfix 932816: Workflow not continue after Pause For Duration

• Hotfix 936867: Export fails with FatalError User cannot be found

• Hotfix 934790: peoplepicker-searchadcustomquery filter broken

• Hotfix 926284: List view web part not retained saving template

• Hotfix 938888: Edit document fails/IE Crash side by side Office

• Hotfix 932091: Hotfix packages break customer deployments primarily

• Hotfix 936867: Inherit perms causes destructive error

• Daylight savings time update

• Fixes to support Indexing Public Folders based on Exchange 2007

• Fixed Crawling IBM Notes Indexing ID access issues

• Fix to Alerts logic to address mails not being sent in specific scenarios

• Migration related fixes

• Important security cross site scripting vulnerability

Obszary ingerencji SP1

Content Managament

§ MOSS: Scrambled data in case of a COMMA in the username, “tp_title”, CommaSeparatedAccounts, _layouts/PageSettings.aspx and peoplepicker

§ File cannot be move to the root of its document library

§ MOSS: “Check for Unpublished items” function shows DBCS word in vertical lines.

§ Access Denied when running spellcheck in a subweb without permission in parent

§ Variations: Create Hierarchies does not Dispose SPWeb resulting in memory leaking with large hierarchies

§ CMS12 - Variation fails with ASP.NET 2.0 webparts.

SharePoint Designer

§ Workflow generated on German MOSS 2007 site with German SharePoint Designer 2007 does not work as expected, falls always through to the fallback

§ WSS 3.0: DateTime field in a “WebPart” cannot be updated in any other languages except US-English and Canada-French

Project Server

§ PSVR2007 Long names in Timesheet view can cause for cumbersome navigating to input time

§ Deadlocks with UpdateTask PSI calls

§ European Extended characters are not correctly displayed by controls in PWA

§ “File not found” error when attempting to create a new issue, risk or deliverable in a project.

§ PRJSVR2007 - Received Unknown error when Import a Timesheet in PWA

§ PSVR2007 : Custom filter for Project Type, in Project Centre view, does not work

§ PWA2007: Project Center Team View does not show RBS code

§ PSVR2007 : Custom Field Default Value box in PWA does not display correctly with multi-level values with long descriptions.

§ PSVR2007 - Assigning two resources to a task with a custom field can cause an ‘unexpected error’ on My Task page

§ IE has encountered a problem with an add-on and needs to close - PJGRID12.ocx

§ PSVR2007 : Unable to view all potential owners in the Project Owner field in the Edit project properties page

Search

§ Error message: “The query server index file location on Server_Name is not shared”

§ Dynamics: URL for search result detail wrong for special characters

§ Manage Search Service provides incorrect data for drive on query server

§ People returned twice on Intranet tab

§ Need a supported method to cleanup/remove orphaned entries in mssdocprops that result in people eing returned multiple times on Intranet tab

§ Advanced search is not working with the property ‘created date’ with site collection

§ needs the ability to exclude content during crawl that is behind a complex url

§ Queries on the live redmond SSP take over 3mins and occasionally timeout during index master merge

§ unable to add best bet with url including a plus sign ‘+’

§ Intermittent site collection usage reports timeout error

§ NTBACKUP always fails with TimeOut Error(0×80042319) on Moss Search Server

§ ‘Refine Your Search’ returns incorrect URLs through a reverse proxy

§ [WSS Search & MOSS Search] stsadm and Web UI do not allow you to reset the service credentials when they become corrupt.

§ Search does not crawl attachment to discussion board

§ Incremental crawl will index http://…/07.020n subsites but full-crawl never

§ Inability to revert a property back to default type

§ Searching for terms with character ‘ in them cause search result error

§ stsadm -o editssp is unable to replace a down indexer with a new value

§ site admin selects add best bets gets access denied

§ Retrieving search results through code, FullTextSqlQuery statement and valid search results omitted when ordering by null or empty columns

§ Advanced search not returning results as expected

MOSS 2007

§ Owstimer memory leak

§ discussion items with a URL in the title and -includeusersecurity cause PRIME import to fail

§ (^) Using audience-based web parts on NTLM based site breaks anonymous access on Forms-Based Authorization site that is mapped to the NTLM site

§ MCMS 2002 to MOSS 2007 migration fails on x64 MOSS server due memory read error (access violation) on SID conversion

§ Availability web control on My Site Profile page off by 1 hour (DST)

§ Personal documents on MySite that was created with language other than the default language has the same permissions than Shared Documents

§ Manager field cannot be updated to null value which causes all users with no manager to be peers

§ New site not saved in the SiteList of sitedirectory

§ Customer needs ability to map datetime fields in BDC against managed property

§ ‘I Need to…’ webpart fails if more than one are on the same page

§ RFH - Search doesn’t process membership for DLs in OUs with a comma in the name

§ SPSv2 –> MOSS: When a v2 portal is upgraded to v3, on subsites that were Topic areas, changing the masterpage doesn’t take effect

§ The ampersand of the image URL displayed on the public page of the Personal Site will be decoded as &

WSS

§ WSSv3 - Error at ‘Manage Permissions from Parent’

§ WSS v3 ‘Operation aborted’ error on mouse hover

§ Versioning not applied correctly to documents

§ Resorting Content Type causes template type association to be messed up.

§ RFH: Content-type looses required field during save as template

§ Unable to cancel ItemDeleting event using Drag’n Drop in Explorer View

§ Deadlock failures on ListItem related operations (on multi-proc machines)

§ Import fails for pages with lookup columns

§ Workflow task to copy list item fails if infopath form has more than 15 boolean fields.

§ Group By does not always work correctly for Date/Time columns

§ “Cannot complete this action” error message when creating a list from an STP file when the “EnableAssignToEmail” was set to true in the original list.

§ Calendar items beyond 5th of the month are not displayed in Monthly view if selected date is 1st day of the month

§ Workflow file range condition fails to fire if initial value is 1

§ WSSV3 List Group By Date is Off by One Day

§ Title and alt tag in Webpart Menu Area HTML encoded twice

§ failed to set item based security on list 998th item in a list which has multi value lookup column - incorrect SQL syntax

§ Anonymous user can’t reply to discussion board

Jak wdrożyć SP1 w istniejącym środowisku?

Dla WSS 3.0: http://technet2.microsoft.com/windowsserver/WSS/en/library/91649a7e-6b5a-4e5a-9ee5-51951f4b857f1033.mspx

Dla MOSS 2007: http://technet2.microsoft.com/Office/en-us/library/f484f5f2-35bb-4d70-bf56-dd1c4c287c721033.mspx?mfr=true