GP2015 Installation Issue

(0) Share

Report

Posted on by Community Member

Recently downloaded GP2015 Version : 14.00.0524 and installed it successfully. While creating dynamics database on SQL 2012 or SQL 2014(both above version 11.0), system throws an error -

The following SQL statement produced an error: EXEC wfDeployClrAssemblies

ERROR [Microsoft][SQL Server Native Client 11.0][SQL Server]CREATE ASSEMBLY for assembly 'System.IdentityModel' failed because assembly 'System.IdentityModel' failed verification. Check if the referenced assemblies are up-to-date and trusted.

However, system database gets created with specified errors and in the same manner, company database also gets created with error but doesn't allow to login.

I tried on a fresh machine where workflow is not installed.

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Mike Lupro 50 on at

Like (0)

Report

I have an official support case filed with Microsoft on this exact issue. Two linked up sessions so far with no resolution. I'm hoping to post a response here when the case if finalized.

Nasty problem. I'm into this now for several hours now. Un-billable hours. Grrr.

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

What is the host OS? is UAC turned off? Are you installing as local administrator? How about running the installation by selecting "Run as Administrator"? Are you using the 'sa' account for SQL? Is the local or domain admin account also a sysadmin in SQL?

Was this reply helpful? Yes No
Suggested answer

Ian Grieve 22,784 on at

Like (0)

Report

I've seen this error when GP Utilities was being run on a client other than the SQL Server.

Was this reply helpful? Yes No
Verified answer

Brian Allrich on at

Like (4)

Report

Verify that .NET 4.5.1 is installed on the SQL Server machine.

You can query the sys.dm_clr_properties (select * from sys.dm_clr_properties) to identify the directory where the system assemblies will be pulled from when being registered in the SQL CLR. Navigate to the directory in File Explorer and determine the file version for the System.IdentityModel.dll: Right-click > Properties > Details. It appears that anything greater than or equal to a File Version of 4.0.3019.19001 will be .NET 4.5.1.

Was this reply helpful? Yes No
Mike Lupro 50 on at

Like (0)

Report

Great tip Brian. Hope it works. Here's what I found.

Directory C:\Windows\Microsoft.NET\Framework64\v4.0.30319\18408

09/11/2013

I'm working with our hosting partner to see if they can get .Net 4.5.1 installed.

Thank you for this tip and the GREAT instructions on how to locate this information.

Mike

Was this reply helpful? Yes No
Suggested answer

Mike Lupro 50 on at

Like (0)

Report

Brian: You are this weeks HERO. Your suggestion, and excellent instructions correctly diagnosed the problem. Our server DID NOT have .Net 4.5.1 and, once it was updated, GP 2015 sailed on to a full and complete installation for Fabrikam.

THANK YOU VERY MUCH.

Mike

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Thanks Brian. I have done several install on GP 2015 and haven;t had issues but was coming up with the error on this particular fresh install today. The SQL Server did not have .Net Framework 4.5.1 (it had 4.5) so I upgrade the framework version and it worked perfect after that. Thanks for the help. Saved me hours of troubleshooting.

Was this reply helpful? Yes No
Robyn 1,753 on at

Like (0)

Report

You saved my night as well. Thanks for posting and helping others.

Was this reply helpful? Yes No
Arunsh 606 on at

Like (0)

Report

Thanks guys. your reply was very valuable. I got the same pbm and tried every solution found across the community but , simple machine restart solved my pbm. :)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

In my case, when installing GP 2015 I saw it run the .NET update. It prompted to reboot, but I chose to do that later. Utilities was ran to upgrade from GP 2013 to 2015 BEFORE I rebooted. To get rid of the error I just had to simply reboot. Based on my experience, I believe this issue is caused by not rebooting after the update of .NET.

Was this reply helpful? Yes No