Share via

SharePoint 2016 Jan 2026 Security Update breaks custom SOAP services – “Type is not registered as safe”

Hamid Mahmood Sial 0 Reputation points
2026-01-25T12:07:27.9333333+00:00

After installing SharePoint Server 2016 Security Update – January 13, 2026, our custom SOAP (ASMX) services stopped working in Site Pages.

When opening the page, we get the following error:
Sorry, something went wrong. The type is not registered as safe.
Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.

Environment

SharePoint Server 2016 (On-Prem)

  • SOAP/ASMX services
  • Services were working correctly before applying Security updates

Sample ASMX service in SharePoint Designer
:
[Moderator note: personal info removed]

After adding SOAP service in Data sources, we use this service in our pages by adding DataFormWebPart.

How to fix it?

Thanks in Advance

Microsoft 365 and Office | SharePoint Server | Development
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Michelle-N 12,755 Reputation points Microsoft External Staff Moderator
    2026-01-26T03:25:31.5533333+00:00

    Please note that Q&A forum is a public platform, and moderators will modify the question to hide personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data. I will move your information to Private Message to protect your privacy.

    Hi @Hamid Mahmood Sial

    Thank you for posting your question in the Microsoft Q&A forum. 

    Based on the information you provided, I understand that after installing the SharePoint Server 2016 Security Update dated January 13, 2026, your custom SOAP (ASMX) services stopped working on Site Pages. When opening pages that contain these services (via DataFormWebPart), the error “The type is not registered as safe” is displayed, although the services were working correctly before applying the security update.

    According to the documentation and similar cases, SharePoint currently allows Web Parts and controls that are explicitly declared as safe in the SafeControls configuration. Any custom control or service that is not registered in the SafeControls list of the Web Application may be blocked, which can lead to the error “The type … is not registered as safe” and prevent the page from rendering properly.

    This behavior is similar to issues previously observed with workflows, where certain security patches removed or disabled entries under AuthorizedTypes or SafeControls in the web.config file. To restore functionality for your custom SOAP services, you need to register the related custom controls or assemblies in the SafeControls section of the SharePoint configuration. In other words, the Web Part or assembly used by the SOAP service must be explicitly added to the SafeControls list so that SharePoint treats it as “safe.”

    However, as a moderator, I do not have the resources to access or troubleshoot specific customer environments directly. Therefore, you may consider raising a support ticket to receive more in-depth assistance from the official support team.

    Services Hub

    Please note that Services Hub is intended for paid support tickets, and access is subject to certain conditions. You can find more details at: Services Hub sign in FAQs | Microsoft Learn

    I hope this information is helpful.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread 

     


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.