Sage 100

Hi there,

Setup a silent ODBC dsn for two workstations at the same customer site.  In both cases, added the company code and user in UPPERCASE then added the pw and saved the connection.  On one workstation its been working flawlessly and never requires a login.  On the other workstation it will work for a while (a few hours up to a day) then will ask for login creds - when it prompts for the creds we go back into the dsn and the login creds are gone.  

Have checked/ tried:
deleted / recreated dsn.  Setup a completely new dsn with new name
odbc registry permissions for this user
tried creating a system dsn logged in as the network admin and saved that - same result drops creds

Anyone ran into this before or have any ideas what to try?

Thank you,
Marc
Technology Integrators

------------------------------
Marc Cregan
Technology Integrators
------------------------------

You aren't using something like VDI on the workstations, are you? 
VDI=Virtual Desktop Infrastructure
One of the symptoms of VDI use is if the user settings get overwritten the next time they log in.
It is probably something you already checked but thought it worth mentioning.

I had never worked extensively with VDI until about 2 years ago when a big customer I picked up had to configure Sage for VDI. It's very similar to an RDP connection except the end-user generally can't make configuration changes that survive a reboot.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

DSN's named SOTAMAS90 will maintain credentials ONLY until the next login. Name it anything other than SOTAMAS90 and they will be retained across logins.

------------------------------
Dan Burleson
Software Consultant
Connex Software
------------------------------

Marc - What @Wayne Schulz said. The IT admin may need to create a new VDI image if they use VDI and you think it's happening when they logon. When you create a Silent Connect DSN (and generally System DSN is better idea than User DSN), it creates a registry entry which when it's working the 3 credential values are populated correctly. Here's the location in regedit:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI  (this is for normal 32-bit o/s)
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI  (this is for 64-bit o/s)

My DSN is called SILENTMAS90 so I browse down to the SILENTMAS90 subkey under \ODBC.INI. You do the equivalent. Then notice UID, PWD, and Company values. They'll be blank when not working. Tell the IT guy/gal something is overwriting that, making it not persist. If you can duplicate the issue by logging off of Windows and logging back on again, that will be helpful for them. It could be the particular user needs to be moved to a different domain group. If they use VDIs then likely the VDI image needs to be refreshed.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph:
------------------------------

We only create System DSN's, which are more stable than User DSN's.
For SQL DSN's, always use Windows authentication, since SQL DSN's don't save SQL authentication passwords.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
------------------------------