Share
ReportWe have a Dynamics installation that has been around for a very long time, including several upgrades. We have a couple of users that are exhibiting very strange log-in behavior. One user usually goes through Citrix to attach to Dynamics. There are two ODBC connections: one that specifies the name of the server explicitly and one that uses an alias. Otherwise the connection parameters are identical. Both test fine.
The user (bob) can successfully use the connection that uses the alias, but not the explicit name. Most other users can use either without a problem, though most go through the explicitly-named ODBC connection.
What is also strange is that the behavior seems to continue if the user uses my local workstation to get into Dynamics: the aliased server connection works, but the other does not. My login (a fairly recent addition) gets in fine using either.
The only other item of note is that only Dynamics seems to be affected in this manner: using SQL Server Management Studio or an Excel workbook with an ADO connection string relying on network user name for authentication seem to work just fine no matter how the naming is set up.
Not sure if this is related, but when I try to view the Properties -> Securables tab for the user through Management Studio, I did get a collation conflict error.
Very bizarre.
*This post is locked for comments
All responses (
Answers (
65,271
