Forum Discussion
2609 issue with Reporting Services Point
I updated our Config Manager site last night to version 2609 and I'm seeing an issue with the Reporting Services Point. Every minute in the srsrp.log I'm getting the below error (I replaced the actual server name with Server FQDN), yet reporting services is functioning perfectly fine. I tried removing and re-adding the role this morning and it went right back to this error. The role is functioning properly and everything else that gets written in this log before these lines seems normal. This seems like it may be a bug.
(!) InitializeSrsWhenNeeded error = The system cannot find the file specified.
Failures reported during periodic health check by the SRS Server (Server FQDN).
3 Replies
- dhebert2026Copper Contributor
I have just upgraded to 2609 and i'm having the same issue with Reporting .
it's an aggravation for sure. does Microsoft have a bug fix for this?
- edd080Iron Contributor
I think I manged to find a workaround for this error; so obviously proceed with caution:
This seems to have worked out for me ( logs still showing healthy)
On the remote Reporting Services Point server, I ran Procmon and set the filters as follows:(
Process Name is smsexec.exe,
Result is NAME NOT FOUND,
Path ends with .dll,
excluding GAC ; \en\ ; .resources.dll)
I then restarted the SMS_EXECUTIVE service. It showed a number of missing DLL files
I copied them from the site server's bin\x64 folder (without overwriting any existing files) to the reporting service server and restarted SMS_EXECUTIVE.
The log went clean and Component Status turned green.
Hope this might help you and anyone else on 2609 with a remote SSRS server
Again this is a workaround and I assume an official fix will be released...
- edd080Iron Contributor
Hello I am getting the exact same error here too, after upgrading our sccm server to 2609 I also get the below error:
the reporting page is accessible via the portal and seems to be working normaly. Only issue i have is with the reporting services point. Removing the role from Administration --> Site Configuration --> Server & Site System Roles; then adding it again makes no difference; the log still eventually shows the attached same error. I am at a loss at what might be causing this issue.
Any help or feedback would be appreciated.