Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Upgrade 2017- Sync Issue while doing data upgrade
teja
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
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
0
Best Answer
-
kalyankandimalla
Member Posts: 56
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.5
Answers
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
Thanks for reply
In our db, there were no stored Procedures.
Regards,
Teja . G
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.
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 vremeni4,
thanks for the reply. we have checked with the triggers in sql. Not able to found the trace of OMA triggers.
Hi Kalyan,
thanks for the reply. we will have to check the same and update you .
Regards,
Teja . G
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.