When trying to log in with the web interface of the Devolutions Password Server, you can possibly get a Login failed error.
The Login failed for user 'Domain\ServerName$ error with a '$' at the end of the server name is caused by a wrong setting of the Application Pool Identity in Internet Information Services Manager (IIS). The Application Pool Identity must be set with a specific account when activating the Integrated Security option in the Server Settings of Devolutions Password Server. For more information about Integrated security, please refer to How to Configure Devolutions Password Server to use integrated security.
Login failed for user 'Domain\ServerName$'
1.Please open the IIS Manager and select the Application Pools in the Connections pane. Then, select the Application of your Devolutions Password Server and click on the Advanced Settings from the Actions pane.
IIS Manager - Application Pools
2.On the Advanced Settings dialog, select Identity and click on the ellipsis button on the right.
Application Pools - Advanced Settings
3.Select Custom account and click on the Set... button.
Application Pool Identity
4.Fill in the credentials and click on the OK button. This account must have the proper rights in order to run the web interface of the Devolutions Password Server.
5.Now the Application Pool Identity is set with an account with proper rights for running this application.
The Login failed for user 'IIS APPPOOL\ApplicationPoolName' error is related to insufficient permissions for the ApplicationPoolIdentity or inexisting user ApplicationPoolName on the SQL database. I when the SQL Server and Devolutions Password Server are hosted on the same machine.
Login failed for user 'IIS APPPOOL\ApplicationPoolName'
1.Using Microsoft SQL Server Management Studio, right-click on the Security branch and select New - Login.
SQL Server Management Studio
2.For the login, type IIS APPPOOL\AppPoolName and DO NOT CLICK SEARCH (If a search is executed, it will resolve to an account with ServerName\AppPoolName and SQL will be unable to resolve the account’s SID since it is virtual).
Create SQL User
3.Please follow the instructions from step 4 of the online help page How to Grant access to SQL Server instance.