EDMX not working in newer versions

EDMX not working in post 17.12.4

Unable to generate the model because of the following exception: 'System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

at System.Data.SqlClient.SqlDataReader.get_MetaData()

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

at System.Data.Entity.Infrastructure.Interception.InternalDispatche1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func3 operation, TInterceptionContext interceptionContext, Actio3 executing, Action3 executed)

at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)

at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)

What’s Going Wrong

The EDMX designer internally runs queries to introspect the database schema.
If your database or views include query hints (like OPTION (FORCEPLAN) or WITH (NOLOCK)), the designer fails to generate the model.
This behavior changed after Visual Studio 17.12.4, making previously working EDMX files break.

Workarounds You Can Try

Remove Query Hints Temporarily
- If possible, modify your views or stored procedures to remove query hints during model generation.
- Once the EDMX is generated, you can revert the changes.
Use an Older Visual Studio Version
- Developers have confirmed that EDMX generation works fine in 17.12.2.
- If you're not locked into the latest version, rolling back could be a quick fix.
Switch to Code-First or EF Core
- If you're already exploring Entity Framework Core, this might be a good time to migrate.
- EF Core doesn’t rely on EDMX and gives you more control over schema and mappings.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Deepika Sawant11mo ago
What’s Going Wrong
- The EDMX designer internally runs queries to introspect the database schema.
- If your database or views include query hints (like OPTION (FORCEPLAN) or WITH (NOLOCK)), the designer fails to generate the model.
- This behavior changed after Visual Studio 17.12.4, making previously working EDMX files break.
Workarounds You Can Try
1. Remove Query Hints Temporarily
  
  If possible, modify your views or stored procedures to remove query hints during model generation.
  
  Once the EDMX is generated, you can revert the changes.
2. Use an Older Visual Studio Version
  
  Developers have confirmed that EDMX generation works fine in 17.12.2.
  
  If you're not locked into the latest version, rolling back could be a quick fix.
3. Switch to Code-First or EF Core
  
  If you're already exploring Entity Framework Core, this might be a good time to migrate.
  
  EF Core doesn’t rely on EDMX and gives you more control over schema and mappings.