MicrosoftDocs / SCCMdocs

Configuration Manager documentation public repo
https://docs.microsoft.com/sccm/
Creative Commons Attribution 4.0 International
251 stars 361 forks source link

Reporting Services Server name does not stay !!! #791

Closed felymich closed 5 years ago

felymich commented 6 years ago

Hello, for the steps:

3.On the Home tab, in the Settings group, click Report Options. 4.Select the default report server in the list, and then click OK. If no reporting services points are listed in the list, verify that you have a reporting services point successfully installed and configured in the site.

I am doing this to point to our Reporting Services Server but if I am going back to 4. it is gone !! with a red ! on the right... something to be checked... in front of doing this action... Thanks, Dom


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

aczechowski commented 6 years ago

Thanks @felymich for sharing this feedback, and I'm sorry that you're having trouble. Can you help clarify what you mean? What do you suggest is checked before doing this action?

Also, if you're having technical problems, I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:

felymich commented 6 years ago

Thank you @aczechowski . When opening "Report Options" as describe in the article I am getting an empty field with a red exclamation mark. 2018-08-30 11_25_52-vrpsccmpr01 - remote desktop connection then I am filling up using the drop down (it is our Reporting Server) 2018-08-30 11_28_49-vrpsccmpr01 - remote desktop connection Click ok The list of reports is refresh but still I cannot use the Create/Edit options only the Run is working... 2018-08-30 11_32_14-vrpsccmpr01 - remote desktop connection

if I go back to Report Options I have again the same screen as before with the red exclamation mark...

Thanks, Dom

aczechowski commented 6 years ago

This sounds related to issue #803, if not the same? For support requests, please use the options mentioned above.

I'll keep this issue open to include a note similar to the warning you received. This article touches upon Report Builder version in the section to Configure reporting to Use Report Builder 3.0, but we could provide further information about the versions needing to match.

felymich commented 6 years ago

Yes it looks like it was the same between #803 and #791. Report Builder works perfectly on the Reporting Server by itself... but apparently is not accessible from the Primary Server where the console is hosted... I can run the report from the Primary Server but that's it !

Thank you, Dom

yoke88 commented 5 years ago

My Env:

  1. SQL Server 2017 Std with reporting service 2017 installed
  2. ConfigMgr 1802 then upgrade to 1810, after upgrade i installed the reporting service role.

Encounter the same problem, and i resolved my problem by:

  1. Add firewall exceptions to 80,443 port on the reporting service server
  2. change regedit on the server which installed ConfigMgr Console to use report builder 3.0

after the two steps,i can view and run reports in ConfigMgr console,but can not edit or create report default

  1. then i installed SQL Server 2016 Report Builder Here on the server which has ConfigMgr console installed. and i can edit and create report in the console now.
aczechowski commented 5 years ago

I revised this article, the changes will publish live around 11am Pacific time