i:0#.w|Ali.Mazaheri : Windows SharePoint Services

Upgrade and Migration Resource Center for SharePoint Server 2010 (Beta)

AMazaheri — Thu, 05 Nov 2009 20:08:51 GMT

If you are planning for upgrading your MOSS 2007/WSS 3.0 to upcoming Microsoft SharePoint Server 2010/Microsoft SharePoint Foundation 2010 I definitely encourage you to look at the “Upgrade and Migration Resource Center for SharePoint Server 2010 (Beta)” site.

Service Pack 2 Update

AMazaheri — Fri, 26 Jun 2009 07:05:00 GMT

The public update for the Service Pack 2 expiration date issue is now available for download.

The update can be applied before or after Service Pack 2 installation. If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.

More info here.

IIS 7.0 and RequestLimitsElement

AMazaheri — Mon, 11 May 2009 22:45:00 GMT

As we all know in ASP.NET we can configure the maximum length of the request using httpRuntime's "maxRequestLength" attribute (By default this is set to 4KB and SharePoint uses 50MB as a default value). While this setting works with IIS 6.0, in IIS 7.0 a new attribute "RequestLimitsElement" needs to be configured as well to allow uploading files larger than 30 MB through HTTP.

More information can be found here and KB944981.

WSS 3.0 and MOSS 2007 SP2

AMazaheri — Sat, 18 Apr 2009 03:19:00 GMT

Just a quick note that the SP2 for WSS 3.0 and MOSS 2007 will be available on April 28th 2009! More information can be found here.

Microsoft Certified Master program for SharePoint 2007

AMazaheri — Thu, 16 Apr 2009 03:31:00 GMT

I just wrapped up an intensive Three week MCM training up in Redmond and wanted to share couple of posts on the program from colleagues who attended the R2 (Beta) for folks who are interested:

As soon as I get a chance I will share my experience as well, also Arpan Shah had a great post on MCM which can be found here.

Update:

I just found out today that I am officially a MCM for SharePoint 2007!

Troubleshooting team site's default page errors caused by adding faulty web part

AMazaheri — Sun, 08 Feb 2009 03:39:00 GMT

In cases when SharePoint cannot load the default page for a team site caused by adding a faulty web part, "Web Part Maintenance" page can help the site admin to remove the fault web part or reset the page to its default setting. While a link to this page is available on the "Edit Item" form for pages added to document library, adding "?contents=1" to the end of the URL for default page will cause a redirect to the "Web Part Maintenance" page for default.aspx.

More info can be found at : Customize Web Parts

Server Upgrade and Migration Tool for Microsoft Office InfoPath

AMazaheri — Thu, 18 Dec 2008 00:01:00 GMT

The Server Upgrade and Migration tool allows a SharePoint farm administrator to change hard-coded URLs in InfoPath form templates, UDC files, and content types to ensure that the form templates continue to work correctly in the following circumstances:

When performing a gradual upgrade from Microsoft Windows SharePoint Services 2.0 to Microsoft Windows SharePoint Services 3.0 or from Microsoft Office SharePoint Portal Server to Microsoft Office SharePoint Server 2007.
When migrating InfoPath forms and form templates from one Windows SharePoint Services 3.0 or Office SharePoint Server 2007 or Web site collection to another.

And can be downloaded here.

December Cumulative Update for MOSS 2007 and WSS 3.0 is now available for download!

AMazaheri — Wed, 17 Dec 2008 23:45:00 GMT

December Cumulative Update for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 is now available for download:

December Cumulative Update for Windows SharePoint Services 3.0
December Cumulative Update for Microsoft Office Servers

More information can be found here.

Support for WSS 3.0 and MOSS 2007 withouht SP1 will end on January 13th 2009

AMazaheri — Wed, 10 Dec 2008 23:03:00 GMT

Per our "Lifecycle Supported Service Packs" link the support for WSS 3.0 and MOSS 2007 without SP1 will end on January 13th 2009 and it is recommended to apply SP1 before the deadline to be in supported state.

Patterns and practices for SharePoint is published on MSDN

AMazaheri — Fri, 07 Nov 2008 07:17:00 GMT

This guidance helps architects and developers design, build, test, deploy and upgrade SharePoint intranet applications. A reference implementation that is named the Contoso Training Management application demonstrates solutions to common architectural, development, and application lifecycle management challenges.

This guidance discusses the following:

Architectural decisions about patterns, feature factoring, and packaging.
Design tradeoffs for common decisions many developers encounter, such as when to use SharePoint lists or a database to store information.
Implementation examples that are demonstrated in the Training Management application and in the QuickStarts.
How to design for testability, create unit tests, and run continuous integration.
How to set up different environments including the development, build, test, staging, and production environments.
How to manage the application life cycle through development, test, deployment, and upgrading.
Team-based intranet application development.

check for publisher's certificate revocation slowing down SharePoint

AMazaheri — Thu, 16 Oct 2008 06:32:00 GMT

While working on an engagement deploying a medium farm on Windows 2008 with no internet connection I noticed a considerable performance hit causing by check for publisher's certificate revocation which is on by default.

Basically by having this option set, all managed code go through a cert check against crl.microsoft.com (Certification revocation check) by .net runtime before startup. While disabling this option is not recommended for security reasons, for a development environment with no internet connectivity turning off this check should increase the overall performance.

In order to disable this option simply go to Internet Options and uncheck "Check for publisher's certificate revocation" under advanced tab.

Note:

As an alternative, adding the following line to Hosts file should also resolve the issue (Thanks to my friend Ashkan for the hint):

127.0.0.1 crl.microsoft.com

MOSS 2007 Best Practices articles are now live!

AMazaheri — Fri, 29 Aug 2008 03:01:00 GMT

Recently I collaborated on a SharePoint Collaboration best practice article which just got published on Technet along with a series of great articles on Operation, Publishing, Search and My Sites:

· Ops: http://technet.microsoft.com/en-us/library/cc850692.aspx

· Pub: http://technet.microsoft.com/en-us/library/cc850698.aspx

· Collab: http://technet.microsoft.com/en-us/library/cc850694.aspx

· Search: http://technet.microsoft.com/en-us/library/cc850696.aspx

· My Sites: http://technet.microsoft.com/en-us/library/cc262706.aspx

Known issue with Infrastructure Update for Windows SharePoint Services 3.0

AMazaheri — Mon, 28 Jul 2008 01:12:30 GMT

If you are planning to deploy this update to your production environment, pay attention to a known issue that may affect AAM functionality in which discovered after release of Infrastructure Update for WSS 3.0, the KB 951695 has been recently updated with more information on the issue:

"Installing the Infrastructure Update in a SharePoint farm that uses Alternate Access Mapping with a reverse proxy or a network load balancer, such as in an extranet deployment, may cause some public URLs to become unresponsive.
Microsoft is aware of this issue and is developing a solution. Before installing the Infrastructure Update, customers who use this configuration should use a test environment to verify that public URLs remain accessible after the update is installed."

Using nested StateActivity to send regular reminders in Visual Studio SharePoint State Machine Workflow

AMazaheri — Sat, 26 Jul 2008 23:44:35 GMT

Note. I want to thank Daniel Odievich for providing the content of this post, a must read!

When developing SharePoint workflows, one often needs to send email notification for a task, and then keep sending regular reminders for this task at scheduled intervals. When developing workflows in SharePoint Designer, one can use DelayUntilActivity and DelayForActivity, but those were not designed for in Visual Studio workflows.

When using State Machine workflows, the implementation for regular reminders is quite different than that in Sequential workflow. One can use put in EventDrivenActivity with DelayActivity but it will only execute once so you can only have one-time reminder, instead of regular reminders. If you try to wrap DelayActivity in a WhileActivity, the EventDrivenActivity won’t compile because its first child must be IEventActivity (such as DelayActivity).

Unlike with the Sequential workflow, ConditionedActivityGroupActivity cannot be used in State machine EventDrivenActivity. Also, one cannot write a loop around DelayActivity as it is supposed to be the first child of EventDrivenActivity.

The approach that can be taken is to use WF ability to reenter the same StateActivity over and over and thus reset the workflow. It is suggested here http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3553632&SiteID=1 but the following discussion adopts it for the SharePoint reality of task correlation tokens.

One common way to use StateMachineActivity in SharePoint is to create a task in StateInitializationActivity, register for OnTaskChanged or OnItemChanged event using EventDrivenActivity and use EventDrivenActivity with DelayActivity to send reminders. When using State Machine and SharePoint tasks, you most likely expect to reenter this state over and over, creating more tasks of the same kind (one common scenario is multi-stage approval with ability to send back the approval to previous people for re-approval). If you expect to reenter this task, you must set the all-important correlation tokens for the task should be set to use the containing StateActivity as a parent. Following is the structure you might create:

</StateInitializationActivity>

</EventDrivenActivity>

</EventDrivenActivity>

</EventDrivenActivity>

</StateFinalizationActivity>

If you run this code, you will notice the following sequence of events:

1. <CreateTask CorrelationTokenParent=“MyCustomTaskState” />

2. <SendEmail Type=“Task Created” />

3. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> - register

4. <OnItemChanged /> - register

5. <DelayActivity /> - sleep

The workflow will then go to sleep and wait for either OnTaskChanged event, OnItemChanged event or for DelayActivity to elapse.

If OnTaskChanged or OnItemChange event wakes up workflow before DelayActivity has ever elapsed, and the user action causes workflow to move to another state everything is going to run correctly. However, once DelayActivity elapses, it wakes up and the following sequence of events occurs:

1. <DelayActivity /> - wake

2. <SendEmail Type=“Reminder” />

3. <SetStateActivity Target=“MyCustomTaskState” />

4. <CompleteTask CorrelationTokenParent=“MyCustomTaskState” />

5. <SendEmail Type=“Task Completed” />

6. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> - register

7. <CreateTask CorrelationTokenParent=“MyCustomTaskState” />

8. <SendEmail Type=“Task Created” />

9. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> - register

10.<OnTaskChanged /> - register

11.<DelayActivity /> - sleep

As you can see, your task will be completed and immediately new task of the same type will be created and new notification emails will be sent. If you sent link to the original task in the emails, the URLs in the email are no longer valid.

To avoid this, you might be tempted to wrap the activities in StateInitializationActivity and StateFinalizationActivity to avoid completing and recreating the task. If you do, you will discover that after reentering the state, OnTaskChanged events will no longer register correctly with exception indicating that correlation token for the task has not been initialized. This is because the correlation tokens use the StateActivity as a parent, and when it is reentered, they are reset, and you have orphaned your original task. There is no way to preserve those correlation tokens from one entry of StateActivity to another. A different approach is needed.

The correct approach is to use ability of StateActivity to host another StateActivity and break up task creation, task completion and task events into three separate StateActivity entities, and set the correlation token to use the top-most parent StateActivity:

</StateInitializationActivity>

</EventDrivenActivity>

</EventDrivenActivity>

</EventDrivenActivity>

</StateInitializationActivity>

If you run this code, you will notice the following sequence of events:

1. <CreateTask CorrelationTokenParent=“MyCustomTaskState” />

2. <SendEmail Type=“Task Created” />

3. <SetStateActivity Target=“TaskEventsState” />

4. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> - register

5. <OnItemChanged /> - register

6. <DelayActivity /> - sleep

The workflow will then go to sleep and wait for either OnTaskChanged event, OnItemChanged event or for DelayActivity to elapse. Once DelayActivity elapses, following sequence of events occurs:

1. <DelayActivity /> - wake

2. <SendEmail Type=“Reminder” />

3. <SetStateActivity Target=“MyCustomTaskState” />

4. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> - register

5. <OnTaskChanged /> - register

6. <DelayActivity /> - sleep

Whenever the task change occurs that indicates that workflow is ready to move to another state, the following sequence of events occurs:

1. <OnTaskChanged CorrelationTokenParent=“MyCustomTaskState” /> or

2. <UpdateTask CorrelationTokenParent=“MyCustomTaskState” />

3. <IfElseActivity>

4. <IfElseBranch Condition=“Task Completed”>

5. <SetStateActivity Target=“CompleteTaskState” />

6. <CompleteTask CorrelationTokenParent=“MyCustomTaskState” />

7. <SendEmail Type=“Task Completed” />

8. <IfElseActivity>

9. <IfElseBranch Condition=“Task Completed”>

10.<SetStateActivity Target=“OtherState” />

Whenever the item change occurs that indicates that workflow is ready to move to another state, the following sequence of events occurs:

1. <OnItemChanged />

2. <SetStateActivity Target=“TaskEventsState” />

3. <IfElseActivity>

4. <IfElseBranch Condition=“Task Completed”>

5. <SetStateActivity Target=“CompleteTaskState” />

6. <CompleteTask CorrelationTokenParent=“MyCustomTaskState” />

7. <SendEmail Type=“Task Completed” />

8. <IfElseActivity>

9. <IfElseBranch Condition=“Task Completed”>

10.<SetStateActivity Target=“OtherState” />

The workflow designer outline of this is shown below:

Overall view of the parent state

Overall hierarchy of all activities

CreateTaskState with creation of the task and events

Properties window of CreateTask activity with correlation token pointing to parent state of all three activities

EventDrivenActivity for OnTaskChanged event

EventDrivenActivity for OnItemChanged event

EventDrivenActivity for DelayActivity and reminder email

CompleteTaskState and transition to another state

Deploying External Collaboration Toolkit for SharePoint in a medium farm

AMazaheri — Thu, 19 Jun 2008 05:46:00 GMT

Update:

The External Collaboration Toolkit for SharePoint (ECTS) is now available exclusively on CodePlex, Microsoft’s open source Web site. To access these resources, visit the Community Kit for SharePoint on CodePlex. http://cks.codeplex.com/

External Coolaboration Toolkit for SharePoint (ECTS) was recently released by The Solution Accelerators – Security and Compliance (SA-SC) team which allows SharePoint administrators to easily invite external users to connect and collaborate with corporate's internal users on existing or new Team/Project sites.

After doing a dry-run deployment for one of my customers I noticed some issues with the installting the solution on a medium farm with more than one web front end server and found quite few posts on the "SharePoint-Collaboration" forum regarding the similar issues and challenges.

I finally managed to successfully deploy the solution by following these steps:

When deploying the ECTS to a farm with multiple front-end servers the “ECTSBase.wsp” and “ECTSSolution.wsp” may not be fully deployed when the setup script tries to activate the features and you may get an error.To mitigate this issue make sure to put a Wscript.sleep(60000) before the feature activation steps in ects_setup_sharepoint.vbs
In Central Administration click on Application Management tab and select Manage Web Application features, make sure both “ECTSBase” and “External Collaboration” are activated for the web application.
Web.config for both Main (Default zone) and Extranet web applications should contain the following settings:

<membership defaultProvider="ADAMUser">
<providers>
<clear />
<add name="ADAMUser" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ADAMConnectionString" attributeMapUsername="userPrincipalName" requiresQuestionAndAnswer="true" enablePasswordReset="true" attributeMapPasswordQuestion="eatmuPasswordQuestion" attributeMapPasswordAnswer="eatmuPasswordAnswer" attributeMapFailedPasswordAnswerCount="eatmuFPAC" attributeMapFailedPasswordAnswerTime="eatmuFPAT" attributeMapFailedPasswordAnswerLockoutTime="eatmuFPALT" />
</providers>
</membership>
...

If the above settings are missing in Central Administration, click the Application Management tab and then, under Application Security, click Authentication providers. Verify that you are configuring the proper Web application, and then click Extranet. On the Edit Authentication page click Save again(without modifying the settings). This will magically update the WebConfigurationChanges objects in Configuration database and eventually pushes all the custom settings to the web.config for both Internal and external web application.

Note.

When installing ECTS on a single server this happens automatically as part of the ECTSBase feature activation at web application level.

As part of “External Collaboration” feature activation process, “ExternalCollaboration.resx” should be copied to “App_GlobalResources” folder for both Internal (Default zone) and Extranet web applications under “[Drive]:\Inetpub\wwroot\wss\virtualdirectories\”, make sure that after installing the solution the file exists on all servers to avoid the following error when accessing the ETCS application pages provisioned under “_layouts” virtual folder: