Sage 100

Client needing to use CS ODBC driver. Last night it was working, BUT got an error message when trying to print checks and found issue with path - it included an E$. So we changed around the share and have Sage finally working again (4 hours of working on permissions - ready to kill) but when trying to print something, it pops up with Database Login for the CS ODBC. Running ODBCAD32 shows a mapped drive from the server's point of view (but we are on the workstation). Tried changing path to UNC. Connection still failed. Sage not much help. Anyone have some doc?

Can you browse to the UNC in Windows explorer? If not there may be a permission issue.

Yeah I can.

Another thought - Dies the account that is running the service have domain admin rights?

Wait - odbc service - let me check

Currently running as app logged in as Admin

OK, so latest thing is that if you test the connection, it only sees 100 files

And I get an error again when trying to print Unable to preview Bad Index (same report runs fine without CS ODBC)

OK. I'm going to start over. Did an upgrade. Only issue was slow printing and an error during check printing. Turned on ODBC for slow printing and it worked great. But then the check printing error was still happening, and we looked at the ODBC path and it contained ""E$"". So we shared on the server at ""Sage"" and reran wksetup (as Admin). All hell broke loose as we SLOWLY worked through security issues. At this point, we are able to run Sage again, but if we try to use the CS ODBC, we get the Bad Index error.

Here's the install instructions that I have https://www.evernote.com/l/AAHH4UeMwltM0q1aMmykEaTapYUTvXFgy0Q

Extremely Random Thoughts Domain admin or local admin? Using the Alnoor service login ""bible"", do you pass all the challenges that he has you check for? I use the same login that I use for the Sage service. I also used the UNC path initially for the CS service but every time the server rebooted, I had to restart the service. So with the help of my trusty IT guy, we switched it to the local C drive (on the server). Is the E drive above a mapped path or a physical one? Sure wish it were easier to install and troubleshoot as I would use it more often..

Haven't the instructions changed with version 2013 on up? I've been looking for something that comprehensive but for the new versions.

The name of the file changed, but I think most everything else is the same...

OK, then Happy Monday. I won't be able to sleep Sunday night for the anticipation.