Sage 100

Sage 100 Advanced (MAS 200) version 4.5.0.5 .0 having an ODBC Connection issue. The specified DSN contains an architecture mismatch between the Driver and the Application. Has anyone seen this error message before? KB can't find the error message.

@GaryFeldman thats got 32 bit odbc driver on a 64-bit system written all over it.

Small update. This is an EES version install. We tried to reinstall the workstation to update the driver without success.

OK I think you may be correct. Is is a 64 bit system. Recommended next step?

what are you trying to connect to the DSN through? a script?

SIA setup in class. Fails on the extract. To verify the problem I went into Excel and couldn't read the tables. Went in to DSN admin and got the message above.

to administer the DSN you need to run ODBCAD32 from the windows\syswow64 folder.

I can remove the driver but can't configure because it is the wrong driver is my best gues.

btw the 64-bit driver is available now. Not sure but my guess is it would work with 4.5

And of course I am having portal access issues and can not download anyhting from portal now.

you can't configure it with the 32-bit version in syswow64?

with that version I can get in to the ODBC driver, but what is there to configure. I don't want to hardwire?

I'm sorry, really nothing. you were just trying to get in and I was surprised it wouldn't let you. I found another 90 Minds post that talks about the 64-bit driver not being backwards compatible. Are there SIA instructions for installing in 64-bit environment?

SIA doesn't care about the environment as long is it is not broken. IF ODBC works, SIA will work. I will try and get my staff to download.

I understand, Gary. I think the ODBC works. It's strange...the 32-bit odbc driver works on a 64-bit computer to run Crystal reports from Sage 100. You just can't use it without specifically using it in ""32-bit mode"". Sage and/or Crystal Reports must automatically handle that when running reports.

I tried to change compatibility in properties of Extractor to run in Windows Server 2003 mode (figuring that was 32 bit) but it still failed.