Welcome to EMC Consulting Blogs Sign in | Join | Help

Stuart Preston's Blog

Stuart was CTO for Application Consulting EMEA at EMC Consulting until October 2009, now blogging at http://stuartpreston.net

Many Sharepoint 2007 hotfixes, already.

I was looking at Microsoft's support site earlier today for a hotfix for Windows Server 2003 when I noticed a few hotfixes for Sharepoint 2007 had been released already.  As I couldn't see a single place to find this information publicly I'm reposting them here.

I’d also recommend keeping an eye on this page for some handy tips and workarounds… http://support.microsoft.com/search/default.aspx?catalog=LCID%3D2057&spid=11373&query=&adv=&mode=s&cat=False

You cannot open a SharePoint Server 2007 notification message in Outlook 2007 when your mailbox is on an Exchange 2003 server
http://support.microsoft.com/kb/930807 (note hotfix is for Exchange Server 2003!)

“Consider the following scenario:

-          You have a mailbox on a server that is running Microsoft Exchange Server 2003.
-          You use Microsoft Office SharePoint Server 2007 to send a notification message to the mailbox.
-          You try to open the SharePoint Server 2007 notification message in Microsoft Office Outlook 2007.
-          Outlook 2007 is running in Cached Exchange Mode.

In this scenario, you cannot open the notification message in Outlook 2007.”

You cannot crawl case-sensitive Web content in SharePoint Server 2007 http://support.microsoft.com/kb/932619/ 

“In Microsoft Office SharePoint Server 2007, you add a content source to crawl Web content that resides on a computer that is not running Microsoft Windows. Additionally, the computer supports case-sensitive file names and case-sensitive folder names. When you search for crawled content in a folder that has a name that contains uppercase letters, the search query returns no results. For example, this problem occurs when you search for crawled content in a folder that is named FOLDERNAME.

Additionally, the crawl log contains an error message for each URL that contains an uppercase folder name or an uppercase file name. However, the URLs in the crawl log are displayed in lowercase letters.” 

March 3, 2007 hotfix package:
http://support.microsoft.com/kb/933586

"When SharePoint Server 2007 crawls a Microsoft Exchange Server public folder, the following error message is logged to the gatherer log:

The item could not be accessed on the remote server because its address has an invalid syntax

This problem occurs if the subject line of a message in the public folder contains one or both of the following special characters:

- A slash mark (/)
- Quotation marks ("")"

February 26, 2007 hotfix package:
http://support.microsoft.com/kb/932919 

"You run a program that uses the SharedWebService.OnlineServerAddresses Web service to determine the URL for its search service. When several requests are made to the same Web service at the same time, a deadlock situation may occur.

When this deadlock situation occurs, the Web working process (W3wp.exe) where the search service is executing may start to use 100 percent of CPU resources. Additionally, Internet Information Services (IIS) cannot recycle the W3wp.exe process in a timely manner. This behavior may cause SharePoint Server 2007 to stop responding."

January 25, 2007 hotfix package
http://support.microsoft.com/kb/931497

“When you build a Web site that is based on SharePoint Server 2007, the Web site may intermittently show incomplete navigation menus.

Note This problem is difficult to reproduce consistently, and it requires the server to be under a heavy load condition. Under this condition, a ThreadAbortException exception may be thrown while the navigation system is initializing its list of items to display during navigation.

This cached list may be only partially populated when the exception occurs. However, the list persists anyway. On successive requests for this list of navigation items, the partially populated list is taken to be complete. Therefore, several items may be left out.

This problem will continue to occur until a change (such as a write operation) causes the cache to be reinitialized or until the cache is manually flushed."

Published 19 March 2007 20:26 by Stuart.Preston

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

No Comments

Leave a Comment

(required) 
(optional)
(required) 
Submit

This Blog

Syndication

News

I have now left EMC Consulting and can be found at http://stuartpreston.net
Powered by Community Server (Personal Edition), by Telligent Systems