Nintex Connect

The Official Community Site for Nintex Software Products, including Nintex Workflow 2007, Nintex Podcast 2007 and Nintex SmartLibrary.
Welcome to Nintex Connect Sign in | Join | Help
in Search

Known issue and workaround with SharePoint 2007 SP1

Last post 03-27-2008, 4:40 PM by Cameron_McConnell. 0 replies.
Sort Posts: Previous Next
  •  03-27-2008, 4:40 PM 239

    Known issue and workaround with SharePoint 2007 SP1

    An issue was discovered after the release of Service Pack 1 for MOSS and WSS 3 was released. Please read below for the details.

    Background
    For a type to be used within the workflow, it must be registered as an Authorized Type in the web.config file. All of our workflow actions and custom types are registered as authorized types.

    Some of our workflow actions have a property of a type that inherits from a generic list, that is List<T>. List<T> is a basic system type provided in .NET.

    This worked before Service Pack 1 for MOSS and WSS 3 was released.

    Problem
    With the application of SP1, List<T> is no longer authorized. Workflow actions that use a type that inherits from List<T> no longer run or publish.

    The SharePoint web service to validate workflows returns the following error when publishing:

    <Error><CompilerError Line="0" Column="0" Text="Type System.Collections.Generic.List`1, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as authorized in the application configuration file." /></Error>

    Work around
    We added this authorized type entry to the web.config as a fix:

    <authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.Generic" TypeName="List`1" Authorized="True" />

    Fix
    Download and install Nintex Workflow 2007 build 18023 or greater (released 9th Jan 2008). Please contact support@nintex.com if you do not know how to upgrade.

    PLEASE NOTE: The 'Web Application Activation' step from the installation instructions (Section 3.1, page 8) must be repeated in SharePoint Central Administration to enable the fix.

    Unfortunately, running workflow instances that are failing will need to be terminated.

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems