Announcements
No record found.
Hi,
Im getting following Error while Synchronizing DB in ax 2012 R2. Any Help?I have tried deleting View's. still error is coming.
*This post is locked for comments
Hi Mani,
I think you tried to restore a database from one environment to another? All environments can have environment specific element ID's. Then you can have this kind of errors. If you are restoring a backup of a database, you also need to use the model store belonging to that environment.
If you need to have a copy of the data only and use the original model store, you can use the Test Data Transfer Tool which is availabe on the Downloadable tools section of Lifecycle services. lcs.dynamics.com/.../LocalTools
This error is in Live server . and db is never restored.
Then please inform why you performed the synchronization. Is there any deployment of customizations ongoing?
Yes,of course. Our dev team working on customizations. when a report is deployed in live, its taking one day to effect the changes.(restarting any service is not helping),some times wflow is stops working,also this "can not create a table in ledger journal table-- the record already exist". so one our dev told us that we have Db synch issue which is not automatically syncing. What I planned is to install again with new DB. but want to keep data only.
Oh man, it really physically hurts me to read about your installation.
Have you guys considered having the development environment separate? Not on the live server where people work?
The error about the record already existing in the ledger journal was most probably related to caching, very unlikely that it was a DB sync issue.
As for the specific errors - somebody changed some times or the view itself, it seems like.
In the view, you seem to have a union of tables, and thus the types of columns that are part of the result set need to match, but they do not on your installation. This is a development error and should be corrected as such by your dev.team.
The error says that field CarrierName is not compatible with field Name (in a union query). Please review the data types; maybe you have changed on of them and they now have different lengths.
Yes, We have development environment as well, but the old dev team messed the live server. now we hired new dev's and they pointing to me
Like Ivan mentioned, it is the best that your new dev team will take a look at this. There are mismatches between the element ID's in the model store and your live database.
You may have some data from an older synchronization job laying around. Try to have a look at this article: www.agermark.com/.../odd-synchronization-issues-in-ax-2012.html
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Joris dG 5
Alexey Lekanov 2
Henrik Nordlöf 2 User Group Leader
