Forum Discussion

Konrad_Golińczak's avatar
Konrad_Golińczak
Ideator II
2 years ago

An exception was thrown while activating Aras.Server.Core.EditItemModule after restoring the DB

Hi, I received this error after restoring and connecting the DB toin InnovatorServer.xml. Dont see any post here on this. Anyone have a solutiioon to this?
An exception was thrown while activating Aras.Server.Core.EditItemModule -> Aras.Server.Core.UpdateItemInternal -> Aras.Server.Core.ChangeTracker.ChangeTrackerContainer -> λ:Aras.Server.Core.Abstractions.Internal.IDerivedRelationshipsChangeTracker.

7 Replies

  • jaohol's avatar
    jaohol
    Ideator II
    2 years ago

    I'm receiving the same error. Has anyone found a solution yet?

    • KMGANAPATHI's avatar
      KMGANAPATHI
      Ideator I
      2 years ago

      An exception was thrown while activating Aras.Server.Core.EditItemModule -> Aras.Server.Core.UpdateItemInternal -> Aras.Server.Core.ChangeTracker.ChangeTrackerContainer -> λ:Aras.Server.Core.Abstractions.Internal.IDerivedRelationshipsChangeTracker.

    • jaohol's avatar
      jaohol
      Ideator II
      2 years ago

      So what I had to do was uninstall Aras, install a newer SQL Express Server (2019) and reinstall Aras. Even then I could not log in with "innovator" or "innovator_regular", but I was able to as "root" with password "innovator".

      • KMGANAPATHI's avatar
        KMGANAPATHI
        Ideator I
        2 years ago

        In my case, I have restore the DB of Aras 12 to Aras 14. So now I have two DBs, DB14 and DB12, I am able to login to DB14 but not to DB12 (restored one)

  • Daronmont's avatar
    Daronmont
    Ideator II
    2 years ago

    Hi,

    I have received same error message after installing Aras 14.0.9, just wondering, if you have a resolution to this error message? I have uninstalled and re-installed the app, created a new database to no avail.

    Appreciate your assistance.

    Thanks

  • asebastian's avatar
    asebastian
    Community Manager
    2 years ago

    Hi,

    It seems this error can occur when your database is corrupted, or is restored without the post-restore SQL queries. I'd recommend running the following queries on the database giving you issues.

    [embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:3635a448-6cb9-4b89-bc45-db20f362561b:type=text&text=--%20Query%201%20%28should%20succeed%29%0D%0Asp_change_users_login%20%27Update_One%27%2C%27innovator%27%2C%27innovator%27%0D%0AGO%0D%0Asp_change_users_login%20%27Update_One%27%2C%27innovator_regular%27%2C%27innovator_regular%27%0D%0AGO%0D%0A%0D%0A--%20Command%28s%29%20completed%20successfully.%0D%0A--%20Query%202%20%28should%20fail%29%0D%0Asp_grantdbaccess%20%27innovator%27%2C%27innovator%27%0D%0AGO%0D%0A%0D%0A--%20Msg%2015023%2C%20Level%2016%2C%20State%201%2C%20Line%201%0D%0A--%20User%2C%20group%2C%20or%20role%20%27innovator%27%20already%20exists%20in%20the%20current%20database.%0D%0A--%20Query%203%20%28should%20succeed%29%0D%0Asp_addrolemember%20%27db_owner%27%2C%27innovator%27%0D%0AGO%0D%0A%0D%0A--%20Command%28s%29%20completed%20successfully.]