We have SharePoint 2016 and many info path 2010 forms that use soap service we do database in place upgrade to SharePoint Subscription edition all content upgrade find but we face problem with info path forms when form load it should retrieve user info us

Zayan Zaki 0 Reputation points
2026-06-17T14:07:00.0133333+00:00

The following query failed: GetUserProfileByName (User: 0#.w|xxx, Form Name: System Log Review Form, IP: , Connection Target: , Request: http://xxxx/_layouts/15/FormServer.aspx?XsnLocation=httpSystem Log Review Forma//home.egypt.arabbanking.local/sites/WorkFlow/Shared Documents/System Log Review Form.xsn&SaveLocation=httpSystem Log Review Forma//home.egypt.arabbanking.local/sites/WorkFlow/System Log Review Form&ClientInstalled=true&Source=httpSystem Log Review Forma//home.egypt.arabbanking.local/sites/WorkFlow/SitePages/ThankyouPage.aspx&DefaultItemOpen=1, Form ID: [Moderator note: personal info removed] Type: DataAdapterException, Exception Message: The remote server returned an error: (500) Internal Server Error. Server was unable to process request. ---> Attempted to perform an unauthorized operation. The remote server returned an error: (500) Internal Server Error.)

Microsoft 365 and Office | SharePoint Server | For business
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-06-17T14:07:16.9966667+00:00

    The error indicates that after the in‑place upgrade to SharePoint Server Subscription Edition, InfoPath forms that call SOAP web services (for example, GetUserProfileByName against the User Profile web service) are now receiving HTTP 500 “Attempted to perform an unauthorized operation”. This is an authorization/configuration issue in the upgraded farm, not a content database problem.

    Based on the provided information, the following areas must be checked and configured in the Subscription Edition farm for InfoPath forms and their service calls to work:

    1. InfoPath Forms Services configuration
      After upgrade, InfoPath Forms Service is not configured automatically. It must be explicitly configured in Central Administration:
      • In Central Administration, go to General Application Settings.
      • In the InfoPath Forms Services section, select Configure InfoPath Forms Services.
      • Ensure that InfoPath Forms Services is configured and that any required settings for browser-enabled forms are enabled.
      • If administrator‑deployed form templates or data connection files were used in the old farm, export them from the old farm and import them into the new Subscription Edition farm using Export-SPInfoPathAdministrationFiles, then update URLs if needed with Update-SPInfoPathAdminFileUrl.
    2. State Service configuration
      InfoPath Forms Services requires a State Service connection for browser forms to function correctly:
      • In Central Administration, under Application Management, select Manage web applications.
      • Select the web application hosting the InfoPath forms.
      • On the ribbon, select Service Connections.
      • In Configure Service Application Associations, ensure the State Service checkbox is selected for this web application.
      • If there is no State Service, create one and then associate it.
    3. User Profile Service and permissions
      The failing query is GetUserProfileByName, which depends on the User Profile Service Application and its permissions. After upgrade to Subscription Edition:
      • Ensure the User Profile Service Application is correctly upgraded and running.
      • Verify that the application pool identity and any service accounts used by InfoPath forms have the required permissions on the User Profile Service and its databases.
      • If profiles are not accessible due to SQL or service permissions, calls like GetUserProfileByName can fail with authorization errors.
    4. Re‑deploy or update InfoPath templates and data connections
      If the InfoPath forms or their data connections were administrator‑deployed in the previous farm:
      • Export the .xsn templates and .udcx data connection files from the old farm.
      • Import them into the new Subscription Edition farm using Export-SPInfoPathAdministrationFiles.
      • If the farm URL changed, run Update-SPInfoPathAdminFileUrl to update internal URLs used by the templates and connections.
    5. Consider platform support
      InfoPath Forms Service is removed and no longer supported in SharePoint Server Subscription Edition. While existing forms may still function in some scenarios, the platform is not supported going forward. The recommended approach is to plan migration of these forms to alternatives such as Microsoft Power Apps.

    In summary, for the current error: ensure InfoPath Forms Services is configured, the web application is associated with a State Service, the User Profile Service and its permissions are correctly configured after upgrade, and any administrator‑deployed InfoPath templates and data connections are re‑imported and updated in the new farm. Then retest the form to confirm that GetUserProfileByName calls succeed.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Michelle-N 20,735 Reputation points Microsoft External Staff Moderator
    2026-06-17T14:47:11.6166667+00:00

    Hi @Zayan Zaki

    Based on the information you provided, I understand that you have successfully completed a database in-place upgrade from SharePoint Server 2016 to SharePoint Server Subscription Edition (SE). While the content upgrade itself completed without issues, your legacy InfoPath 2010 forms that rely on SOAP web services are now failing. Specifically, when a form attempts to load and call the GetUserProfileByName web service to retrieve user data, it throws a 500 Internal Server Error due to an "Attempted to perform an unauthorized operation" exception.

    After reviewing similar upgrade scenarios, this error occurs because the security context under which the InfoPath Forms Services engine executes SOAP calls is being blocked by the User Profile Service Application (UPA) in SharePoint SE, which enforces stricter security boundaries than SharePoint 2016.

    To resolve this authentication/authorization bottleneck, please go through the following troubleshooting and configuration steps:

    -InfoPath forms rely heavily on the State Service to maintain session data during SOAP calls. Ensure it is correctly provisioned and associated with your web application.

    Open the SharePoint Management Shell and verify the State Service exists:

    Get-SPStateServiceApplication Get-SPWebApplication | Get-SPServiceApplicationProxyGroup | Select *

    Go to Central Administration and ensure both the State Service Proxy and the User Profile Service Application Proxy are checked.

    -The web application pool identity running your InfoPath forms (or your claims-based user account) lacks the explicit backend permission to query the UPA via SOAP.

    1. Go to Central Administration > Application Management > Manage Service Applications.
    2. Select the row for your User Profile Service Application (do not click the link, just highlight the row).
    3. Click the Permissions button in the top ribbon.
    4. Add the Application Pool account of your SharePoint Web Application.
    5. Check the box for Full Control (or at least Retrieve User Profile Data for InfoPath Forms Services) and click OK.
    6. Next, click the Administrators button in the ribbon and ensure that same app pool account has appropriate administrative connection rights.

    Because SharePoint SE relies heavily on claims-based authentication, legacy InfoPath SOAP queries using standard NTLM/Kerberos endpoints can fail if the server denies local loopback calls. Try converting the data connection within the InfoPath designer to use a Universal Data Connection (UDCX) file stored in a trusted data connection library, and configure it to use explicit authentication if necessary.

    As you manage this migration to SharePoint Subscription Edition, please keep in mind a critical support timeline: InfoPath Forms Services support is officially ending on July 14, 2026. Beyond this rapidly approaching date, Microsoft will no longer provide security patches, bug fixes, or technical support for InfoPath rendering components. While your forms might continue to function temporarily after this date, relying on legacy InfoPath code tied to deprecated SOAP endpoints poses a high operational and security risk.

    Moving forward, I highly recommend using this migration period to plan a transition from InfoPath to Power Apps (if connecting via hybrid environments). These modern frameworks natively query user profile properties via modern REST APIs or Microsoft Graph, completely bypassing legacy SOAP vulnerabilities.

    Please apply the UPA application pool permissions and let me know if the forms successfully load the user profile data!

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    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.

    Was this answer helpful?

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.