In the last few days, I found a sync error when trying to synchronise any model in veda2_1.190.1.1.
Screenshot attached.
after some hours working with @ravinder @kanors yesterday, it looks like some registry keys were corrupted from MS office 365. We are not sure how this happened.
in any case, the solution is to uninstall and resintall Office 365 using the automated tool from Microsoft, which also repairs the registry.
If you don't actually want to uninstall and reinstall Office 365, you can also just repair it.
To repair your Office 365 installation, just open Programs and Features in the Control Panel and once you are there, select Microsoft Office 365 in the program list and then Change/Repair on the command bar.
(01-12-2020, 12:30 PM)AKanudia Wrote: Thanks for this post James
Thank you for the information.
@Amit, is there anything we as users should do to avoid it from happening? Or will it be taken care of in the next VEDA update
An update to this problem:
I went back to VEDA 1 today for a different model run, (that i have not ported to veda 2 yet.
VEDA2 1.8182.1.1 and 1.190.1.1 was working fine this morning.
I had to reinstall accessdatabaseengine2007.exe to get VFE1 to read my model from Excel365 after reinstalling office 365 last night.
after installed accessdatabaseengine2007.exe VEDA2 1.8182.1.1 and 1.190.1.1 reproduces the same synchronisation error as previously and stops working.
so perhaps there is some inconsistency between accessdatabaseengine2007.exe and veda2?
(01-12-2020, 02:16 PM)Antti-L Wrote: If you don't actually want to uninstall and reinstall Office 365, you can also just repair it.
To repair your Office 365 installation, just open Programs and Features in the Control Panel and once you are there, select Microsoft Office 365 in the program list and then Change/Repair on the command bar.
