As part of a continuing saga of internal DNN frustrations, I will keep this brief.
Our group hosts our DNN sites on Azure. Unbeknownst to us, a copy of our DNN resource was made, utilizing the same production database. At some point in time, two different instances (nearly identical to each other) were interacting with one database. This caused several problems, the biggest of which I have posted here for about which was files and modules not installing and behaving correctly.
The public facing resource is the one to which we deploy modules; however, we are hoping to move off of it as it is not in our control. These modules only display on that resource, but I assume exist in the shared db for all of the resources. Not knowing this, I installed the module again to a second resource, to the same page. This brought the site down with the "Sequence contains more than one matching element" error.
Does anyone have any suggestions about where in the DB to look to resolve this issue? A quick google search turns up this issue for different reasons and has not been helpful. It's almost certainly related to installing an identical module to this same page more than once.
I can provide the entire log file for the day, but this is the error that clearly is written to the log each time the resource is accessed:
there seem to be still references to old, removed providers in your web.config file. DNN is unable to load outdated navigation providers, did you recently upgrade DNN or remove providers? besides, there are errors writing to the log file and there seem to be duplicate entries in TabUrls table.
To my knowledge the install hasn't been upgraded or changed since December or early January when we upgraded to 9.8. This issue began in March after installing a module to a page that already had that module installed on alias.
The site is fairly static and only has new development once maybe every four months. This particular issue began immediately after installing a module on a page that was supposed to already have it (and did on an alias) and then refreshing the page when it didn't display.
I'll look at TabUrls and the webconfig - Are the tables that are written to when a module is installed? I could check those for duplicate rows as well. Or the module install could have simply been the straw that broke the camel's back.
Posted By hbilbrey on 12 Apr 2021 12:37 PM As part of a continuing saga of internal DNN frustrations, I will keep this brief. At some point in time, two different instances (nearly identical to each other) were interacting with one database.
At some point in time, two different instances (nearly identical to each other) were interacting with one database.
Do you mean you have 2 DNN installations using the same database (might lead to a lot of issues)? Or 2 DNN portals within the same DNN installation (normal user case)?
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.