HI Beth,

Remove the User DSN instance of SOTAMAS90 on the workstation. Remove any other SOTAMAS90 DSN's under System or File DSN

Start Sage 100 and the SOTAMAS90 will recreate it.

If this does not resolve the issue, please rerun workstation setup.

Thx

John Nichols

Sage

She's done the rerunning of workstation setup, but not a removal.  I'll see if that can happen.

Deleted them all, uninstalled Sage, reinstalled Sage - still the same thing.  :-(

When you uninstalled, did you remove the local workstation folder (with sota.ini...)?

The local folder was removed.  :-(

Hi Beth, The only time I've seen what you are describing is when no companies have been activated and accessed in Sage 100.

Can you provide more information.

Sage 100 Standard, Advanced or Premium

Version

Alternate directories Y/N

Terminal services Y/N

Workstation O/S

verify these files exist in ..\mas90 directory on workstation

• pvodbsec.ini
• pvxsec64.dll  (only on x64 operating system)
• PvxSec32.dll

I'm sure you ran Autorun.exe from WKSetup as Administrator, right? Maybe turn off UAC?

I will get the details.

Again, if we setup a company-specific ODBC (login info filled in), it runs for that company with all modules available.  It is only if we do NOT enter login info in the setup that it does not prompt.  And it doesn't matter what we call it - TEST, NOCOMPANY, etc - if there is no company saved in the login, it will not prompt for it.