Part of the problem here is obviously the lack of a small, localizable data
set that we can use to consistently reproduce the problem to be able to
determine if it is:
* An issue with the feature data that the KingOracle FDO provider or
MapGuide is failing to properly process/sanitize.
* A
Hi Michael
my suggestion is come back to Autodesk Oracle FDO provider, because you have
a licensed version of AIMS
Or I'm curious to know the reason you migrate to King.
Did you also tried to open a ticket with official Autodesk support?
Best regards
johnny
--
View this message in context:
Hi,
We have just upgraded a customer to AIMS 2016 and are experiencing frequent
crashes of the AIMS windows service. The 2 major changes in this upgrade where
moving from AIMS 2014 -> 2016 and replacing the Autodesk Oracle FDO Provider
with the King Oracle FDO provider. The error did not
