Upgrade 2017- Sync Issue while doing data upgrade

tejateja Member Posts: 78
Hi All,

we are doing data upgrade from 2016 - 2017, After the upgrade, we have deleted the Table : Object Manager objects from the Db using Force sync Mode. The Objects were deleted successfully. Now while coming any table in the object we are facing the below issue.


Microsoft Dynamics NAV Development Environment
The following SQL Server error or errors occurred when accessing the Object table:

208,"42S02",[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'OM - Setup'.

SQL:
UPDATE [TEST2017-UPGRADE].[dbo].[Object] SET [BLOB Reference]= NULL WHERE ([Type]=1 AND [Company Name]='' AND [ID]=9183) AND ([timestamp]<=0x0000000004A95A7B)
OK


we have checked in Object Metadata Snapshot table also but, we didn't see any records for this table.

after that, we tried to import back all the objects which were deleted. System is not allowing them to import. And it is showing the same error.

please suggest..

Regards,
Teja. G

Best Answer

Answers

  • mohana_cse06mohana_cse06 Member Posts: 5,503
    check whether you have any stored procedure running in SQL
  • tejateja Member Posts: 78
    Hi Mohan,

    Thanks for reply :smile:
    In our db, there were no stored Procedures.

    Regards,
    Teja . G
  • vremeni4vremeni4 Member Posts: 323
    Hi,

    Object manager by default installs a trigger on the Object table in order to store the versions of the objects when they are changed.
    If you start SQL Studio manger or look at the table Object, I am pretty sure you will find an SQL trigger for Object manager.
    Delete it and it will fix the issue.

    I hope this helps.
  • tejateja Member Posts: 78
    edited 2017-04-05
    vremeni4 wrote: »
    Hi,

    Object manager by default installs a trigger on the Object table in order to store the versions of the objects when they are changed.
    If you start SQL Studio manger or look at the table Object, I am pretty sure you will find an SQL trigger for Object manager.
    Delete it and it will fix the issue.

    I hope this helps.

    Hi vremeni4,

    thanks for the reply. we have checked with the triggers in sql. Not able to found the trace of OMA triggers.
  • tejateja Member Posts: 78
    edited 2017-04-05
    Hi Teja,

    May be you have force removed Object Manager from 2016 database. If that is the case please deactivate first Object Manager from 2016 by deleting the Object Manger setup . Deleting the setup will remove all the data related to object manager, and then removing objects will overcome this issue. Please check.

    Hi Kalyan,

    thanks for the reply. we will have to check the same and update you .

    Regards,
    Teja . G
  • awarnawarn Member Posts: 261
    Hi Tega,

    Did you overcome this issue? I also am doing an upgrade and cannot remove these objects with our license, the company has so far not been able to help, so I am investigating removing the objects manually via SQL.
    Our company changed hands and apparently OM is only available in the license of our old company, not the new one, hence our issue.
Sign In or Register to comment.