In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/03 Report--
Environment description:
SCCM:System Center 2012 R2 Configuration Manager
SQL:SQL Server 2008 R2
The two servers are installed separately.
Nagging:
Troubleshooting is a long process, and it takes a long time (but it's all worth it after the problem is solved), and you need to look carefully at every possible point, in which logs play a big role. Note that it is specifically stated here that online posts are only auxiliary and cannot be copied blindly. With different environmental structures, the wrong directions may be quite different.
SCCM server side of the error:
After installing the Reporting Services role, click report options to select the report server and report an error:
There was a problem connecting to the specified report server. Please check the connection and make sure that sql reporting service is running on the specified server.
1) "report options" cannot connect to the report server
2) SCCM console-Monitoring-system status-site status-Reporting Services point. Right-click on the "status message Viewer", as shown below:
Note: after the Reporting Services role installation fails, it will be automatically reinstalled every 60 minutes.
3) SCCM console-Monitoring-system status-component status-SMS_SRS_REPORTING_POINT to view error status messages, as follows:
Troubleshooting:
According to the instructions on the Internet, the log related to srsrp was not found under C:\ Program Files\ Microsoft Configuration Manager\ Logs, so there is a dead horse medicine solution below.
The SCCM server side that tried to troubleshoot:
PS: the following operations have also been done on the SQL server (srsrp.msi path: d:\ SMS\ bin\ x64), and the effect is the same.
1) search for srsrp.msi and install it manually, as follows:
2) after installation, the Reporting Services error does not stop, and the following files will be generated in the root directory:
The SQL server side that tried to troubleshoot:
1) delete the report database ReportServer, and then reinstall the Reporting Services role
The SQL server side of the correct way to troubleshoot:
1) View the log file::\ SMS\ Logs\ srsrpsetup.log
PS: although SCCM's "status message Viewer" prompts you to check the logs srsrpsetup.log and srsrpmsi.log, it feels like you can check srsrpsetup.log, which is characterized by short space and information in place.
2) according to the prompt of the log above, open the D disk and find that the SMS_SRSRP directory does not exist, only the files that were manually installed before srsrp.msi, these files are actually files in the SMS_SRSRP directory, but they are manually installed and are not in the SMS_SRSRP directory, so they do not take effect.
3) after successfully installing the Reporting Services role in the SCCM test environment, it is found that the SMS_SRSRP directory will be generated on disk D.
Error resolution:
1) Delete the Reporting Services role
2) delete the D disk of SCCM and SQL respectively, and manually install the files generated by srsrp.msi.
3) copy the SQL server of the SMS_SRSRP directory of the test environment under disk D (I feel that this step can be omitted because it will be overwritten when the role is installed again)
4) install the Reporting Services role (if you have deleted the ReportServer database, you need to install it first)
5) it is found that the SMS_SRSRP directory of disk D is overwritten (determined by the creation time)
6) the Reporting Services role is installed successfully. The srsrpsetup.log and its status messages are as follows:
PS: at first, it was suspected that it was caused by the permission of disk D of SQL server, and then sqladmin full control permission and Users read permission were added, but it had no effect. Moreover, after reinstalling the Reporting Services role, the permission of disk D will be reset, so it is certain that it is not caused by the permission.
Here comes the picture that I haven't seen for a long time:
At this point, after many days of depression, today finally disappeared, ^ _ ^
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.