Unable to Access PBIRS Dev after restore from Prod

[Abdelmajid]

Hello,

We have performed a restore on PBIRS Dev environment using Prod Backup. I can see that the conetnt is there when I query it, but getting this error message when trying to access the PBIRS Dev environment from browser:

"The service is not available.

The report server isn’t configured properly. Contact your system administrator to resolve the issue. System administrators: Check the report server trace log for details.
"

PBIRS Dev is a single node environment.

Checking the 'Report server Configuration Manager'  I don't see the node deatils mentioned under 'Scale-out Deployment' tab.

Is there anything that needs to be done at the 'Encription Keys' tab?

The server name is not coming up here.

Appreciate any help, thank you! 

[AbhiSSRS]

Did you overwrite the Dev ReportServer DB with prod backup? Usually that creates issues like you see here.

A better option that has worked for me in past is to restore the Prod database as a new one and then change the ReportServer Database in Configuration manager to the restored DB. Once that is done we delete or archive the old DEv DB . The restored DB can then be renamed for consistency or kept as is. 

[FarhanAhmed]

Did you restore the "Dev" Machine or "Dev" SQL Database on the Production server? Restoring database may require Encryption keys

Also, make sure that  PBIRS & SQL Server Services are running properly.

[Abdelmajid]

Thank you Farhan, there was an issue with access permissions and also the Encryption Keys had to be resotored from Prod as well.

I am able to access PBIRS Dev and see all reports, but I am not sure why I am seeing the Prod nodes added to the scale-out-deployment as shown below.

Trying to remove the Prod nodes results in the beow error:

Appreciate if any help.

[FarhanAhmed]

There is a table in reporting server database "dbo.keys" which have entries of deployment servers

Removing from that table will remove entries from "Scale-out" deployment. 

But you should be careful on how you would delete such entry.

Try backup this table and then try to remove the wrong entries and restart the reporting server  services 

Then this error will probably be gone.