SharePoint group audience targeting stops functioning

After you install the updates that are described in Microsoft Knowledge Base articles 952294 and 946517, Microsoft Office SharePoint 2007 audience targeting stops functioning for nested SharePoint groups for global navigation and for any SharePoint group audience targeting for Web parts. The navigation links and Web parts in these cases are not visible at all. Therefore, they are inaccessible to the user targeted.

Hot Fix :

Description of the SharePoint Server 2007 hotfix package (Coreserver.msp): October 28, 2008
http://support.microsoft.com/kb/957693
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=957693

WSS & SharePoint Update / Hot Fix

Announcing August Cumulative Update for Office SharePoint Server 2007 and Windows SharePoint Services 3.0
The Microsoft Office team has changed the way that it delivers hotfixes for reported problems. This change comes in the form of cumulative updates and critical on-demand hotfixes. The objective is to deliver high-quality fixes in an acceptable time and on a predictable schedule. Cumulative updates are scheduled for every two months, so customers can be better prepared to test and apply new updates. Those who need an emergency fix can request critical on-demand (COD) fix. For information, please refer to http://support.microsoft.com/kb/953878.
The detail of August Cumulative Update (CU) for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 can be found here:
Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008
Description of the Windows SharePoint Services 3.0 hotfix package: August 26, 2008
Description of the SharePoint Server 2007 hotfix package: August 26, 2008
Customers are not needed to install these updates unless they are affected by specific problems described in the KB articles. And these cumulative updates will be rolled in to Service Pack 2.
To keep all files in a SharePoint installation updated, we recommend customers to follow the path below:
1. Windows SharePoint Services 3.0 Service Pack 1
2. The 2007 Microsoft Office Servers Service Pack 1
3. The Windows SharePoint Services Infrastructure Update x86 x64
4. The Microsoft Office Servers Infrastructure Update x86 x64
5. KB 953397: Excel Server Security Update x86 x64
6. KB 955586: Document Lifecycle Workflow Update
7. August Cumulative Update for Windows SharePoint Services 3.0 (Global)
8. August Cumulative Update for Windows SharePoint Services 3.0 (Local)
9. August Cumulative Update for Microsoft Office Servers
After applied all these updates, run SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b” in command line. This need to be done on every server in the farm with SharePoint installed.
The version of databases should be 12.0.6327 after all these updates.
For a better guided update process, customers would also like to check out the following guides. These articles provide a correct way to deploy updates, as well as known issues and how to do slipstream builds.
Deploy software updates for Windows SharePoint Services 3.0
http://technet.microsoft.com/en-us/library/cc288269.aspx
Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

Update: October Cumulative Update has been released on Oct 28th. Here're the download links and descriptions.

______________________________________________________________

Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers: October 28, 2008

http://support.microsoft.com/kb/958847

Description of the Windows SharePoint Services 3.0 hotfix package: October 28, 2008

http://support.microsoft.com/kb/957691

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=957691

Description of the SharePoint Server 2007 hotfix package (Coreserver.msp): October 28, 2008

http://support.microsoft.com/kb/957693

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=957693

Announcing December Cumulative Update for Office SharePoint Server 2007 and Windows SharePoint Services 3.0

___________________________________________________

We are happy to announce that December Cumulative Update for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 is available now. Despite the fixes and improvements, this new update package is also an effort to create a more convenient way for SharePoint administrators to keep all files in their SharePoint installations up-to-date. In this post, we will guide you on how and when to update, and the background of this new update model improvement.

December Cumulative Update Steps & Suggestions
Customers do not need to install these updates unless they are affected by the specific problems described in the KB articles. These cumulative updates will be rolled in to Service Pack 2.
To keep all the files in a SharePoint installation up-to-date, we recommend that customers install updates in the following sequence:

1. Windows SharePoint Services 3.0 Service Pack 1
2. The 2007 Microsoft Office Servers Service Pack 1
3. December Cumulative Update for Windows SharePoint Services 3.0
4. December Cumulative Update for Microsoft Office Servers

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed. The version of content databases should be 12.0.0.6335 after successfully applying these updates.

The detail of December Cumulative Update (CU) for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 can be found here:
Description of the Windows SharePoint Services 3.0 cumulative update package: December 16, 2008 (The link will be active soon)
Description of the SharePoint Server 2007 cumulative update package: December 16, 2008 (The link will be active soon)

Visual Studio 2010 Tools for SharePoint & .NET Framework 4.0

Visual Studio 2010 Tools for SharePoint Announced at TechEd EMEA Developers 2008

This week at TechEd EMEA in Barcelona, Jason Zander, the GM for Visual Studio, announced and demonstrated the Visual Studio 2010 tools for SharePoint. Here's a quick summary of what he showed:
•Server Explorer for SharePoint viewing Lists and other artifacts in SharePoint directly inside of Visual Studio
•Windows SharePoint Services Project (WSP file) Import to create a new solution
•Added a new web part project item and showed the Visual web part designer which loads a user control as a web part for SharePoint
•Showed adding an event receiver for SharePoint and using the wizard to choose the event receiver and to just create a source file with that event receiver.
•Added an ASPX workflow initiation form to a workflow project and showed how this workflow initiation form has designer capability
•Showed the packaging explorer and the packaging editor which lets you structure the SharePoint features and WSP file that is created

Web Url: http://msdn.microsoft.com/en-us/vs2008/products/cc948977.aspx

Visual Studio 2010: http://www.microsoft.com/visualstudio/2010/overview.mspx

.NET Framework 4.0 [Dublin] : http://www.microsoft.com/net/Dublin.aspx

Custom Site Theme for SharePoint 2007 (MOSS 2007) and WSS 3.0

The easiest and the fastest way to apply the same look and feel on any SharePoint site is creating a site theme. A SharePoint site theme basically consists of theme.inf, theme.css, and image files. Theme.inf file simply represents the title of the theme. Theme.css is a stylesheet file that defines colors, header images and layouts of a site and image files can be referenced here to display on the page. By creating a custom site theme, you can easily change the style but in fact, writing and editing the stylesheet can be somewhat chanllenging when you have more than a hundred of elements to deal with.

Here is a short procedure of creating a custom site theme named "India":
1. Copy any theme folder in "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\THEMES" folder and paste with its name replaced with "India". In this example, copy GRANITE folder.
2. In India folder, rename GRANITE.INF file to INDIA.INF in upper case.
3. Open INDIA.INF file with notepad.
4. Change the value of title under [Info] to India.
5. Replace every word, Granite, under [titles] with India.
6. Open "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\SPTHEMES.XML" file with notepad.
7. Add the following lines under tag:
Templates>
TemplateID>India
DisplayName>India
Description>We love India .
Thumbnail>images/India.gif
Preview>images/India.gif
/Templates>

Notice that preview and thumbnail paths are images/India.gif. By default, MOSS 2007 and WSS 3.0 will not have such image files.

8. In order to display thumbnail and preview correctly, you will need to capture the screen and save the file in "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES" folder with India.gif name. You can change the .gif file name if you change the thumbnail and preview file names in tag.

9. Do an iisrest for the server to recognize the new theme.

Pretty simple procedure. Now you are ready to test your new theme. In Site Settings, you can now choose India theme; however, the theme will not differ from Base theme. Now, it is time for you to play with theme.css file!

Patrick, you'll be greatly missed...

Yesterday I got word that the legendary SharePoint developer, presenter, author, instructor, and friend Patrick Tissghem suddenly and unexpectedly passed away. I had just talked to him over IM just a day earlier. If the name isn't familiar to you, well you have surely used some of this work. From the blog posts, the books, the screencasts... you name it, he's been instrumental in the SharePoint world for years.
But it isn't just SharePoint. Patrick was a great person... someone who was a ton of fun and a real joy to be around. I consider myself quite fortunate in working with him over email and virtually over the last few years and fortune to get to finally meet him last year at TechEd.

My thoughts are with Patrick's family and extended family at U2U. You will be greatly missed.

Integrating ASP.NET AJAX with SharePoint

How does Microsoft ASP.NET AJAX integrate with SharePoint? Here are some notes I've collected on this.

Microsoft ASP.NET AJAX 1.0: A Background

Microsoft ASP. NET AJAX 1.0 lets developers build Web 2.0 sites using the latest Ajax techniques.
ASP.NET AJAX extends ASP.NET 2.0 and makes several new tools and techniques available to help you build applications more quickly:

• Extensions to JavaScript. ASP.NET AJAX extends the JavaScript library to bring standard object oriented concepts to JavaScript. It brings a formal type declaration system, with support for inheritance. It also provides a significant number of out of the box types, including types such as Sys.Net.WebRequest for working with web services. Finally, it helps to abstract some cross-browser issues such as XML element traversal. This makes it much easier to create robust JavaScript libraries and frameworks which are commonly needed by rich internet applications.
• ASP.NET Control Extenders. Extenders are additional ASP.NET controls which can extend the functionality of existing controls with additional Ajax capabilities. A common example is an extender which allows existing textbox controls to have autocomplete functionality with no modification to the extended control. (The autocomplete extender is included with the ASP.NET AJAX Control Toolkit.)
• UpdatePanels. UpdatePanels allow your existing ASP.NET controls and web parts to achieve the fluid, no-postback updates of Ajax-based applications with minimal re-coding of your control or part. Quite simply, controls within the UpdatePanel control which ordinarily would post back to update their data will now be routed through an Ajax-style callback, resulting in a silent update back to the server. This makes your application “postback” much less, making interaction with your control more seamless.

For More...

Fix for Forefront Update Timeout Errors

I use Microsoft Forefront Security for SharePoint Server on my SharePoint Server 2007 .Recently I noticed the following error in the Application Event log:

Event Type: ErrorEvent

Source: GetEngineFiles

Event Category: Engine

ErrorEvent ID: 6014

Date: 2/9/2008Time: 10:08:43 AM

User: N/A

Computer: GATEWAY

Description:Microsoft Forefront Server Security encountered an error while performing a scan engine update.Scan Engine: Kaspersky5Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate/x86/Kaspersky5Proxy Settings: DisabledError Code: 0xC0001F58Description: The operation timed out.

Followed immediately by:

Event Type: Information

Event Source: GetEngineFiles

Event Category: General

Event ID: 2017

Date: 2/9/2008

Time: 10:08:43 AM

User: N/A

Computer: GATEWAY

Description:Forefront Server Security has rolled back a scan engine.Scan Engine: Kaspersky5This was happening every 5 minutes after Event ID 2034, which reports that Microsoft Forefront Server Security is attempting a scan engine update of the Kaspersky5 scan engine.

To solve this error make the following change to the registry on the server running Forefront:

> Open Regedit
> Navigate to the following key:
HKLM\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Exchange Server
>Click New DWORD Value
>Type EngineDownloadTimeout, and then press ENTER
>Right-click the new value and select Modify
>Select Decimal as the base, enter 600 in the Value data box, and then click OK. This setting causes the scan engine download process to time out after 600 seconds (10 minutes, instead of 5 minutes)
> Exit Regedit

Note: You do not have to restart Forefront Server services or Exchange Server services after you change this registry entry.
Now perform a manual scanner update in Forefront:
Open Forefront Server Security Administrator
Click Scanner Updates under Settings
Select the appropriate scan engine that was previously timing out. In my case, Kaspersky Antivirus Technology
Click the Update Now button on the right side of the screen
Check the Application event log to ensure that the scan engine has updated properly (Event ID 2012).