Article ID: 953145 - Last Review: August 13, 2008 - Revision: 1.0 Error message when you try to create a Shared Services Provider (SSP) in Office SharePoint Server 2007: "An error occurred while translating user name "<Domain>@<Name>\User1" to a Windows account name - (DS_NAME_ERROR_NOT_FOUND)"SYMPTOMSYou have an account whose NetBIOS domain name contains an at
sign (@). For example, the account is
Domain@Name\User1. You
use this account as the service account. If you try to create a Shared Services
Provider (SSP) in Office SharePoint Server 2007, you may receive the following
error message: An error occurred while translating user
name "Domain@Name\User1"
to a Windows account name - (DS_NAME_ERROR_NOT_FOUND) RESOLUTIONTo
resolve this issue, install the hotfix package that is described in Microsoft
Knowledge Base article 953471.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
953471
(http://support.microsoft.com/kb/953471/
)
Description of the SharePoint Server 2007 post-2007 Microsoft Office servers Service Pack 1 hotfix package: June 5, 2008
Important This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows After you apply the hotfix package, you can add a
registry key to switch to an alternative method of converting an account name
to the Windows NT 4.0
format. This alternative method will use LookupAccountName followed by
LookupAccountSid. To enable this hotfix, follow these steps:
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
| Article Translations
|

Back to the top
