February 6, 2019 at 11:20 am
I am trying to get SSRS running on Server #2, copied from Server #1
What I've done so far.
- Backup Reports & ReportServer databases from Server 1 to server 2
- Realized Server 2 was 1 Cumulative fix behind, so patched to the same level.
- Backed up & restored encryption keys from Server 1 to 2.
- Restarted SQL & SSRS on server 2
When I open SSRS Configuration manager and click "Web Portal URL" I get the error page
" 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."
When I click on RS in management Studio I get the error box "Scale-Out Deployment" is not supported in this edition of Reporting Services (rsOperationNotSupported)
Server # 1 Version on standalone server:
Microsoft SQL Server 2016 (SP1-CU4) (KB4024305) - 13.0.4446.0 (X64) Jul 16 2017 18:08:49 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: )
Server #2 version on VM
Microsoft SQL Server 2016 (SP1-CU4) (KB4024305) - 13.0.4446.0 (X64) Jul 16 2017 18:08:49 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
February 6, 2019 at 11:38 am
homebrew01 - Wednesday, February 6, 2019 11:20 AMI am trying to get SSRS running on Server #2, copied from Server #1
What I've done so far.
- Backup Reports & ReportServer databases from Server 1 to server 2
- Realized Server 2 was 1 Cumulative fix behind, so patched to the same level.
- Backed up & restored encryption keys from Server 1 to 2.
- Restarted SQL & SSRS on server 2When I open SSRS Configuration manager and click "Web Portal URL" I get the error page
" 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."When I click on RS in management Studio I get the error box "Scale-Out Deployment" is not supported in this edition of Reporting Services (rsOperationNotSupported)
Server # 1 Version on standalone server:
Microsoft SQL Server 2016 (SP1-CU4) (KB4024305) - 13.0.4446.0 (X64) Jul 16 2017 18:08:49 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: )Server #2 version on VM
Microsoft SQL Server 2016 (SP1-CU4) (KB4024305) - 13.0.4446.0 (X64) Jul 16 2017 18:08:49 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
Check the keys table in the ReportServer database. It sounds like you may have two entries - one form the old server and one from the current new server. Delete the old server record.
Sue
February 6, 2019 at 11:52 am
Sue_H - Wednesday, February 6, 2019 11:38 AMCheck the keys table in the ReportServer database. It sounds like you may have two entries - one form the old server and one from the current new server. Delete the old server record.
Sue
Hi, there are 3 records in KEYS.
MachineName InstallationID InstanceName Client PublicKey SymmetricKey
------------------------------------------------------------------------------------------------------------------------
NULL 00000000-0000-0000-0000-000000000000 NULL -1 NULL NULL
"From Server 1 Name" 76AA1804-ED63-492D-B319-29D33832524B MSSQLSERVER 1 0x0602000000A.....etc ..... 0x0102000000A.....etc .....
"To Server 2 Name" E5113C0A-2992-40B2-8857-40FC6B64EEA0 MSSQLSERVER 1 0x0602000000A.....etc ..... 0x0102000000A.....etc .....
February 6, 2019 at 11:57 am
homebrew01 - Wednesday, February 6, 2019 11:51 AMSue_H - Wednesday, February 6, 2019 11:38 AMCheck the keys table in the ReportServer database. It sounds like you may have two entries - one form the old server and one from the current new server. Delete the old server record.
Sue
Hi, there are 3 records in KEYS.
MachineName InstallationID InstanceName Client PublicKey SymmetricKey
------------------------------------------------------------------------------------------------------------------------
NULL 00000000-0000-0000-0000-000000000000 NULL -1 NULL NULL
"From Server 1 Name" 76AA1804-ED63-492D-B319-29D33832524B MSSQLSERVER 1 0x0602000000A.....etc ..... 0x0102000000A.....etc .....
"To Server 2 Name" E5113C0A-2992-40B2-8857-40FC6B64EEA0 MSSQLSERVER 1 0x0602000000A.....etc ..... 0x0102000000A.....etc .....
The NULL machine name, installationID 00000000.....is always there. You can ignore it.
Remove the old server record. You want the current server listed for MachineName.
Sue
February 6, 2019 at 12:07 pm
That got me to progress to the next error !...Thanks
I restarted SSRS , tried to open the URL and get
"Could not load Folder Contents"
"Something went wrong, please try again.
There's an icon for the "HOME" folder, but won't open.
February 6, 2019 at 12:12 pm
homebrew01 - Wednesday, February 6, 2019 12:07 PMThat got me to progress to the next error !...ThanksI restarted SSRS , tried to open the URL and get
"Could not load Folder Contents"
"Something went wrong, please try again.There's an icon for the "HOME" folder, but won't open.
That's usually related to permissions. Try to open IE on the Report Server using Run As Administrator. Then add yourself as system administrator.
Sue
February 6, 2019 at 12:21 pm
I am already in the Windows Administrator group.
February 6, 2019 at 12:32 pm
homebrew01 - Wednesday, February 6, 2019 12:21 PMI am already in the Windows Administrator group.
Okay but you still need to run IE as an administrator and add yourself to the system administrators in Reporting Services.
Sue
February 6, 2019 at 12:46 pm
Sue_H - Wednesday, February 6, 2019 12:32 PMOkay but you still need to run IE as an administrator and add yourself to the system administrators in Reporting Services.
Sue
"...add yourself to the system administrators in Reporting Services...."
I don't see where to do that.
I can right click IE, "Run as Administrator"
February 6, 2019 at 12:56 pm
homebrew01 - Wednesday, February 6, 2019 12:46 PMSue_H - Wednesday, February 6, 2019 12:32 PMOkay but you still need to run IE as an administrator and add yourself to the system administrators in Reporting Services.
Sue
"...add yourself to the system administrators in Reporting Services...."
I don't see where to do that.
I can right click IE, "Run as Administrator"
Top right on the home page, select Site Settings.
On the site settings page, use the left side of the pane to select Security.
Click on New Role Assignment.
On the next page, put your Domain\Username in for User Name and the select System Administrator and then click on OK.
Sue
February 6, 2019 at 1:49 pm
Thanks, I added myself as an administrator, but still getting the error.
I'll keep poking around.
February 6, 2019 at 2:08 pm
homebrew01 - Wednesday, February 6, 2019 1:49 PMThanks, I added myself as an administrator, but still getting the error."Could not load folder contents
Something went wrong. Please try again later.I'll keep poking around.
Did you enable My Reports? There is a bug related to that - may or may not be related, depends on your patch level:
FIX: Home page of SSRS web portal becomes empty after you enable My Reports feature in SQL Server 2016
Also, with it being a new instance/migration, it's a good idea to check the Reporting Services logs and check for errors. The logs are in the reporting services\LogFiles directory. I always check it even if I'm don't get any errors or have any issues.
Sue
February 6, 2019 at 2:16 pm
And I thought of one other odd thing that can come up - it's with SPNs and however your network is setup for Kerberos authentication and if you are using a domain account for the service. The fix on that is to create an SPN for the reporting services services account. It won't hurt anything.
And I think now I'm out of ideas so hopefully one of those things gets you up and running.
Sue
February 6, 2019 at 5:34 pm
Sorry if I missed it in the previous posts, but did you go into SSRS Config Manager and change the database connection to point to your new server?
I didn't see that in your steps.
February 7, 2019 at 3:10 am
We had this recently, we added our domain service account to the Local Security Policy, Local Policies, User Rights Assignment to Allow Log on Locally
and that fixed it for us.
Might be worth a try.
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply