"Profile missing" error appears after unpacking a site
This error applies to the Supplier Solution Site. It occurs when the Profiles service cannot locate a user in Microsoft Active Directory.
"The user name might not be included in the following Active Directory containers: OU=MSCS_40_Root and OU=site_name."
Solution
The recommended solution depends on when the error message appears.
Log on to the Supplier site by using a name that was created using Microsoft Commerce Server 2000 run-time components.
If you receive this error just after unpacking the site
In this case, the error occurs because the site uses the Windows Integrated Authentication method by default, and the user attempts to use a login name not created using Commerce Server Business Desk or the Profiles resource.
Use Business Desk to create a user account, and then log onto the server as the newly created user. You should then be able to access the Supplier site.
Another possible solution is to enable Basic Authentication (in Internet Information Services (IIS) 5.0) with the Supplier site. Log on to the site. Make sure you use one of the following formats when typing the user name:
domain_name\user_name
username@fully_qualified_domain_name
If you receive this error (or a similar error) while using AuthFilter with the Windows Authentication mode
Determine whether the GetProfileByKey method on the Login page is functioning properly. If this method is producing an unauthorized authentication mode error message, then an anonymous user does not have permission to get or read the user profile. For more information, see GetProfileByKey.
In this case, make sure the user has a Windows user account that has permissions to get and read the user profile properties from Active Directory.
Another solution is to make sure that you can access the site without the AuthFilter ISAPI filter.
To access the site without AuthFilter
Use Internet Services Manager to remove the filter.
Set the security mode to Basic Authentication only on the Supplier site. Then reset IIS.
Try accessing the site with the correct credentials.
If this does not work, make sure you created the user account with Business Desk, and make sure that is enabled.