Profile Service resource cannot find

SGH 1,211 Reputation points

Getting the below error when we try to access the below URLs in SharePoint 2019




SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,761 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ChelseaWu-MSFT 6,311 Reputation points

    This is a common error suggesting that you are missing the ProfileService.svc file in IIS root folder.

    You can just ignore related error message (e.g. in Event Viewer) if everything works fine in your farm, but here are a few options to fix this issue:
    1 Stop and then restart User Profile Service and User Profile Synchronization Service so that SharePoint can recreate the endpoint listener in IIS.

    2 If you do not need User Profile Synchronization Service or the service is missing, you can manually create the ProfileService.svc file under IIS root folder.
    The default file path for SharePoint Server 2019 is C:\Program Files\Microsoft Office Servers\16.0\WebServices\Profile
    You can create a copy of another svc file in the folder (e.g. ProfilePropertyService.svc), rename it to “ProfileService.svc” and then replace the content with:

      Service="Microsoft.Office.Server.UserProfiles.ProfilePropertyService, Microsoft.Office.Server.UserProfiles, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" 
      Factory="Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceHostFactory, Microsoft.Office.Server.UserProfiles, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" 

    Missing ProfileService.svc.
    Event ID 3: Error “/ProfileService.svc does not exist.” (AD Profile Import).

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    **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. **

    1 person found this answer helpful.
    0 comments No comments