Spurious exceptions from universal providers when application pool starts up with IDbCommandInterceptor

Don't know if this is the right place to post this but i'm having a problem with asp.net universal providers 2.0.0 Entity Framework IDbCommandInterceptor.  When the application pool spins up and i attempt to login the interecptionContext catches this error. Is this a bug or is this intended behavior? 
I am using all of the universal providers in my application.
I am attempting to attach an error logger to the entity framework system FYI.  
Right now my only recourse is to just attach giant if blocks. like so. 
if (interceptionContext.Exception.Message.StartsWith("The operation failed because an index or statistics with name 'IDX_UserName' already exists on table 'Users'.") ||                        ...