SCCM 2609 reporting point error is the new red icon a lot of us found in Site Status right after upgrading to Configuration Manager 2609. The reporting services point goes Critical, srsrp.log fills up with (!) InitializeSrsWhenNeeded error = The system cannot find the file specified. every minute, and yet the reports themselves open and run without complaint. The usual reflexes, removing and re-adding the role, resetting the SSRS account, even moving to SSRS 2022, do not clear it. What does clear it is copying a handful of DLLs that the role now expects but that never landed on the remote server. Below I walk through how to confirm you have this exact problem, the workaround a Microsoft forum member posted, how I would apply it safely, and how to check it worked.
What the SCCM 2609 Reporting Point Error Looks Like
The pattern is consistent across the reports in the Microsoft Tech Community thread that started on October 29, 2026, a few days after 2609 went globally available on October 26. On the server that hosts the reporting services point, srsrp.log shows two lines that repeat on every health check:
(!) InitializeSrsWhenNeeded error = The system cannot find the file specified.
Failures reported during periodic health check by the SRS Server <server FQDN>.Code language: HTML, XML (xml)
In the console you see the other half of it. Under Monitoring > System Status > Site Status the reporting services point is Critical, and the component status messages say the reporting point failed to monitor the SQL Reporting Services server. So this is a case of the reporting services point critical after 2609 upgrade while reporting itself is healthy. That mismatch is the best clue you have: the role’s health check is failing, not SSRS.
I want to be upfront about one thing. As of this writing, Microsoft has not published a known-issue entry for this. The What’s new in version 2609 page lists only one known issue (the ODBC Driver 18.7.1.1 problem with 2603 and earlier). The acknowledgement so far is informal: on November 5 a forum member with a Microsoft badge wrote that Microsoft is aware of the problem and knows the cause. Treat everything below as a workaround until a hotfix ships.
Why the InitializeSrsWhenNeeded Error Happens
At its root, the SCCM 2609 reporting point error is simple. The InitializeSrsWhenNeeded error is a plain Win32 “file not found”. The SMS_EXECUTIVE service on the reporting server tries to load assemblies that are not in its SMS\bin\x64 folder, so the health check component fails before it ever talks to SSRS. Two people in the thread traced it independently. One used Process Monitor, filtering on smsexec.exe with the result NAME NOT FOUND for .dll paths. The other used .NET Fusion (assembly binding) logging. Both landed on DLLs that exist on the site server but not on the remote role server.
My reading of it, and this is my interpretation rather than a Microsoft statement: 2609 changed the SQL client stack. The release notes say the SQL Server Native Client dependency was removed and .NET applications now target 4.7.2. The missing files below include Microsoft.Data.SqlClient.dll, which fits that change. The role installer on the remote site system simply did not bring the new dependencies along. That also explains why reinstalling the role changes nothing: it installs the same incomplete set.
If your reporting services point lives on the site server itself, the files are already in the site server’s bin\x64 folder, and you would not expect this specific error there. Every report in the thread involves a reporting services point on a separate site system server.
Step 1: Confirm You Are on 2609 and Have This Exact Error
Do not apply a DLL workaround to a different problem. First confirm the site version. In the console, open About Configuration Manager in the top-left menu. Version 2609 is build 5.00.9152.1000 according to Microsoft’s Updates and servicing page. If you prefer PowerShell, query the SMS Provider (replace PS1 with your site code and CM01 with your provider server):
Get-CimInstance -ComputerName CM01 -Namespace root\SMS\site_PS1 -ClassName SMS_Site |
Select-Object SiteCode, Version, BuildNumberCode language: JavaScript (javascript)Then check srsrp.log on the reporting server. Microsoft’s log files reference lists srsrp.log, srsrpsetup.log and srsrpMSI.log as site system server logs. On a remote site system they sit in the SMS\Logs folder of the drive where the role is installed, so adjust the path if it is not C:
Get-Content "C:\SMS\Logs\srsrp.log" -Tail 200 | Select-String "InitializeSrsWhenNeeded"Code language: JavaScript (javascript)If you see the InitializeSrsWhenNeeded error lines, the site is on 2609, and the role is on a remote server, you have the SCCM 2609 reporting point error this article covers. If srsrpsetup.log shows the role failing to install, that is a different problem. Fix the installation first.
Step 2: Find the Paths and Back Up the Role Folder
Fixing the SCCM 2609 reporting point error means copying files, so you need two folders: the source on the site server and the target on the reporting server. The default site server source is C:\Program Files\Microsoft Configuration Manager\bin\x64, but plenty of us install to another drive. Rather than guess the target, I read it from the SMS_EXECUTIVE service path on the reporting server:
Get-CimInstance -ComputerName SSRS01 -ClassName Win32_Service -Filter "Name='SMS_EXECUTIVE'" |
Select-Object Name, State, PathNameCode language: JavaScript (javascript)The PathName ends in \bin\x64\smsexec.exe. That bin\x64 folder is your target. Before changing anything, take a copy of it. It costs a few seconds and gives you a clean way back:
$Target = "\\SSRS01\C$\SMS\bin\x64"
Copy-Item -Path $Target -Destination "\\SSRS01\C$\SMS\bin\x64.bak-20261115" -RecurseCode language: PHP (php)Step 3: Copy the Missing DLLs Without Overwriting Anything
On November 11, the Microsoft-badged forum member posted the list of binaries to copy from the site server’s bin\x64 folder to the reporting server’s SMS\bin\x64 folder:
Microsoft.Data.SqlClient.dllMicrosoft.Data.SqlClient.SNI.x64.dllSystem.Buffers.dllSystem.Text.Json.dllSystem.Memory.dllSystem.Runtime.CompilerServices.Unsafe.dll
The earlier community workaround was the same idea with one important rule: copy only files that are missing on the target and never overwrite existing ones. I follow that rule. A file that already exists on the role server may be a different version on purpose, and overwriting it trades one problem for a harder one. This script copies only what is absent and tells you what it did. Run it on the site server from an elevated prompt:
$Source = "C:\Program Files\Microsoft Configuration Manager\bin\x64"
$Target = "\\SSRS01\C$\SMS\bin\x64"
$Files = "Microsoft.Data.SqlClient.dll", "Microsoft.Data.SqlClient.SNI.x64.dll",
"System.Buffers.dll", "System.Text.Json.dll", "System.Memory.dll",
"System.Runtime.CompilerServices.Unsafe.dll"
foreach ($f in $Files) {
$src = Join-Path $Source $f
$dst = Join-Path $Target $f
if (-not (Test-Path $src)) { Write-Warning "Not found on site server: $f"; continue }
if (Test-Path $dst) { Write-Host "Already present, skipped: $f"; continue }
Copy-Item -Path $src -Destination $dst
Write-Host "Copied: $f"
}Code language: PHP (php)
If the script warns that a file is not found on the site server, stop and check your source path before going further. Do not pull those DLLs from NuGet or another machine. The whole point is to match the exact versions your 2609 site server ships.
Step 4: Restart SMS_EXECUTIVE and Verify the SCCM 2609 Reporting Point Error Is Gone
The role only loads the new files when the service starts again. Restarting SMS_EXECUTIVE on the reporting server restarts every Configuration Manager component on that server, so if it also hosts other roles, do it in a quiet window:
Invoke-Command -ComputerName SSRS01 -ScriptBlock {
Restart-Service -Name SMS_EXECUTIVE
Get-Service -Name SMS_EXECUTIVE | Select-Object Name, Status
}Code language: JavaScript (javascript)Give it a few minutes, then read srsrp.log again. The InitializeSrsWhenNeeded error should stop appearing after the restart time stamp:
Get-Content "\\SSRS01\C$\SMS\Logs\srsrp.log" -Tail 100 -WaitCode language: JavaScript (javascript)
Back in the console, the reporting services point turns OK in Site Status after the next health check. Several admins in the thread confirmed both workarounds cleared the SCCM 2609 reporting point error and turned the status green. If the error persists, the role may need a file that is not on the list. That is where the Process Monitor filter above earns its keep. Run it against smsexec.exe while you restart the service and look for NAME NOT FOUND on DLL paths outside the GAC.
Before You Fix the SCCM 2609 Reporting Point Error: Practical Warnings
- It is unsupported until Microsoft says otherwise. Note the change in your change log, with the file list and the backup folder name, so the next person knows why those DLLs are there.
- Watch for the hotfix. When Microsoft ships an in-console hotfix for 2609, install it and recheck srsrp.log. The site will reinstall roles as needed, and you want the official set of binaries.
- Do not overwrite existing files. This is the one rule both workarounds share.
- Do not blame SSRS. Resetting the SSRS service account or reinstalling SSRS did not clear this for anyone in the thread. If reports run, SSRS is fine.
- Check other remote roles. I have not seen confirmed reports of other roles hitting the same missing-assembly pattern after 2609, but if another remote role goes red right after the upgrade, its log is the first place to look for the same “cannot find the file specified” message.
This one taught me again to check the role’s own log before touching the service it depends on. A Critical reporting point with working reports, as in the SCCM 2609 reporting point error, nearly always means the monitoring component is broken, not SSRS. For more SCCM troubleshooting where the log tells the real story, see the guides below.
Read more: SCCM Scan Failed 0x80244022? Fix the WSUS 503 Error Fast
Read more: How to Fix “PXE Boot Aborted” When a Task Sequence Isn’t Deployed Correctly
SCCM 2609 November 2026 Status at a Glance
For anyone landing here from a search, this is the SCCM 2609 November 2026 status in short. Version 2609 (5.00.9152.1000) is globally available since October 26. The SCCM 2609 reporting point error is acknowledged informally but has no KB or hotfix yet, and the DLL copy is the working fix. Microsoft’s official 2609 notes also cover the ODBC 18.7.1.1 issue, the removal of the SQL Server Native Client dependency, the end of SQL Server 2016 support and the new CMG VM sizes. Read those before you upgrade any remaining sites.
What causes the SCCM 2609 reporting point error?
After the 2609 upgrade, a reporting services point on a remote site system server is missing several DLLs it now needs, such as Microsoft.Data.SqlClient.dll. The health check fails with InitializeSrsWhenNeeded error = The system cannot find the file specified in srsrp.log, and the role shows Critical even though reports run.
Does removing and re-adding the reporting services point fix it?
No. Admins in the Microsoft Tech Community thread reported that reinstalling the role, resetting the SSRS account and upgrading to SSRS 2022 did not help. Copying the missing DLLs from the site server bin\x64 folder and restarting SMS_EXECUTIVE did.
Which DLLs need to be copied?
The list posted on November 11, 2026 is Microsoft.Data.SqlClient.dll, Microsoft.Data.SqlClient.SNI.x64.dll, System.Buffers.dll, System.Text.Json.dll, System.Memory.dll and System.Runtime.CompilerServices.Unsafe.dll, copied from the site server bin\x64 folder to the role server SMS\bin\x64 folder without overwriting existing files.
Is there an official Microsoft fix or KB?
Not as of mid-November 2026. A Microsoft-badged forum member said Microsoft is aware and the cause is known, but no KB or hotfix has been published. The 2609 release notes do not list this issue yet.
Where is srsrp.log on a remote reporting server?
Microsoft lists srsrp.log as a site system server log. On a remote site system it is in the SMS\Logs folder on the drive where the role is installed, for example C:\SMS\Logs\srsrp.log.
References
Microsoft Tech Community: 2609 issue with Reporting Services Point
Microsoft Learn: What’s new in Configuration Manager version 2609
Microsoft Learn: Log file reference for Configuration Manager
Microsoft Learn: Updates and servicing for Configuration Manager






