Could not load file or assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified at Configuration class initiation in CrmServiceHelper.cv

-
Hello,

I faced an error when i iniated configuration class of CrmServiceHelper of Microsoft in order to setup Dynamics 365 Customer Engagement (Dynamics CRM online) SDK connection.

The mesage was
"
Could not load file or assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
"

Here is the fix:
Open NuGet Package Manageer froom Tools view in Visual Studio and make an online search for
System.ServiceModel.Primitives

finally install it to the project.


enjoy...
Muhammet Atalay


Comments

Post a Comment

Popular posts from this blog

Exception caught instantiating TERADATA report server extension SQL Reporting Services

-
Hi, If you face an error in Reporting Services Log File (C:\Program Files\Microsoft SQL Server\MSRSxx_xx.MSSQLSERVER\Reporting Services\LogFiles) such as : extensionfactory!ReportServer_0-1!ea4!03/26/2013-08:20:15:: e ERROR: Exception caught instantiating TERADATA report server extension:  System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.  ---> System.IO.FileNotFoundException: Could not load file or assembly 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c' or one of its dependencies. The system cannot find the file specified. File name: 'Teradata.Client.Provider, Version=12.0.0.0, Culture=neutral, PublicKeyToken=76b417ee2e04956c'    at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)    a...
Read more

you face "ISV code aborted the operation" when you change status of the any record in Dynamics CRM 2013

-
Hi,    You may get an error as "ISV code aborted the operation" when you set "activate" or "deactivate" of any record. it seems that because we’re not actually performing the status/state change action directly on the record . The event itself does “bubble up”, though, so stopping the status change also rolls back the entire transaction and none of the fields on the records being the targets of the operation change in the dirty form  ( .getDirty() -> true).  That’s the important part, after all.
Read more