"Distressing, another business relationship from your organization is already signed in on this computer" in Office 2013

  • Article
  • 3 minutes to read
  • Applies to:
    Role 365, Part 2013

Symptoms

When you try to sign in to an Office 2013 app past using your Office 365 user ID and password, yous receive the following error message:

Sorry, some other business relationship from your organization is already signed in on this figurer.

Cause

This beliefs is expected. It occurs if another account is already signed in to Part 2013 past using a different Office 365 user account within the same organization.

Resolution

Sign out of the first account that signed in, so restart that computer. If this solution does not resolve the issue, effort the workaround below.

Workaround

Of import

Follow the steps in this department advisedly. Serious bug might occur if you lot modify the registry incorrectly. Earlier you modify it, back up the registry for restoration in example problems occur.

Annotation

This workaround may crusade some account settings to be lost.

To piece of work around this behavior, remove the existing user business relationship and all continued services from your Role 2013 contour, and then clear cached credentials that may be on the computer:

Footstep 1: Sign out of Office and and then sign back in

Sign out of Microsoft Office using any Office product: Discussion, Excel, PowerPoint, Outlook, etc.

  1. Select File, and then select Business relationship.
  2. Select Sign out.
  3. Close the Office product and so restart it.
  4. Select File, and then select Account.
  5. Select Sign in and use your credentials to sign back in.

Pace 2: Remove the user account from your Role 2013 profile

  1. In the upper-right corner of an Role 2013 app (Word, Excel, PowerPoint), select your name, and then select Switch Business relationship.

  2. On the Accounts screen, select Sign out.

    Sign out on the Accounts page.

  3. Locate the account that you want to remove, and then select Sign out.

Stride 3: Remove continued services from your Office 2013 profile

  1. Get to File, and so select Account.

  2. Under Connected Services, remove all the services for the existing business relationship.

    Screenshot of removing all the services for the existing account under Connected Services.

Step 4: Articulate buried credentials on the computer

  1. Edit the registry to remove cached credentials:

    1. Select Start, select Run, type regedit, and then select OK.

    2. In Registry Editor, locate the following registry subkey:

      HKEY_CURRENT_USER\Software\Microsoft\Role\15.0\Mutual\Identity\Identities

    3. Select the Office account that you want to delete, and then select Delete.

    4. In the Identity subkey, locate Profiles, correct-click the aforementioned Part account that you lot located in Step i of this procedure, then select Delete.

    5. Select File and and so Exit Registry Editor.

  2. Remove the cached credentials in Credentials Manager:

    1. Select Start, then Windows System, then open up the Control Panel and select Credential Manager.

      Notation

      You may have to use the search field in the Command Panel to find the Credential Manager.

    2. Under the Windows Credentials tab, locate the business relationship that you want to remove and then select Remove.

      Note

      In Windows 7, this is listed as Generic Credentials.

      Remove Windows Credentials

  3. Log off, and then log dorsum in to the estimator.

More information

For more than data, see Recommendations on resolving common sign-in issues.

In Office 2013 apps, you tin admission Office 365 content in SharePoint Online past providing your Part 365 user ID and password. If you accept multiple Part 365 user IDs from different organizations, you lot can access content from the SharePoint Online deployments of each organization.

However, Office 2013 only supports one Office 365 user sign-in from each tenant or organization per session.

Office 2013 makes a best effort to preclude a second user from signing in when another user from the same system is already signed in. Withal, at that place may exist cases in which this scenario is not detected and the Office 2013 user interface may evidence that another user is successfully signed in. In this case, the second user cannot access his or her ain content. All Role 365 content that he or she tries to open will be performed by using the commencement user's credentials.

Exist aware that Part 2013 respects the permissions of all documents and SharePoint Online libraries. That is, if the first user doesn't take access to a document that the second user has access to, and the second user (who believes they are signed in) attempts to open that document, the certificate will not open considering Office tries to open up the document every bit the offset user.

To gear up this scenario, the signed-in user should sign out of Office 2013, and then restart his or her computer. Doing this makes sure that a clean land is present when the other user tries to sign in over again.

If restarting the computer does not resolve the issue, then adjusting the registry is the recommended solution.

Notwithstanding need help? Get to Microsoft Community.