Skip to main content

SSRS stopped working after administrator password re-set

Hello friends, As always enjoying cross platform Database support and sharing something  new for you. Today I am going to share on SQL Server reporting services. Sometime a small change can lead the blunder of issues in any IT environment and  you will start running here and there to resolve, if things are not good. Recently I was looking on MSBI-Report on development environment , I was new on this reporting server .

Reporting server was running with .\Administrator logon,  IT team given public access IP to access SSRS report publicly for demo purpose. For keeping security measure and threats in mind I just re-set the administrator password on windows server.  I was assuming when user will access the report it will ask for new windows credential and with new credential they will see the report. After testing I will rollback the password. But things goes wrong as I need to change more. After changing password reporting server started throwing error .

 " Unattended Execution Account in SSRS, The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: unknown user name or bad password".

For the quick resolution I started digging around search engine and experimenting because developer is waiting to see his report back on their web application ,  as his demo was scheduled.
  • I restarted the services of SSRS ... no resolution.
  • I changed the logon services , from .\administrator to local ... no resolution.
  • I found that data source have no connection values as before.. so I said developer to re-deploy the data sources on report server. Actually the report server were able to access but when trying to access report the error was coming. but re-deploying of data source was wrong.

Then took a break just back to reporting server configuration manager and rollback the logon services with .\administrator and put the windows new password over there . Also re-set the password on execution account setting . After that restart the SSRS report .. Reports get executed.

We should also change the new sys login password on configuration manager's on logon service and execution account.



Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription