Forum Discussion
PowerShell DSC Pullserver stops working with SQL database
After updating Windows Server 2025, our DSC Pull Server stopped communicating with its SQL backend database. The issue was not present before the update, and reverting to the previous version of Microsoft.PowerShell.DesiredStateConfiguration.Service.dll immediately restored normal functionality.
With the newer DLL version, the service starts successfully and the endpoint remains available, but no connection is established to the SQL Server database. As a result, database initialization does not occur, required tables are not created or updated, and node registration fails. No database sessions are observed on the SQL Server during registration attempts, indicating that the service does not reach the SQL connection phase.
We compared the previous working DLL version with the updated version and confirmed that the regression is introduced by the newer DLL. Replacing the updated DLL with the earlier version consistently restores SQL database connectivity and normal Pull Server Operation.
1 Reply
This appears to be a regression in the newer Microsoft.PowerShell.DesiredStateConfiguration.Service.dll. The Pull Server starts and the endpoint remains available, but no SQL connection is attempted. Database initialization does not occur, tables are not created or updated, and node registration fails.
Replacing only the updated DLL with the previous version immediately restores normal SQL connectivity and Pull Server operation. This strongly indicates that the issue is introduced by the newer DLL and occurs before the SQL connection stage.
The recommended next step is to open a Microsoft support case and include the Windows Server build, installed KB, both DLL versions, and relevant DSC, IIS, and Application logs. The older DLL can be used as a temporary workaround.
