I am getting the following exception when trying to save an entity...

failed: System.ArgumentException : The element name 'RmaEntity' isn't known in this provider
Parameter name: elementName
    at SD.LLBLGen.Pro.ORMSupportClasses.PersistenceInfoProviderBase.GetElementMappingInfo(String elementName)
    at SD.LLBLGen.Pro.ORMSupportClasses.PersistenceInfoProviderBase.GetAllFieldPersistenceInfos(String elementName)
    at SD.LLBLGen.Pro.ORMSupportClasses.PersistenceInfoProviderBase.GetAllFieldPersistenceInfos(IEntity2 entity)
    at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.GetFieldPersistenceInfos(IEntity2 entity)
    at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.PersistQueue(List`1 queueToPersist, Boolean insertActions, Int32& totalAmountSaved)
    at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave, IPredicateExpression updateRestriction, Boolean recurse)
    at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave)
    RmaCollectionsTests.cs(39,0): at Com.Ims.Rms.Rbi.QuickbookIntegrationBlTests.RmaCollectionsTests.PopulateRmaTable()
    RmaCollectionsTests.cs(46,0): at Com.Ims.Rms.Rbi.QuickbookIntegrationBlTests.RmaCollectionsTests.GetRmaListFromTracReturnsTest()

I have tried clearing out the project files and re-generating the project. That didn't work. What other things can cause this?

Please check whether your problem is related to:

• Bad references: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=9322
• Changes on generated code or templates: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=12589
• CatalogNameOverwrite: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=13575

None of those links were able to solve my problem.

It maybe helpful to know that I am connecting to a MS Access database where the indices and relationships are not well defined. I am unable to clean up this database because it is a third party database that is already in production and cannot be disturbed. Can this sort of error appear with a "messy" database like this? If so, is there a way around it?

When does this start to happen? and Does this happen for all entities? From the stack trace, it could be a problem on DBSpecif project being out of sync.

Please try to generate code to an empty folder, then create a test project that perform your save, just to figure this out. If the test is ok, you will have to clean up your LLBLGen generated code and put it the new ones.

My test project worked. I will try it out soon on my real project and let you know. I'm sure it should work. Thanks for your help.