1003001 Duplicate Members From Same Dimension On Data Record, number Records Completed

Possible Problems
Analytic Services encountered more than one member from a dimension in a single record. Analytic Services will not load this record and will skip to the next record.

Possible Solutions
Make sure that the data source is valid.

Does each record contain only one member name for each dimension? For example, in the Time dimension you can have only the January member in a single record, not January and February. If you have columns containing duplicate members in a record, ignore those columns.
Is each member name mapped to the correct dimension? For example, in the Sample Basic database the January member should be mapped to the Time dimension and not to the Market dimension.
Are duplicate member or alias names under different dimensions? Member and alias names must be unique. For example, you cannot have a January member in both the Time dimension and the Market dimension. If you do have members or aliases with the same name in different dimensions, consider adding a prefix or suffix to the members or aliases in one dimension to make them unique.
Are ranges set up correctly?
Are all members that might contain numbers (such as "100") enclosed in quotation marks in the data source?
Are two members from the same dimension on one line in the data source?
If you are using a rules file, make sure that the rules file is valid.

Are extra member names ignored in the rules file?
Do you need to move columns around to ensure that each member is connected to the correct dimension?
Can you validate the rules file?
If you are using ESSCMD, make sure that the ESSCMD syntax is valid.

Check the error log in the ESSCMD script to determine where the duplicate member exists.
Are the parameters enclosed in quotation marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2 "ACTUALS" "Y";
Are the parameters correct?
Do the files you are loading exist in the correct locations?
Can you run the data load using Administration Services?
If you are using Integration Services, try the following steps:

If the duplicate member is a shared member, make sure that it is tagged as a shared member.
If you have members with the same names in different dimensions, be sure to add prefixes or suffixes to the member names.
Map all members to the correct dimension.
Make sure that you are using the correct Intersolv drivers.
Launch Analytic Services Integration Services using a non-default value for the -B parameter.
In Hyperion OLAP Builder, select the Delete All Members First option.