I\'m trying to make a webapi in ASP.NET MVC 4. The webapi used Entity Framework 5 Spatial types and i have wrote a very simple code.
public List
Just had the same issue. I am using EF6
and calling SQL
which has a SQL function that uses spatial commands. I tested this through a unit test and it worked fine. When I went to wire up my Asp.Net
solution I received the error
Spatial types and functions are not available for this provider because the assembly 'Microsoft.SqlServer.Types' version 10 or higher could not be found.
By adding the NUGET
package "Microsoft.SqlServer.Types" and adding SqlServerTypes.Utilities.LoadNativeAssemblies(Server.MapPath("~/bin"));
to the Application_Start method
in Global.asax.cs
everything worked fine.
The solution for me was just adding this line of code to Global.asax.cs in Application_Start()
:
SqlServerTypes.Utilities.LoadNativeAssemblies(Server.MapPath("~/bin"));
Good luck my brothers.
There are 2 ways to fix that:
Second way is to use NuGet package manager and install
Install-Package Microsoft.SqlServer.Types
Then follow the plugin notes as below
To deploy an application that uses spatial data types to a machine that does not have 'System CLR Types for SQL Server' installed you also need to deploy the native assembly SqlServerSpatial110.dll. Both x86 (32 bit) and x64 (64 bit) versions of this assembly have been added to your project under the SqlServerTypes\x86 and SqlServerTypes\x64 subdirectories. The native assembly msvcr100.dll is also included in case the C++ runtime is not installed.
You need to add code to load the correct one of these assemblies at runtime (depending on the current architecture).
ASP.NET applications For ASP.NET applications, add the following line of code to the Application_Start method in Global.asax.cs:
SqlServerTypes.Utilities.LoadNativeAssemblies(Server.MapPath("~/bin"));
Desktop applications For desktop applications, add the following line of code to run before any spatial operations are performed:
SqlServerTypes.Utilities.LoadNativeAssemblies(AppDomain.CurrentDomain.BaseDirectory);
None of the above solutions worked me.
You know what, this error can also be due to low resources on the server. I restarted SQL server and it got resolved automatically.
The answer above works fine when version 11 (SQL Server 2012) of the assembly can be used.
I had a problem with this as my solution has other dependencies on version 13 (SQL Server 2016) of the same assembly. In this case note that Entity Framework (at least v6.1.3) is hardcoded in its SqlTypesAssemblyLoader (the source of this exception) to only look for versions 10 and 11 of the assembly.
To work around this I discovered you can tell Entity Framework which assembly you want to use like this:
SqlProviderServices.SqlServerTypesAssemblyName = typeof(SqlGeography).Assembly.FullName;
I also encountered this problem, but the Microsoft.SqlServer.Types nuget package was already installed.
What solved the problem for me was going to Solution > References > System.Data.Entity > Properties > Copy Local, and setting it to True.
Note: Copy Local for Microsoft.SqlServer.Types was already set to true, and even though the problem was with System.Data.Entity, the error message was still about Microsoft.SqlServer.Types.
The solution is from Windows Azure forum.