Skip to main content
  • EN
Hi,

 

 

Thought I would post here rather than going to general support, just incase other people have the same issue. I am running FME 2012 SP4 32 bit and have just recently put office 2013 64-bit onto the same machine.

 

 

Well I wasn't surprised that I now get an error reading data, such as (plus many more) "Unable to find provider 'Microsoft.ACE.OLEDB.12.0', falling back to 'Microsoft.Jet.OLEDB.4.0'. The 2007 Office System Driver might be missing from your system; follow this link for more information: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23734"

 

 

I don't think that above detail is going to help me? I have assumed FME 2013 doesn't support the new office yet? Correct me if I am wrong.

 

 

Is there timeline for office 2013 support?

 

 

Cheers,

 

Todd
Hey Todd

 

 

I had a similar issue but with 64 bit FME and 32 bit Office. Downloaded the Microsoft driver and it worked.

 

 

http://fmepedia.safe.com/articles/FAQ/Drivers-required-for-32-bit-FME-with-64-bit-Office-installation

 

 

regards

 

Martin
Thanks Martin,

 

 

I will give that a try when the Access Database Engine Redistributable 2013 is released.. Hopefully that is all that will be needed.

 

 

Cheers,

 

Todd
I am having a similar, problem.  I have the 64 bit office 2010 driver installed, but am running 32-bit fme 2012 (due to compatibility with some reader formats).  I have noticed that some days I can read excel files into various transformers and then other days I cannot.  I have seen this problem within the same workbench, same transformer and using the same external excel file.   All my workbenches are created on the same machine so it isn't a result of changing to a machine with a new build. Is there something I could be doing outside of FME that will cause this occasional error?  I cannot seem to find a pattern.  I would expect to either work all the time or not at all.

 

 

Thanks,

 

Angela

Reply


Community Stats

29,696
Posts
112,870
Replies
37,356
Members
Terms & ConditionsCookie settings