CRM 4.0 Update Rollup 2 workflow regression error

[Zayd]

Hello Good morning everyone,
On my test server I have installed Update Rollup 2 for CRM 4.0.we have been unable to publish workflow rules that contain the Send E-mail action after this procedure.Keep getting error message which says: "An error occurred when the workflow was being created. Try to save the workflow again."This happened previously in a system using a working workflow rule (pre-Update Rollup 2) when attempting a very simple new workflow rule that contains the Send E-mail action.So any one out here to help me..


thanks..!!

[Steve123]

Bro,your issue can be solved with the new update The most common problem I was hearing about is that you could no longer publish workflows after the update if you had a custom web.config file. The fix was to add the following line to web.config in the authorized types section

<authorizedType Assembly=”mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ Namespace=”System.Globalization” TypeName=”CultureInfo” Authorized=”True”/>

[Big Fish]

I made a backup of the existing web.config and appended four lines then I was able to publish workflows. From a bit of research I did after finding this I was able to find out that this problem was thought to be resolved post Update Rollup 2.I doubt is that the error will only show up when the web.config was previously edited after the initial installation of CRM,it can define why we are viewing this semi-frequently on hosting environments, especially the ones with a large amount of customizations.

The four lines I appended is

<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System" TypeName="Void" Authorized="True"/>
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Reflection" TypeName="AssemblyFileVersionAttribute" Authorized="True"/>
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Reflection" TypeName="AssemblyVersionAttribute" Authorized="True"/>
<authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Globalization" TypeName="CultureInfo" Authorized="True"/>

[Zachary]

We are going to install .net 3.5 SP1 on my development machines (win2008 server and windows xp client),then will go for 3 updates (both different setup files for each O.S.) on each server, and hopefully this will combat my issues. I'm not sure but I do hope this will resolve my issues because I did not make any DB backups for this environment since it is a virtual machine based development machine...

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