Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SSIS package may encounter an error 0xC0014100 on a computer that is running Windows Server 2008 or Windows Vista

SSIS package may encounter an error 0xC0014100 on a computer that is running Windows Server 2008 or Windows Vista

View products that this article applies to.

Symptoms

Consider the following scenario:
  • In your environment, you execute multiple Microsoft SQL Server Integration Services (SSIS) packages at the same time.
  • Object names in these SSIS packages use localized characters, for example characters from fareast languages such as Chinese, Japanese, Korean, Thai, etc. This may include names of various objects such as Tasks, Dataflow Components, Variables, or other objects used within the package design. 
  • SSIS package is run on a computer that is running Windows Vista or Windows Server 2008.
In this scenario, the SSIS packages may intermittently fail with one of the following error messages:
Error 1:
HResult = 0xC0014100 
Integer Error = -1073659648
Symbolic Constant = DTS_E_NAMEALREADYADDED 
Text Description = The object cannot be added because another object with the same name already exists in the collection. Use a different name to resolve this error.

Error 2:
HResult = 0xC0047008
Integer Error = -1073451000
Symbolic Constant = DTS_E_DUPLICATENAMESINCOLLECTION
Text Description = The package contains two objects with the duplicate name of "%1" and "%2".


↑ Back to the top

Cause

The problem occurs because the function SSIS internally uses to compare locale specific strings (LCMapString) has a bug that causes two different strings to be classified as the same. When you use localized characters for object names, those may be reported incorrectly as being identical by the LCMapString function, which causes SSIS to report the errors discussed in the Symptoms section.

↑ Back to the top

Resolution

You can resolve the problem by applying the hotfix described in the following article:
  • 971795  Applications may stop responding or may encounter other function failures if these applications call the LCMapString function on a computer that is running Windows Server 2008 or Windows Vista


↑ Back to the top

Workaround

If you are unable to apply the fix documented in the Resolution section, you can workaround the problem either by renaming the tasks to just use ASCII based characters (for example  "Task1") or by reducing the number of SSIS packages that you execute in parallel.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2446955
Revision : 3
Created on : 11/20/2019
Published on : 11/20/2019
Exists online : False
Views : 514