web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics RMS (Archived) / Trying to upgrade data...
Microsoft Dynamics RMS (Archived)

Trying to upgrade database to 2.06 from 2.05 in store ops

(0) ShareShare
ReportReport
Posted on by Roger Oakes 522

Hello,

I previously posted a question which has not been answered, so I thought I would try another way.

One of our store databases will not upgrade to version 2.06 from 2.05 (it is on sql server 2014)

When attempting the upgrade, I get the following error

An error occurred while attempting to upgrade the database: Invalid object name 'dbo.tr_ComputeQuantity'.

This particular object (trigger) is not present in the database. A little investigation showed that the other 5 store databases do indeed have this trigger present under the InventoryTransferLog table. In fact, all of the other databases have a total of 55 different triggers present, while the offending database does not have any at all. I'm not sure how this happened, but I sure would like to know how to fix it!!

Can anyone help?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Antonijo Todorovik Profile Picture
    Antonijo Todorovik 4,025 on at

    Hi Roger.

    It's obvious something happend with that store database, it will be dificult to recreate them all, all the triggers, maybe something else is missing, etc.,...

    What I would do, if your store is syncronized with HQ (sales, inventory, etc...), I would recreate / export it from HQ again, and then update it. When exporting it should create all the needed SQL components...

    Do this in testing environment first, just export this store again, restored on different PC and try to update the database...

    Kind regards, A.

  • Roger Oakes Profile Picture
    Roger Oakes 522 on at

    Thank you.

  • Roger Oakes Profile Picture
    Roger Oakes 522 on at

    Hi Antonijo,

    I did this and it would have worked, but we ended up calling Microsoft to fix the problem and they were able to add 3 triggers to the database that were not, for some reason, created when the database was set up. This solved the problem and saved having to manually enter several days worth of data. Thank you so much for your answer!

  • Suggested answer
    Antonijo Todorovik Profile Picture
    Antonijo Todorovik 4,025 on at

    Hi Roger,

    And thanks for the update. Good to know you have fixed the problem and even more that Microsoft guys helped You. My only worrie is if the database was in use and with missing the trigger, maybe some data was not inserted, updated or deleter... or whatever the trigger is doing...

    Best regards, A.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans