Pablo Peralta's Blog

[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/pabloperalta] 

Hi,

I have faced today with this issue in a Microsoft Dynamics CRM installation. Some workflows I were able to publish and some other weren't.

I just got the generic error: 'An error occurred when the workflow was being created. Try to save the workflow again'. No more usefil info in eventviewer.

Cause

After some reseach I found that this error may be caused if you applied some rollup or hotfix and the web.config file you have is not the default one, but has been manually modified (due to some ISV needs , for instance). This knwoledge base article talks about it.

In this case, the rollup / hotfix setup realizes that the web.config was manually modified and hence does not automatically update it to support rollup/hotfix changes.

Then, a manually update to web.config is needed.

Solution

As said above, I had to manually apply changes to web.config that should have been applied by hotfix/rollup setup but weren't because the file were manually manipulated.

The changes I applied were all within authorizedTypes section. In concrete, I added the following items to this section:

<authorizedTypes>

....

<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="AssemblyVersionAttribute" Authorized="True" />

<authorizedType Assembly="Microsoft.Crm.SdkTypeProxy, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="Microsoft.Crm.SdkTypeProxy.Metadata" TypeName="MetadataService" Authorized="False" />

....

</authorizedTypes>

After applying this, I opened one of the workflows that presented the problem and I could publish it successfully.

Hope this helps to somebody else,

PP

[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/pabloperalta]

[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/pabloperalta] 

Hi,

It recently happened to me that when I wanted to apply latest Rollup on an existent Microsoft Dynamics CRM 4 installation I got the following error:

Microsoft.Crm.Setup.Common.Update.DBUpdateAction failed

After some research I really couldn't find much useful information, and hence, started to try some things. I found that despite the user I was logged on were administrator on CRM server machine, it wasn't Administrator on CRM Deployment Manager. Also found that it wasn't dbowner on CRM databases and didn't have 'CRMReaderRole' on CRM databases neither.

Nevertheless, after having been granted all of that permissions I still had the same error.

The solution.

Finally, the solution was granting the logged on user sysadmin permissions on SQL Server.

After some readings at 'Installation & Deployment in CRM Student_Manual' (Microsoft Official Curruculum) it made some sense as it explicitly says that:

The user installing Microsoft Dynamics CRM must be granted the following privileges at a minimum:

• Ability to create objects within the Active Directory organizational unit that is the target parent organizational unit for installing Microsoft CRM.
• SQL Administrator privilege.
• IIS Server local administrator privilege.
• Local Administrator on the computer where Microsoft Dynamics CRM Server is to be installed.

 

Anyway, it's not so clear that SQL administration privilege is also needed when you want to install a Rollup for instance, but, it seems it is.

So, if you face same error, try granting the user sysadmin privilege on SQL Server.

Hope this helps to save somebodyelse some time,

PP