The process of recreating your mail profile is described here Recreating your mail profile. While you may not notice any issues at first, you might run into "strange" issues later on. When downgrading from a previous version of Outlook, it is highly recommended to recreate your mail profile. Is there a way to get rid of this error without needing to recreate my mail profile? I'm not experiencing any issues aside from getting this error each time I start Outlook. In Windows Control Panel, open Mail, then click Show Profiles, and then click Add.' If you experience problems with this profile, you can create a new profile. 'The mail profile "Outlook" was created with a newer version of Outlook and might contain information that is not compatible with your current Outlook version. A solution is to avoid multiple cascade path.After going back from Outlook 2010 to Outlook 2007 I got the following message upon starting Outlook SQL Server has this constraint and we need to live with. so instead of fixing it, the implementation avoids it by preventing the definition of duplicate cascade paths. SQL Server - Why can't we have multiple cascade paths? I don't know and found no official information about this. ReleaseDateA is removed two times.īut this seems legit, just need to ReleaseDateA one time. And remove SectionTypeA, by cascading this remove again ReleaseDateA. When the SectionA is removed, by cascading this remove also ReleaseDateA and SectionTypeA. To understand, see this data : SectionA -> ReleaseDateA The model has multiple cascade path : Section -> ReleaseDateĪnd SQL Sever don't allow this. NET Core 2.1 and EF Core 2.1 with SQL Server. Public ICollection ReleaseDates Īm I supposed to be fixing this via FluentAPI's Cascade command or is there something I am screwing up in the entities that I should be doing? I am not sure if I have always been doing something wrong in the entities and fixed it somewhere else I can't see it or if something has changed over the years and I am now doing it completely wrong. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints (0x80131904): Introducing FOREIGN KEY constraint 'FK_ReleaseDates_Sections_SectionID' on table 'ReleaseDates' may cause cycles or multiple cascade paths. I have the following two entities which, as far as I remember, worked fine in the old app but now I get an error
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |