Replies to This Discussion

Permalink Reply by Pau Codina on June 15, 2011 at 12:15am

Hi Robin,

When Kaldeera workflow is activated and deployed in a web application, web.config is modified to allow certains workflow authorized types. Some times, the SharePoint activation feature don't perform this modification.

Try to deactivate and re-activate the site collection feature (Kaldeera Workflow Designer). In most cases, this will solve your problem.

If not, you can do some manual modifications to the application web.config file. Edit web.config file and find the <System.Workflow.ComponentModel.WorkflowCompiler> section (usually at the end). Under this section there are <authorizedTypes> and within this should be the following entries (besides others) for the proper functioning of Kaldeera Workflow Designer:

 

<authorizedType Assembly="Kaldeera.WorkflowActivities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=24c49f520dc7eef7" Namespace="Kaldeera.WorkflowActivities*" TypeName="*" Authorized="True" />
<authorizedType Assembly="Kaldeera.WorkflowActivities.Enterprise, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cdad6b32c78e99be" Namespace="Kaldeera.WorkflowActivities.Enterprise*" TypeName="*" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System*" TypeName="*" Authorized="True" />
<authorizedType Assembly="System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="*" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Guid" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Type" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"" Namespace="System" TypeName="RuntimeTypeHandle" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Exception" Authorized="True" />

Make sure that these entries exist. If not, you can add them manually and save the web.config file with these modifications. After this, Kaldeera Workflow Designer should work correctly.

 

• ▶ Reply

Permalink Reply by Pau Codina on October 14, 2011 at 9:57am

In some cases, you need to add additional authorized types (only 2010).

<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Type" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="RuntimeTypeHandle" Authorized="True" />
<authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Diagnostics" TypeName="EventLogEntryType" Authorized="True" />
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Exception" Authorized="True" />

 

Pau

• ▶ Reply

▶ Reply to Discussion