UA: Error 457: "This key is already associated with an element in this collection" Importing Log File

ID: Q156690

The information in this article applies to:

Microsoft Site Server version 2.0, used with:
- Microsoft Usage Analyst for Access, version 2.0
- Microsoft Usage Analyst for SQL Server, version 2.0
Microsoft Site Server, Enterprise Edition, version 2.0, used with:
- Microsoft Usage Analyst for Access, version 2.0
- Microsoft Usage Analyst for SQL Server, version 2.0

SYMPTOMS

When you try to import the log file, you may get the following error 457 message:

This key is already associated with an element in this collection.

For example, you configure a Microsoft Internet Information Server (IIS) standard log data source, two servers with unique IP addresses, and set up two sites in the Server Manager. You then configure the query strings tab for each to use the exact same query string values at Metadata. After you start to import the log file, the error occurs.

CAUSE

The database does not allow two different sites to have the exact same Metadata values. Each value that is used on the Query String tab must be unique to the database.

WORKAROUND

To avoid the problem, use either of the following methods:

Modify the Query String tab for each site so that the information used as Metadata is not identical for the two sites.

Use the Metadata module to manually edit the query string values that are imported.

A fix is available at the following locations:

For Usage Analyst Developer package for Access:

ftp://ftp.microsoft.com/bussys/sitesrv/sitesrv-public/fixes/usa/usage/import-fix/uadeva

For Usage Analyst Developer package for SQL:

ftp://ftp.microsoft.com/bussys/sitesrv/sitesrv-public/fixes/usa/usage/import-fix/uadevs

For Usage Analyst Standard package for Access:

ftp://ftp.microsoft.com/bussys/sitesrv/sitesrv-public/fixes/usa/usage/import-fix/uastda

For Usage Analyst Standard package for SQL:

ftp://ftp.microsoft.com/bussys/sitesrv/sitesrv-public/fixes/usa/usage/import-fix/uastds

STATUS

Microsoft has confirmed this to be a problem in Microsoft Site Server version 2.0.

This problem has been corrected in the latest U.S. Service Pack for Microsoft Site Server version 2.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: duplicate query

Keywords : kberrmsg kbbug2.00
Version : winnt:2.0; :2.0
Platform : winnt
Issue type : kbbug