Password Verification: Enter administrator password", "Database [253] Access Denied"

[Matti_Pellinen1]

I have deployed a number of Thick Clients to different workstations. Some of these clients ask: "Password Verification: Enter administrator password", and give the error "Database [253] Access Denied" after logging into the OnBase using ODBC. Some installations work just fine, they have their workstation name registered as login when the installation was done manually. Now when the client is deployed automatically, workstations are not added into the users-list in the SQL DB, and seems not to work. This is just my theory, but how can I fix this and the deployment? I have not altered HSI's rights in config or in DB. However, deployed application is different: it's just a shortcut to the .exe whereas all client files were put into the workstation when installed manually.

[Chris_Arpajian]

Hi Matti,

While I would recommend contacting your first line of support, here are some questions which may help narrow down your issue:

On an impacted machine, can you navigate directly to the obclnt32.exe and launch it, select your ODBC and login without issue?

Are there any Command Line Switches you've added to the shortcut you are pushing out automatically which other machines do not have?

I assume when this issue is happening, the other machines previously deployed can still login without issue?

Have you checked the ODBC connection you've deployed to ensure you're hitting your same DB Server, Instance and DB as the working machines?

[Matti_Pellinen1]

No, the error comes even if I launch obclnt32.ee directly.
No, there are no additional switches in the shortcat.
Yes, the other machines can login without issue.
Yes, the ODBC is identical.
I think this must be related to the workstation logins in the DB, if I only could verify this. And if I can, it's not the solution yet... 😞

[Scott_McLean]

Try adding the securityadmin role to the HSI login on SQL server.

This is the role used to automatically add the workstation logins on SQL server.

Per the database reference guide:

The minimum permission required for the HSI server login is the securityadmin role. If the HSI login is not assigned this role, and if the sa password is not blank or the same as the HSI default password, then a user logging on to OnBase from a workstation for the first time will receive the message "Enter Administrator Password"

[Matti_Pellinen1]

This is indeed the reason to our problem. But originally, we migrated our OnBaseDB from SQL2005 to SQL2012 server, and at that point the securityadmin role had to be taken away since there are other databases in the server as well. Our DB Admin didn't quess the results but says if he had known this he would have installed OnBase DB into it's own SQL Server instance.
Now we are in limbo: for security reasons we can't add securityadmin role to the HSI user, and it's not able to create workstation users. I could create workstation users manually, before their deployment, but I don't know which password to give them, it's hidden in OnBase dll-files or somewhere. Any workarounds?