LINQ Query Issue, Sequence contains no elements LINQ Query Issue, Sequence contains no elements asp.net asp.net

LINQ Query Issue, Sequence contains no elements


The query must not be returning any data. Run a profiler on the SQL database to see the physical query being executed and try to execute it manually against the database to see what the data looks like. You probably have to adjust the query (or the data) to get the results you're looking for.

"Sequence contains no elements" is basically LINQ's way of telling you that you're trying to reference an element from a list that doesn't have anything. So calls to things like .First() or .Single() can't find anything, hence the error.

When you change the calls to something like .FirstOrDefault() or .SingleOrDefault() then it will go with "default" value for that type, and for reference types the default is null. So if you set something to null and then try to call a method on it, you'll get object reference not set to an instance of an object.


The Single method throws this exception when there are no elements in list(query) or there are multiple elements.

The SingleOrDefault method throws an exception when there are multiple elements in the list. Returns null when there are no elements.

The FirstOrDefault method return the first item in the list or null. There are no exceptions.

Use it and the check the reference for null

if (ta != null )   {      ta.status = Allowncedtl.status;       ce.SaveChanges()   }

The source will always be an object, so no worries about it in your case.


All that means is that your query isn't matching anything. Presumably Allowncedtl.tvrid is an ID which doesn't match anything in the database. You shouldn't assume that SingleOrDefault will return a non-null value. Only use SingleOrDefault when you're expecting that there may be no values - and cope with that. If a failure to find a value indicates a bug, you should use Single (or perhaps First) instead.

We can't tell anything about what the underlying cause of your error is - you should log which ID you were looking for, work out why you were looking for that, and then check it in the database.