In older versions of Infor CRM SLX, all of the LAN programs used the same Data Link connection. Starting with version 8.5.1, Application Architect has begun using its own 64-bit connection to the database, configured separately from the Connection Manager (which is 32-bit). While these two connections are set up independently of each other, it is important for each connection to have the exact same name. Otherwise, the client site will not work.
To show this in detail, let’s take a look a test system that uses the eval database. When we set up the Data Link connection in the Infor CRM SLX Connection Manager, the documentation strongly recommends we give it the same name as the database. Giving it some other name does not cause any specific issue, other than making harder to keep track of which connection goes to which database, but we will name it the same here.
Now we will set up the connection in Application Architect. Back when Infor CRM SLX was originally written, there was only the one connection. Now that Application Architect has its own connection, we need to make sure to give it the same name as the Data Link connection we just created in Connection Manager for all the other LAN programs to use, since the underlying coded was not designed to take multiple connections into account.
(There is also this connection to the Data Link in Data Link Manager that we need to make for all the other LAN programs to use. While there is no particular requirement for what we name it, makes sense to use the same name we have used for all the other connections. Infor CRM SLX will automatically create the first connection here. There is no separate program to edit the Data Link Manager. It is accessed by clicking the ellipses next to the connection name in any of the LAN programs.)
So what happens if we forget to keep the names the same, or just mistype something, and the connections don’t have identical names. I am sorry to say the error you will see is neither unique nor consistent. If we change the name of our connection in Application Architect to something that does not match the Connection Manager, build and deploy the site, and then try to visit the web client, we get a login error (even though the password is correct). As there are a number of things that could cause a similar error, it might not be obvious that mismatched connection names are the cause. On that front, all I can offer is that you include verifying that both connections’ names are identical in the list of things to check when troubleshooting. I must also add we did have a case in which a client with mismatched connection names was unable to login, but instead of the error shown here they were just kicked back to the login screen with the URL was repeating the path to the login page multiple times. Usually the URL showing that repeating pattern means some file on website is corrupt, and the site needs to be redeployed. In that case, it was fixed when we fixed the connections names.
