You are unable to publish workflows after you install or remove a Microsoft Dynamics CRM 4.0 hotfix or update rollup. The following error occurs:
"An error occurred when the workflow was being created. Try to save the workflow again."
The Platform Trace includes the following:
Type System.Globalization.CultureInfo is not marked as authorized in the application configuration file.
It may also include the following:
Type System.Reflection.AssemblyVersionAttribute, mscorlib, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as authorized in the application configuration file Type System.Reflection.AssemblyFileVersionAttribute, mscorlib, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b77a5c561934e089 is not marked as authorized in the application configuration file
The Web.config file is an unversioned file that is installed and managed by Microsoft Dynamics CRM 4.0. Because it is an unversioned file that can be customized, it may require manual modification after the installation or removal of a Microsoft Dynamics CRM hotfix.
Microsoft Dynamics CRM 4.0 Hotfix Installer behavior during the installation of unversioned files
If the already installed version of a file has been modified since it was installed, the Microsoft Dynamics CRM Hotfix Installer will not replace it with the latest version. This behavior assumes that if the file was modified, the modifications were intentional and should not be overwritten.
Microsoft Dynamics CRM 4.0 Hotfix Installer behavior during the removal of unversioned files
All affected files are reverted to the previously installed versions, regardless of whether they have been modified. This behavior assumes that the removal is performed to restore a previous state, even if that means overwriting changes that were made since that previous state.
To resolve this issue, you must manually modify the Web.config file to apply supported changes that the installer did not apply during the installation. For more information about what changes must be made, see the "History of changes to the Web.config file" section. If the removal scenario from the "Summary" section occurs, you must reapply the customizations that the installer overwrote when the unversioned file was removed. To modify the Web.config file, follow these steps.
Note As always, we recommend that you fully back up your system before you install or remove any hotfixes or update rollups.
Locate the Web.config file:
On a server, the default location is as follows:
On a client, the default location is as follows:
<system drive>:\Program Files\ Microsoft CRM\Client\res\Web
Back up the existing Web.config file by copying the file, and then renaming it. For example, rename the file as Web.config.<date>.
Open the file in Notepad or in another text-editing program.
Apply any necessary changes.
Save the file.
History of changes to the Web.config file
The following changes were introduced in the Microsoft Knowledge Base article or update rollup that is listed. However, the changes are required for each additional update rollup that is installed. For example, if Update Rollup 3 is the first hotfix that you installed, you must make the change for Update Rollup 3 and the changes for Update Rollup 2 and Update Rollup 1. All changes should be applied within the existing <authorizedTypes.> tag as follows. If you find that the content already exists, you do not have to add it again.
Changes that are included in 957975, Update Rollup 3, and all later hotfixes and update rollups