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

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >>    Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >>    Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page..

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 recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..