Sage 100

Am I missing a step on the 64-bit ODBC install? Customer is on v2013 Advanced - we run the ODBC 64 bit from the install disk. Appears to just install as SOTAMAS90. The ABOUT shows 64-Bit. a. Does it use the same name as the 32 bit ODBC? b. Looks as if it drops the ODBC into System32 instead of SYSWOW64?

Sounds about right. Can you connect to the database from a 64-bit application? SYSWOW64 is where the 32-bit versions live, while System32 is where the 64-bit versions live. Confusing, right?

@AaronClark Makes me think they were trying to confuse people.

Anyone ever user Excel 2013 Power Pivot and had an issue connecting to 64 Bit ODBC? I'm at a customer where they can use the regular Excel 2013 to pull in data via ODBC but when they try to use PowerPivot it either hangs or if they try to preview data they get an error about data not being accessible (which is odd because we can pull it in via ODBC through regular Excel query). Anyone deal with this before?

It does seem that way, doesn't it?

Wayne, I was never successful at getting power pivot to connect to either 32 or 64 bit odbc. I gave up on power pivot. I found it to be a resource hog, and never found a compelling benefit.

I have not tried your above steps - does it help to have a silent dsn - my bet is maybe the authentication prompts are not happening.

We are able to connect using Excel and 64 bit ODBC. It's just PowerPivot that seems to be causing problem. And a complete bummer because one of the reasons the customer had for upgrading was to gain access to 64 bit ODBC. The customer created a silent DSN (that's how they were using it in prior PowerPivot). Does not appear to fix the issue in Excel 2013 using PowerPivot.

Push the data to SQL and then I bet it will work like a charm!

Did you see the hot fix 5004 or 5005 for 2013 PU2 or PU3? It has to do with the install of the 64bit ODBC. Thought it worth the mention.