Solved
FME Server 2012 sp4 upgrade to ArcGIS 10.1 - does not see ESRI libraries
We have upgraded out FME server 2012 sp4 to arcgis 10.1. For some reason it seems not to be able to see the ESRI Libraries now. We installed full ArcGIS 10.1. What can we check to see why it is not finding the libraries ?
Best answer by mferwerda
32 bit
We have looked at that article. From what I can see since we installed full ArcGIS we should not have to set manalluy the env variables. We do have this working OK in our Develpement envrionment, but for soem reason it is not seeign the esri stuff in our production env. The non esri stuff works, so the ArcSDE30 readers work and see that it is 10.1.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Hi,
did you install the 32-bit or 64-bit version of FME Server?
Also, see here: http://fmepedia.safe.com/articles/Samples_and_Demos/Notes-on-FME-and-ESRI-Versions-and-Compatibility
David
32 bit
We have looked at that article. From what I can see since we installed full ArcGIS we should not have to set manalluy the env variables. We do have this working OK in our Develpement envrionment, but for soem reason it is not seeign the esri stuff in our production env. The non esri stuff works, so the ArcSDE30 readers work and see that it is 10.1.
Hi,
With FME2010 we came across this problem also special when working with a 64 bit platform and 32 bit applications.
The key to find the root cause was understanding deputil.tcl script which searches for the ArcGIS dependency (FMEDEP_GEODBREGISTERED) and ensuring the registry key
{HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\ESRI}
was also used in the checking logic when the standard
{HKEY_LOCAL_MACHINE\\SOFTWARE\\ESRI}
doesnot work.
Don't forget to inform of your findings.
Marc