Sage 100

On-site with a client who can't print checks. When she runs a print preview, she receives an error about ODBC. (Copy of message attached) I then tested ODBC but trying to pull MAS data into an Excel spreadsheet. I got an ODBC error here as well. (Copy attached) The thing is, I had another client yesterday with almost the same issue interfacing MAS and eRequester. We were able to find a work around there by using an older 32 bit driver already installed on the server for a temporary fix but that's not possible here. Seeing the same issue at two client sites miles apart in the same week causes me greater concern. I realize that twice does not a pattern make but it's awful suspicious. I checked the windows update log and no OS updates were posted overnight. I will research the Sage knowledgebase next but wanted to start here; one to find a quick solution, and two to give a heads up on a possible pattern. Thanks in advance for any help you can provide.

What happens if you uninstall and reinstall workstation setup - as administrator. There are some general Google hits on this (though not for Sage) which tend to point toward corrupt odbc and/or registry

Could someone have backleveled or forwardleveled your ODBC drivers such you running the wrong version. You didn't mention the version of MAS.

That was my next option. I tried to get to the partner portal on clients workstation and IE locks up so now even more concerned about her workstation. However, what would toast the ODBC on her workstation? Same thing happened on the MAS server at another client. Curiouser and curiouser to say the least.

@DanBurleson MAS version is 4.40.0.6. I don't recognize the terms you are using so excuse my ignorance. As we say here in OK, what chu talkin' about leveling??

That message must be from your Excel test and not from the printing checks error because that wouldn't use Microsoft Query. Is the printing checks message exacly the same?

Sorry, image didn't attach. Trying again.

By backleveled I mean could someone have run a workstation setup from version 4.0x or below.

Other community posts reported that re-running workstation setup cured the problem. http://community.sagemas.com/t5/Technical-and-Installation/Stubborn-ODBC-driver/td-p/48030

I don't think a prior ws install was run but going to uninstall and reinstall the client to see if that takes care of the issue. Woudl this be the same if we had a problem on the server where MAS 90 resides? The real question I guess I am asking is when does an ODBC driver get loaded onto a MAS server; when the base app is installed or when a workstation is installed? I will have to research that when I return to the office.

The ODBC driver is loaded when the workstation setup is run. The MAS 200 server application doesn't use ODBC.

@DanBurleson I thought so but it's nice getting confirmation. Now to find out what is tripping through my garden of clients, bopping the pvxodbc32.dll drivers on the head!

Just an update, uninstalled and then reinstalled the workstation and the ODBC error resolved.

Little Bunny Foo Foo?

Haven't found where the pesky resides. Will wait see if it happens again. In the meantime, would like to know if anyone else see something similar over the next few weeks. Two clients with the same issue in two days; suspicious!

I had the same exact message as your check printing error just the other day. Their ODBC driver was corrupt because I was not able to even open the user DSN in the ODBC administrator without receiving an error. Funny thing is, this was for a new MAS 90 user and I had just run the workstation setup in the past week. Uninstalling and reinstalling workstation setup resolved the problem, but I'd love to know what's causing this.

What WIN os's are involved?

@JeffSchwenk The client workstation runs XP. The second instance was on a Windows 2003 server.

@BarbRippberger curiouser and curiouser. I haven't been able to tie either instance to a specific event like a Windows update. I don't believe much in coincidences so two occurrences at two different clients in 24 hour period causes my antenna to perk up.