Sage 100

The world has turned upside down! ;) Just upgraded a client from version 4.5 to 5.2 Advanced and the ODBC Driver is installing with the SERVER's drive letter. This causes all sorts of crazy errors in only certain parts of the program (IE crystal reports run ok, but Explorer does not). If we go into ODBC and update it to UNC, all is well, but every time they reload Sage, the ODBC defaults right back to the drive letter. Verified the sota.ini file is referencing the UNC, and no UAC or anti-virus interfering. Running in MAS90 Mode works just fine, running from server works fine. Happens running both as an application and as a service (with admin logon)

Hi - Disable Client-server ODBC

already disabled

is ""enable for all users"" checked or un-checked

unchecked

you may want to check the CSODBC fields in SY_SYSTEM.M4T manually to be sure nothing is strange

What if I enable and then redisable... will that re-write the table? I have never used that do I am not sure what it affects

Something to do with the user running the service?

make a copy of SY_SYSTEM.m4t in MAS_SYSTEM first. then no harm to try.

What does the C/S do differently than the normal ODBC? I did what you suggested, and you were right! There was a random character in the box. Removed that and BOOM! We are working.

if you run the server side of the client server ODBC (used to be called pvxiosvr.exe) - it speeds up ODBC access - used for slower speed connections (WAN) or odbc against very large tables in providex. You will need to open up port 20222 on the server's firewall if it is on, once you run the server side odbc. It is enabled by user. Info in the Advanced install pdf glad the world is now back ....

I am having a very similar issue. Upgrade from v4.5 to v2015. ODBC is now an issue when running from workstation (not server). I tried using the CS ODBC but I can't get it to install. I posted the error message a while back. I will have to circle back to the issue next week.