We are experiencing the same issues with VEDA 4.5.5 here. Tested so far on 3 different machines, while not changing anything on the model, which worked well before. Attached is the error message.
I've been testing around a bit and found out that VEDA always crashes during sync when reading the file
ScenTrade_TRADEPARAMETERS.xlsx (also see attached).
When row 8 (i.e. the one where CAP_BND is defined) is being removed, the problem does not occur any longer (!)
So far we had been using Excel 2013 64 bit without any problems. Unfortuantely, installing Excel 2016 is not an option for us, since our institute does not have any licenses so far. Any ideas?
But Amit, Fabian said: "...while not changing anything on the model, which worked well before".
So, if this worked well before even with such an innocent "typo", should we now be forced to change our templates?
Could you thus also explain how/why this change may have occurred? Is this difference caused by the ACE driver? If so, are there other differences caused by it, such that models might no longer work as they worked before?
07-11-2017, 05:35 PM (This post was last modified: 07-11-2017, 05:36 PM by fg.
Edit Reason: format
)
(07-11-2017, 03:54 PM)AKanudia Wrote: remove "AT" from the AllRegions Col in Row 8.
Ok, first of all, thank you! It now works again.
(07-11-2017, 04:28 PM)Antti-L Wrote: But Amit, Fabian said: "...while not changing anything on the model, which worked well before".
So, if this worked well before even with such an innocent "typo" [...]
In fact, this is not a typo. Concerning the tradeparameters file I have been told that in the AllRegions column the exporting region should be written in, while the actual value for CAP_BND should be placed in the region column of the importing region (which I could never really make sense of, since the process is already defined in Pset_PN). Maybe this was a wrong advice and simply did not result in an error in the previous versions?
Unfortunately, I cannot test this on my own without adminstrative privileges after our IT has uninstalled the previous version.
Hi Vikrant,
has this issue been resolved? Is there a solution or patch?
I'm having the same issue today after upgrading to VFE_4.5.4.
I cannot sync TIAM without multiple errors., the same that Olex listed in his earlier post in this thread.
Neither reinstalling 32bit or 64bit excel 2016 seem to be a solution for me after doing fresh installs and reinstalling the AccessDatabaseEngine.exe connector.
best
James
(25-01-2018, 11:49 PM)JGlynn Wrote: Hi Vikrant,
has this issue been resolved? Is there a solution or patch?
I'm having the same issue today after upgrading to VFE_4.5.4.
I cannot sync TIAM without multiple errors., the same that Olex listed in his earlier post in this thread.
Neither reinstalling 32bit or 64bit excel 2016 seem to be a solution for me after doing fresh installs and reinstalling the AccessDatabaseEngine.exe connector.
best
James
James, get the latest installer from support website and update to latest versions.
(31-10-2017, 07:06 PM)olexandr Wrote: I have finally managed to fix this problem by uninstalling Office 365 and installing Office 2016 instead. So it seems that VEDA 4.5.5 has some compatibility issues with Office 365. I hope KanORS fixes it at some point because at least in DTU we are switching to Office 365 in the near future.
Here is a sample of the errors that this incompatibility causes:
- Automation error The server threw an exception.
- The remote server machine does not exist or is unavailable
- Method '~' of object '~' failed
- Unable to get the SpecialCells property of the Range class
Cheers,
Olex
I encountered the same issue. The same spreadsheet worked fine with office 2013 but did not sync with office 365/2016.
The problem was solved by removing the "Freeze Pane" option from the spreadsheet.
