Following are steps that need to be performed if you start getting login failed for unattended execution account error.
“An error occurred during client rendering.
The report server has encountered a configuration error. Logon failed for the unattended execution account
Logon failed (rsLogonFailed) Logon failure: unknown user name or bad password.”
If this happens then it means there are unattended execution account was configured and there is some problem with the account mentioned in the configurations. Either it has changed in Active Directory setup and the password has been expired or changed. This is optional setting but if you have configured it then it must be updated when there is change in the account information or password. Otherwise you may start getting the aforementioned error message.
To configure the account:
Launch the reporting services configuration manager and connect to the report server.
“An error occurred during client rendering.
The report server has encountered a configuration error. Logon failed for the unattended execution account
Logon failed (rsLogonFailed) Logon failure: unknown user name or bad password.”
If this happens then it means there are unattended execution account was configured and there is some problem with the account mentioned in the configurations. Either it has changed in Active Directory setup and the password has been expired or changed. This is optional setting but if you have configured it then it must be updated when there is change in the account information or password. Otherwise you may start getting the aforementioned error message.
To configure the account:
Launch the reporting services configuration manager and connect to the report server.
- Go to Execution Account and select the Specify an execution account checkbox.
- Enter the account information and click on Apply button. This must be the domain account.
Go to the report manager and access the reports and it should now run properly.
1 comment:
Thanks. The trick worked. The Password for the execution account was changed and just retyping in the SSRS configuration did the trick.
Post a Comment