An old Access 2003 .adp project is currently running on Windows 7 machines, while SQL Server 2008 is on the backend. Since the app is moved to a Windows 10 machine, the app will trigger "Cannot generate SSPI context" error.
There are a lot of messages over the Internet to explain possible reasons and solutions.
In our case, we may overcome the problem running Msaccess.exe from commandline, using:
runas /netonly /user:userdomain\useralias "C:\Program Files\<path-to-office-folder>Msaccess.exe"
The downside is that the user is prompted for password each time the shortcut is being used.
The weird fact is that the context under which the program is running is apparently the same as the Windows 10 user has the right credentials to access domain resources (can access server side networks shares correctly), and also has credentials within SQL server configuration. As a proof, under Windows 7, the same credentials are being used without errors.
It looks like the app in Windows 10 is incorrectly passing computername\useralias credentials to SQL Server in place of userdomain\useralias.....
Is there a way to fix this so that the app (or Windows 10) are addressing the domain user name correctly, avoiding the error?