Article ID: 112243, created on Sep 9, 2011, last review on May 10, 2014

  • Applies to:
  • Operations Automation 5.4
  • Business Automation 5.5

Symptoms

The background POA task Set SPS info for user fails with the error message User does not exist.

More detailed diagnostics of the problem are provided below:

Provisioning request failed. Unknown error 0x80131509
[<response><errorContext description="User does not exist: HOSTING\test.user"
code="0x80131509" executeSeqNo="3"><errorSource namespace="Error Provider"
procedure="SetError"/><errorSource namespace="Error Provider Ex"
procedure="RethrowError"/></errorContext></response>]

Cause

The problem user from the failed task has been manually unassigned from the SharePoint site.

Resolution

Step 1: Make sure the user is not assigned to the SharePoint site using the STSADM.EXE utility:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o enumusers -url http://example.com
<Users Count="1">
  <User>
    <Login>HOSTING\user1</Login>
    <Email>user1@example.com</Email>
    <Name>User 1</Name>
  </User>
</Users>

Replace http://example.com in the command above with the actual URL of the problem SharePoint site.

If you do not see the problem user in the output of the command above, it means that the user is not assigned to the SharePoint site.

Step 2: Assign the user to the SharePoint site manually:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o adduser -url http://example.com -userlogin HOSTING\test.user -useremail test.user@example.com -role Reader -username "Test User"

Note: The provided commands have to be run on the SharePoint server for which the failed task was scheduled.

Search Words

task failed

User does not exist

SharePoint user

Task failing

stuck deleting sharepoint user

Provisioning request failed. Unknown error 0x80131509 [<response><errorContext description="

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF