03-18-2014 06:00 AM
03-18-2014 06:26 AM
Ron
I have seen this error in the past. It is referring to the SQL user and SQL login IDs. In the past I have fixed it by accessing the database and looking for the name of the workstation that is trying to connect as a SQL login . Then drop (delete) that login. After that you should be able to login.
03-18-2014 06:56 AM
03-18-2014 07:59 AM
Ron
I only ever went in and dealt with this when I had the Fatal DB Error you referenced. Most of the time I never worried about old SQL logins. If you migrate to Web or Unity this becomes less of an issue as users are going through the Web / App Server(s). Best if you are not the DBA to discuss this with them. I probably should have put that disclaimer in earlier 🙂 Anyway have you been able to login the new workstation?
03-18-2014 08:18 AM
Yes, in MS SQL you really have two security levels. The first is to allow you to connect to the SQL Server or instance its self. The second one is at the database. This allows the user to connect and access the database. The main user you want to delete is at the database level especially if that same user is accessing other databases. If they aren't, then you can go ahead and delete both, the instance logon as well as the database. This should allow the user you are attempting to logon as connect to OnBase.
You also mentioned that the connection was 64bit. Remember to create 32 bit ODBC connections. From a 64 bit system, this is accomplished by using the odbcad32.exe located in the Windows\SysWOW64 directory.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.