????

Your IP : 18.222.107.172

Current Path : C:/Program Files/Microsoft SQL Server/150/DTS/Binn/Resources/1033/

Current File : C:/Program Files/Microsoft SQL Server/150/DTS/Binn/Resources/1033/dtsmsg150.rll

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$�����ծ��ծ��ծ���Q��ծ���9��ծ������ծ�Rich�ծ�PEd�
��]�" �@� `A ��8?.rdatap@@.rsrc � � @@
��]
TGCTL.rdataT.rdata$zzzdbg �.rsrc$01� 0�.rsrc$02(�@�X�p����� � � �� 0� �|��}��LPP
�
�h@ `
@@�0@0@� 5@5@�$Q@Q@�%Q@Q@�'`@`@D(%`@(`@*6`@9`@4+@`@I`@�.Q`@T`@�5�@�@d7�@�@,8N�@N�@|8a�@b�@@9��@��@�9�@�@p:#�@#�@�:&�@&�@8;Q�@R�@�;X�@X�@@<b�@b�@�<f�@f�@�<p�@p�@4=t�@t�@|=x�@x�@�=��@��@8>��@��@�>��@��@?��@��@h?��@��@�?�@�@@�@�@x@�@�@�@�@�@DA�@�@�A0@0@B'p@'p@D�@�@xD�@��@�K1@1@�Lm @m @d^� @� @�_'� @(� @``�� @�� @�cڐ @� @�d� @� @�o"� @"� @t@� @@� @Pt,� @,� @�t6�7��v�����x���y � ��z# �# �ȇ% �& �H�( �( ���* �* �0�2 �5 �ĎQ �R ���T �U �ēW �Z ���X@�X@���q�q�h�r�r���������������������������������/��/�������ȯ+��+����V��V��t� � ����������d��d��h�������ĶƑ�ʑ��z��z��t�������Ⱥ������<�����p�"��"���1��3��t�9��9����C��C���G��G��@�V��V����`��`��,�d��d����h��h����r��r��P�v��v����������<���������������<������������������������������������������l�����������0�p�p�|�4p�4p�P�ip�ip���op�op���vp�vp����p��p�p��p��p�D��p��p����p��p�,��p��p����p��p�h�����������������p� � �l�+ �+ ���c �c ��f �f ��� �� ���
@ �
@ ����p ��p ���� �� ���� �� ���� �� ���� �� ���� �� ��!� �!� ���+� �+� ���-� �.� ���P� �S� ���u� �v� �p~� �~� �<�� ��� �8�� ��� ���� ��� �l� �� �T�� ��� ��� ��� �h� �� �\� �� �@!� �!� �4W� �W� �� 2�6�T!�`��`� &E��E��0'�����('��'���(���)��,�
�t-���1�� :���<�.��?���O� �XS
��tb
�
��d � ��d � �dg! �$ ��g) �) �j7 �7 ��jI �I �mP �P �n0�0��n@�W@��pY@�e@�\�A�A�h�A�A���A�A���P�P�L�P�P���Q�Q�l�`�`�� `�'`�,)`�5`��:`�:`��I`�M`�0P`�P`���`��`�t�`��`�`p�
p��!p�p�p*r�r�,1�����2�����3������l4����h7�����9����@:�����=����B����C����DF�����J�� ��HK�����M!��*��lU,��3��`6��6���g8��8�� h:��:���h@��A���i������Dl������(r��
��l{ �� ��H�"��%��܃'��)��,�0��4��,�]��]����� �� ��� �� ��� �� �H�� �� ���!�!��5!�5!�L�A�A���A�A��A�
A�P�����ܧ��T����V��`����b��c�� �e��s����u���������ő��ˑ�ˑ�p͑���,����� ���f��th��y��HO{������V������La�������b�������q����dr����<t ��!����$��%����'��'����0��1���4��4����7��8���@��@���B��B��T�D��F����I��I��D�P��P��̈S��W��,�Y��Y����`��a���c��e���g��i��\�q��s��ďu��w����y��y�����������������ܔ��������������H���������������P�����ԛ����$��� ��؞����������L����������������\�����d�!��!����&��&���(��)����1��1����C��F������ � �د@�H���p�p���p�p���p�p�`�p�&p���(p�3p�P�5p�;p� �?p�Ap���Cp�Cp�X�Fp�Qp�@�Sp�Sp���Vp�Wp�H�Zp�\p��^p�hp��jp��p���p��p�p)�p��p�8R�p��p�DT�p��p��k�p��p��w�p��p�\��p�q��r�r����� �������������������Ա��"��������\�0��h����������(�������������<������� Ӑ�Ր��ݐ��������$�������O��O���%�����&�����'7�7��( � ��) � �D, � �- � �/ � �L/ � ��1 �( ��7, �- �>0 �1 ��>: �; ��?> �E ��@G �M ��ES �S ��JU �U � KX �X ��KZ �b �Ld �e ��Ug �l �pXn �w ��^y �� �xg� �� �$u� �� ���� �� ���� �� � �� �� ��� �� ��� �� �H�� �� �8�� �! �h�1 �1 ���@ �@ �l�@ �@ ���@ �@ ��
@ �@ ��@ �@ ���@ � @ ���#@ �(@ �P�*@ �-@ �@�p �p ���
p �p ���p �p ���p �p ��� �� ��� �
� ��
� �� �\� �� �� �!� �h#� �@� �l� �� �D3� �� �|4
� �� ��<� �#� ��C&� �&� ��F(� �.� �G0� �@� �(KB� �c� �lWe� �g� �Pns� �y� �`p�� ��� �4t�� ��� ��|�� ��� ��}�� �� �t~ � �� ��� �� ���� � � ���"� �&� �X�)� �*� �ȶ,� �,� �ȷ/� �O� �x�T� �t� �(�w� �}� ���� ��� ����� ��� ���� ��� �HF� �I� �K� �[� ��]� �]� ��� �� �(� �� �� �� �X� �� ��"� �%� �`)� �/� ��!>� �?� �8-i� �}� �/� ��� �:�� ��� ��?�� ��� ��?�� ��� ��A�� ��� �8D�� ��� ��M�� �Ő � Oɐ �ː �0Y͐ �͐ ��\ϐ �Ґ �]֐ �ِ �\_ܐ �ܐ �|e� �� � f� �� ��g� �� ��i�� ��� �n�� ��� �t�� ��� ��y�� ��� �ȁ� �� �4�� �� ���� �� �P�� �� ��*� �*� ��@� �E� �<�L� �M� ���P� �\� �H��ȴ��
����ܵ(Service Control

@Running Package Management

pStarting Microsoft SSIS Service.%nServer version %1

pMicrosoft SSIS Service started.%nServer version %1

�Stopping Microsoft SSIS Service.%n%nStop all running packages on exit: %1

pMicrosoft SSIS Service stopped.%nServer version %1

pMicrosoft SSIS Service failed to start.%nError: %1

lError stopping Microsoft SSIS Service.%nError: %1

�Microsoft SSIS Service configuration file does not exist.%nLoading with default settings.

Microsoft SSIS Service configuration file is incorrect.%nError reading config file: %1%n%nLoading server with default settings.

Microsoft SSIS Service: %nRegistry setting specifying configuration file does not exist. %nAttempting to load default config file.

HMicrosoft SSIS Service: stopping running package.%nPackage instance ID: %1%nPackage ID: %2%nPackage name: %3%nPackage description: %4%nPackage started by: %5.

�The table "%1!s!" has changed. New columns might have been added to the table.

0The value is NULL.

The string value was truncated. The buffer received a string that was too long for the column, and the string was truncated by the buffer.

@A truncation occurred during evaluation of the expression. The truncation occurred during evaluation, which may include any point in an intermediate step.

tStarting distributed transaction for this container.

�Committing distributed transaction started by this container.

dAborting the current distributed transaction.

<Package "%1!s!" started.

XPackage "%1!s!" finished successfully.

PPackage "%1!s!" has been cancelled.

8Package "%1!s!" failed.

@Module %1 cannot load DLL %2 to call entry point %3 because of error %4. The product requires that DLL to run, but the DLL could not be found on the path.

TModule %1 loaded DLL %2, but cannot find entry point %3 because of error %4. The named DLL could not be found on the path, and the product requires that DLL to run.

\Mutex "%1!s!" was successfully acquired.

\Mutex "%1!s!" was successfully released.

XMutex "%1!s!" was successfully created.

xDebug dump files will be generated for any error event.

�Debug dump files will be generated for the following event codes: "%1!s!"

�Event code, 0x%1!8.8X!, triggered generation of debug dump files in the folder "%2!s!".

dCreating SSIS information dump file "%1!s!".

XDebug dump files successfully created.

�The package format was migrated from version %1!d! to version %2!d!. It must be saved to retain migration changes.

�The scripts in the package were migrated. The package must be saved to retain migration changes.

8Receiving file "%1!s!".

4Sending file "%1!s!".

DFile "%1!s!" already exists.

�Cannot get extra error information due to an internal error.

lThe attempt to delete file "%1!s!" failed. This may occur when the file does not exist, the file name was spelled incorrectly, or you do not have permissions to delete the file.

�The package is attempting to configure from a registry entry using the registry key "%1!s!".

�The package is attempting to configure from the environment variable "%1!s!".

�The package is attempting to configure from the .ini file "%1!s!".

�The package is attempting to configure from SQL Server using the configuration string "%1!s!".

�The package is attempting to configure from the XML file "%1!s!".

�The package is attempting to configure from the parent variable "%1!s!".

�Attempting an upgrade of SSIS from version "%1!s!" to version "%2!s!". The package is attempting to upgrade the runtime.

�Attempting to upgrade "%1!s!". The package is attempting to upgrade an extensible object.

�The package will be saving checkpoints to file "%1!s!" during execution. The package is configured to save checkpoints.

�The package restarted from checkpoint file "%1!s!". The package was configured to restart from checkpoint.

�Checkpoint file "%1!s!" was updated to record completion of this container.

�Checkpoint file "%1!s!" was deleted after successful completion of the package.

\Checkpoint file "%1!s!" update starting.

�Based on the system configuration, the maximum concurrent executables are set to %1!d!.

lMaximum concurrent executables are set to %1!d!.

HBeginning of package execution.

<End of package execution.

�The provider name for the connection manager "%1!s!" has been changed from "%2!s!" to "%3!s!".

PSucceeded in upgrading the package.

�Attempting to downgrade "%1!s!". The package is attempting to downgrade an extensible object.

HDirectory "%1!s!" was deleted.

XFile or directory "%1!s!" was deleted.

�Overwriting the database "%1!s!" on the destination server "%2!s!".

"%1!s!".

�Skipping error message "%1!s!" since it already exists on the destination server.

\"%1!s!" Error Messages were transferred.

hThe task transferred "%1!s!" Stored Procedures.

DTransferred "%1!s!" objects.

`There are no Stored Procedures to transfer.

HThere are no Rules to transfer.

LThere are no Tables to transfer.

HThere are no Views to transfer.

lThere are no User Defined Functions to transfer.

PThere are no Defaults to transfer.

lThere are no User Defined Data Types to transfer.

dThere are no Partition Functions to transfer.

`There are no Partition Schemes to transfer.

LThere are no Schemas to transfer.

XThere are no SqlAssemblies to transfer.

lThere are no User Defined Aggregates to transfer.

dThere are no User Defined Types to transfer.

hThere are no XmlSchemaCollections to transfer.

LThere are no Logins to transfer.

HThere are no Users to transfer.

<Truncating table "%1!s!"

XPrepare for Execute phase is beginning.

HPre-Execute phase is beginning.

LPost Execute phase is beginning.

@Cleanup phase is beginning.

HValidation phase is beginning.

@"%1!s!" wrote %2!ld! rows.

@Execute phase is beginning.

pA new file %1!s! has been created for the data tap.

|The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. %1!d! buffers were considered and %2!d! were locked. Either not enough memory is available to the pipeline because not enough is installed, other processes are using it, or too many buffers are locked.

�The buffer manager failed a memory allocation call for %3!d! bytes, but was unable to swap out any buffers to relieve memory pressure. %1!d! buffers were considered and %2!d! were locked. Either not enough memory is available to the pipeline because not enough are installed, other processes were using it, or too many buffers are locked.

0The buffer manager has allocated %1!d! bytes, even though the memory pressure has been detected and repeated attempts to swap buffers have failed.

�Buffer manager allocated %1!d! megabyte(s) in %2!d! physical buffer(s).

�Component "%1!s!" (%2!d!) owns %3!d! megabyte(s) physical buffer.

D%1!s! has cached %2!d! rows.

X%1!s! has cached a total of %2!d! rows.

0 Event Name: %1%r Message: %9%r Operator: %2%r Source Name: %3%r Source ID: %4%r Execution ID: %5%r Start Time: %6%r End Time: %7%r Data Code: %8

�The raw source adapter opened a file, but the file contains no columns. The adapter will not produce data. This could indicate a damaged file, or that there are zero columns and, therefore, no data.

dAn OLE DB informational message is available.

Fuzzy match performance can be improved if the exact join FuzzyComparisonFlags on the input column "%1!s!" are set to match with the default SQL collation for reference table column "%2!s!". It is also necessary that no fold flags are set in FuzzyComparisonFlagsEx.

Fuzzy match performance can be improved if an index is created upon the reference table across all of the specified exact match columns.

`Error and truncation dispositions were not reviewed. Make sure this component is configured to redirect rows to error outputs, if you wish to further transform those rows.

,The Aggregate transformation has encountered %1!d! key combinations. It has to re-hash data because the number of key combinations is more than expected. The component can be configured to avoid data re-hash by adjusting the Keys, KeyScale, and AutoExtendFactor properties.

�The Aggregate transformation has encountered %1!d! distinct values while performing a "count distinct" aggregation on "%2!s!". The transformation will re-hash data because the number of distinct values is more than expected. The component can be configured to avoid data re-hash by adjusting the CountDistinctKeys, CountDistinctKeyScale, and AutoExtendFactor properties.

`The processing of file "%1!s!" has started.

\The processing of file "%1!s!" has ended.

�The total number of data rows processed for file "%1!s!" is %2!I64d!.

�The final commit for the data insertion in "%1!s!" has started.

�The final commit for the data insertion in "%1!s!" has ended.

�%1!u! rows are added to the cache. The system is processing the rows.

The %1!s! processed %2!u! rows in the cache. The processing time was %3!s! seconds. The cache used %4!I64u! bytes of memory.

�The %1!s! failed to process the rows in the cache. The processing time was %2!s! second(s).

�The %1!s! succeeded in preparing the cache. The preparation time was %2!s! seconds.

�The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference database, and performed %4!I64u! lookups using partial cache.

4The %1!s! has performed the following operations: processed %2!I64u! rows, issued %3!I64u! database commands to the reference database, performed %4!I64u! lookups using partial cache and %5!I64u! lookups using the cache for rows with no matching entries in the initial lookup.

hThe %1!s! is writing the cache to file "%2!s!".

lThe %1!s! has written the cache to file "%2!s!".

DUn-matched Pivot Key Values:

xThe number of unique rows added to the cache is %1!u!.

The Maximum insert commit size property of the OLE DB destination "%1!s!" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

�There are %1!lu! days left in the evaluation. When it expires, packages will not be able to be executed.

�Integration Services evaluation period has expired. The package can only be executed in debug mode.

The log provider "%1!s!" cannot log messages on the installed edition of SQL Server. The log provider requires %2!s! or higher.

Warning(s) raised. There should be more specific warnings preceding this one that explain the specifics of the warning(s).

�Cannot create an XML document object instance. Verify that MSXML is installed and registered correctly.

�Cannot load the XML configuration file. The XML configuration file may be malformed or not valid.

�The configuration file name "%1" is not valid. Check the configuration file name.

The configuration file loaded, but is not valid. The file is not formatted correctly, may be missing an element, or may be damaged.

�The configuration file "%1!s!" cannot be found. Check the directory and file name.

`Configuration registry key "%1!s!" was not found. A configuration entry specifies a registry key that is not available. Check the registry to ensure that the key is there.

The configuration type in one of the configuration entries was not valid. Valid types are listed in the DTSConfigurationType enumeration.

TThe package path referenced an object that cannot be found: "%1!s!". This occurs when an attempt is made to resolve a package path to an object that cannot be found.

8The configuration entry, "%1!s!", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" to the package path.

DThe configuration entry "%1!s!" had an incorrect format. This can occur because of a missing delimiter or formatting errors, like an invalid array delimiter.

�Configuration from a parent variable "%1!s!" did not occur because there was no parent variable collection.

hFailure importing configuration file: "%1!s!".

�Configuration from a parent variable "%1!s!" did not occur because there was no parent variable. Error code: 0x%2!8.8X!.

�The configuration file was empty and contained no configuration entries.

�The configuration type for configuration "%1!s!" is not valid. This may occur when an attempt is made to set the type property of a configuration object to an invalid configuration type.

The configuration type for the registry configuration was not found in key "%1!s!". Add a value called ConfigType to the registry key and give it a string value of "Variable", "Property", "ConnectionManager", "LoggingProvider", or "ForEachEnumerator".

@The configuration value for the registry configuration was not found in key "%1!s!". Add a value called Value to the registry key of type DWORD or String.

�Process configuration failed to set the destination at the package path of "%1!s!". This occurs when attempting to set the destination property or variable fails. Check the destination property or variable.

�Process configuration failed to load the project connection managers.

�Failed to retrieve value from the .ini file. The ConfiguredValue section is either empty, or does not exist: "%1!s!".

�Failed to retrieve value from the .ini file. The ConfiguredType section is either empty, or does not exist: "%1!s!".

�Failed to retrieve value from the .ini file. The PackagePath section is either empty, or does not exist: "%1!s!".

�Failed to retrieve value from the .ini file. The ConfiguredValueType section is either empty, or does not exist: "%1!s!".

�Configuration from SQL Server was not successfully imported: "%1!s!".

�The .ini configuration file is not valid due to empty or missing fields.

@Table "%1!s!" does not have any records for configuration. This occurs when configuring from a SQL Server table that has no records for the configuration.

�Error using same name for different custom events. The custom event "%1!s!" was defined differently by different children of this container. There may be an error when executing the event handler.

�The configuration attempted to change a read-only variable. The variable is at the package path "%1".

Calling ProcessConfiguration on the package failed. The configuration attempted to change the property at the package path "%1".

�Failed to load at least one of the configuration entries for the package. Check configuration entries for "%1!s!" and previous warnings to see descriptions of which configuration failed.

�The configuration entry "%1!s!" in the configuration file was not valid, or failed to configure the variable. The name indicates which entry failed. In some cases, the name will not be available.

�This task or container has failed, but because FailPackageOnFailure property is FALSE, the package will continue. This warning is posted when the SaveCheckpoints property of the package is set to TRUE and the task or container fails.

0The path is empty.

The data flow task identification %1!s! was not found during execution. The specified data tap file %2!s! for path %3!s! was not generated.

�SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (%1!d!) reached the maximum allowed (%2!d!); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

�The configuration environment variable was not found. The environment variable was: "%1!s!". This occurs when a package specifies an environment variable for a configuration setting but it cannot be found. Check the configurations collection in the package and verify that the specified environment variable is available and valid.

�The sensitive data in the project cannot be decrypted because a password has not been specified or is incorrect.

Unable to decrypt the sensitive data in the project. The project uses a protection level which encrypts sensitive data using a user key. You may not be the user who encrypted the project or you are not using the same computer that was used to save the project.

The version of provider name in configuration is older than the current version. The value in configuration will be used, which may cause connection issue. Property path: "%1!s!", current connection string: "%2!s!", connection string in configuration: "%3!s!".

�An exception occurred while reading the upgrade mapping files. The exception is "%1!s!".

�There is a duplicate mapping in file, "%1!s!". The tag is "%2!s!", and the key is "%3!s!".

The extension, "%1!s!", was implicitly upgraded to "%2!s!". Add a mapping for this extension to the UpgradeMappings directory.

(A mapping in the file, "%1!s!", is not valid. Values cannot be null or empty. The tag is "%2!s!", the key is "%3!s!", and the value is "%4!s!".

The DataTypeCompatibility property of ADO type connection manager "%1!s!" was set to 80 for backward compatibility reasons.

HThe For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern, or the specified directory was empty.

�Cannot resolve a package path to an object in the package "%1!s!". Verify that the package path is valid.

�The iteration expression is not an assignment expression: "%1!s!". This error usually occurs when the expression in the assignment expression on the ForLoop is not an assignment expression.

�The initialization expression is not an assignment expression: "%1!s!". This error usually occurs when the expression in the iterate expressions on the ForLoop is not an assignment expression.

�The executable "%1!s!" was pasted successfully. However a log provider that was associated with the executable was not found in the collection "LogProviders". The executable was pasted without log provider information.

�The "%1!s!" ProgID has been deprecated. The new ProgID for this component "%2!s!" should be used instead.

@Unsupported column - %1!s!

<Operation "%1!s!" failed.

xThe encryption algorithm "%1!s!" uses weak encryption.

\Task failed to execute operation "%1!s!".

TFile/Process "%1!s!" is not in path.

4The subject is empty.

�The address in the "To" line is malformed. It is either missing the "@" symbol or is not valid.

�The address in the "From" line is malformed. It is either missing the "@" symbol or is not valid.

�The address in the "Cc" line is malformed. It is either missing the "@" symbol or is not valid.

�The address in the "Bcc" line is malformed. It is either missing the "@" symbol or is not valid.

TThe two XML documents are different.

(DTD Validation will use the DTD file defined in the DOCTYPE line in the XML document. It will not use what is assigned to the property "%1!s!".

LTask failed to validate "%1!s!".

�The transfer action value was invalid. It is being set to copy.

�The transfer method value was invalid. It is being set to an online transfer.

|A problem occurred with the following messages: "%1!s!".

�The error message "%1!s!" already exists at destination server.

tThe job "%1!s!" already exists at destination server.

�Skipping the transfer of job "%1!s!" since it already exists at destination.

pOverwriting the job "%1!s!" at destination server.

�Persisted enumeration value of property "FailIfExists" was changed and rendered invalid. Resetting to default.

\Overwriting Login "%1!s!" at destination.

tOverwriting Stored Procedure "%1!s!" at destination.

xStored procedure "%1!s!" already exists at destination.

`Rule "%1!s!" already exists at destination.

dTable "%1!s!" already exists at destination.

`View "%1!s!" already exists at destination.

�User Defined Function "%1!s!" already exists at destination.

hDefault "%1!s!" already exists at destination.

�User Defined Data Type "%1!s!" already exists at destination.

|Partition Function "%1!s!" already exists at destination.

xPartition Scheme "%1!s!" already exists at destination.

dSchema "%1!s!" already exists at destination.

pSqlAssembly "%1!s!" already exists at destination.

�User Defined Aggregate "%1!s!" already exists at destination.

|User Defined Type "%1!s!" already exists at destination.

�XmlSchemaCollection "%1!s!" already exists at destination.

dThere are no elements specified to transfer.

dLogin "%1!s!" already exists at destination.

`User "%1!s!" already exists at destination.

LPossible data truncation on output parameter, "%1!d!". The task cannot determine the datetime type of the output parameter because the BypassPrepare property is set to True. If the output parameter type is datetime2, use a string variable instead of a datetime variable for the output parameter to prevent truncation. To allow the task to determine the output parameter type in the future, set BypassPrepare to False.

�The lineage IDs of the input columns cannot be validated because the execution trees contain cycles.

�The DataFlow task has no components. Add components or remove the task.

�The IsSorted property of %1!s! is set to TRUE, but all of its output columns' SortKeyPositions are set to zero.

�Source "%1!s!" (%2!d!) will not be read because none of its data ever becomes visible outside the Data Flow Task.

�The output column "%1!s!" (%2!d!) on output "%3!s!" (%4!d!) and component "%5!s!" (%6!d!) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.

�Component "%1!s!" (%2!d!) has been removed from the Data Flow task because its output is not used and its inputs either have no side effects or are not connected to outputs of other components. If the component is required, then the HasSideEffects property on at least one of its inputs should be set to true, or its output should be connected to something.

�Rows were given to a thread, but that thread has no work to do. The layout has a disconnected output. Running the pipeline with the RunInOptimizedMode property set to TRUE will be faster, and prevents this warning.

�The external columns for %1!s! are out of synchronization with the data source columns. %2!s!

�The column "%1!s!" needs to be added to the external columns.

lThe external column "%1!s!" needs to be updated.

|The %1!s! needs to be removed from the external columns.

�The result string for expression "%1!s!" may be truncated if it exceeds the maximum length of %2!d! characters. The expression could have a result value that exceeds the maximum size of a DT_WSTR.

�A call to the ProcessInput method for input %1!d! on %2!s! unexpectedly kept a reference to the buffer it was passed. The refcount on that buffer was %3!d! before the call, and %4!d! after the call returned.

tThe "%1!s!" on "%2!s!" has usage type READONLY, but is not referenced by an expression. Remove the column from the list of available input columns, or reference it in an expression.

Cannot find the "%1!s!" value for component %2!s!. The CurrentVersion value for the component cannot be located. This error occurs if the component has not set its registry information to contain a CurrentVersion value in the DTSInfo section. This message occurs during component development, or when the component is used in a package, if the component is not registered properly.

xThe buffer manager could not get a temporary file name.

The buffer manager could not create a temporary file on the path "%1!s!". The path will not be considered for temporary storage again.

�Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.

LThe package contains data flow components with multiple inputs. Run-time dependencies that exist among these components may increase memory usage and reduce performance. Consider removing the dependency chain for the following component IDs and output IDs: %1!hs!, to improve performance.

hThere is a partial row at the end of the file.

4The end of the data file was reached while reading header rows. Make sure the header row delimiter and the number of header rows to skip are correct.

The sort key position or comparison flag values for the "%1!s!" column in the appended data do not match the corresponding values for the"%1!s!" column in the existing file. Appending the data to the existing file will change the sort order information.

�Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "%1!s!" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

�The data is already sorted as specified so the transform can be removed.

@The %1!s! references an external data type that cannot be mapped to a Data Flow task data type. The Data Flow task data type DT_WSTR will be used instead.

,The expression "%1!s!" will always result in a truncation of data. The expression contains a static truncation (the truncation of a fixed value).

�The input column "%1!s!" with ID %2!d! at index %3!d! is unmapped. The lineage ID for the column is zero.

�The specified delimiters do not match the delimiters used to build the pre-existing match index "%1!s!". This error occurs when the delimiters used to tokenize fields do not match. This can have unknown effects on the matching behavior or results.

�The MaxOutputMatchesPerInput property on the Fuzzy Lookup transformation is zero. No results will be produced.

hThere were no valid input columns with JoinType column property set to Fuzzy. Performance on Exact joins may be improved by using the Lookup transform instead of FuzzyLookup.

|The reference column "%1!s!" may be a SQL timestamp column. When the fuzzy match index is built, and a copy of the reference table is made, all reference table timestamps will reflect the current state of the table at the time of the copy. Unexpected behavior may occur if the CopyReferenceTable is set to false.

�A table with the name '%1!s!' given for MatchIndexName already exists and DropExistingMatchIndex is set to FALSE. Transform execution will fail unless this table is dropped, a different name is specified, or DropExisitingMatchIndex is set to TRUE.

The length of input column '%1!s!' is not equal to the length of the reference column '%2!s!' that it is being matched against.

The code pages of the DT_STR source column "%1!s!" and the DT_STR dest column "%2!s!" do not match. This may cause unexpected results.

�There are more than 16 exact match joins, so performance may not be optimal. Reduce the number of exact match joins to improve performance. SQL Server has a limit of 16 columns per index, the inverted index will be used for all lookups.

HThe Exhaustive option requires that the entire reference be loaded into main memory. Since a memory limit has been specified for the MaxMemoryUsage property, it is possible that the entire reference table will not fit within this bound and that the match operation will fail at runtime.

�The cumulative lengths of the columns specified in the exact match joins exceeds the 900 byte limit for index keys. Fuzzy Lookup creates an index on the exact match columns to increase lookup performance and there is a possibility that creation of this index may fail and the lookup will fall back to an alternative, possibly slower, method of finding matches. If performance is a problem, try removing some exact match join columns or reduce the maximum lengths of variable length exact match columns.

�Failed to create an index for exact match columns. Reverting to alternative fuzzy lookup method.

�The following Fuzzy Grouping internal pipeline warning occurred with warning code 0x%1!8.8X!: "%2!s!".

@No maximum length was specified for the %1!s! with external data type %2!s!. The SSIS Data Flow Task data type "%3!s!" with a length of %4!d! will be used.

�The %1!s! references external data type %2!s!, which cannot be mapped to a SSIS Data Flow Task data type. The SSIS Data Flow Task data type DT_WSTR with a length of %3!d! will be used instead.

�The data type "%1!s!" found on column "%2!s!" is not supported for the %3!s!. This column will be converted to DT_NTEXT.

�No rows will be sent to error output(s). Configure error or truncation dispositions to redirect rows to the error output(s), or delete data flow transformations or destinations that are attached to the error output(s).

�Rows sent to the error output(s) will be lost. Add new data flow transformations or destinations to receive error rows, or reconfigure the component to stop redirecting rows to the error output(s).

�The column %1!s! in table %2!s! in the XML schema does not have a mapping in the external metadata columns.

�For the %1!s! with external data type %2!s!, the XML schema specified a maxLength constraint of %3!d!, which exceeds the maximum allowed column length of %4!d!. The SSIS Data Flow Task data type "%5!s!" with a length of %6!d! will be used.

�The %1!s! encountered duplicate reference key values when caching reference data. This error occurs in Full Cache mode only. Either remove the duplicate key values, or change the cache mode to PARTIAL or NO_CACHE.

0Truncation may occur due to inserting data from data flow column "%1!s!" with a length of %2!d! to database column "%3!s!" with a length of %4!d!.

0Truncation may occur due to retrieving data from database column "%1!s!" with a length of %2!d! to data flow column "%3!s!" with a length of %4!d!.

�Batch mode is not currently supported when error row disposition is used. The BatchSize property will be set to 1.

�No rows were successfully inserted into the destination. This may be due to a data type mismatch between columns, or due to the use of a datatype that is unsupported by your ADO.NET provider. Since the error disposition for this component is not "Fail component", error messages are not shown here; set the error disposition to "Fail component" to see error messages here.

@Potential data loss may occur due to inserting data from input column "%1!s!" with data type "%2!s!" to external column "%3!s!" with data type "%4!s!". If this is intended, an alternative way to do conversion is using a Data Conversion component before ADO NET destination component.

`The %1!s! has been out of synchronization with the database column. The latest column has %2!s!. Use advanced editor to refresh available destination columns if needed.

@The %1!s! does not exist in the database. It may have been removed or renamed. Use Advanced Editor to refresh the available destination columns if needed.

0A new column with name %1!s! has been added to the external database table. Use advanced editor to refresh available destination columns if needed.

�No rows will be sent to the no match output. Configure the transformation to redirect rows with no matching entries to the no match output, or delete the data flow transformations or destinations that are attached to the no match output.

�Exception received while enumerating ADO.Net providers. The invariant was "%1!s!". The exception message is: "%2!s!"

XThe external column "%1!s!" of "%2!s!" has a data type that cannot be mapped to a Data Flow task data type. The Data Flow task data type DT_NTEXT will be used instead.

�'Row by Row' fetch method is enforced because the table has LOB column(s). Column %1!s! is LOB

XAn internal object or variable was not initialized. This is an internal product error. This error is returned when a variable should have a valid value but does not.

pIntegration Services evaluation period has expired.

xThis property cannot be assigned a negative value. This error occurs when a negative value is assigned to a property that can only contain positive values, such as the COUNT property.

�Indexes cannot be negative. This error occurs when a negative value is used as an index to a collection.

�Failed to create COM Component Categories Manager due to error 0x%1!8.8X! "%2!s!".

Invalid server name "%1!s!". SSIS service does not support multi-instance, use just server name instead of "server name\instance".

hMigration for VSA scripts can not be done on 64 bit platforms due to lack of Visual Tools for Applications designer support. Run the migration under WOW64 on 64 bit platforms.

XThe command execution generated errors.

�To run a SSIS package outside of SQL Server Data Tools you must install %1!s! of Integration Services or higher.

(The variable cannot be found. This occurs when an attempt is made to retrieve a variable from the Variables collection on a container during execution of the package, and the variable is not there. The variable name may have changed or the variable is not being created.

tError trying to write to a read-only variable, "%1".

�Unable to find the directories containing Tasks and Data Flow Task components. Check the integrity of your installation.

�Package name is too long. The limit is 128 characters. Shorten the package name.

�Package description is too long. The limit is 1024 characters. Shorten the package description.

�VersionComments property is too long. The limit is 1024 characters. Try shortening the VersionComments.

�The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.

�The specified package could not be loaded from the SQL Server database.

The variable value assignment is not valid. This error happens when the client or a task assigns a runtime object to a variable value.

�Error assigning namespace to the variable. The namespace "System" is reserved for system use. This error happens when a component or task attempts to create a variable with a namespace of "System".

The connection "%1!s!" is not found. This error is thrown by Connections collection when the specific connection element is not found.

�The variable "%1!s!" is a 64-bit integer variable, which is not supported on this operating system. The variable has been recast to 32-bit integer. Variables of type VT_I8 and VT_UI8 are not supported on Microsoft Windows 2000.

�An attempt change to a read-only attribute on variable "%1" occurred. This error happens when a read-only attribute for a variable is being changed at runtime. Read-only attributes can be changed only at design time.

�Invalid attempt to set a variable to a container reference. Variables are not allowed to reference containers.

�Assigning invalid value or object to variable "%1!s!". This error happens when a value is not appropriate for variables.

�One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.

Error getting or setting an array value. The type "%1!s!" is not allowed. This occurs when loading an array into a variable.

�Unsupported type in array. This happens when saving an array of unsupported types into a variable.

hError loading value "%1!s!" from node "%2!s!".

�Node "%1!s!" is not a valid node. This happens when saving fails.

�The object "%1!s!" references ID "%2!s!", but no object in the package has this ID. If the object "%1!s!" was added to the package by a manual edit ensure that the referenced object with ID "%2!s!" is also added to the package.

�The expected attribute "%3!s!" was not found on the "%2!s!" element while processing an object at "%1!s!".

�The expected attributes "%3!s!" were not found on the "%2!s!" element while processing an object at "%1!s!

�Cannot change the protection level of a project connection manager. It inherits from the project

�Failed to load task "%1!s!", type "%2!s!". The contact information for this task is "%3!s!".

tElement "%1!s!" does not exist in collection "%2!s!".

lThe ObjectData element is missing in the XML block of a hosted object. This occurs when the XML parser attempts to locate the data element for an object and it cannot be found.

<The variable "%1!s!" cannot be found. This error occurs when an attempt to retrieve a variable from a variables collection on a container during execution of the package occurs, and the variable is not there. A variable name may have changed or the variable is not being created.

�The "%1!s!" task has been deprecated and cannot be used with this version of Integration Services.

�The package cannot execute because it contains tasks that failed to load.

�The task has failed to load. The contact information for this task is "%1!s!".

@Error loading task "%1!s!".

�Error loading task. This happens when loading a task from XML fails.

�Exception "%1!s!" occurred during "%2!s!" for task "%3!s!".

�Cannot modify project parameters collection through the IDTSVariables100 interface. Use the Managed Runtime instead.

8The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=219816

tCannot cast object to type IDTSObjectVersionUpdate100

�Task "%1!s!" (type "%2!s!") failed to initialize due to error 0x%3!8.8X! "%4!s!".

tAn error has occurred. The error code was 0x%1!8.8X!.

�The %1!s! cannot write to the cache because %2!s! has already written to it.

\Failed to prepare the cache for new data.

dFailed to mark the cache as filled with data.

|The cache is not initialized and cannot be read by %1!s!.

hFailed to prepare the cache for providing data.

�The cache is being written to by %1!s!, and cannot be read by %2!s!.

�The cache is being read from %1!s! and cannot be written to by %2!s!.

�The runtime object cannot be loaded from the specified XML node. This happens when trying to load a package or other object from an XML node that is not of the correct type, such as a non-SSIS XML node.

|Failed to open package file "%1!s!" due to error 0x%2!8.8X! "%3!s!". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage or the specified XML file has an incorrect format.

\Failed to load XML due to error 0x%1!8.8X! "%2!s!". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name to the LoadPackage method or the specified XML file has an incorrect format.

�Failed to load XML from package file "%1!s!" due to error 0x%2!8.8X! "%3!s!". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name to the LoadPackage method or the specified XML file has an incorrect format.

,Failed to open package file. This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name to the LoadPackage method or the specified XML file has an incorrect format.

lUnable to decode a binary format in the package.

Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.

pError loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.

�Cannot create an instance of the XML Document Object Model due to error 0x%1!8.8X! "%2!s!". MSXML may not be registered.

8The package cannot be loaded. This occurs when attempting to load an older version package, or the package file refers to an invalid structured object.

DFailed to save package file.

�Failed to save package file "%1!s!" with error 0x%2!8.8X! "%3!s!".

xThe object must inherit from IDTSName100 and does not.

(The configuration entry, "%1!s!", has an incorrect format because it does not begin with package delimiter. There was no "\package" delimiter.

DThe configuration entry "%1!s!" had an incorrect format. This can occur because of a missing delimiter or formatting errors, like an invalid array delimiter.

TFailure exporting configuration file.

\Properties collection cannot be modified.

�Unable to save configuration file. The file may be read only.

�FailPackageOnFailure property is not applicable to the package container.

�The task "%1!s!" cannot run on the installed edition of Integration Services. It requires %2!s! or higher.

|Unable to save xml to "%1!s!". The file may be read only.

tFailed to convert a type in the configuration "%1!s!" for the package path "%2!s!". This happens when a configuration value cannot be converted from a string to the appropriate destination type. Check the configuration value to ensure it can be converted to the type of the destination property or variable.

Configuration failure. This is a generic warning for all configuration types. Other warnings should precede this with more information.

�Package failed validation from the ExecutePackage task. The package cannot run.

tFailed to create mutex "%1!s!" with error 0x%2!8.8X!.

�Mutex "%1!s!" already exists and is owned by another user.

xFailed to acquire mutex "%1!s!" with error 0x%2!8.8X!.

xFailed to release mutex "%1!s!" with error 0x%2!8.8X!.

�The wrappers task pointer is not valid. The wrapper has an invalid pointer to a task.

8The executable has been added to the Executables collection of another container. This occurs when a client tries to add an executable to more than one Executables collection. You need to remove the executable from the current Executables collection before attempting to add it.

<The connection type "%1!s!" specified for connection manager "%2!s!" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

�An object was created but the attempt to add it to a collection failed. This can occur due to an out-of-memory condition.

�There was an error creating an Open Database Connectivity (ODBC) environment.

� There was an error creating an Open Database Connectivity (ODBC) database connection.

�There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.

�The qualifier is already set on this instance of the connection manager. The qualifier may be set once per instance.

The qualifier has not been set on this instance of the connection manager. Setting the qualifier is required to complete initialization.

�This connection manager does not support specification of qualifiers.

�Connection manager "0x%1!s!" cannot be cloned for out-of-process execution.

The log provider for SQL Server Profiler was unable to load pfclnt.dll. Please check that SQL Server Profiler is installed.

HThe SSIS logging infrastructure failed with error code 0x%1!8.8X!. This error indicates that this logging error is not attributable to a specific log provider.

<The SSIS logging provider "%1!s!" failed with error code 0x%2!8.8X! (%3!s!). This indicates a logging error attributable to the specified log provider.

The SaveToSQLServer method has encountered OLE DB error code 0x%1!8.8X! (%2!s!). The SQL statement that was issued has failed.

The LoadFromSQLServer method has encountered OLE DB error code 0x%1!8.8X! (%2!s!). The SQL statement that was issued has failed.

The RemoveFromSQLServer method encountered OLE DB error code 0x%1!8.8X! (%2!s!) The SQL statement that was issued has failed.

�The ExistsOnSQLServer method has encountered OLE DB error code 0x%1!8.8X! (%2!s!). The SQL statement issued has failed.

�OLE DB has failed making a database connection when using the supplied connection string.

�When adding a precedence constraint, a From executable was specified that is not a child of this container.

�When adding a precedence constraint, the To executable specified is not a child of this container.

(There was an error trying enlist an ODBC connection in a transaction. The SQLSetConnectAttr failed to set the SQL_ATTR_ENLIST_IN_DTC attribute.

dThe connection manager "%1!s!" will not acquire a connection because the package OfflineMode property is TRUE. When the OfflineMode is TRUE, connections cannot be acquired.

�The SSIS Runtime has failed to start the distributed transaction due to error 0x%1!8.8X! "%2!s!". The DTC transaction failed to start. This could occur because the MSDTC Service is not running.

The SetQualifier method cannot be called on a connection manager during package execution. This method is used at design-time only.

LStoring or modifying packages in SQL Server requires the SSIS runtime and database to be the same version. Storing packages in earlier versions is not supported.

TConnection "%1!s!" failed validation.

�The file name "%1!s!" specified in the connection was not valid.

�Multiple file names cannot be specified on a connection when the Retain property is TRUE. Vertical bars were found on the connection string, meaning multiple file names are being specified and, in addition, the Retain property is TRUE.

LAn ODBC error %1!d! has occurred.

�There was an error in the precedence constraint between "%1!s!" and "%2!s!".

Failed to populate the ForEachEnumeratorInfos collection with native ForEachEnumerators with the following error code: %1!s!.

8The GetEnumerator method of the ForEach Enumerator has failed with error 0x%1!8.8X! "%2!s!". This occurs when the ForEach Enumerator cannot enumerate.

HThe raw certificate data cannot be obtained from the supplied certificate object (error: %1!s!). This occurs when CPackage::put_CertificateObject cannot instantiate the ManagedHelper object, when the ManagedHelper object fails, or when the ManagedHelper object returns a malformed array.

dFailed to create certificate context (error: %1!s!). This occurs in CPackage::put_CertificateObject or CPackage::LoadFromXML when the corresponding CryptoAPI function fails.

0Opening MY certificate store failed with error "%1!s!".This occurs in CPackage::LoadUserCertificateByName and CPackage::LoadUserCertificateByHash.

The certificate specified by name in MY store cannot be found (error: %1!s!). This occurs in CPackage::LoadUserCertificateByName.

Unable to find the specified certificate by hash in "MY" store (error: %1!s!). Occurs in CPackage::LoadUserCertificateByHash.

The hash value is not a one-dimensional array of bytes (error: %1!s!). This occurs in CPackage::LoadUserCertificateByHash.

�The data in the array cannot be accessed (error: %1!s!). This error can occur wherever GetDataFromSafeArray is called.

<The SSIS managed helper object failed during creation with error 0x%1!8.8X! "%2!s!". This occurs whenever CoCreateInstance CLSID_DTSManagedHelper fails.

�The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x%1!8.8X! "%2!s!".

�Package signing failed with error 0x%1!8.8X! "%2!s!". This occurs when the ManagedHelper.SignDocument method fails.

Failed to check for XML signature envelope in package XML with error 0x%1!8.8X! "%2!s!". This occurs in CPackage::LoadFromXML.

Failed to obtain XML source from XML DOM object with error 0x%1!8.8X! "%2!s!". This occurs when IXMLDOMDocument::get_xml fails.

DThe cryptographic signature of the package failed verification due to error 0x%1!8.8X! "%2!s!". This occurs when the signature verification operation fails.

|Failed to obtain cryptographic key pair associated with the specified certificate with error 0x%1!8.8X! "%2!s!". Verify that you have the key pair for which the certificate was issued. This error usually occurs when trying to sign a document using a certificate for which the person does not have the private key.

�The digital signature is not valid. The contents of the package have been modified.

�The digital signature is valid; however the signer is not trusted and, therefore, authenticity cannot be guaranteed.

�The connection does not support enlisting in distributed transaction.

�Failed to apply package protection with error 0x%1!8.8X! "%2!s!". This error occurs when saving to Xml.

�Failed to remove package protection with error 0x%1!8.8X! "%2!s!". This occurs in the CPackage::LoadFromXML method.

�The package is encrypted with a password. The password was not specified, or is not correct.

A precedence constraint already exists between the specified executables. More than one precedence constraint is not allowed.

�The package failed to load due to error 0x%1!8.8X! "%2!s!". This occurs when CPackage::LoadFromXML fails.

DFailed to find package object in signed XML envelope with error 0x%1!8.8X! "%2!s!". This occurs when signed XML does not contain a SSIS package, as expected.

�The lengths of parameter names, types, and descriptions arrays are not equal. The lengths must be equal. This occurs when the lengths of the arrays are mismatched. There should be one entry per parameter in each array.

�An OLE DB error 0x%1!8.8X! (%2!s!) occurred while enumerating packages. A SQL statement was issued and failed.

The log provider type "%1!s!" specified for log provider "%2!s!" is not recognized as a valid log provider type. This error occurs when an attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name.

�The log provider type is not recognized as a valid log provider type. This error occurs when an attempt is made to create a log provider for unknown log provider type. Verify the spelling in the log provider type name.

�The connection type specified for connection manager is not a valid connection manager type. This error occurs when an attempt is made to create a connection manager for unknown connection type. Verify the spelling of the connection type name.

�An error was encountered when trying to remove the package "%1!s!" from SQL Server.

xThe connection manager "%1!s!" will not acquire a connection because the connection manager OfflineMode property is TRUE. When the OfflineMode is TRUE, connections cannot be acquired.

�An error was encountered when trying to create a folder on SQL Server named "%1!s!" in folder "%2!s!".

The CreateFolderOnSQLServer method has encountered OLE DB error code 0x%1!8.8X! (%2!s!) The SQL statement issued has failed.

�An error occurred when renaming folder " %1!s!\\%2!s!" to "%1!s!\\%3!s!" on SQL Server.

�The RenameFolderOnSQLServer method encountered OLE DB error code 0x%1!8.8X! (%2!s!). The SQL statement issued has failed.

\Error deleting SQL Server folder "%1!s!".

�The RemoveFolderOnSQLServer method encountered OLE DB error code 0x%1!8.8X! (%2!s!). The SQL statement issued has failed.

0The specified package path does not contain a package name. This occurs when the path does not contain at least one backslash or one forward slash.

@Cannot find folder "%1!s!".

�While trying to find a folder on SQL an OLE DB error was encountered with error code 0x%1!8.8X! (%2!s!).

�The SSIS logging provider has failed to open the log. Error code: 0x%1!8.8X!.

<Failed to get ConnectionInfos collection with error 0x%1!8.8X! "%2!s!". This error occurs when the call to IDTSApplication100::get_ConnectionInfos fails.

�Deadlock detected while trying to lock variables. The locks cannot be acquired after 16 attempts. The locks timed out.

4The Variables collection has not been returned from the VariableDispenser. An operation was attempted that is only allowed on dispensed collections.

This Variables collection has already been unlocked. The Unlock method is called only once on a dispensed Variables collection.

XOne or more variables failed to unlock.

<The Variables collection was returned the from VariableDispenser and cannot be modified. Items cannot be added to or removed from dispensed collections.

The variable "%1!s!" is already on the read list. A variable may only be added once to either the read lock list or the write lock list.

The variable "%1!s!" is already on the write list. A variable may only be added once to either the read lock list or the write lock list.

�Failed to lock variable "%1!s!" for read access with error 0x%2!8.8X! "%3!s!".

�Failed to lock variable "%1!s!" for read/write access with error 0x%2!8.8X! "%3!s!".

�The custom event "%1!s!" is already declared with a different parameter list. A task is trying to declare a custom event, which another task has already declared with a different parameter list.

PThe task providing the custom event "%1!s!" does not allow this event to be handled in the package. The custom event was declared with AllowEventHandlers = FALSE.

�The VariableDispenser received an unsafe Variables collection. This operation cannot be repeated.

�GetPackagePath was called on the ForEachEnumerator but there was no ForEachLoop package path specified.

$A deadlock was detected while trying to lock variable "%1!s!" for read access. A lock could not be acquired after 16 attempts and timed out.

8A deadlock was detected while trying to lock variables "%1!s!" for read/write access. A lock cannot be acquired after 16 attempts. The locks timed out.

�A deadlock was detected while trying to lock variables "%1!s!" for read access and variables "%2!s!" for read/write access. A lock cannot be acquired after 16 attempts. The locks timed out.

�The protection level of the package requires a password, but PackagePassword property is empty.

XFailed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.

�Failed to decrypt a package that is encrypted with a user key. You may not be the user who encrypted this package, or you are not using the same machine that was used to save the package.

\The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.

TLoadFromSQLServer method has failed.

The package cannot be loaded because the state of the digital signature violates signature policy. Error 0x%1!8.8X! "%2!s!"

@The package is not signed.

�The log provider for SQL Server Profiler was unable to load pfclnt.dll because it is only supported on 32-bit systems.

0The object cannot be added because another object with the same name already exists in the collection. Use a different name to resolve this error.

XThe object name cannot be changed from "%1!s!" to "%2!s!" because another object in the collection already uses that name. Use a different name to resolve this error.

�There was an error enumerating the package dependencies. Check other messages for more information.

The current package settings are not supported. Please change the SaveCheckpoints property or the TransactionOption property.

�The connection manager failed to defect from the transaction.

LThe specified breakpoint ID already exists. This error occurs when a task calls CreateBreakpoint with the same ID multiple times. It is possible to create a breakpoint with the same ID multiple times if the task calls RemoveBreakpoint on the first creation before creating the second one.

�The specified breakpoint ID does not exist. This error occurs when a task references a breakpoint that does not exist.

The file, "%1!s!", could not be opened for writing. The file could be read-only, or you do not have the correct permissions.

�No result rowset is associated with the execution of this query. The result is not correctly specified.

�Debug dump files were not generated correctly. The hresult is 0x%1!8.8X!.

�The URL specified is not valid. This can happen when the server or proxy URL is null, or in an incorrect format. A valid URL format is in the form of http://ServerName:Port/ResourcePath or https://ServerName:Port/ResourcePath.

�The URL %1!s! is not valid. This can happen when a scheme other than http or https is specified, or the URL is in an incorrect format. A valid URL format is in the form of http://ServerName:Port/ResourcePath or https://ServerName:Port/ResourcePath.

Connection to server %1!s! cannot be established. This error can occur when the server does not exist, or the proxy settings are incorrect.

�The connection with the server has been reset or terminated. Try again later.

The login attempt failed for "%1!s!". This error occurs when the login credentials provided are incorrect. Verify the login credentials.

�The server name specified in the URL %1!s! cannot be resolved.

�Proxy authentication failed. This error occurs when login credentials are not provided, or the credentials are incorrect.

�SSL certificate response obtained from the server was not valid. Cannot process the request.

�The request has timed out. This error can occur when the timeout specified was too short, or a connection to the server or proxy cannot be established. Ensure that the server and proxy URL are correct.

�Client certificate is missing. This error occurs when the server is expecting an SSL client certificate and the user has provided an invalid certificate, or has not provided a certificate. A client certificate must be configured for this connection.

�The specified server, URL %1!s!, has a redirect and the redirect request failed.

Server authentication failed. This error occurs when login credentials are not provided, or the credentials are incorrect.

dRequest cannot be processed. Try again later.

�Server returned status code - %1!u! : %2!s!. This error occurs when the server is experiencing problems.

pThis platform is not supported by WinHttp services.

�Timeout value is not valid. Timeout should be in the range of %1!d! to %2!d! (in seconds).

�The chunk size is not valid. The ChunkSize property should be in the range of %1!d! to %2!d! (in KB).

�Error processing client certificate. This error can occur when the client certificate provided was not found in the Personal Certificate Store. Verify that the client certificate is valid.

HServer returned error code "403 - Forbidden". This error can occur when the specified resource needs "https" access, but the certificate validity period has expired, the certificate is not valid for the use requested, or the certificate has been revoked or revocation can not be checked.

XError initializing HTTP session with proxy "%1!s!". This error can occur when an invalid proxy was specified. HTTP connection manager only supports CERN-type proxies.

LError opening certificate store.

�Failed to decrypt protected XML node "%1!s!" with error 0x%2!8.8X! "%3!s!". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

�Failed to decrypt protected connection string for server "%1!s!" with error 0x%2!8.8X! "%3!s!". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

LThe version number cannot be negative. This error occurs when the VersionMajor, VersionMinor, or VersionBuild property of the package is set to a negative value.

$The package has been migrated to a later version during loading. It must be reloaded to complete the process. This is an internal error code.

�Package migration from version %1!d! to version %2!d! failed with error 0x%3!8.8X! "%4!s!".

dPackage migration module has failed to load.

TPackage migration module has failed.

LUnable to persist object using default persistence. This error occurs when the default persistence is unable to determine which objects are on the hosted object.

xCannot add or remove an element from a package in runtime mode. This error occurs when an attempt is made to add or remove an object from a collection while the package is executing.

�The "%1!s!" node cannot be found in custom default persistence. This error occurs if the default saved XML of an extensible object was changed in a way that a saved object is no longer found, or if the extensible object itself changed.

�This collection cannot be modified during package validation or execution.

The "%1!s!" collection cannot be modified during package validation or execution. "%2!s!" cannot be added to the collection.

|Connection with the FTP server has not been established.

�An error occurred in the requested FTP operation. Detailed error description: %1!s!

�The number of retries is not valid. The number of retries should be between %1!d! and %2!d!.

�The FTP connection manager needs the following DLL to function: %1!s!.

PThe port specified in the connection string is not valid. The ConnectionString format is ServerName:Port. Port should be an integer value between %1!d! and %2!d!.

PCreating folder "%1!s!" ... %2!s!.

PDeleting folder "%1!s!" ... %2!s!.

dChanging current directory to "%1!s!". %2!s!.

No files to transfer. This error can occur when performing a Send or Receive operation and no files are specified for the transfer.

�Specified local path is not valid. Specify a valid local path. This can occur when the specified local path is null.

DNo files specified to delete.

�Internal error occurred while loading the certificate. This error could occur when the certificate data is invalid.

�Internal error occurred while saving the certificate data.

�The "%1!s!" collection cannot be modified during package validation or execution.

Checkpoint file "%1!s!" does not match this package. The ID of the package and the ID in the checkpoint file do not match.

An existing checkpoint file is found with contents that do not appear to be for this package, so the file cannot be overwritten to start saving new checkpoints. Remove the existing checkpoint file and try again. This error occurs when a checkpoint file exists, the package is set to not use a checkpoint file, but to save checkpoints. The existing checkpoint file will not be overwritten.

The checkpoint file "%1!s!" is locked by another process. This may occur if another instance of this package is currently executing.

�Checkpoint file "%1!s!" failed to open due to error 0x%2!8.8X! "%3!s!".

�Checkpoint file "%1!s!" failed during creation due to error 0x%2!8.8X! "%3!s!".

�The FTP Port contains an invalid value. The FTP Port value should be an integer between %1!d! and %2!d!.

�Connecting to the Integration Services service on the computer "%1!s!" failed with the following error: "%2!s!".

@Connecting to the Integration Services service on the computer "%1!s!" failed with the following error: "%2!s!".%n%nThis error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.

�Connecting to the Integration Services service on the computer "%1!s!" failed with the following error: "%2!s!".%n%nThis error occurs when the computer host name does not exist, or cannot be reached.

LConnecting to the Integration Services service on the computer "%1!s!" failed with the following error: "%2!s!"%n%nBy default, only administrators have access to the Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service.

�The Expression property is not supported on Variable objects. Use the EvaluateAsExpression property instead.

�The expression "%1!s!" on property "%2!s!" cannot be evaluated. Modify the expression to be valid.

DThe result of the expression "%1!s!" on property "%2!s!" cannot be written to the property. The expression was evaluated, but cannot be set on the property.

The evaluation expression for the loop is not valid. The expression needs to be modified. There should be additional error messages.

�The expression "%1!s!" must evaluate to True or False. Change the expression to evaluate to a Boolean value.

There is no expression for the loop to evaluate. This error occurs when the expression on the For Loop is empty. Add an expression.

�The assignment expression for the loop is not valid and needs to be modified. There should be additional error messages.

The initialization expression for the loop is not valid and needs to be modified. There should be additional error messages.

�The version number in the package is not valid. The version number cannot be greater than current version number.

�The version number in the package is not valid. The version number is negative.

�The package has an older format version, but automatic package format upgrading is disabled.

�A truncation occurred during evaluation of the expression.

�The expression will not be evaluated because it contains the variable "%1!s!" that references sensitive parameter variables in its expression. Verify that the expression is used properly and that it protects sensitive information.

�The expression will not be evaluated because it contains sensitive parameter variable "%1!s!". Verify that the expression is used properly and that it protects the sensitive information.

xAccessing value of the parameter variable for the sensitive parameter "%1!s!" is not allowed. Verify that the variable is used properly and that it protects the sensitive information.

�An error occurred while applying a data tap configuration on data flow task "%1!s!". The specified data flow path identification is "%2!s!" and the file name is "%3!s!". The error description is "%4!s!".

�The wrapper was unable to set the value of the variable specified in the ExecutionValueVariable property.

�The expression for variable "%1!s!" failed evaluation. There was an error in the expression.

,The project cannot be saved because it does not pass consistency check. Use the Events object to get more detailed errors from consistency check.

`The package already belongs to a project.

�You must use the same protection level for the project and the packages within the project.

�You must use the same password for the project and the packages within the project.

�The project is encrypted with a password. The password was not specified, or is not correct.

�Failed to decrypt a project that is encrypted with a user key. You may not be the user who encrypted this project, or you are not using the same machine that was used to save the project.

�The attempted operation is not supported with this database version.

�Transaction cannot be specified when a retained connection is used. This error occurs when Retain is set to TRUE on the connection manager, but AcquireConnection was called with a non-null transaction parameter.

�Incompatible transaction context was specified for a retained connection. This connection has been established under a different transaction context. Retained connections can be used under exactly one transaction context.

Resume call failed because the package is not suspended. This occurs when the client calls resume, but the package is not suspended.

pExecute call failed because the executable is already executing. This error occurs when the client calls Execute on a container that is still executing from the last Execute call.

�Suspend or Resume call failed because the executable is not executing, or is not the top-level executable. This occurs when the client calls Suspend or Resume on an executable that is not currently processing an Execute call.

The file specified in the For Each File enumerator is not valid. Check that the file specified in the For Each File enumerator exists.

�The value index is not an integer . Mapping a For Each Variable number %1!d! to the variable "%2!s!".

�The value index is negative. The ForEach Variable Mapping number %1!d! to variable "%2!s!".

�ForEach Variable Mapping number %1!d! to variable "%2!s!" cannot be applied.

�Failure when adding an object to a ForEachPropertyMapping that is not a direct child of the ForEachLoop container.

�Failed to remove a system variable. This error occurs when removing a variable that is a required variable. Required variables are variables that are created by the runtime for communicating between tasks and the runtime.

�Changing the property of a variable failed because it is a system variable. System variables are read-only.

�Changing the name of a variable failed because it is a system variable. System variables are read-only.

�Changing the namespace of a variable failed because it is a system variable. System variables are read-only.

�Changing the event handler name failed. Event handler names are read-only.

xCannot retrieve path to object. This is a system error.

�The type of the value (%2!s!) being assigned to variable "%1!s!" differs from the current variable type (%3!s!). Variables may not change type during execution. Variable types are strict, except for variables of type Object.

Invalid characters in string: "%1!s!". This occurs when a string supplied for a property value contains unprintable characters.

�SSIS object name is invalid. More specific errors would have been raised explaining the exact naming problem.

xThe specified data type for parameter value is invalid.

@The parameter value could not be assigned because the data types did not match. The provided value was of type "%1!s!", the expected data type was "%2!s!".

�Failed to retrieve the parameter value as no value has been specified for the parameter.

DThe parameter "%1!s!" cannot be found. This error occurs when an attempt to retrieve a parameter from a parameters collection and the parameter is not there.

�Changing the %1!s! of a variable failed because it is a parameter variable. Parameter variables are read-only.

TThe value of parameter "%1!s!" could not be assigned because the data types do not match. The provided value was of type "%2!s!", the expected data type was "%3!s!".

�The property "%1!s!" is read only. This occurs when a change to a read-only property is attempted.

�The object does not support type information. This occurs when the runtime attempts to get the type information from an object to populate the Properties collection. The object must support type information.

�An error occurred while retrieving the value of property "%1!s!". The error code is 0x%2!8.8X!.

�An error occurred while retrieving the value of property "%1!s!". The error code is 0x%2!8.8X! "%3!s!".

�An error occurred while setting the value of property "%1!s!". The error returned is 0x%2!8.8X!.

�An error occurred while setting the value of property "%1!s!". The error returned is 0x%2!8.8X! "%3!s!".

LThe property "%1!s!" is write-only. This error occurs when trying to retrieve the value of a property through a property object, but the property is write-only.

PThe object does not implement IDispatch. This error occurs when a property object or properties collection attempts to access an IDispatch interface on an object.

|Unable to retrieve the type library of the object. This error occurs when the Properties collection attempts to retrieve the type library for an object through its IDispatch interface.

�Cannot create a task from XML for task "%1!s!", type "%2!s!" due to error 0x%3!8.8X! "%4!s!".

\Failed to create an XML document "%1!s!".

@An error occurred because there is a property mapping from a variable to a property with a different type. The property type must match the variable type.

4Attempted to set property mapping to target unsupported object type. This error occurs when passing an unsupported object type to a property mapping.

�Cannot resolve a package path to an object in the package "%1!s!". Verify that the package path is valid.

�The destination property for the property map is empty. Set the destination property name.

�The package failed to restore at least one property mapping.

HThe variable name is ambiguous because multiple variables with this name exist in different namespaces. Specify namespace-qualified name to prevent ambiguity.

XThe destination object in a property mapping has no parent. The destination object is not a child of any sequence container. It may have been removed from the package.

�The property mapping is not valid. The mapping is ignored.

�Failure when alerting property mappings that a target is being removed.

An invalid property mapping is found on the For Each Loop. This occurs when the ForEach property mapping fails to restore.

hA destination property was specified on a property mapping that is invalid. This occurs when a property is specified on a destination object that in not found on that object.

$Cannot create a task from XML. This occurs when the runtime is unable to resolve the name to create a task. Verify that the name is correct.

�Cannot replace the existing checkpoint file with the updated checkpoint file. The checkpoint was successfully created in a temporary file, but overwriting the existing file with the new file failed.

�The package is configured to always restart from a checkpoint, but checkpoint file is not specified.

PThe attempt to load the XML checkpoint file "%1!s!" failed with error 0x%2!8.8X! "%3!s!". Check that the file name specified is correct, and that the file exists.

(The package failed during execution because the checkpoint file cannot be loaded. Further execution of the package requires a checkpoint file. This error usually occurs when the CheckpointUsage property is set to ALWAYS, which specifies that the package always restarts.

The evaluation condition expression on the For Loop "%1!s!" is empty. There must be a Boolean evaluation expression in the For Loop.

The result of the assignment expression "%1!s!" cannot be converted to a type that is compatible with the variable that it was assigned to.

�Error using a read-only variable "%1!s!" in an assignment expression. The expression result cannot be assigned to the variable because the variable is read only. Choose a variable that can be written to, or remove the expression from this variable.

�Cannot evaluate expression "%1!s!" because the variable "%2!s!" does not exist or cannot be accessed for writing. The expression result cannot be assigned to the variable because the variable was not found, or could not be locked for write access.

�The expression "%1!s!" has a result type of "%2!s!", which cannot be converted to a supported type.

LThe conversion of the result of the expression"%1!s!" from type "%2!s!" to a supported type failed with error code 0x%3!8.8X!. An unexpected error occurred when trying to convert the expression result to a type supported by the runtime engine, even though the type conversion is supported.

�The object name is not valid. The name cannot be set to NULL.

xThe object name is not valid. The name cannot be empty.

�The object name "%1!s!" is not valid. The name cannot contain any of the following characters: / \ : [ ] . =

�Object name "%1!s!" is not valid. The name cannot contain control characters that render it unprintable.

�Object name "%1!s!" is not valid. Name cannot begin with a whitespace.

�Object name "%1!s!" is not valid. Name cannot end with a whitespace.

�Object name "%1!s!" is not valid. Name must begin with an alphabetical character.

�Object name "%1!s!" is not valid. Name must begin with an alphabetical character or underscore "_".

�Object name "%1!s!" is not valid. Name must contain only alphanumeric characters or underscores "_".

�Object name "%1!s!" is not valid. The name cannot contain any of the following characters: / \ : ? " < > |

�The object name is too long. The length of the object name cannot exceed the maximum length.

�Failed to load the value property "%1!s!" using default persistence.

lConnection manager "%1!s!" is not of type "%2!s!"

,"%1!s!" is empty

tInvalid data node in the nodelist enumerator section

DNo enumerator can be created

lThe operation failed because the cache is in use.

LThe property cannot be modified.

HThe package upgrade has failed.

(An error occurred while accessing an internal object. This could indicate a custom extension built for Integration Services 2005 is being used.

(The Project Connection Manager "%1" is not accessible inside this package because a connection manager declared in the package has the same name as the Project Connection Manager. Change the name of either the Project Connection Manager or the Package Connection Manager.

�The SSIS Runtime has failed to commit the distributed transaction due to error 0x%1!8.8X! "%2!s!".

�The SSIS Runtime has failed to abort the distributed transaction due to error 0x%1!8.8X! "%2!s!".

�A transaction error occurred. See previous error messages for details.

XTeradata driver %1!s! is not installed.

�Error 0x%1!8.8X! while loading package file "%3!s!". %2!s!.

DThe package is not specified.

LThe connection is not specified.

The connection manager "%1!s!" has an unsupported type "%2!s!". Only "FILE" and "OLEDB" connection managers are supported.

�Error 0x%1!8.8X! while loading package file "%3!s!" into an XML document. %2!s!.

�Error 0x%1!8.8X! while preparing to load the package. %2!s!.

LThere is no project to reference.

xFailed to locate the specified package in the project.

Error 0x%1!8.8X!. Unable to access the package file, "%2!s!". Make sure that the file exists and that you have permission to access it.

�Error 0x%1!8.8X!. Failed to get the user name. Make sure the user name property is specified correctly on the task.

�Error 0x%1!8.8X!. Failed to get the server name. Make sure the server name property is specified correctly on the task.

�Error 0x%1!8.8X!. Failed to load the package "%2!s!" from SQL Server "%3!s!". Make sure that the package exists on the instance of SQL Server and that you have the correct credentials to access it.

�Error 0x%1!8.8X!. Failed to create an instance of empty child package. The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services, may be corrupted on your machine.

Error 0x%1!8.8X!. Failed to set properties on the XML Document Object Model object. Your DOM installation might be corrupted.

$Error 0x%1!8.8X!. Failed to get an XML document from the Document Object Model. The package data or your DOM installation might be corrupted.

Variable "%1!s!" bound to child package parameter "%2!s!" contains a sensitive value. The child package parameter is not sensitive.

pFailed to locate the variable or parameter "%1!s!".

�One or more required parameters have not been assigned values.

�Error 0x%1!8.8X! while executing package from project reference package "%3!s!". %2!s!.

`The delimiter must not be an empty string.

XThe Validate method on the task failed, and returned error code 0x%1!8.8X! (%2!s!). The Validate method must succeed and indicate the result using an "out" parameter.

<The Execute method on the task returned error code 0x%1!8.8X! (%2!s!). The Execute method must succeed, and indicate the result using an "out" parameter.

A failure occurred on task "%1!s!": 0x%2!8.8X! while retrieving dependencies. The runtime was retrieving dependencies from the task's dependencies collection when the error occurred. The task may have incorrectly implemented one of the dependency interfaces.

\There were errors during task validation.

�The connection string format is not valid. It must consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero components is set on database connection manager.

The connection string components cannot contain unquoted semicolons. If the value must contain a semicolon, enclose the entire value in quotes. This error occurs when values in the connection string contain unquoted semicolons, such as the InitialCatalog property.

(Validation of one or more log providers failed. The package cannot execute. The package does not execute when a log provider fails validation.

8Invalid value in array.

`An element of the enumerator returned by the ForEach Enumerator does not implement IEnumerator, contradicting the CollectionEnumerator property of the ForEach Enumerator.

�The enumerator failed to retrieve element at index "%1!d!".

0Function not found.

�ActiveX Script Task was initiated with a wrong XML element.

0Handler not found.

�An error occurred while attempting to retrieve the scripting languages installed on the system.

�An error occurred while creating the ActiveX script host. Verify that you have the script host installed properly.

PAn error occurred while trying to instantiate the script host for the chosen language. Verify that the script language you have chosen is installed on your system.

4An error occurred while adding the SSIS variables to the script host namespace. This might prevent the task from using SSIS variables in the script.

A fatal error occurred while trying to parse the script text. Verify that the script engine for the chosen language is installed properly.

�The function name entered is not valid. Verify that a valid function name has been specified.

An error occurred while executing the script. Verify that the script engine for the selected language is installed properly.

An error occurred while adding the managed type library to the script host. Verify that the DTS 2000 runtime is installed.

|Bulk Insert Task was initiated with a wrong XML element.

DData file name not specified.

0Handler not found.

tFailed to acquire the specified connection: "%1!s!".

lAttempt to obtain the Connection Manager failed.

DThe connection is not valid.

8The connection is null.

,Execution failed.

�An error occurred while retrieving the tables from the database.

�An error occurred while retrieving the columns of the table.

dAn error occurred in the database operation.

The specified connection "%1!s!" is either not valid, or points to an invalid object. To continue, specify a valid connection.

�The destination connection specified is not valid. Supply a valid connection to continue.

`You must specify a table name to continue.

lError occurred in LoadFromXML at the tag "%1!s!".

hError occurred in SaveToXML at the tag "%1!s!".

DThe connection is not valid.

,Execution failed.

�Error occurred while retrieving the tables from the database.

|Error occurred while retrieving the columns of the table.

pError occurred while trying to open the data file.

�Cannot convert the input OEM file to the specified format.

DError in database operation.

LNo connection manager specified.

�Connection "%1!s!" is not an Analysis Services connection.

TUnable to locate connection "%1!s!".

�Analysis Services Execute DDL task received an invalid task data node.

�Analysis Services Processing task received an invalid task data node.

4The DDL is not valid.

lThe DDL found in ProcessingCommands is not valid.

�The Execution result cannot be saved in a read-only variable.

PVariable "%1!s!" it's not defined.

dConnection Manager "%1!s!" it's not defined.

�Connection Manager "%1!s!" it's not a FILE Connection Manager.

d"%1!s!" was not found during deserialization.

hThe trace has been stopped due to an exception.

<Execution of DDL failed.

tThere is no file associated with connection "%1!s!".

LVariable "%1!s!" is not defined.

XFile connection "%1!s!" is not defined.

�Execute DTS 2000 Package task is initiated with a wrong XML element.

0Handler not found.

HPackage name is not specified.

DPackage ID is not specified.

XPackage version GUID is not specified.

DSQL Server is not specified.

PSQL Server user name not specified.

LStorage file name not specified.

XThe DTS 2000 package property is empty.

xAn error occurred while executing the DTS 2000 package.

�Cannot load the available SQL Servers from the network. Check the network connection.

�The data type cannot be null. Please specify the correct data type to use for validating the value.

dCannot validate a null against any data type.

DA required argument is null.

<To execute the DTS 2000 Package task, start SQL Server Setup and use the Advanced button from the Components to Install page to select Legacy Components.

D"%1!s!" is not a value type.

TCould not convert "%1!s!" to "%2!s!".

`Could not validate "%1!s!" against "%2!s!".

lError occurred in LoadFromXML at the tag "%1!s!".

hError occurred in SaveToXML at the tag "%1!s!".

dThe time-out value provided is not valid. Specify the number of seconds that the task allows the process to run. The minimum time-out is 0, which indicates that no time-out value is used and the process runs to completion or until an error occurs. The maximum time-out is 2147483 (((2^31) - 1)/1000).

�Cannot redirect streams if the process can continue executing beyond the lifetime of the task.

8The process timed out.

LThe executable is not specified.

XThe standard out variable is read-only.

\The standard error variable is read-only.

�The Execute Process task received a task data node that is not valid.

�In Executing "%2!s!" "%3!s!" at "%1!s!", The process exit code was "%4!s!" while the expected was "%5!s!".

TThe directory "%1!s!" does not exist.

|File/Process "%1!s!" does not exist in directory "%2!s!".

TFile/Process "%1!s!" is not in path.

\Working Directory "%1!s!" does not exist.

�The process exited with return code "%1!s!". However, "%2!s!" was expected.

HSynchronization object failed.

|The File System task received an invalid task data node.

DThe Directory already exists.

h"%1!s!" is not valid on operation type "%2!s!".

pDestination property of operation "%1!s!" not set.

dSource property of operation "%1!s!" not set.

\Type of Connection "%1!s!" is not a file.

LVariable "%1!s!" does not exist.

LVariable "%1!s!" is not a string.

,All file attributes for the Set Attributes operation have been configured as No Change. At least one file attribute must be set to True or False.

�File or directory "%1!s!" represented by connection "%2!s!" does not exist.

�The destination file connection manager "%1!s!" has an invalid usage type: "%2!s!".

�The source file connection manager "%1!s!" has an invalid usage type "%2!s!".

0FileSystemOperation

xProvides information regarding File System operations.

,File System Task

�Perform file system operations, such as copying and deleting files.

HSynchronization object failed.

HUnable to obtain the file list.

<The local path is empty.

<The remote path is empty.

DThe local variable is empty.

DThe remote variable is empty.

lThe FTP task received an invalid task data node.

�The connection is empty. Verify that a valid FTP connection is provided.

�The connection specified is not an FTP connection. Verify that a valid FTP connection is provided.

pCannot initialize the task with a null XML element.

dCannot save the task to a null XML document.

lError occurred in LoadFromXML at the tag "%1!s!".

HThere are no files at "%1!s!".

HThe variable "%1!s!" is empty.

hThe File "%1!s!" doesn't contain file path(s).

pThe variable "%1!s!" doesn't contain file path(s).

LVariable "%1!s!" is not a string.

LVariable "%1!s!" does not exist.

PInvalid path on operation "%1!s!".

8"%1!s!" already exists.

\Type of Connection "%1!s!" is Not a file.

`File represented by "%1!s!" does not exist.

pDirectory is not specified in the variable "%1!s!".

@No files found in "%1!s!".

�Directory is not specified in the file connection manager "%1!s!".

TUnable to delete local file "%1!s!".

\Unable to remove local directory "%1!s!".

\Unable to create local directory "%1!s!".

XUnable to receive files using "%1!s!".

PUnable to send files using "%1!s!".

lUnable to create remote directory using "%1!s!".

lUnable to remove remote directory using "%1!s!".

dUnable to delete remote files using "%1!s!".

hUnable to connect to FTP server using "%1!s!".

\Variable "%1!s!" doesn't start with "/".

`Remote path "%1!s!" doesn't start with "/".

�There was an error acquiring the FTP connection. Please check if you have specified a valid connection type "%1!s!".

TOpening the certificate store failed.

�An error occurred while retrieving the display name of the certificate.

�An error occurred while retrieving the issuer name of the certificate.

�An error occurred while retrieving the friendly name of the certificate.

TThe MSMQ connection name is not set.

lTask was initialized with the wrong XML element.

<Data file name is empty.

xThe name specified for the data file to save is empty.

PFile size should be less than 4 MB.

DSaving the data file failed.

DString filter value is empty.

<Queue path is not valid.

�The message queue task does not support enlisting in distributed transactions.

HThe message type is not valid.

�The message queue timed out. No message has been received.

�The property specified is not valid. Verify that the argument type is correct.

DMessage is not authenticated.

�You are trying to set the value of Encryption Algorithm with an invalid object.

lThe variable to receive string message is empty.

hVariable to receive variable message is empty.

XConnection "%1!s!" is not of type MSMQ.

The data file "%1!s!" already exists at the specified location. Cannot overwrite the file as the Overwrite option is set to false.

�The specified variable "%1!s!" to receive string message is not found in the package variable collection.

\The connection manager "%1!s!" is empty.

hThe connection manager "%1!s!" does not exist.

�Error "%1!s!": "%2!s!"\r\nLine "%3!s!" Column "%4!s!" through "%5!s!".

lThere was an error compiling the script: "%1!s!".

�Error "%1!s!": "%2!s!"\r\nLine "%3!s!" Columns "%4!s!"-"%5!s!"\r\nLine Text: "%6!s!".

XUser script returned a failure result.

LUser script files failed to load.

\User script threw an exception: "%1!s!".

|Could not create an instance of entrypoint class "%1!s!".

�There was an exception while loading Script Task from XML: "%1!s!".

lSource item "%1!s!" was not found in the package.

lBinary item "%1!s!" was not found in the package.

x"%1!s!" was not recognized as a valid script language.

�The script name is not valid. It cannot contain spaces, slashes, special characters, or begin with a number.

`The script language specified is not valid.

LCannot initialize to a null task.

�The Script Task user interface must initialize to an Script Task.

pThe Script Task user interface is not initialized.

4Name cannot be empty.

�The project name is not valid. It cannot contain spaces, slashes, special characters, or begin with a number.

`The script language specified is not valid.

8Entry point not found.

�The script language is not specified. Verify that a valid script language is specified.

lUser interface initialization: The task is null.

�The Script Task user interface is initialized with an incorrect task.

@No recipient is specified.

�The Simple Mail Transfer Protocol (SMTP) server is not specified. Provide a valid name or IP address of the SMTP server.

�Send Mail task is initiated with an incorrect XML element.

�Either the file "%1!s!" does not exist or you do not have permissions to access the file.

�Verify that the Simple Mail Transfer Protocol (SMTP) server specified is valid.

XConnection "%1!s!" is not of type File.

pOn operation "%1!s!", file "%2!s!" does not exist.

XVariable "%1!s!" is not of type string.

XConnection "%1!s!" is not of type SMTP.

DConnection "%1!s!" is empty.

lThe specified connection "%1!s!" does not exist.

TNo Transact-SQL statement specified.

lThe connection does not support XML result sets.

�Cannot locate a handler for the specified connection type.

PNo connection manager is specified.

|Cannot acquire a connection from the connection manager.

PCannot have a null parameter name.

LThe parameter name is not valid.

lValid parameter names are of type Int or String.

�Variable "%1!s!" cannot be used in a result binding because it is read-only.

dThe index is not assigned in this collection.

�The variable "%1!s!" cannot be used as an "out" parameter or return value in a parameter binding because it is read-only.

dThe object does not exist in this collection.

TCannot acquire a managed connection.

�Cannot populate the result columns for a single row result type. The query returned an empty result set.

�There is an invalid number of result bindings returned for the ResultSetType: "%1!s!".

�The result binding name must be set to zero for full result set and XML results.

`The parameter directions flag is not valid.

lThe XML fragment does not contain SQL Task data.

�A parameter with type return value is not the first parameter, or there are more than one parameter of type return value.

tConnection "%1!s!" is not a file connection manager.

`File represented by "%1!s!" does not exist.

XType of variable "%1!s!" is not string.

xVariable "%1!s!" does not exist or could not be locked.

`Connection manager "%1!s!" does not exist.

(Failed to acquire connection "%1!s!". Connection may not be configured correctly or you may not have the right permissions on this connection.

�Result binding by name "%1!s!" is not supported for this connection type.

�A result set type of single row is specified, but no rows were returned.

�No disconnected record set is available for the Transact-SQL statement.

,Unsupported type.

$Unknown type.

�Parameter names cannot be an mix of ordinal and named types.

�The parameter direction on parameter binding \"%s\" is not valid.

�The data type on result set binding \"%s\" is not supported.

\The result column index %d is not valid.

dCannot find column \"%s\" in the result set.

�No result rowset is associated with the execution of this query.

�Disconnected recordsets are not available from ODBC connections.

�The data type in the result set, column %hd, is not supported.

PCannot load XML with query result.

�A connection name or variable name for the package must be specified.

DFailed to create the package.

\The TableMetaDataNode is not an XMLNode.

HFailed to create the pipeline.

TThe variable is not the correct type.

�The connection manager specified is not a FILE connection manager.

�Invalid file name specified on the connection manager "%1!s!".

�The connection is empty. Verify that a valid HTTP connection is specified.

�The connection does not exist. Verify that a valid, existing HTTP connection is specified.

�The connection specified is not a HTTP connection. Verify that a valid HTTP connection is specified.

�The Web Service name is empty. Verify that a valid web service name is specified.

�The web method name is empty. Verify that a valid web method is specified.

�The web method is empty or may not exist. Verify that there is an existing web method to specify.

�The output location is empty. Verify that an existing file connection or variable is specified.

�The variable cannot be found. Verify that the variable exists in the package.

�Cannot save the result. Verify that the variable is not read-only.

lError occurred in LoadFromXML at the tag "%1!s!".

hError occurred in SaveToXML at the tag "%1!s!".

dCannot save the task to a null XML document.

pCannot initialize the task with a null XML element.

�The Web Service Task is initiated with an incorrect XML element.

DUnexpected XML element found.

�There was an error acquiring the HTTP connection. Verify that a valid connection type is specified.

�Cannot save the result. Verify that there is an existing file connection.

tCannot save the result. Verify that the file exists.

�Cannot save the result. The file name is empty or the file is in use by another process.

�There was an error in acquiring the file connection. Verify that a valid file connection is specified.

�Only Complex Types with Primitive values, Primitive Arrays, and Enumerations are supported.

�Only Primitive, Enum, Complex, PrimitiveArray, and ComplexArray types are supported.

XThis version of WSDL is not supported.

`Initialized with an incorrect XML element.

PA mandatory attribute is not found.

�The enum "%1!s!" does not have any values. The WSDL is corrupted.

HThe connection cannot be found.

XConnection by this name already exists.

PConnection cannot be null or empty.

�The connection specified is not a HTTP connection. Verify that a valid HTTP connection is specified.

�The specified Uniform Resource Identifier (URI) does not contain a valid WSDL.

�Could not read the WSDL file. The input WSDL file is not valid. The reader threw the following error: "%1!s!".

PService Description cannot be null.

DService name cannot be null.

0URL cannot be null.

XThe service is not currently available.

hThe service is not available on the SOAP port.

�Failed to parse the Web Services Description Language (WSDL). Cannot find the Binding that corresponds to the SOAP port.

�Failed to parse the Web Services Description Language (WSDL). Cannot find a PortType that corresponds to the SOAP port.

�Cannot find the message that corresponds to the method specified.

Could not generate the proxy for the given web service. The following errors were encountered while generating the proxy "%1!s!".

�Could not load the proxy for the given web service. The exact error is as follows: "%1!s!".

�Could not find the specified service. The exact error is as follows: "%1!s!".

�The Web Service threw the following error during method execution: "%1!s!".

�Could not execute the web method. The exact error is as follows: "%1!s!".

@MethodInfo cannot be null.

0The specified WebMethodInfo is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue is not of type PrimitiveValue.

0The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found is not of type EnumValue.

8The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found is not of type ComplexValue.

4The WebMethodInfo specified is not correct. The ParamValue supplied does not match the ParamType. The DTSParamValue found is not of type ArrayValue.

�The WebMethodInfo you have specified is wrong. "%1!s!" is not Primitive Type.

�The format of the ArrayValue is not valid. There should be at least one element in the array.

�The value of the enumeration cannot be null. Select a default value for the enumeration.

dCannot validate a null against any datatype.

TThe enumeration Value is not correct.

�The class specified does not contain a public property by the name "%1!s!".

TCould not convert "%1!s!" to "%2!s!".

�Cleanup failed. The proxy that was created for the web service may not have been deleted.

�Could not create an object of type "%1!s!". Please check whether the default constructor exists.

D"%1!s!" is not a value type.

`Could not validate "%1!s!" against "%1!s!".

�The data type cannot be null. Specify the value of the data type to validate.

The ParamValue cannot be inserted at this position. The index specified might be lesser than zero or greater than the length.

LThe input WSDL file is not valid.

HSynchronization object failed.

<The WQL query is missing.

DThe destination must be set.

<No WMI connection is set.

|WMI Data Reader Task received an invalid task data node.

@The task failed validation.

DFile "%1!s!" does not exist.

`Connection manager "%1!s!" does not exist.

lVariable "%1!s!" is not of type string or object.

\Connection "%1!s!" is not of type "FILE".

\Connection "%1!s!" is not of type "WMI".

DFile "%1!s!" already exists.

TConnection manager "%1!s!" is empty.

�Variable "%1!s!" should be of type object to be assigned a data table.

hTask failed due to invalid WMI query: "%1!s!".

�Unable to write to variable "%1!s!" since it set to keep its original value.

HSynchronization object failed.

<The WQL query is missing.

HThe WMI connection is missing.

\The task failed to execute the WMI query.

�The WMI Event Watcher Task received a task data node that is not valid.

`Connection manager "%1!s!" does not exist.

DFile "%1!s!" does not exist.

XVariable "%1!s!" is not of type string.

\Connection "%1!s!" is not of type "FILE".

\Connection "%1!s!" is not of type "WMI".

DFile "%1!s!" already exists.

TConnection manager "%1!s!" is empty.

�Timeout of "%1!s!" second(s) occurred before event represented by "%2!s!".

8Watching for the Wql query caused the following system exception: "%1!s!". Check the query for errors or WMI connection for access rights/permissions.

\The Operations specified is not defined.

LThe connection type is not File.

tCannot get an XmlReader from the source XML document.

xCannot get an XmlReader from the changed XML document.

�Cannot get the XDL diffgram reader from the XDL diffgram XML.

8The node list is empty.

@The element was not found.

\The Operations specified is not defined.

`Unexpected content item in XPathNavigator.

XNo schema found to enforce validation.

�A validation error occurred when validating the instance document.

HSynchronization object failed.

DThe root nodes do not match.

�The Edit Script Operation type in the final Edit Script is not valid.

�CDATA nodes should be added with DiffgramAddSubtrees class.

�Comment nodes should be added with DiffgramAddSubtrees class.

�Text nodes should be added with DiffgramAddSubtrees class.

�Significant white space nodes should be added with DiffgramAddSubtrees class.

�Correct the OperationCost array so that it reflects the XmlDiffOperation enumeration.

TThere are no operations in the task.

�The document already contains data and should not be used again.

@The node type is not valid.

|The XML Task received a task data node that is not valid.

PVariable data type is not a String.

DCannot get encoding from XML.

<Source is not specified.

LSecond operand is not specified.

�Invalid XDL diffgram. "%1!s!" is an invalid path descriptor.

�Invalid XDL diffgram. No node matches the path descriptor "%1!s!".

�Invalid XDL diffgram. Expecting xd:xmldiff as a root element with namespace URI "%1!s!".

�The XDL diffgram is not valid. The srcDocHash attribute on the xd:xmldiff element is missing.

�The XDL diffgram is not valid. The options attribute on the xd:xmldiff element is missing.

�The XDL diffgram is not valid. The srcDocHash attribute has an invalid value.

�The XDL diffgram is not valid. The options attribute has an invalid value.

�The XDL diffgram is not applicable to this XML document. The rcDocHash value does not match.

�Invalid XDL diffgram; more than one node matches the "%1!s!" path descriptor on the xd:node or xd:change element.

�The XDL diffgram is not applicable to this XML document. A new XML declaration cannot be added.

�Internal Error. XmlDiffPathSingleNodeList can contain only one node.

�Internal Error. "%1!s!" nodes left after the Patch operation, expecting 1.

�The File/Text Produced by the XSLT is not a valid XmlDocument, thus can not be set as result of operation: "%1!s!".

tThere is no file associated with connection "%1!s!".

�Property "%1!s!" has no source Xml text; Xml Text is either invalid, null or empty string.

DFile "%1!s!" already exists.

XA source connection must be specified.

`A destination connection must be specified.

|The connection "%1!s!" could not be found in the package.

<The connection "%1!s!" specifies a SQL Server instance with a version that is not supported for transfer. Only versions 7, 2000, and 2005 are supported.

(The source connection "%1!s!" must specify a SQL Server instance with a version earlier than or the same as the destination connection "%2!s!".

TA source database must be specified.

�The source database "%1!s!" must exist on the source server.

\A destination database must be specified.

�The source database and the destination database can not be the same.

�The transfer file information %1!s! is missing the filename.

�The transfer file information %1!s! is missing the folder part.

�The transfer file information %1!s! is missing the network share part.

�The number of source transfer files and the number of destination transfer files must be the same.

`Enlisting in transactions is not supported.

�The following exception occurred during an offline database transfer: %1!s!.

dThe network share "%1!s!" could not be found.

�The network share "%1!s! could not be accessed. The error is: %2!s!.

�The user "%1!s!" must be a DBO or a sysadmin for "%2!s!" in order to perform an online database transfer.

�The user "%1!s!" must be a sysadmin on "%2!s!" to perform an offline database transfer.

�Full text catalogs can only be included when performing an offline database transfer between 2 SQL Server 2005 servers.

�The database "%1!s!" already exists on the destination server "%2!s!".

`At least one source file must be specified.

�Could not find the file "%1!s!" in the source database "%2!s!".

The database file "%1!s!" is already used by the source database. Source and destination databases cannot use the same database files.

�The operation requested is not allowed in systems compliant with U.S. FIPS 140-2.

�Executing the query "%1!s!" failed with the following error: "%2!s!". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

xError reading stored procedure names from the xml file.

|Invalid data node for the Transfer Stored Procedure task.

hConnection "%1!s!" is not of type "SMOServer".

pExecution failed with the following error "%1!s!".

�An error occurred with the following error message: "%1!s!".

DBulk insert execution failed.

<Invalid destination path.

�Can not create directory. User chose to fail the task if directory exists.

The task has a transaction option of "Required" and connection "%1!s!" is of type "ODBC". ODBC connections don't support transactions.

�An error occurred while assigning a value to variable "%1!s!": "%2!s!".

4The source is empty.

<The destination is empty.

\File or directory "%1!s!" does not exist.

�Variable "%1!s!" is used as a source or destination and is empty.

XFile or directory "%1!s!" was deleted.

HDirectory "%1!s!" was deleted.

�The variable "%1!s!" should be of type object to be assigned a data table.

xThe variable "%1!s!" does not have a string data type.

�There was an error acquiring the FTP connection. Verify that a valid connection type is specified in "%1!s!".

tThe FTP connection manager "%1!s!" can not be found.

�File usage type of connection "%1!s!" should be "%2!s!" for operation "%3!s!".

�The source server can not be the same as the destination server.

\There are no Error Messages to transfer.

�The lists of error messages and their corresponding languages are of different sizes.

<The error message id "%1!s!" is out of the allowed range of user defined error messages. User defined error message ids are between 50000 and 2147483647.

hThis task can not participate in a transaction.

tFailed to transfer some or all of the Error Messages.

�The error message "%1!s!" already exists at destination server.

�The error message "%1!s!" can not be found at source server.

pExecution failed with the following error: "%1!s!".

HFailed to transfer the Job(s).

HThere are no Jobs to transfer.

tThe job "%1!s!" already exists at destination server.

pThe job "%1!s!" can not be found at source server.

`The list of "Logins" to transfer is empty.

tCan not get the list of "Logins" from source server.

pLogin "%1!s!" already exists at destination server.

XLogin "%1!s!" does not exist at source.

dFailed to transfer some or all of the logins.

�Failed to transfer the stored procedure(s). More informative error should have been raised.

tStored Procedure "%1!s!" is not found at the source.

�Stored procedure "%1!s!" already exists at destination server.

`There are no stored procedures to transfer.

LFailed to transfer the object(s).

`The list of "Objects" to transfer is empty.

xStored procedure "%1!s!" does not exist at the source.

xStored procedure "%1!s!" already exists at destination.

�An error occurred while trying to get set the Stored Procedures list to transfer: "%1!s!".

`Rule "%1!s!" does not exist at the source.

`Rule "%1!s!" already exists at destination.

�An error occurred while trying to get set the Rules list to transfer: "%1!s!".

`Table "%1!s!" does not exist at the source.

dTable "%1!s!" already exists at destination.

�An error occurred while trying to get set the Tables list to transfer: "%1!s!".

`View "%1!s!" does not exist at the source.

`View "%1!s!" already exists at destination.

�An error occurred while trying to get set the Views list to transfer: "%1!s!".

�User Defined Function "%1!s!" does not exist at the source.

�User Defined Function "%1!s!" already exists at destination.

�An error occurred while trying to get set the User Defined Functions list to transfer: "%1!s!".

dDefault "%1!s!" does not exist at the source.

hDefault "%1!s!" already exists at destination.

�An error occurred while trying to get set the Defaults list to transfer: "%1!s!".

�User Defined Data Type "%1!s!" does not exist at the source.

�User Defined Data Type "%1!s!" already exists at destination.

�An error occurred while trying to get set the User Defined Data Types list to transfer: "%1!s!".

|Partition Function "%1!s!" does not exist at the source.

|Partition Function "%1!s!" already exists at destination.

�An error occurred while trying to get set the Partition Functions list to transfer: "%1!s!".

xPartition Scheme "%1!s!" does not exist at the source.

xPartition Scheme "%1!s!" already exists at destination.

�An error occurred while trying to get set the Partition Schemes list to transfer: "%1!s!".

dSchema "%1!s!" does not exist at the source.

dSchema "%1!s!" already exists at destination.

�An error occurred while trying to get set the Schemas list to transfer: "%1!s!".

lSqlAssembly "%1!s!" does not exist at the source.

pSqlAssembly "%1!s!" already exists at destination.

�An error occurred while trying to get set the SqlAssemblies list to transfer: "%1!s!".

�User Defined Aggregate "%1!s!" does not exist at the source.

�User Defined Aggregate "%1!s!" already exists at destination.

�An error occurred while trying to get set the User Defined Aggregates list to transfer: "%1!s!".

xUser Defined Type "%1!s!" does not exist at the source.

|User Defined Type "%1!s!" already exists at destination.

�An error occurred while trying to get set the User Defined Types list to transfer: "%1!s!".

|XmlSchemaCollection "%1!s!" does not exist at the source.

�XmlSchemaCollection "%1!s!" already exists at destination.

�An error occurred while trying to get set the XmlSchemaCollections list to transfer: "%1!s!".

�Objects of type "%1!s!" are only supported between SQL Server 2005 or newer servers.

DThe databases list is empty.

`Login "%1!s!" does not exist at the source.

dLogin "%1!s!" already exists at destination.

�An error occurred while trying to get set the Logins list to transfer: "%1!s!".

`User "%1!s!" does not exist at the source.

`User "%1!s!" already exists at destination.

�An error occurred while trying to get set the Users list to transfer: "%1!s!".

�The task can not have a retained connection manager in a transaction.

�Unable to obtain XML data from SQL Server as Unicode because the provider does not support the OUTPUTENCODING property.

�For the FTP operation "%1!s!", the FILE connection manager "%2!s!" can not be found.

�"Logins" are server level objects and can not be dropped first since the source and destination are the same server. Dropping objects first will remove the logins from the source as well.

�Parameter "%1!s!" cannot be negative. (-1) is used for the default value.

4Possible data truncation on parameter, "%1!d!". To prevent truncation, use a string variable instead of a datetime variable for the output parameter.

\A type conversion error occurred: "%1!s!"

�The value type (%1!s!) can only be converted to variables of type Object.

�An error occurred while setting up a binding for the "%1!s!" column. The binding status was "%2!s!".

$An error occurred while setting up a binding for the "%1!s!" column. The binding status was "%2!s!". The data flow column type is "%3!s!". The conversion from the OLE DB type of "%4!s!" to the destination column type of "%5!s!" might not be supported by this provider.

�Data Flow objects cannot be loaded. Check if Microsoft.SqlServer.PipelineXml.dll is properly registered.

\Column %1!s! does not have a valid cache

�Cannot update cache on input columns when the EnableCacheUpdate is false on the pipeline

�Data Flow objects cannot be saved. Check if Microsoft.SqlServer.PipelineXml.dll is properly registered.

LFailed to save Data Flow objects.

LFailed to load Data Flow objects

�Failed to save Data Flow objects. The specified format is not supported.

�Failed to load Data Flow objects. The specified format is not supported.

�Failed to set the XML persistence events property for the Data Flow objects.

�Failed to set the persistence XML DOM property for the Data Flow objects.

�Failed to set the persistence XML ELEMENT property for the Data Flow objects.

�Failed to set xml persistence properties for the Data Flow objects.

�Failed to get custom property collection for Data Flow components.

PAn execution tree contains a cycle.

�The %1!s! object "%2!s!" (%3!d!) is disconnected from the layout.

`The ID for the layout object is not valid.

�A required input object is not connected to a path object.

dPath '%1!s!' does not have a valid end point.

l%1!s! has an invalid synchronous input ID %2!d!.

x%1!s! has lineage ID %2!d!, but should have had %3!d!.

�The package contains two objects with the duplicate name of "%1!s!" and "%2!s!".

�The "%1!s!" and the "%2!s!" are in the same exclusion group, but they do not have the same synchronous input.

�Two objects in the same collection have a duplicate lineage ID of %1!d!. The objects are %2!s! and %3!s!.

DThe layout failed validation.

\One or more component failed validation.

|The layout and one or more components failed validation.

�The Data Flow task engine failed at startup because it cannot create one or more required threads.

tA thread failed to create a mutex at initialization.

|A thread failed to create a semaphore at initialization.

�The system reports %1!d! percent memory load. There are %2!s! bytes of physical memory with %3!s! bytes free. There are %4!s! bytes of virtual memory with %5!s! bytes free. The paging file has %6!s! bytes with %7!s! bytes free.

dA buffer failed while allocating %1!d! bytes.

\The Buffer Manager could not be created.

hBuffer Type %1!d! had a size of %2!I64d! bytes.

�%1!s! is marked as dangling, but has a path attached to it.

�%1!s! failed validation and returned error code 0x%2!8.8X!.

�%1!s! failed the post-execute phase and returned error code 0x%2!8.8X!.

�%1!s! failed the prepare phase and returned error code 0x%2!8.8X!.

�%1!s! failed the pre-execute phase and returned error code 0x%2!8.8X!.

�%1!s! failed the cleanup phase and returned error code 0x%2!8.8X!.

�%1!s! has lineage ID %2!d! that was not previously used in the Data Flow task.

�Cannot connect %1!s! to %2!s! because a cycle would be created.

The data type "%1!s!" cannot be compared. Comparison of that data type is not supported, so it cannot be sorted or used as a key.

�This thread has shut down and is not accepting buffers for input.

�SSIS Error Code DTS_E_THREADFAILED. Thread "%1!s!" has exited with error code 0x%2!8.8X!. There may be error messages posted before this with more information on why the thread has exited.

�SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "%1!s!" (%2!d!) failed with error code 0x%3!8.8X! while processing input "%4!s!" (%5!d!). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

dA set of virtual buffers cannot be realized.

�The number of threads required for this pipeline is %1!d!, which is more than the system limit of %2!d!. The pipeline requires too many threads as configured. There are either too many asynchronous outputs, or EngineThreads property is set too high. Split the pipeline into multiple packages, or reduce the value of the EngineThreads property.

�The data tap on path "%1!s!" failed with error code 0x%2!8.8X!.

�The data flow engine failed to create the data tap file "%1!s!" with error code 0x%2!8.8X!.

�The Data Flow engine scheduler cannot obtain a count of the sources in the layout.

�The Data Flow engine scheduler cannot obtain a count of the destinations in the layout.

�The component view is unavailable. Make sure the component view has been created.

The component view ID is incorrect. The component view may be out of synchronization. Try releasing the component view and recreating it.

tThis buffer is not locked and cannot be manipulated.

�The Data Flow task cannot allocate memory to build a buffer definition. The buffer definition had %1!d! columns.

�The Data Flow task cannot register a buffer type. The type had %1!d! columns and was for execution tree %2!d!.

�The UsesDispositions property cannot be changed from its initial value. This occurs when the XML is edited and the UsesDispositions value is modified. This value is set by the component when it is added to the package and is not allowed to change.

The Data Flow task failed to initialize a required thread and cannot begin execution. The thread previously reported a specific error.

The Data Flow task failed to create a required thread and cannot begin running. The usually occurs when there is an out-of-memory state.

�The synchronous input of "%1!s!" cannot be set to "%2!s!" because a cycle would be created.

lA custom property named "%1!s!" is invalid because there is a stock property with that name. A custom property cannot have the same name as a stock property on the same object.

LThe buffer was already unlocked.

�%1!s! failed initialization and returned error code 0x%2!8.8X!.

�%1!s! failed during shut down and returned error code 0x%2!8.8X!. A component failed to release its interfaces.

,SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on %1!s! returned error code 0x%2!8.8X!. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

hSSIS Error Code DTS_E_THREADCANCELLED. Thread "%1!s!" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled.

�Distributor for thread "%1!s!" failed to initialize property "%2!s!" on component "%3!s!" because of error 0x%8.8X. The distributor could not initialize the component's property and cannot continue running.

�The Data Flow task cannot register a view buffer type. The type had %1!d! columns and was for input ID %2!d!.

xThere is not enough memory to create an execution tree.

�There is not enough memory to insert an object into the hash table.

TThe object is not in the hash table.

�Cannot create a component view because another one already exists. Only one component view can exist at a time.

At input "%1!s!" (%2!d!), the virtual input column collection does not contain a virtual input column with lineage ID %3!d!.

pThe requested object has the incorrect object type.

�The buffer manager cannot create a temporary storage file on any path in the BufferTempStoragePath property. There is an incorrect file name or no permission or the paths have been full.

�The buffer manager could not seek to offset %1!d! in file "%2!s!". The file is damaged.

�The buffer manager cannot extend the file "%1!s!" to length %2!lu! bytes. There was insufficient disk space.

�The buffer manager cannot write %1!d! bytes to file "%2!s!". There was insufficient disk space or quota.

�The buffer manager cannot read %1!d! bytes from file "%2!s!". The file is damaged.

hBuffer ID %1!d! supports other virtual buffers and cannot be placed into sequential mode. IDTSBuffer100.SetSequentialMode was called on a buffer that supports virtual buffers.

�This operation could not be performed because buffer is in read-only mode. A read-only buffer cannot be modified.

�ID %1!s! cannot be set to %2!d! because a cycle would be created.

The buffer manager ran out of memory while trying to extend the table of buffer types. This is caused by an out-of-memory condition.

xThe buffer manager failed to create a new buffer type.

�The Data Flow engine scheduler failed to retrieve the execution tree with index %1!d! from the layout. The scheduler received a count containing more execution trees than actually exist.

xThe Data Flow task failed to create a buffer to call PrimeOutput for output "%3!s!" (%4!d!) on component "%1!s!" (%2!d!). This error usually occurs due to an out-of-memory condition.

4The Data Flow engine scheduler failed to create a thread object because not enough memory is available. This is caused by an out-of-memory condition.

lThe Data Flow engine scheduler cannot retrieve object with ID %1!d! from the layout. The Data Flow engine scheduler previously located an object that is now no longer available.

�The Data Flow task failed to prepare buffers for the execution tree node beginning at output "%1!s!" (%2!d!).

�The Data Flow task cannot create a virtual buffer to prepare for execution.

�The maximum ID has been reached. There are no more IDs available to assign to objects.

�The %1!s! is already attached and cannot be attached again. Detach it and try again.

Column name "%1!s!" on output "%2!s!" cannot be used because it conflicts with a column of the same name on synchronous input "%3!s!".

�The Data Flow task cannot to create a buffer to mark the end of the rowset.

xA managed user component has thrown exception "%1!s!".

,The Data Flow engine scheduler cannot allocate enough memory for the execution structures. The system was low on memory before execution started.

�An out-of-memory condition prevented the creation of the buffer object.

�An out-of-memory condition prevents the mapping of a buffer's lineage IDs to DTP_HCOL indexes.

�The "%1!s!" cannot cache the Variables collection and returned error code 0x%2!8.8X.

�The "%1!s!" failed to cache the component metadata object and returned error code 0x%2!8.8X!.

"%1!s!" has a non-zero SortKeyPosition, but its value (%2!ld!) is too large. It must be less than or equal to the number of columns.

xThe IsSorted property of %1!s! is set to TRUE, but the absolute values of the non-zero output column SortKeyPositions do not form a monotonically increasing sequence, starting at one.

�"%1!s!" failed validation and returned validation status "%2!s!".

Component "%1!s!" could not be created and returned error code 0x%2!8.8X! "%3!s!". Make sure that the component is registered correctly.

�The module containing "%1!s!" is not registered or installed correctly.

�The module containing "%1!s!" cannot be located, even though it is registered.

�The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script Component Editor by clicking Design Script button to cause binary code to be generated.

�The buffer manager cannot create a file to spool a long object on the directories named in the BLOBTempStoragePath property. Either an incorrect file name was provided, or there are no permissions, or the paths have been full.

�The SynchronousInputID property on "%1!s!" was %2!d!, and %3!d! was expected.

PNo object exists with the ID %1!d!.

�Unable to locate an object with ID %1!d! because of the error code 0x%2!8.8X!.

The code page %1!d! specified on output column "%2!s!" (%3!d!) is not valid. Select a different code page for output column "%2!s!".

�The EventInfos collection could not be cached by "%1!s!" and returned error code 0x%2!8.8X!.

�Component %1!s! failed to initialize due to error 0x%2!8.8X! "%3!s!".

�The name for "%1!s!" is a duplicate. All names must be unique.

�There is no output column associated with input column "%1!s!" (%2!d!).

("%1!s!" has a virtual buffer extending from a root source. There is an exclusion group that is not zero with a synchronous input that is zero.

�"%1!s!" cannot be an error output because error outputs cannot be placed on synchronous, non-exclusive outputs.

�A divide-by-zero error occurred. The right side operand evaluates to zero in the expression "%1!s!".

�The literal "%1!s!" is too large to fit into type %2!s!. The magnitude of the literal overflows the type.

�The result of the binary operation "%1!s!" on data types %2!s! and %3!s! exceeds the maximum size for numeric types. The operand types could not be implicitly cast into a numeric (DT_NUMERIC) result without loss of precision or scale. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

lThe result of the binary operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude of the result of the operation overflows the type of the result.

�The result of the function call "%1!s!" is too large to fit in type "%2!s!". The magnitude of the result of the function call overflows the type of the operand. An explicit cast to a larger type may be required.

The data types "%1!s!" and "%2!s!" are incompatible for binary operator "%3!s!". The operand types could not be implicitly cast into compatible types for the operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

�The data type "%1!s!" cannot be used with binary operator "%2!s!". The type of one or both of the operands is not supported for the operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

4There is a sign mismatch for the bitwise binary operator "%1!s!" in operation "%2!s!". Both operands for this operator must be positive or negative.

The binary operation "%1!s!" failed with error code 0x%2!8.8X!. An internal error occurred, or an out-of-memory condition exists.

�Attempt to set the result type of binary operation "%1!s!" failed with error code 0x%2!8.8X!.

`Comparing "%1!s!" to string "%2!s!" failed.

�The data type "%1!s!" cannot be used with unary operator "%2!s!". This operand type is not supported for the operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

The unary operation "%1!s!" failed with error code 0x%2!8.8X!. An internal error occurred, or there is an out-of-memory condition.

�Attempt to set the result type of unary operation "%1!s!" failed with error code 0x%2!8.8X!.

,The function "%1!s!" does not support the data type "%2!s!" for parameter number %3!d!. The type of the parameter could not be implicitly cast into a compatible type for the function. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�The function "%1!s!" was not recognized. Either the function name is incorrect or does not exist.

4The length %1!d! is not valid for function "%2!s!". The length parameter cannot be negative. Change the length parameter to zero or a positive value.

@The start index %1!d! is not valid for function "%2!s!". The start index value must be an integer greater than 0. Start index is one-based, not zero-based.

�The function "%1!s!" cannot perform the character mapping on string "%2!s!".

x"%1!s!" is not a valid date part for function "%2!s!".

tParameter number %1!d! of the function NULL with data type "%2!s!" is not valid. The parameters of NULL() must be static, and cannot contain dynamic elements such as input columns.

dParameter number %1!d! of the function NULL with data type "%2!s!" is not an integer. A parameter of NULL() must be an integer or a type that can be converted to an integer.

8Parameter number %1!d! of the function "%2!s!" is not static. This parameter must be static, and cannot contain dynamic elements such as input columns.

lParameter number %1!d! of the cast to data type "%2!s!" is not valid. The parameters of cast operators must be static, and cannot contain dynamic elements such as input columns.

`Parameter number %1!d! of the cast to data type "%2!s!" is not an integer. A parameter of a cast operator must be an integer or a type that can be converted to an integer.

�Cannot cast expression "%1!s!" from data type "%2!s!" to data type "%3!s!". The requested cast is not supported.

�Attempt to parse the expression "%1!s!" failed. The token "%2!s!" at line number "%3!s!", character number "%4!s!" was not recognized. The expression cannot be parsed because it contains invalid elements at the location specified.

�An error occurred when parsing the expression "%1!s!". The expression failed to parse for an unknown reason.

�Attempt to parse the expression "%1!s!" failed and returned error code 0x%2!8.8X!. The expression cannot be parsed. It might contain invalid elements or it might not be well-formed. There may also be an out-of-memory error.

The expression "%1!s!" is not valid and cannot be parsed. The expression may contain invalid elements or it may not be well-formed.

�There was no expression to compute. An attempt was made to compute or get the string of an empty expression.

�Attempt to compute the expression "%1!s!" failed with error code 0x%2!8.8X!.

|Attempt to generate a string representation of the expression failed with error code 0x%1!8.8X!. Failed when attempting to generate a displayable string that represents the expression.

�Cannot convert the expression result data type "%1!s!" to the column data type "%2!s!". The result of the expression should be written to an input/output column, but the data type of the expression cannot be converted to the data type of the column.

�The conditional expression "%1!s!" of the conditional operator has an invalid data type of "%2!s!". The conditional expression of the conditional operator must return a Boolean, which is type DT_BOOL.

0The data types "%1!s!" and "%2!s!" are incompatible for the conditional operator. The operand types cannot be implicitly cast into compatible types for the conditional operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

�Attempt to set the result type of conditional operation "%1!s!" failed with error code 0x%2!8.8X!.

�This buffer has been orphaned. The buffer manager has shut down, leaving an outstanding buffer and no cleanup will occur for the buffer. There is a potential for memory leaks and other problems.

@Attempt to find the input column named "%1!s!" failed with error code 0x%2!8.8X!. The input column specified was not found in the input column collection.

<Attempt to find the input column with lineage ID %1!d! failed with error code 0x%2!8.8X!. The input column was not found in the input column collection.

�The expression contains unrecognized token "%1!s!". If "%1!s!" is a variable, it should be expressed as "@%1!s!". The specified token is not valid. If the token is intended to be a variable name, it should be prefixed with the @ symbol.

tThe expression contains unrecognized token "#%1!d!".

�The variable "%1!s!" was not found in the Variables collection. The variable might not exist in the correct scope.

�Attempt to parse the expression "%1!s!" failed. The expression might contain an invalid token, an incomplete token, or an invalid element. It might not be well-formed, or might be missing part of a required element such as a parenthesis.

|The name for "%1!s!" is blank, and names cannot be blank.

@The "%1!s!" has the HasSideEffects property set to TRUE, but "%1!s!" is synchronous and cannot have side effects. Set the HasSideEffects property to FALSE.

8The value, %1!d!, specified for the code page parameter of the cast to data type "%2!s!", is not valid. The code page is not installed on the machine.

�The value %1!d! specified for the precision parameter of the cast to data type "%2!s!" is not valid. Precision must be in the range %3!d! to %4!d! and the precision value is out of range for the type cast.

The value %1!d! specified for the scale parameter of the cast to data type "%2!s!" is not valid. The scale must be in the range %3!d! to %4!d! and the scale value is out of range for the type cast. Scale must not exceed precision and must be positive.

�The IsSorted property for "%1!s!" is false, but %2!lu! of its output columns' SortKeyPositions are non-zero.

The code pages must match for operands of conditional operation "%1!s!" for type %2!s!. The code page of the left operand does not match the code page of the right operand. For the conditional operator on the specified type, the code pages must be the same.

dInput "%1!s!" (%2!d!) references input "%3!s!" (%4!d!), but they do not have the same number of columns. Input %5!d! has %6!d! columns, while input %7!d! has %8!d! columns.

dNo object exists with a lineage ID of %1!d!.

tThe output column for the file name cannot be found.

�The output column for the file name is not a null-terminated Unicode character string, which is data type DT_WSTR.

A distributor failed to give a buffer to thread "%1!s!" because of error 0x%2!8.8X!. The target thread is probably shutting down.

tThe LocaleID %1!ld! is not installed on this system.

,The string literal "%1!s!" contains an illegal hexadecimal escape sequence of "\x%2!s!". The escape sequence is not supported in string literals in the expression evaluator. The hexadecimal escape sequences must be of the form \xhhhh where h is a valid hexadecimal digit.

�The string literal "%1!s!" contains an illegal escape sequence of "\%2!c!". The escape sequence is not supported in string literals in the expression evaluator. If a backslash is needed in the string, use a double backslash, "\\".

�"%1!s!" contains no output columns. An asynchronous output must contain output columns.

�The "%1!s!" has a long object data type of DT_TEXT, DT_NTEXT, or DT_IMAGE, which is not supported.

�Output ID %1!d! was given multiple error output configurations. First %2!d! and %3!d!, then %4!d! and %5!d!.

�The OLE DB provider failed during the data type conversion verification for "%1!s!".

hThis buffer represents the end of the rowset and its row count cannot be altered. An attempt was made to call AddRow or RemoveRow on a buffer that has the end of rowset flag.

�The data type "%1!s!" is not supported in an expression. The specified type is not supported or is not valid.

�The PrimeOutput method on "%1!s!" returned success, but did not report an end of the rowset. There is an error in the component. It should have reported an end-of-row. The pipeline will shut down execution to avoid unpredictable results.

An overflow occurred while converting from data type "%1!s!" to data type "%2!s!". The source type is too large for the destination type.

Conversion from data type "%1!s!" to data type "%2!s!" is unsupported. The source type cannot be converted to the destination type.

�Error code 0x%1!8.8X! occurred attempting to convert from data type %2!s! to data type %3!s!.

The conditional operation "%1!s!" failed with error code 0x%2!8.8X!. There was an internal error or an out-of-memory error.

�Casting expression "%1!s!" from data type "%2!s!" to data type "%3!s!" failed with error code 0x%4!8.8X!.

�Evaluating function "%1!s!" failed with error code 0x%2!8.8X!.

�Parameter number %1!d! of the function "%2!s!" cannot be converted to a static value.

LThe error row disposition on "%1!s!" cannot be set to redirect the row when the fast load option is turned on, and the maximum insert commit size is set to zero.

$The code pages for operands of binary operator "%1!s!" for type "%2!s!" must match. Currently, the code page of the left operand does not match the code page of the right operand. For the specified binary operator on the specified type, the code pages must be the same.

�Retrieving the value of Variable "%1!s!" failed with error code 0x%2!8.8X!.

�The data type of variable "%1!s!" is not supported in an expression.

(Unable to cast expression "%1!s!" from data type "%2!s!" to data type "%3!s!" because the code page of the value being cast (%4!d!) does not match the requested result code page (%5!d!). The code page of the source must match the code page requested for the destination.

PThe default buffer size must be between %1!d! and %2!d! bytes. An attempt was made to set the DefaultBufferSize property to a value that is too small or too large.

@The default buffer maximum rows must be larger than %1!d! rows. An attempt was made to set the DefaultBufferMaxRows property to a value that is too small.

�The code page on %1!s! is %2!d! and is required to be %3!d!.

�Failed to assign %3!d! to the EngineThreads property of the Data Flow task. The value must be between %1!d! and %2!d!.

Parsing the expression "%1!s!" failed. The single quotation mark at line number "%2!s!", character number "%3!s!", was not expected.

�Parsing the expression "%1!s!" failed. The equal sign (=) at line number "%2!s!", character number "%3!s!", was not expected. A double equals sign (==) may be required at the location specified.

�Component "%1!s!" failed to cache the runtime object reference tracker collection and returned error code 0x%2!8.8X!.

�There are multiple input columns with the name "%1!s!". The desired input column must be specified uniquely as [Component Name].[%2!s!] or referenced by lineage ID. Currently, the input column specified exists on more than one component.

0Locating the input column named "[%1!s!].[%2!s!]" failed with error code 0x%3!8.8X!. The input column was not found in the input column collection.

`There are multiple variables with the name "%1!s!". The desired variable must be specified uniquely as @[Namespace::%2!s!]. The variable exists in more than one namespace.

The Data Flow engine scheduler failed to reduce the execution plan for the pipeline. Set the OptimizedMode property to false.

�The function SQRT cannot operate on negative values, and a negative value was passed to the SQRT function.

�The function LN cannot operate on zero or negative values, and a zero or negative value was passed to the LN function.

�The function LOG cannot operate on zero or negative values, and a zero or negative value was passed to the LOG function.

�The parameters passed to the function POWER cannot be evaluated and yield an indeterminate result.

�The runtime cannot provide a cancel event because of error 0x%1!8.8X!.

�The pipeline received a request to cancel and is shutting down.

�The result of the unary minus (negation) operation "%1!s!" exceeds the maximum size for result data type "%2!s!". The magnitude of the result of the operation overflows the type of the result.

�The placeholder "%1!s!" was found in an expression. This must be replaced with an actual parameter or operand.

�The length %1!d! specified for function "%2!s!" is negative, and is not valid. The length parameter must be positive.

�The repeat count %1!d! is negative and is not valid for function "%2!s!". The repeat count parameter cannot be negative.

�Reading the variable "%1!s!" failed with error code 0x%2!8.8X!.

�For operands of a binary operation, the data type DT_STR is supported only for input columns and cast operations. The expression "%1!s!" has a DT_STR operand that is not an input column or the result of a cast, and cannot be used in a binary operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�For operands of the conditional operator, the data type DT_STR is supported only for input columns and cast operations. The expression "%1!s!" has a DT_STR operand that is not an input column or the result of a cast, and cannot be used with the conditional operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�The occurrence count %1!d! is not valid for function "%2!s!". This parameter must be greater than zero.

�"%1!s!" failed to cache the LogEntryInfos collection and returned error code 0x%2!8.8X!.

�The date part parameter specified for function "%1!s!" is not valid. It must be a static string. The date part parameter cannot contain dynamic elements, such as input columns, and must be of type DT_WSTR.

The value %1!d! specified for the length parameter of the cast to data type %2!s! is negative and not valid. The length must be positive.

HThe value %1!d! specified for the code page parameter of the NULL function with data type "%2!s!" is not valid. The code page is not installed on the computer.

LThe value %1!d! specified for the precision parameter of the NULL function with data type "%2!s!" is out of range. Precision must be in the range %3!d! to %4!d!.

�The value %1!d! specified for the scale parameter of the NULL function with data type %2!s! is out of range. Scale must be in the range %3!d! to %4!d!. Scale must not exceed precision and must not be negative.

8The value %1!d! specified for the length parameter of the "NULL" function with data type %2!s! is negative and not valid. The length must be positive.

dThe %1!s! can't be assigned a negative value.

LThe "%1!s!" custom property for "%2!s!" cannot be set to true. The column data type must be one of the following: DT_I1, DT_I2, DT_I4, DT_I8, DT_UI1, DT_UI2, DT_UI4, DT_UI8, DT_DBTIMESTAMP, DT_DBTIMESTAMP2, DT_DBTIMESTAMPOFFSET, DT_DATE, DT_DBDATE, DT_DBTIME, DT_DBTIME2, or DT_FILETIME.

�The "%1!s!" cannot be reattached. Delete the path, add a new one, and attach it.

,The function "%1!s!" requires %2!d! parameters, not %3!d! parameter. The function name was recognized, but the number of parameters is not valid.

,The function "%1!s!" requires %2!d! parameter, not %3!d! parameters. The function name was recognized, but the number of parameters is not valid.

0The function "%1!s!" requires %2!d! parameters, not %3!d! parameters. The function name was recognized, but the number of parameters is not valid.

�Attempt to parse the expression "%1!s!" failed because there was an out-of-memory error.

�The %1!s! failed to be able to perform its required product level check and returned error code 0x%2!8.8X!.

�The %1!s! cannot run on the installed edition of Integration Services. It requires %2!s! or higher.

�A string literal in the expression exceeds the maximum allowed length of %1!d! characters.

�The variable %1!s! contains a string that exceeds the maximum allowed length of %2!d! characters.

�The %1!s! was found, but it does not support a required Integration Services interface (IDTSRuntimeComponent100). Obtain an updated version of this component from the component provider.

�Failed to configure data tap while the package is running.

xThe specified data flow path identification is invalid.

�There is already a data tap configuration on the given path. No more configurations are allowed.

�The data flow engine could not find the folder settings in the system registry for the data tap location.

dThe specified data tap file name is invalid.

`The registry key "%1!s!" cannot be opened.

@Cannot get the file name for the component with a CLSID of "%1!s!". Verify that the component is registered properly or that the CLSID provided is correct.

�The CLSID for one of the components is not valid. Verify that all the components in the pipeline have valid CLSIDs.

�The CLSID for one of the components with ID %1!d! is not valid.

8The index is not valid.

�The Application object cannot be accessed. Verify that SSIS is correctly installed.

�Retrieving the file name for a component failed with error code 0x%1!8.8X!.

�Cannot retrieve property "%1!s!" from component with ID %2!d!.

�Attempting to use ID %1!d! more than once in the Data Flow Task.

�Cannot retrieve an item by lineage ID from a collection that does not contain columns.

�Cannot find the connection manager with ID "%1!s!" in the connection manager collection due to error code 0x%2!8.8X!. That connection manager is needed by "%3!s!" in the connection manager collection of "%4!s!". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.

�Thread "%1!s!" received a buffer for input %2!d!, but this thread is not responsible for that input. An error occurred, causing the Data Flow engine scheduler to build a bad execution plan.

�The component "%1!s!" (%2!d!) cannot provide an IDTSRuntimeComponent100 interface.

�The Data Flow task engine attempted to copy a buffer to assign another thread, but failed.

�The Data Flow task engine failed to create a view buffer of type %1!d! over type %2!d! for buffer %3!d.

The buffer manager could not create a temporary file on the path "%1!s!". The path will not be considered for temporary storage again.

�The buffer manager attempted to push an error row to an output that was not registered as an error output. There was a call to DirectErrorRow on an output that does not have the IsErrorOut property set to TRUE.

�A call was made to a buffer method on a private buffer and private buffers do not support this operation.

pPrivate mode buffers do not support this operation.

`This operation cannot be called on a buffer passed to PrimeOutput. A call was made to a buffer method during PrimeOutput, but that call is not allowed during PrimeOutput.

dThis operation cannot be called on a buffer passed to ProcessInput. A call was made to a buffer method during ProcessInput, but that call is not allowed during ProcessInput.

xThe buffer manager could not get a temporary file name.

lThe code encountered a column that was too wide.

0Cannot get the ID of the runtime connection manager specified by "%1!s!" in the connection manager collection, Connections, of "%2!s!" due to error code 0x%3!8.8X!. Verify that the ConnectionManager.ID property of the runtime connection object has been set for the component.

�The "%1!s!" in the connection manager collection, Connections, of "%2!s!" does not have a value for the ID property. Verify that the ConnectionManagerID property of the runtime connection object has been set for the component.

dMetadata cannot be changed during execution.

The component metadata for "%1!s!" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

�The version of %1!s! is not compatible with this version of the DataFlow.

,The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "%1!s!".

�The method was called on the wrong buffer. Buffers that are not used for component output do not support this operation.

xAn error occurred during computation of the expression.

dDivision by zero occurred in the expression.

�The magnitude of the literal value was too big to fit in the type requested.

`The result of a binary operation was too big for the maximum size for numeric types. The operand types could not be implicitly cast into a numeric (DT_NUMERIC) result without loss of precision or scale. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

�The magnitude of the result of a binary operation overflows the maximum size for result data type.

lThe magnitude of the result of a function call was too big to fit in the result type, and overflowed the type of the operand. An explicit cast to a larger type may be required.

�Incompatible data types were used with a binary operator. The operand types could not be implicitly cast into compatible types for the operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

�An unsupported data type was used with a binary operator. The type of one, or both, of the operands is not supported for the operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

There is a sign mismatch for the bitwise binary operator. The operands for this operator must be both positive or both negative.

�A binary operation failed. There was an out-of-memory condition, or an internal error occurred.

tSetting the result type of a binary operation failed.

@Cannot compare two strings.

�An unsupported data type is used with a unary operator. The operand type is not supported for the operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�A unary operation failed. An out-of-memory condition occurred, or there was an internal error.

tSetting the result type of a unary operation failed.

�A function has a parameter with an unsupported data type. The type of the parameter cannot be implicitly cast into a compatible type for the function. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�An invalid function name appeared in the expression. Verify that the function name is correct and does exist.

�The length parameter was not valid for function SUBSTRING. The length parameter cannot be negative.

@The start index was not valid for function SUBSTRING. The start index value must be an integer greater than zero. The start index is 1-based, not 0-based.

An incorrect number of parameters was given to a function. The function name was recognized, but the number of parameters was not correct.

TA character mapping function failed.

�An unrecognized date part parameter was specified for a date function.

0An invalid parameter was given for function NULL. The parameters of NULL must be static, and cannot contain dynamic elements such as input columns.

An invalid parameter was given for function NULL. A parameter of NULL must be an integer, or a type that can be converted to an integer.

An invalid parameter was given for a function. This parameter must be static and cannot contain dynamic elements such as input columns.

DAn invalid parameter was given for a cast operation. Parameters of cast operators must be static, and cannot contain dynamic elements such as input columns.

8An invalid parameter was given for a cast operation. A parameter of a cast operator must be an integer, or a type that can be converted to an integer.

pThe expression contained an unsupported type cast.

The expression contained a token that was not recognized. The expression could not be parsed because it contains invalid elements.

�The expression is not valid and could not be parsed. It might contain invalid elements, or it might not be well-formed.

lThe result of a unary minus (negation) operation overflowed the maximum size for result data type. The magnitude of the result of the operation overflows the type of the result.

\Attempt to compute the expression failed.

�Attempt to generate a string representation of the expression failed.

�Cannot convert the expression result data type to the column data type. The result of the expression should be written to an input/output column, but the data type of the expression cannot be converted to the data type of the column.

The conditional expression of the conditional operator has invalid data type. The conditional expression must be of type DT_BOOL.

0The data types of the operands of the conditional operator were incompatible. The operand types could not be implicitly cast into compatible types for the conditional operation. To perform this operation, one or both operands need to be explicitly cast with a cast operator.

�Setting the result type of a conditional operation failed.

�The input column specified was not found in the input column collection.

�Attempt to find an input column by lineage ID failed. The input column was not found in the input column collection.

\The expression contains an unrecognized token that appears to be an input column reference, but the input column collection is not available to process input columns. The input column collection has not been provided to the expression evaluator, but an input column was included in the expression.

DA variable specified was not found in the collection. It might not exist in the correct scope. Verify that the variable exists and that the scope is correct.

�Attempt to parse the expression failed. The expression contains an invalid or incomplete token. It may contain invalid elements, be missing part of a required element such as closing parentheses, or may not be well formed.

PThe value specified for the code page parameter of the cast to data type DT_STR or DT_TEXT is not valid. The specified code page is not installed on the computer.

�The value specified for the precision parameter of a cast operation is out of range for the type cast.

DThe value specified for the scale parameter of a cast operation is out of range for the type cast. Scale must not exceed precision and must not be negative.

�The code pages do not match in a conditional operation. The code page of the left operand does not match the code page of the right operand. For the conditional operator of that type, the code pages must be the same.

�A string literal contains an illegal hexadecimal escape sequence. The escape sequence is not supported in string literals in the expression evaluator. Hexadecimal escape sequences must be of the form \xhhhh where h is a valid hexadecimal digit.

�The string literal contains an illegal escape sequence. The escape sequence is not supported in string literals in the expression evaluator. If a backslash is needed in the string, format it as a double backslash, "\\".

�An unsupported or unrecognized data type was used in the expression.

�An overflow occurred while converting between data types. The source type is too large to fit in the destination type.

�The expression contains an unsupported data type conversion. The source type cannot be converted to the destination type.

An error occurred while attempting to perform data conversion. The source type could not be converted to the destination type.

LThe conditional operation failed.

�An error occurred while attempting to perform a type cast.

XConverting "%1!s!" from type DT_STR to type DT_WSTR failed with error code 0x%2!8.8X!. An error occurred while performing the implicit conversion on the input column.

4Converting an input column from type DT_STR to type DT_WSTR failed. An error occurred while performing the implicit conversion on the input column.

lAn error occurred while evaluating the function.

0A function parameter cannot be converted to a static value. The parameter must be static and cannot contain dynamic elements such as input columns.

�The length parameter is not valid for function RIGHT. The length parameter cannot be negative.

�The repeat count parameter is not valid for function REPLICATE. This parameter cannot be negative.

�The code pages do not match in a binary operation. The code page of the left operand does not match the code page of the right operand. For this binary operation, the code pages must be the same.

`Retrieving the value for a variable failed.

�The expression contains a variable with an unsupported data type.

�Unable to cast the expression because the code page of the value being cast does not match the requested result code page. The code page of the source must match the code page requested for the destination.

�The expression contains an unexpected single quotation mark. A double quotation mark may be required.

�The expression contains an unexpected equal sign (=). This error usually occurs when a double equals sign (==) is needed.

hAn ambiguous input column name was specified. The column must be qualified as [Component Name].[Column Name] or referenced by lineage ID. This error occurs when the input column exists on more than one component, and must be differentiated by the addition of component name or by using the lineage ID.

A placeholder function parameter or operand was found in an expression. This should be replaced with an actual parameter or operand.

lAn ambiguous variable name was specified. The desired variable must be qualifed as @[Namespace::Variable]. This error occurs when the variable exists in more than one namespace.

tFor operands of binary operation, the data type DT_STR is only supported for input columns and cast operations. A DT_STR operand that is not an input column or the result of a cast cannot be used with a binary operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�For operands of the conditional operator, the data type DT_STR is only supported for input columns and cast operations. A DT_STR operand that is not an input column or the result of a cast cannot be used with the conditional operation. To perform this operation, the operand needs to be explicitly cast with a cast operator.

�The occurrence count parameter is not valid for function FINDSTRING. This parameter must be greater than zero.

�The "date part" parameter specified for a date function is not valid. "Date part" parameters must be static strings, and cannot contain dynamic elements such as input columns. They must be of type DT_WSTR.

�The value specified for the length parameter of a cast operation is not valid. The length must be positive. The length specified for the type cast is negative. Change to a positive value.

�The value specified for the length parameter of a NULL function is not valid. The length must be positive. The length specified for the NULL function is negative. Change to a positive value.

The value specified for the code page parameter of the NULL function with data type DT_STR or DT_TEXT is not valid. The code page specified is not installed on the computer. Either change the code page that is specified, or install the code page on the computer.

<The value specified for the precision parameter of a NULL function is not valid. The precision that was specified is out of range for the NULL function.

�The value specified for the scale parameter of a NULL function is not valid. The scale that was specified is out of range for the NULL function. Scale must not exceed precision and must be positive.

�The %1!s! failed attempting to write data to %2!s! on %3!s!. %4!s!

�Lookup transform has received a cancel request from the user.

�Processing of character or binary large object (LOB) data has stopped because the 4-GB limit was reached.

�The managed pipeline component "%1!s!" could not be loaded. The exception was: %2!s!.

PThe CanProcess method of the component (ID: %1!d!) returned false for all inputs. No further input data can be processed. Check the implementation of this method.

The GetDependentInputs method of the component (ID: %1!d!) returned a list that contains invalid number of input IDs (%2!d!). The number of IDs in the list cannot be 0 or more than the number of inputs minus 1. Check the implementation of this method.

tThe GetDependentInputs method of component (ID: %1!d!) returned a list that contains an input ID (%2!d!) that already reached end of rowset. Check the implementation of this method.

The component metadata for "%1!s!" could not be downgraded to the older version of the component. The PerformDowngrade method failed.

LSSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

The cache file is damaged, or the file was not created by using the Cache connection manager. Provide a valid cache file.

�Failed to execute the pacakge that has been deployed to the Integration Services catalog.

�The SQL command has not been set correctly. Check SQLCommand property.

�COM error object information is available. Source: "%1!s!" error code: 0x%2!8.8X! Description: "%3!s!".

`Unable to access the acquired connections.

PThe number of columns is incorrect.

lColumn "%1!s!" cannot be found at the datasource.

�An OLE DB record is available. Source: "%1!s!" Hresult: 0x%2!8.8X! Description: "%3!s!".

�SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x%1!8.8X!.

�Component is already connected. The component needs to be disconnected before attempting to connect it.

hThe value of the property "%1!s!" is incorrect.

LCannot open the datafile "%1!s!".

No destination flat file name was provided. Make sure the flat file connection manager is configured with a connection string. If the flat file connection manager is used by multiple components, ensure that the connection string contains enough file names.

xThe text qualifier for column "%1!s!" cannot be found.

tConversion from "%1!s!" to "%2!s!" is not supported.

�The error code 0x%1!8.8X! was returned when validating type conversion from %2!s! to %3!s!.

0Cannot find input column with lineage ID "%1!d!" which is needed by "%2!s!". Check SourceInputColumnLineageID custom property of the output column.

�The number of outputs is incorrect. There must be at least %1!d! outputs.

�The number of outputs is incorrect. There must be exactly %1!d! output(s).

XA string was too long to be converted.

�The number of inputs is incorrect. There must be exactly %1!d! inputs.

tThe number of input columns for %1!s! cannot be zero.

�This component has %1!d! inputs. No input is allowed on this component.

�ProcessInput was called with an invalid input ID of %1!d!.

xThe custom property "%1!s!" needs to be of type %2!s!.

�The buffer type is not valid. Make sure the Pipeline layout and all components pass validation.

pThe value for custom property "%1!s!" is incorrect.

xAn error occurred due to no connection. A connection is required when requesting metadata. If you are working offline, uncheck Work Offline on the SSIS menu to enable the connection.

hThe custom property "%1!s!" cannot be created.

�The custom property collection cannot be retrieved for initialization.

�Cannot create an OLE DB accessor. Verify that the column metadata is valid.

�PrimeOutput was called with an invalid output ID of %1!d!.

xThe value for property "%1!s!" on "%2!s!" is not valid.

XA connection is required to read data.

dAn error occurred while reading header rows.

HDuplicate column name "%1!s!".

lCannot get the name of the column with ID %1!d!.

dDirect row to output "%1!s!" (%2!d!) failed.

�Cannot create the bulk insert thread due to error "%1!s!".

�The thread for the SSIS Bulk Insert task failed initialization.

�The thread for the SSIS Bulk Insert task is already running.

�The thread for the SSIS Bulk Insert task terminated with errors or warnings.

�Failed to open a fastload rowset for "%1!s!". Check that the object exists in the database.

�Error due to no connection. A connection is required before metadata validation can proceed.

hA destination table name has not been provided.

The OLE DB provider used by the OLE DB adapter does not support IConvertType. Set the adapter's ValidateColumnMetaData property to FALSE.

�The OLE DB provider used by the OLE DB adapter cannot convert between types "%1!s!" and "%2!s!" for "%3!s!".

PColumn metadata validation failed.

�"%1!s!" is a row ID column and cannot be included in a data insertion operation.

�Attempting insertion into the row version column "%1!s!". Cannot insert into a row version column.

tFailure inserting into the read-only column "%1!s!".

�Unable to retrieve column information from the data source. Make sure your target table in the database is available.

�A buffer could not be locked. The system is out of memory or the buffer manager has reached its quota.

�The %1!s! has a ComparisonFlags property that includes extra flags with the value %2!d!.

pThe column metadata was unavailable for validation.

HCannot write to the data file.

xThe column delimiter for column "%1!s!" was not found.

tFailed to parse the column "%1!s!" in the data file.

|The file name is not properly specified. Supply the path and name to the raw file either directly in the FileName property or by specifying a variable in the FileNameVariable property.

�File "%1!s!" cannot be opened for writing. Error may occur when there are no file privileges or the disk is full.

An I/O buffer cannot be created for the output file. Error may occur when there are no file privileges or the disk is full.

�Cannot write %1!d! bytes to file "%2!s!". See previous error messages for details.

�Encountered bad metadata in file header. The file is damaged or not a SSIS-produced raw data file.

PError occurred because the output file already exists and the WriteOption is set to Create Once. Set the WriteOption property to Create Always, or delete the file.

�Error caused by conflicting property settings. Both the AllowAppend property and the ForceTruncate property are set to TRUE. Both properties cannot be set to TRUE. Set one of the two properties to FALSE.

�The file had bad version and flags information. The file is damaged or not a SSIS-produced raw data file.

(The output file was written by an incompatible version and cannot be appended. The file may be an older file format that is no longer useable.

$Cannot append output file because no column in the existing file matches column "%1!s!" from the input. Old file does not match in metadata.

dCannot append output file because the number of columns in the output file does not match the number of columns in this destination. The old file does not match in metadata.

�There was an error retrieving column code page information.

�Cannot read %1!d! bytes from file "%2!s!". The cause of the failure should have been previously reported.

$Unexpected end-of-file encountered while reading %1!d! bytes from file "%2!s!". The file ended prematurely because of an invalid file format.

�The column %1!s! cannot be used. The raw adapters do not support image, text, or ntext data.

DThe adapter encountered an unrecognized data type of %1!d!. This could be caused by a damaged input file (source) or by an invalid buffer type (destination).

String too long. The adapter read a string that was %1!d! bytes long, and expected a string no longer than %2!d! bytes, at offset %3!d!. This could indicate a damaged input file. The file shows a string length that is too large for the buffer column.

�The raw adapter attempted to skip %1!d! bytes in the input file for unreferenced column "%2!s!" with lineage ID %3!d!, but there was an error. The error returned from the operating system should have been previously reported.

�The raw adapter attempted to read %1!d! bytes in the input file for column "%2!s!" with lineage ID %3!d!, but there was an error. The error returned from the operating system should have been previously reported.

�The file name property is not valid. The file name is a device or contains invalid characters.

�Unable to bulk copy data. You may need to run this package as an administrator.

`Database object name "%1!s!" is not valid.

@Order clause is not valid.

TFile "%1!s!" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause is reported in previous error message.

�Unable to create the Microsoft.AnalysisServices.TimeDimGenerator.TimeDimGenerator.

�Unable to configure the Microsoft.AnalysisServices.TimeDimGenerator.

XUnsupported datatype for column %1!d!.

�The attempt to read from the Microsoft.AnalysisServices.TimeDimGenerator failed with error code 0x%1!8.8X!.

The attempt to read column "%2!d!" data from the Microsoft.AnalysisServices.TimeDimGenerator failed with error code 0x%2!8.8X!.

�The VariableName property is not set to the name of a valid variable. Need a runtime variable name to write to.

|Unable to create or configure the ADODB.Recordset object.

dError writing to the ADODB.Recordset object.

�The file name is not valid. The file name is a device or contains invalid characters.

�The file name "%1!s!" is not valid. The file name is a device or contains invalid characters.

�Unable to retrieve destination column descriptions from the parameters of the SQL command.

�Parameters are not bound. All parameters in the SQL command must be bound to input columns.

�The PivotUsage value for the input column "%1!s!" (%2!d!) is not valid.

�Too many Pivot Keys found. Only one input column can be used as the Pivot Key.

�No Pivot Key found. One input column must be used as the Pivot Key.

�More than one output column (such as "%1!s!" (%2!d!)) is mapped to input column "%3!s!" (%4!d!).

�Output column "%1!s!" (%2!d!) cannot be mapped to PivotKey input column.

�Output column "%1!s!" (%2!d!) has a SourceColumn %3!d! that is not a valid input column lineage ID.

�Output column "%1!s!" (%2!d!) is mapped to a Pivoted Value input column, but its PivotKeyValue property value is missing.

�Output column "%1!s!" (%2!d!) is mapped to a Pivoted Value input column with a non-unique PivotKeyValue property value.

�Input column "%1!s!" (%2!d!) is not mapped to any output column.

|Failure occurred while comparing values for the set keys.

�The Input column "%1!s!" (%2!d!) cannot be used as a Set Key, Pivot Key, or Pivot Value because it contains long data.

$Incorrect output type. The output column "%1!s!" (%2!d!) must have the same data type and metadata as the input column to which it is mapped.

lFailure when trying to pivot the source records.

\The pivot key value "%1!s!" is not valid.

`An error occurred while skipping data rows.

�An error occurred while processing file "%1!s!" on data row %2!I64d!.

�An error occurred while initializing the flat file parser.

�Unable to retrieve column information from the flat file connection manager.

�The column name for column "%1!s!" could not be written. The column name may be longer than the available column size.

�The column type for column "%1!s!" is incorrect. It is type "%2!s!". It can only be either "%3!s!" or "%4!s!".

�The attempt to write data of %1!d! bytes into the disk I/O failed. The disk I/O buffer has %2!d! free bytes.

tAn error occurred while writing out the file header.

�An error occurred while getting the file size for file "%1!s!".

�An error occurred while setting the file pointer for file "%1!s!".

xAn error occurred while setting up the disk I/O buffer.

�The column data for column "%1!s!" overflowed the disk I/O buffer.

�An unexpected disk I/O error occurred while reading the file.

tAn disk I/O time out occurred while reading the file.

The Usage Type specified for the input columns to this transform cannot be read/write. Change the Usage Type to be read-only.

|Cannot copy or convert flat file data for column "%1!s!".

�Data conversion failed. The data conversion for column "%1!s!" returned status value %2!d! and status text "%3!s!".

`The Variables collection is not available.

Duplicate PivotKeyValue. Input column "%1!s!" (%2!d!) is mapped to a Pivoted Value output column and has a non-unique PivotKeyValue.

No unpivot destination found. At least one input column must be mapped with a PivotKeyValue to an DestinationColumn in the output.

LPivotKeyValue is not valid. In an UnPivot transform with more than one unpivoted DestinationColumn, the set of PivotKeyValues per destination must match exactly.

�Incorrect UnPivot metadata. In an UnPivot transform, all input columns with a PivotKeyValue that is set, and are pointing to the same DestinationColumn, must have metadata that exactly matches the DestinationColumn.

�Cannot convert the pivot key value "%1!s!" to the data type of the pivot key column.

�Too many Pivot Keys specified. Only one output column can be used as the Pivot Key.

�Output column "%1!s!" (%2!d!) is not mapped by any input column's DestinationColumn property.

`No output column is marked as the PivotKey.

Input column "%1!s!" (%2!d!) has a DestinationColumn property value that does not refer to a valid output column LineageID.

�Duplicate destination error. More than one non-pivoted input column is mapped to the same destination output column.

�No input columns found. At least one input column must be mapped to an output column.

DThe number of input and output columns are not equal. The total number of input columns on all inputs must be the same as the total number of output columns.

�"%1!s!" must be sorted. If possible, sort the data at the source and mark the data as sorted by setting the IsSorted and SortKeyPosition properties in the Advanced Editor. Otherwise, add a Sort Transformation to the path before the merge.

$The JoinType custom property for the %1!s! contains a value of %2!ld!, which is not valid. Valid values are 0 (full), 1 (left), or 2 (inner).

The NumKeyColumns value is not valid. In the %1!s!, the value for the NumKeyColumns custom property must be between 1 and %2!lu!.

�No key columns are found. The %1!s! must have at least one column with a SortKeyPosition that is non-zero.

�Not enough key columns. The %1!s! must have at least %2!ld! columns with non-zero SortKeyPosition values.

�Datatype mismatch occurred. The datatypes for the columns with SortKeyPosition value %1!ld! do not match.

�The column with the SortKeyPosition value of %1!ld! is not valid. It should be %2!ld!.

�Sort direction mismatch. The sort directions for the columns with SortKeyPosition value %1!ld! do not match.

�Missing column. The %1!s! must have an associated input column.

Input columns must have output columns. There are input columns with a usage type of read-only that do not have associated output columns.

�The comparison flags are not zero. The comparison flags for non-string columns must be zero.

�The comparison flags for the columns with SortKeyPosition value %1!ld! do not match.

DUnrecognized pivot key value.

�Lineage item value %1!ld! is not valid. The valid range is between %2!ld! and %3!ld!.

�Input columns not allowed. The number of input columns must be zero.

�The datatype for "%1!s!" is not valid for the specified lineage item.

�The length for "%1!s!" is not valid for the specified lineage item.

�The metadata for "%1!s!" does not match the metadata for the associated output column.

�There are output columns that have SortKeyPosition values that don't match the associated input columns' SortKeyPosition.

�The attempt to add a row to the Data Flow task buffer failed with error code 0x%1!8.8X!.

HData conversion failed while converting column "%1!s!" (%2!d!) to column "%3!s!" (%4!d!). The conversion returned status value %5!d! and status text "%6!s!".

�The attempt to allocate a row handle buffer failed with error code 0x%1!8.8X!.

�The attempt to send a row to SQL Server failed with error code 0x%1!8.8X!.

�The attempt to prepare the buffer status failed with error code 0x%1!8.8X!.

�The attempt to retrieve the start of the buffer row failed with error code 0x%1!8.8X!.

The thread for the SSIS Bulk Insert is no longer running. No more rows can be inserted. Try increasing the bulk insert thread timeout.

xThe source file is not valid. The source file is returning a count of more than 131,072 columns. This usually occurs when the source file is not produced by the raw file destination.

�The %1!s! is an extra unattached input and will be removed.

�The %1!s! is not attached but is not marked as dangling. It will be marked as dangling.

PDuplicate pivot key value "%1!s!".

@Duplicate pivot key value.

�Failure retrieving component locale ID. Error code 0x%1!8.8X!.

�Mismatched locale IDs. The component locale ID (%1!d!) does not match the connection manager locale ID (%2!d!).

The component locale ID has not been set. Flat file adapters need to have the locale ID on the flat file connection manager set.

\The binary field is too large. The adapter attempted to read a binary field that was %1!d! bytes long, but expected a field no longer than %2!d! bytes at offset %3!d!. This usually occurs when the input file is not valid. The file contains a string length that is too large for the buffer column.

�The percentage, %2!ld!, is not valid for the "%1!s!" property. It must be between 0 and 100.

�The number of rows, %2!ld!, is not valid for the "%1!s!" property. It must be greater than 0.

The adapter was asked to write a string that was %1!I64d! bytes long, but all data must be less than 4294967295 bytes in length.

�No inputs were mapped to an output. The "%1!s!" must have at least one input column mapped to an output column.

�Conversion from "%1!s!" with code page %2!d! to "%3!s!" with code page %4!d! is not supported.

�The external metadata column mapping for %1!s! is not valid. The external metadata column ID cannot be zero.

�The %1!s! is mapped to an external metadata column that does not exist.

�Writing long object data of type DT_TEXT, DT_NTEXT, or DT_IMAGE to Data Flow task buffer failed for column "%1!s!".

�Opening a rowset for "%1!s!" failed. Check that the object exists in the database.

�Accessing variable "%1!s!" failed with error code 0x%2!8.8X!.

The connection manager "%1!s!" is not found. A component failed to find the connection manager in the Connections collection.

|The upgrade from version "%1!s!" to version %2!d! failed.

�A value in an input column is too large to be stored in the ADODB.Recordset object.

�Columns "%1!s!" and "%2!s!" cannot convert between unicode and non-unicode string data types.

�The variable "%1!s!" specified by VariableName property is not a valid variable. Need a valid variable name to write to.

$The variable "%1!s!" specified by VariableName property is not an integer. Change the variable to be of type VT_I4, VT_UI4, VT_I8, or VT_UI8.

�No column was specified to allow the component to advance through the file.

�The "%1!s!" has IsSorted set to TRUE, but the SortKeyPosition on all output columns are zero. Either change the IsSorted to FALSE, or select at least one output column to contain a non-zero SortKeyPosition.

�The "%1!s!" metadata does not match the metadata of the input column.

�The value of the specified variable cannot be located, locked, or set.

�The column "%1!s!" cannot be processed because more than one code page (%2!d! and %3!d!) are specified for it.

�The column "%1!s!" can't be inserted because the conversion between types %2!s! and %3!s! is not supported.

�Column "%1!s!" cannot convert between unicode and non-unicode string data types.

�The %1!s! cannot find the column with LineageID %2!ld! in its input buffer.

�The %1!s! cannot get the column information for column %2!lu! from its input buffer.

�The %1!s! cannot get the column information for column "%2!lu!" from its copy buffer.

�The %1!s! cannot register a buffer type for its copy buffer.

�The %1!s! cannot create a buffer to copy its data into for sorting.

�DataReader client has failed to call Read or has closed the DataReader.

xNo column information was returned by the SQL command.

�The %1!s! was unable to retrieve column information for the SQL command. The following error occurred: %2!s!

`A source table name has not been provided.

tThe cache index position, %1!d!, is not valid. For non-index columns, the index position should be 0. For index columns, the index position should be a sequential, positive number.

lThe index position, %1!d!, is a duplicate. For non-index columns, the index position should be 0. For index columns, the index position should be a sequential, positive number.

LAt least one index column should be specified for the Cache connection manager. To specify an index column, set the Index Position property of the cache column.

hCache index positions must be contiguous. For non-index columns, the index position should be 0. For index columns, the index position should be a sequential, positive number.

DThe property "%1!s!" cannot be set on "%2!s!". The property being set is not supported on the specified object. Check the property name, case, and spelling.

�The property type cannot be changed from the type that was set by the component.

�Output ID %1!d! failed during insert. The new output was not created.

Cannot delete output ID %1!d! from the output collection. The ID may not be valid, or the ID may have been the default or error output.

`Failed to set property "%1!s!" on "%2!s!".

�Failed to set the type of %1!s! to type: "%2!s!", length: %3!d!, precision: %4!d!, scale: %5!d!, codepage: %6!d!.

�More than one error output was found on the component, and there can be only one.

hThe property on an output column cannot be set.

�The data type for "%1!s!" cannot be modified in the error "%2!s!".

4The "%1!s!" cannot have its IsSorted property set to TRUE because it is not a source output. A source output has a SynchronousInputID value of zero.

The "%1!s!" cannot have a SortKeyPosition property set to non-zero because "%2!s!" is not a source output. The output column "colname" (ID) cannot have its SortKeyPosition property set to non-zero because its output "outputname" (ID) is not a source output.

The ComparisonFlags property cannot be set to a non-zero value for "%1!s!" because the "%2!s!" is not a source output. The output column "colname" (ID) cannot have a ComparisonFlags property set to non-zero because its output "outputname" (ID) is not a source output.

0The comparison flags for "%1!s!" must be zero because its type is not a string type. ComparisonFlags can only be non-zero for string type columns.

�The "%1!s!" cannot have a ComparisonFlags property set to non-zero because its SortKeyPosition is set to zero. An output column's ComparisonFlags can only be non-zero if its SortKeyPosition is also non-zero.

@The property is read-only.

tThe %1!s! had an invalid datatype value (%2!ld!) set.

�The "%1!s!" requires a code page to be set but the value passed was zero.

�The "%1!s!" has a length that is not valid. The length must be between %2!ld! and %3!ld!.

�The "%1!s!" has a scale that is not valid. The scale must be between %2!ld! and %3!ld!.

�The "%1!s!" has a precision that is not valid. The precision must be between %2!ld! and %3!ld!.

<The "%1!s!" has a value set for length, precision, scale, or code page that is a value other than zero, but the data type requires the value to be zero.

�The %1!s! does not allow setting output column datatype properties.

�The "%1!s!" contains an invalid data type. "%1!s! " is a special error column, and the only valid data type is DT_I4.

xThe component does not supply error code descriptions.

�The specified error code is not associated with this component.

�A truncation caused a row to be redirected, based on the truncation disposition settings.

The "%1!s!" is unable to make the column with lineage ID %2!d! read/write because that usage type is not allowed on this column. An attempt was made to change the usage type of an input column to a type, UT_READWRITE, that is not supported on this component.

�The %1!s! has forbidden the requested use of the input column with lineage ID %2!d!.

�The "%1!s!" was unable to make the requested change to the input column with lineage ID %2!d!. The request failed with error code 0x%3!8.8X!. The specified error occurred while attempting to set the usage type of an input column.

�Attempt to set the data type properties on "%1!s!" failed with error code 0x%2!8.8X!. The error occurred while attempting to set one or more of the data type properties of the output column.

�The metadata for "%1!s!" cannot be retrieved. Make sure the object name is correct and the object exists.

�The output column cannot be mapped to an external metadata column.

tThe variable %1!s! is required to be of type "%2!s!".

�The %1!s! does not allow setting external metadata column datatype properties.

\The ID, %1!lu!, is neither an input ID nor an output ID. The specified ID must be the input ID or the output ID that the external metadata collection is associated with.

�The external metadata collection on "%1!s!" is marked as not used, so no operations can be performed on it.

�The %1!s! is a synchronous output and the buffer type cannot be retrieved for a synchronous output.

�The input column "%1!s!" must be read-only. The input column has a usage type other than read-only, which is not allowed.

�The "%1!s!" is missing the required property "%2!s!". The object is required to have the specified custom property.

�The output %1!s! cannot not have property "%2!s!", but currently has that property assigned.

�The %1!s! must be in exclusion group %2!d!. All outputs must be in the specified exclusion group.

�The property "%1!s!" is empty. The property cannot be empty.

,Memory cannot be allocated for the expression "%1!s!". There was an out-of-memory error while creating an internal object to hold the expression.

�Cannot parse the expression "%1!s!". The expression was not valid, or there is an out-of-memory error.

�Computing the expression "%1!s!" failed with error code 0x%2!8.8X!. The expression may have errors, such as divide by zero, that cannot be detected at parse time, or there may be an out-of-memory error.

(Memory cannot be allocated for the Expression objects. An out-of-memory error occurred while creating the array of Expression object pointers.

�The %1!s! failed with error code 0x%2!8.8X! while creating the Expression Manager.

�The expression "%1!s!" is not Boolean. The result type of the expression must be Boolean.

hThe expression "%1!s!" on "%2!s!" is not valid.

(The column "%1!s!" (%2!d!) cannot be matched to any input file column. The output column name or input column name cannot be found in the file.

Attempting to set the result column for the expression "%1!s!" on %2!s! failed with error code 0x%3!8.8X!. The input or output column that was to receive the result of the expression cannot be determined, or the expression result cannot be cast to the column type.

xThe %1!s! failed to get the locale ID from the package.

�The parameter mapping string is not in the correct format.

�The SQL command requires %1!d! parameters, but the parameter mapping only has %2!d! parameters.

�The SQL command requires a parameter named "%1!s!", which is not found in the parameter mapping.

�There is more than one data source column with the name "%1!s!". The data source column names must be unique.

�There is a data source column with no name. Each data source column must have a name.

dA component is disconnected from the layout.

`The ID for a layout component is not valid.

dA component has an invalid number of inputs.

dA component has an invalid number of outputs.

lA component does not have any inputs or outputs.

�Not enough memory was available to allocate a list of the columns that are being manipulated by this component.

Output column "%1!s!" (%2!d!) references input column with lineage ID %3!d!, but no input could be found with that lineage ID.

�At least one input column must be marked as a sort key, but no keys were found.

�Both column "%1!s!" (%2!d!) and column "%3!s!" (%4!d!) were marked with sort key weight %5!d!.

�The component cannot perform the requested metadata change until the validation problem is fixed.

pAn input cannot be added to the inputs collection.

tAn output cannot be added to the outputs collection.

xAn input cannot be deleted from the inputs collection.

|An output cannot be removed from the outputs collection.

hThe usage type of the column cannot be changed.

�The %1!s! must be read/write to have custom property "%2!s!". The input or output column has the specified custom property, but is not read/write. Remove the property, or make the column read/write.

0The %1!s! is read/write and is required to have custom property "%2!s!". Add the property, or make remove the read/write attribute from the column.

�The column cannot be deleted. The component does not allow columns to be deleted from this input or output.

�The component does not allow adding columns to this input or output.

�The connection "%1!s!" cannot be found. Verify that the connection manager has a connection with that name.

<The runtime connection manager with the ID "%1!s!" cannot be found. Verify that the connection manager collection has a connection manager with that ID.

PSSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "%1!s!" failed with error code 0x%2!8.8X!. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

�The connection acquired from the connection manager "%1!s!" is not valid.

The connection manager "%1!s!" is an incorrect type. The type required is "%2!s!". The type available to the component is "%3!s!".

�Cannot acquire a managed connection from the run-time connection manager.

�An input cannot be created to initialize the inputs collection.

�An output cannot be created to initialize the outputs collection.

�Writing to the file "%1!s!" failed with error code 0x%2!8.8X!.

�The connection manager "%1!s!" returned an object of an incorrect type from the AcquireConnection method.

�The "%3!s!" property is required on input column "%1!s!" (%2!d!), but is not found. The missing property should be added.

�The "%1!s!" is marked read-only, but is not referenced by any other column. Unreferenced columns are not allowed.

The "%1!s!" references column ID %2!d!, and that column is not found on the input. A reference points to a nonexistent column.

�The "%1!s!" references "%2!s!", and that column is not of a BLOB type.

�The "%1!s!" references output column ID %2!d!, and that column is not found on the output.

�Reading from the file "%1!s!" failed with error code 0x%2!8.8X!.

�There must be at least one column of Fixed, Changing, or Historical type on the input of a Slowly Changing Dimension transform. Verify that at least one column is a FixedAttribute, ChangingAttribute, or HistoricalAttribute.

�The ColumnType property of "%1!s!" is not valid. The current value is outside the range of acceptable values.

�The input column "%1!s!" cannot be mapped to external column "%2!s!" because they have different data types. The Slowly Changing Dimension transform does not allow mapping between column of different types except for DT_STR and DT_WSTR.

\The data type for "%1!s!" is DT_NTEXT, which is not supported with ANSI files. Use DT_TEXT instead and convert the data to DT_NTEXT using the data conversion component.

`The data type for "%1!s!" is DT_TEXT, which is not supported with Unicode files. Use DT_NTEXT instead and convert the data to DT_TEXT using the data conversion component.

hThe data type for "%1!s!" is DT_IMAGE, which is not supported. Use DT_TEXT or DT_NTEXT instead and convert the data from, or to, DT_IMAGE using the data conversion component.

Format "%1!s!" is not supported by Flat File Connection Manager. Supported formats are Delimited, FixedWidth, RaggedRight, and Mixed.

�The "%1!s!" should contain a file name, but it is not of a String type.

�Error caused by conflicting property settings. The "%1!s!" has both the AllowAppend property and the ForceTruncate property set to TRUE. Both properties cannot be set to TRUE. Set one of the two properties to FALSE.

The %1!s! references column ID %2!d!, but that column is already referenced by %3!s!. Remove one of the two reference to the column.

|A connection manager has not been assigned to the %1!s!.

�The %1!s! references the output column with ID %2!d!, but that column is already referenced by %3!s!.

�The "%1!s!" is not referenced by any input column. Each output column must be referenced by exactly one input column.

XThe "%1!s!" references "%2!s!", and that column is not the correct type. It must be DT_TEXT, DT_NTEXT, or DT_IMAGE. A reference points to a column that must be a BLOB.

�The "%1!s!" should contain a file name, but it is not a String type.

@The "%1!s!" has the ExpectBOM property set to TRUE for %2!s!, but the column is not NT_NTEXT. The ExpectBOM specifies that the Import Column transformation expects a byte-order mark (BOM). Either set the ExpectBOM property to false or change the output column data type to DT_NTEXT.

�Data output columns must be DT_TEXT, DT_NTEXT, or DT_IMAGE. The data output column may only be set to a BLOB type.

�If the FailOnFixedAttributeChange property is set to TRUE, the transformation will fail when a fixed attribute change is detected. To send rows to the Fixed Attribute output, set the FailOnFixedAttributeChange property to FALSE.

,The Lookup transformation failed to retrieve any rows. The transform fails when the FailOnLookupFailure is set to TRUE and no rows are retrieved.

(There must be at least one column type of Key on the input of a Slowly Changing Dimension transformation. Set at least one column type to Key.

hCannot find external column with name "%1!s!".

�Inferred indicator column "%1!s!" must be of type DT_BOOL.

�The %1!s! must have its error row disposition value set to RD_NotUsed.

�The %1!s! must have its truncation row disposition value set to RD_NotUsed.

�Cannot find input column with lineage ID %1!d! needed by output column with ID %2!d!.

�Invalid output data type for aggregate type specified at output column ID %1!d!.

�Invalid input data type for %1!s! used for the specified aggregate at %2!s!.

�Data types of input column lineage ID %1!d! and output column ID %2!d! do not match.

pCannot get input buffer handle for input ID %1!d!.

tCannot get output buffer handle for output ID %1!d!.

�Cannot find column with lineage ID %1!d! in output buffer.

|Cannot find column with lineage ID %1!d! in input buffer.

xThe number of output columns for %1!s! cannot be zero.

The number of columns in the flat file connection manager must be the same as the number of columns in the flat file adapter. The number of columns for the flat file connection manager is %1!d!, while the number of columns for the flat file adapter is %2!d!.

4The column "%1!s!" at index %2!d! in the flat file connection manager was not found at index %3!d! in the column collection of the flat file adapter.

�The external metadata column with ID %1!d! has already been mapped to %2!s!.

�The transform encountered a key column that was larger than %1!u! characters.

�The transform encountered a result value that was longer than %1!u! bytes.

@Unable to allocate memory.

`The input column "%1!s!" is not referenced.

�The Sort transformation could not create a thread pool with %1!d! threads. Not enough memory is available.

�The Sort transformation cannot queue a work item to its thread pool. There is not enough memory available.

A worker thread in the Sort transformation stopped with error code 0x%1!8.8X!. A catastrophic error was encountered while sorting a buffer.

�MaxThreads was %1!ld!, and should be between 1 and %2!ld!, inclusive or -1 to default to the number of CPUs.

<Unable to load from XML.

8Unable to save to XML.

pUnable to convert the value "%1!s!" to an integer.

lUnable to convert the value "%1!s!" to a Boolean.

lLoad error encountered near object with ID %1!d!.

|The value "%1!s!" is not valid for the attribute "%2!s!".

dThe %1!s! is not mapped to an output column.

�The %1!s! has a mapping that is not valid. An output column with an ID of %2!ld! does not exist on this component.

`The %1!s! has no input column mapped to it.

�The %1!s! is mapped to an output column that already has a mapping on this input.

�Could not convert input column with Lineage ID %1!ld! to DT_WSTR due to error 0x%2!8.8X!.

tReferenced object with ID %1!d! not found in package.

�Cannot read a persistence property required for the pipelinexml module. The property was not provided by the pipeline.

|The value "%1!s!" is not valid for the attribute "%2!s!".

\Cannot retrieve custom property "%1!s!".

xAn input column with the lineage ID %1!d!, referenced in the ParameterMap custom property with the parameter on position number %2!d!, cannot be found in the input columns collection.

`Unable to locate reference column "%1!s!".

�%1!s! and reference column named "%2!s!" have incompatible data types.

�The parameterized SQL statement yields metadata which does not match the main SQL statement.

�The parameterized SQL statement contains an incorrect number of parameters. Expected %1!d!, but found %2!d!.

h%1!s! has a datatype which cannot be joined on.

d%1!s! has a datatype which cannot be copied.

�The %1!s! has an unsupported datatype. It must be DT_STR or DT_WSTR.

�The %1!s! has an unsupported datatype. It must be DT_STR, DT_WSTR, DT_TEXT, DT_NTEXT, or DT_IMAGE.

�The %1!s! has an unsupported datatype. It must be DT_STR, DT_WSTR, DT_TEXT, or DT_NTEXT.

@The Sort transformation cannot create an event to communicate with its worker threads. Not enough system handles are available to the Sort transformation.

�The Sort transformation cannot create a worker thread. Not enough memory is available to Sort transformation.

�The Sort transformation failed to compare row %1!d! in buffer ID %2!d! to row %3!d! in buffer ID %4!d!.

@The Lookup transformation reference metadata contains too few columns. Check the SQLCommand property. The SELECT statement must return at least one column.

�Unable to allocate memory for an array of ColumnInfo structures.

�Could not allocate memory for an array of ColumnPair structures.

�Unable to allocate memory for an array of BUFFCOL structures for the creation of a main workspace.

\Unable to create a main workspace buffer.

\Unable to allocate memory for hash table.

�Unable to allocate memory to create a heap for hash nodes.

hUnable to allocate memory for a hash node heap.

�Unable to create a heap for LRU nodes. An out-of-memory condition occurred.

�Unable to allocate memory for the LRU node heap. An out-of-memory condition occurred.

�OLE DB error occurred while loading column metadata. Check SQLCommand and SqlCommandParam properties.

�OLE DB error occurred while fetching rowset. Check SQLCommand and SqlCommandParam properties.

�OLE DB error occurred while populating internal cache. Check SQLCommand and SqlCommandParam properties.

�OLE DB error occurred while binding parameters. Check SQLCommand and SqlCommandParam properties.

�OLE DB error occurred while creating bindings. Check SQLCommand and SqlCommandParam properties.

�An invalid case was encountered in a switch statement during runtime.

�Unable to allocate memory for a new row for the main workspace buffer. An out-of-memory condition occurred.

�OLE DB error occurred while fetching parameterized rowset. Check SQLCommand and SqlCommandParam properties.

�OLE DB error occurred while fetching parameterized row. Check SQLCommand and SqlCommandParam properties.

�Unable to allocate memory for a new row for the main workspace buffer. An out-of-memory condition occurred.

\Unable to create a main workspace buffer.

dUnable to allocate memory for the hash table.

�Unable to allocate memory to create a heap for the hash nodes.

lUnable to allocate memory for the hash node heap.

�Unable to allocate memory to create a heap for CountDistinct nodes.

xUnable to allocate memory for CountDistinct node heap.

�Unable to allocate memory to create a heap for CountDistinct chains.

xUnable to allocate memory for CountDistinct hash table.

�Unable to allocate memory for a new row for the CountDistinct workspace buffer.

pUnable to create a CountDistinct workspace buffer.

�Unable to allocate memory for CountDistinct Collapse array.

pUnable to allocate memory for CountDistinct chains.

�Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column for copymap does not have the same metadata (datatype, precision, scale, length, or codepage).

0The output column with lineage ID "%1!d!" is incorrectly mapped to an input column. The CopyColumnId property of the output column is not correct.

lFailed to retrieve long data for column "%1!s!".

�Long data was retrieved for a column but cannot be added to the Data Flow task buffer.

�Output "%1!s!" (%2!d!) has output columns, but multicast outputs do not declare columns. The package is damaged.

�Unable to load a localized resource ID %1!d!. Verify that the RLL file is present.

�Cannot acquire Events Interface. An invalid Events interface was passed to the data flow module for persisting to XML.

�An error occurred while setting a path object during XML load.

`Error setting input object during XML load.

dError setting output object during XML load.

pError setting input column object during XML load.

pError setting output column object during XML load.

hError setting property object during XML load.

lError setting connection object during XML load.

�Special transformation-specific columns are either missing or have incorrect types.

�Fuzzy Grouping transformation failed to create required tables and accessors.

pFuzzy Grouping transformation failed to copy input.

|Fuzzy Grouping transformation failed to generate groups.

�An unexpected error occurred in Fuzzy Grouping when applying the settings of property '%1!s!'.

�The Fuzzy Grouping transformation failed to pick a canonical row of data to use in standardizing the data.

�Fuzzy Grouping does not support input columns of type IMAGE, TEXT, or NTEXT.

�A fuzzy match is specified on column "%1!s!" (%2!d!) that is not a data type of DT_STR or DT_WSTR.

�A Fuzzy Grouping transformation pipeline error occurred and returned error code 0x%1!8.8X!: "%2!s!".

�The code page %1!d! specified on column "%2!s!" (%3!d!) is not supported. You must first convert this column to DT_WSTR which can be done by inserting a Data Conversion Transform before this one.

�Failure encountered while setting end of data flag for the buffer driving output "%1!s!" (%2!d!).

�The input buffer could not be cloned. An out-of-memory condition occurred or there was an internal error.

�Column "%1!s!" requests that Katakana and Hiragana characters be produced at the same time.

�Column "%1!s!" requests that Simple Chinese and Traditional Chinese characters be produced at the same time.

�Column "%1!s!" requests operations to generate both full width and half width characters.

�Column "%1!s!" combines operations on Japanese characters with operations for Chinese characters.

�Column "%1!s!" combines operations on Chinese characters with uppercase and lowercase operations.

�Column "%1!s!" combines operations on Japanese characters with uppercase and lowercase operations.

�Column "%1!s!" maps the column to both uppercase and lowercase.

�Column "%1!s!" combines flags other than uppercase and lowercase with the linguistic casing operation.

�The data type of column "%1!s!" cannot be mapped as specified.

�The version (%1!s!) of the pre-existing match index "%2!s!" is not supported. The version expected is "%3!s!". This error occurs if the version persisted in the index metadata does not match the version which the current code was built for. Fix the error by rebuilding the index with the current version of the code.

TThe table "%1!s!" does not appear to be a valid pre-built match index. This error occurs if the metadata record cannot be loaded from the specified pre-built index.

�Unable to read specified pre-built match index "%1!s!". OLEDB Error code: 0x%2!8.8X!.

�There were no input columns with a valid join to a reference table column. Make sure that there is at least one join defined using the input column properties JoinToReferenceColumn and JoinType.

The specified pre-existing match index "%1!s!" was not originally built with fuzzy match information for column "%2!s!". It must be rebuilt to include this information. This error occurs when the index was built with the column not being a fuzzy join column.

�The name "%1!s!" given for property "%2!s!" is not a valid SQL identifier name. This error occurs if the name for the property does not conform to the specifications for a valid SQL identifier name.

The MinSimilarity threshold property on the Fuzzy Lookup transformation must be a value greater than or equal to 0.0 but less than 1.0.

tThe value "%1!s!" for property "%2!s!" is not valid.

�The fuzzy lookup specified between input column "%1!s!" and reference column "%2!s!" is not valid because fuzzy joins are only supported between string columns, types DT_STR and DT_WSTR.

�The exact lookup columns, "%1!s!" and "%2!s!", do not have equal data types or are not comparable string types. Exact joins are supported between columns with equal data types or a DT_STR and DT_WSTR combination.

@The copy columns, "%1!s!" and "%2!s!", do not have equal data types or are not trivially convertible string types. This occurs because copying from reference to output between columns with equal data types, or a DT_STR and DT_WSTR combination, is supported, but other types are not.

\The passthrough columns, "%1!s!" and "%2!s!", do not have equal data types. Only columns with equal data types are supported as passthrough columns from input to output.

XCannot locate reference column "%1!s!".

An output column must have exactly one CopyColumn or PassThruColumn property specified. This error occurs when neither the CopyColumn or the PassThruColumn properties, or both the CopyColumn and PassThruColumn properties, are set to non-empty values.

The source lineage id '%1!d!' specified for property '%2!s!' on output column '%3!s!' was not found in the input column collection. This occurs when the input column id specified on an output column as a passthrough column is not found in the set of inputs.

�The column "%1!s!" in the pre-built index "%2!s!" was not found in the reference table/query. This happens if the schema/query of the reference table has changed since the pre-existing match index was built.

�The component encountered a token that was larger than 2147483647 characters.

�The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has type %2!s! and the input column has type %3!s!. The metadata for the column does not match on data type.

�The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has maximum length %2!d! and the input column has maximum length %3!d!. The metadata for the column does not match in length.

�The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has code page %2!d! and the input column has code page %3!d!. The metadata for the named column does not match on code page.

�The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has precision %2!d! and the input column has precision %3!d!. The metadata for the named column does not match on precision.

�The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has scale %2!d! and the input column has scale %3!d!. The metadata for the named column does not match on scale.

pUnable to determine the DBMS name and version on "%1!s!". This occurs if the IDBProperties on the connection did not return information needed to verify the DBMS name and version.

�The DBMS type or version of "%1!s!" is not supported. A connection to Microsoft SQL Server version 8.0 or later is required. This occurs if IDBProperties on the connection did not return a the correct version.

�The %1!s! is a special error output column and cannot be deleted.

�The data type specified for column "%1!s!" is not the expected type "%2!s!".

,The input column lineage ID "%1!s!" referenced by property "%2!s!" on output column "%3!s!" could not be located in the input column collection.

TThe input column "%1!s!" referenced by the "%2!s!" property on output column "%3!s!" must have property ToBeCleaned=True and have a valid ExactFuzzy property value.

The reference table '%1!s!' does not have a clustered index on an integer identity column, which is required if the property 'CopyRefTable' is set to FALSE. If CopyRefTable is false, the reference table must have a clustered index on an integer identity column.

pThe reference table '%1!s!' contains a non-integer type identity column which is not supported. Use a view of the table without the column '%2!s!'. This error occurs because when a copy is made of the reference table, an integer identity column is added, and only one identity column is allowed per table.

`Both MatchContribution and hierarchy information cannot be specified at the same time. This is not allowed because these properties are both weighing factors for scoring.

hLevels in hierarchy should be unique numbers . Valid level in hierarchy values are integers greater than or equal to 1. The smaller the number is, the lower the column is in the hierarchy. The default value is 0, indicating that the column is not part of a hierarchy. Overlaps and gaps are not allowed.

$No columns to fuzzy group on were defined. There must be at least one input column with column properties ToBeCleaned=true and ExactFuzzy=2.

�The column with ID '%1!d!' was not valid for an undetermined reason.

lThe data type of column '%1!s!' is not supported.

�The length of output column '%1!s!' is less than that of its source column '%2!s!'.

XThere should be only one input column.

`There should be exactly two output columns.

�The input column can only have DT_WSTR or DT_NTEXT as its data type.

�The output column [%1!d!] can only have '%2!s!' as its data type.

�The reference column can only have DT_STR or DT_WSTR as its data type.

�An error occurred while locating the reference column '%1!s!'.

�The Term Type of the transformation can only be WordOnly, PhraseOnly or WordPhrase.

�The value of Frequency Threshold should not be lower than '%1!d!'.

�The value of Max Length of Term should not be lower than '%1!d!'.

�Term Extraction reference metadata contains too few columns.

`An error occurred while allocating memory.

tAn error occurred while creating a workspace buffer.

lAn OLEDB error occurred while creating bindings.

hAn OLEDB error occurred while fetching rowsets.

|An OLEDB error occurred while populating internal cache.

LAn error occurred while extracting terms on row %1!ld!, column %2!ld!. The error code returned was 0x%3!8.8X!. Please remove it from the input as a work-around.

|The number of the term candidates exceeds its limit, 4G.

�The reference table, view, or column that is used for Exclusion Terms is not valid.

�The length of string column '%1!s!' exceeds 4000 characters. A conversion from DT_STR to DT_WSTR is necessary, so a truncation would occur. Either reduce the column width or use only DT_WSTR column types.

�The reference table, view, or column to be used for an Exclusion Terms has not been set.

dTerm Lookup contains too few output columns.

�The reference column can only have DT_STR or DT_WSTR as its data type.

�An error occurred while locating the reference column '%1!s!'.

|Term Lookup reference metadata contains too few columns.

`An error occurred while normalizing words.

tAn error occurred while creating a workspace buffer.

lAn OLEDB error occurred while creating bindings.

hAn OLEDB error occurred while fetching rowsets.

|An OLEDB error occurred while populating internal cache.

LAn error occurred while looking up terms on row %1!ld!, column %2!ld!. The error code returned was 0x%3!8.8X!. Please remove it from the input as a work-around.

�At least one Passthrough column is not mapped to an output column.

�There should be exactly one input column mapped to one reference column.

�The input column mapped to a reference column can only have DT_NTXT or DT_WSTR as its data type.

�The reference table name "%1!s!" is not a valid SQL identifier. This error occurs if the table name cannot be parsed from the input string. There may be unquoted spaces in the name. Verify that the name is correctly quoted.

�An error occurred while the Term Filter was starting its iteration.

�An error occurred while reclaiming the buffer used for caching terms. The error code returned was 0x%1!8.8X!.

xAn std::length_error occurred from the STL containers.

�An error occurred while saving words with punctuation characters. The error code returned was 0x%1!8.8X!.

tAn error occurred while processing the %1!ld!th reference term. The error code returned was 0x%2!8.8X!. Please remove the reference term from your reference table as a work-around.

�An error occurred while sorting reference terms. The error code returned was 0x%1!8.8X!.

�An error occurred while counting term candidates. The error code returned was 0x%1!8.8X!.

�Fuzzy Lookup was unable to load the entire reference table into main memory as is required when the Exhaustive property is enabled. Either we ran out of system memory or a limit was specified for MaxMemoryUsage which was not sufficient to load the reference table. Either set MaxMemoryUsage to 0 or increase it significantly. Alternatively, disable Exhaustive.

�An error occurred while initializing the engine of Term Lookup. The error code returned was 0x%1!8.8X!.

�An error occurred while processing sentences. The error code returned was 0x%1!8.8X!.

�An error occurred while adding strings to an internal buffer. The error code returned was 0x%1!8.8X!.

�An error occurred while saving part-of-speech tags from an internal buffer. The error code returned was 0x%1!8.8X!.

�An error occurred while counting term candidates. The error code returned was 0x%1!8.8X!.

�An error occurred while initializing the part-of-speech processor. The error code returned was 0x%1!8.8X!.

�An error occurred while loading the finite state automata. The error code returned was 0x%1!8.8X!.

�An error occurred while initializing the engine of Term Extraction. The error code returned was 0x%1!8.8X!.

�An error occurred while processing within a sentence. The error code returned was 0x%1!8.8X!.

�An error occurred while initializing the part-of-speech processor. The error code returned was 0x%1!8.8X!.

�An error occurred while adding strings to an internal buffer. The error code returned was 0x%1!8.8X!.

�An error occurred while adding words to a statistical decoder. The error code returned was 0x%1!8.8X!.

�An error occurred while decoding for a sentence. The error code returned was 0x%1!8.8X!.

�An error occurred while setting exclusion terms. The error code returned was 0x%1!8.8X!.

�An error occurred while processing a document in the input. The error code returned was 0x%1!8.8X!.

�An error occurred while testing whether a dot is a part of an acronym. The error code returned was 0x%1!8.8X!.

�An error occurred while setting reference terms. The error code returned was 0x%1!8.8X!.

�An error occurred while processing a document in the input. The error code returned was 0x%1!8.8X!.

�The value for the property %1!s! is %2!d!, which is not allowed. The value must be greater than or equal to %3!d!.

�The value for the property %1!s! is %2!d!, which must be less than or equal to the value of %3!d! for property %4!s!.

�An error was encountered when trying to delete the existing fuzzy match index named "%1!s!". It is possible that this table was not created by Fuzzy Lookup (or this version of Fuzzy Lookup), it has been damaged, or there is another problem. Try manually deleting the table named "%2!s!" or specify a different name for the MatchIndexName property.

�The Score Type of the transformation can only be Frequency or TFIDF.

xThe reference table specified has too many rows. Fuzzy Lookup only works with reference tables having less than 1 billion rows. Consider using a smaller view of your reference table.

Unable to determine the size of the reference table '%1!s!'. It is possible that this object is a view and not a table. Fuzzy Lookup does not support views when CopyReferentaceTable=false. Make sure that the table exists and that CopyReferenceTable=true.

�The SSIS Data Flow Task data type "%1!s!" on the %2!s! is not supported for the %3!s!.

$Unable to set data type properties for the output column with ID %1!d! on the output with ID %2!d!. The output or column could not be found.

�The value of custom property "%1!s!" on the %2!s! cannot be changed.

�The %1!s! on the non-error output has no corresponding output column on the error output.

�The %1!s! on the error output has no corresponding output column on the non-error output.

�The %1!s! on the error output has properties that do not match the properties of its corresponding data source column.

�The data type of output columns on the %1!s! cannot be changed, except for DT_WSTR and DT_NTEXT columns.

�The data type of "%1!s!" does not match the data type "%2!s!" of the source column "%3!s!".

�The %1!s! does not have a matching source column in the schema.

�The reference table/view or column used for the reference terms is invalid.

�The reference table/view or column used for the reference terms has not been set.

�The %1!s! is mapped to the external metadata column with ID %2!ld!, which is already mapped to another column.

The SQL object name '%1!s!' specified for property '%2!s!' contains more than the maximum number of prefixes. The maximum is 2.

dThe value was too large to fit in the column.

HThe SSIS IDataReader is closed.

xThe SSIS IDataReader is past the end of the result set.

lThe ordinal position of the column is not valid.

�Cannot convert the %1!s! from data type "%2!s!" to data type "%3!s!".

`The %1!s! has unsupported code page %2!d!.

`The %1!s! has no mapping to the XML schema.

�Columns with lineage IDs %1!d! and %2!d! have mismatched metadata. The input column that is mapped to an output column does not have the same metadata (datatype, precision, scale, length, or codepage).

�The SSIS IDataReader is closed. The read timeout has expired.

�An error occurred executing the provided SQL command: "%1!s!". %2!s!

�The JoinType property specified for input column '%1!s!' differs from the JoinType specified for the corresponding reference table column when the Match Index was initially created. Either rebuild the Match Index with the given JoinType or change the JoinType to match the type used when the Match Index was created.

�The data type "%1!s!" found on column "%2!s!" is not supported for the %3!s!.

�The data type "%1!s!" found on %2!s! is not supported for the %3!s!.

�The data type of the %1!s! is not supported for the %2!s!.

�Failed to add project reference "%1!s!" while migrating %2!s!. Migration might need to be completed manually.

Multiple entry points with the name "%1!s!" were found during the migration of %2!s!. Migration might need to be completed manually.

�No entry point was found during the migration of %1!s!. Migration might need to be completed manually.

�ADO NET Source has failed to acquire the connection %1!s! with the following error message: "%2!s!".

�An exception has occurred during data insertion, the message returned from the provider is: %1!s!

�Failed to retrieve the provider invariant name from %1!s!, it is currently not supported by ADO NET Destination component

An argument exception has occurred while data provider tried to insert data to destination. The returned message is : %1!s!

tThe BatchSize property must be a non-negative integer

�An error has occurred while sending this row to destination data source.

�Executing tSQL command throws an exception, the message is : %1!s!

�The data type "%1!s!" found on column "%2!s!" is not supported for the %3!s!.

�ADO NET Destination has failed to acquire the connection %1!s! with the following error message: "%2!s!".

�The specified connection %1!s! is not managed, please use managed connection for ADO NET destination.

�The destination component does not have an error output. It may have been corrupted.

�The lineageID %1!s! associated with external column %2!s! does not exist at run time.

�The %1!s! does not exist in the database. It may have been removed or renamed.

Failed to get properties of external columns. The table name you entered may not exist, or you do not have SELECT permission on the table object and an alternative attempt to get column properties through connection has failed. Detailed error messages are: %1!s!

�Input column error disposition is not supported by ADO NET Destination component.

�Input column truncation disposition is not supported by ADO NET Destination component.

�Input truncation row disposition is not supported by ADO NET Destination component.

The Table or View name is not expected. \n\t If you are quoting the table name, please use the prefix %1!s! and the suffix %2!s! of your selected data provider for quotation. \n\t If you are using multipart name, please use at most three parts for the table name.

pAn exception occurred while initializing the SqlBulkCopy interface. Disable SqlBulkCopy by setting the UseBulkInsertWhenPossible property to false. The exception message is: %1!s!

�Failed to find column "%1!s!" with lineage ID %2!d! in the buffer. The buffer manager returned error code 0x%3!8.8X!.

�Failed to get information for column "%1!s!" (%2!d!) from the buffer. The error code returned was 0x%3!8.8X!.

�Arithmetic overflow encountered while aggregating "%1!s!".

�Failed to get information for row %1!ld!, column %2!ld! from the buffer. The error code returned was 0x%3!8.8X!.

�Failed to set information for row %1!ld!, column %2!ld! into the buffer. The error code returned was 0x%3!8.8X!.

PA required buffer is not available.

�The attempt to get buffer boundary information failed with error code 0x%1!8.8X!.

�Setting the end of rowset for the buffer failed with error code 0x%1!8.8X!.

hFailed to get data for the error output buffer.

�Removing a row from the buffer failed with error code 0x%1!8.8X!.

�The attempt to set buffer error information failed with error code 0x%1!8.8X!.

�There was an error with %1!s! on %2!s!. The column status returned was: "%3!s!".

PUnable to cache reference metadata.

PRow yielded no match during lookup.

�The %1!s! has an invalid error or truncation row disposition.

�Directing the row to the error output failed with error code 0x%1!8.8X!.

�Preparing column statuses for insert failed with error code 0x%1!8.8X!.

�An attempt to find %1!s! with lineage ID %2!d! in the Data Flow Task buffer failed with error code 0x%3!8.8X!.

tFailed to find any non-special error column in %1!s!.

�SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "%1!s!" failed because error code 0x%2!8.8X! occurred, and the error row disposition on "%3!s!" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.

�The "%1!s!" failed because truncation occurred, and the truncation row disposition on "%2!s!" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

�The expression "%1!s!" on "%2!s!" evaluated to NULL, but the "%3!s!" requires a Boolean results. Modify the error row disposition on the output to treat this result as False (Ignore Failure) or to redirect this row to the error output (Redirect Row). The expression results must be Boolean for a Conditional Split. A NULL expression result is an error.

�The expression evaluated to NULL, but a Boolean result is required. Modify the error row disposition on the output to treat this result as False (Ignore Failure) or to redirect this row to the error output (Redirect Row). The expression results must be Boolean for a Conditional Split. A NULL expression result is an error.

�The file format of UTF-16 big endian is not supported. Only UTF-16 little endian format is supported.

tThe file format of UTF-8 is not supported as Unicode.

<Cannot read ID attribute.

�The cache index column %1!s! is referenced by more than one lookup input column.

,Lookup does not reference all cache connection manager index columns. Number of joined columns in lookup: %1!d!. Number of index columns: %2!d!.

�The data value cannot be converted for reasons other than sign mismatch or data overflow.

hThe data value violated the schema constraint.

8The data was truncated.

�Conversion failed because the data value was signed and the type used by the provider was unsigned.

�Conversion failed because the data value overflowed the type used by the provider.

8No status is available.

�The user did not have the correct permissions to write to the column.

�The data value violated the integrity constraints for the column.

8No status is available.

�The data value cannot be converted for reasons other than sign mismatch or data overflow.

8The data was truncated.

�Conversion failed because the data value was signed and the type used by the provider was unsigned.

�Conversion failed because the data value overflowed the type used by the provider.

hThe data value violated the schema constraint.

�The data value cannot be converted for reasons other than sign mismatch or data overflow.

8The data was truncated.

�Conversion failed because the data value was signed and the type used by the provider was unsigned.

�Conversion failed because the data value overflowed the type used by the provider.

8No status is available.

�The user did not have the correct permissions to write to the column.

hThe data value violates integrity constraints.

�The data value cannot be converted for reasons other than sign mismatch or data overflow.

8The data was truncated.

�Conversion failed because the data value was signed and the type used by the provider was unsigned.

�Conversion failed because the data value overflowed the type used by the data conversion transform.

8No status is available.

�The data value cannot be converted for reasons other than sign mismatch or data overflow.

8The data was truncated.

�Conversion failed because the data value was signed and the type used by the flat file source adapter was unsigned.

�Conversion failed because the data value overflowed the type used by the flat file source adapter.

8No status is available.

�Opening the file "%1!s!" for reading failed with error code 0x%2!8.8X!.

LFailed to open file for reading.

�Opening the file "%1!s!" for writing failed with error code 0x%2!8.8X!.

LFailed to open file for writing.

<Failed to read from file.

<Failed to write to file.

Too many array elements were found when parsing a property of type array. The elementCount is less than the number of array elements found.

Too few array elements were found when parsing a property of type array. The elementCount is more than the number of array elements found.

�Opening the file "%1!s!" for writing failed. The file cannot be found.

�Opening the file for writing failed. The file cannot be found.

�Opening the file "%1!s!" for writing failed. The path cannot be found.

�Opening the file for writing failed. The path cannot be found.

�Opening the file "%1!s!" for writing failed. There are too many files open.

�Opening the file for writing failed. There are too many files open.

�Opening the file "%1!s!" for writing failed. You do not have the correct permissions.

�Opening the file for writing failed. You do not have the correct permissions.

�Opening the file "%1!s!" for writing failed. The file exists and cannot be overwritten. If the AllowAppend property is FALSE and the ForceTruncate property is set to FALSE, the existence of the file will cause this failure.

�Opening a file for writing failed. The file already exists and cannot be overwritten. If both the AllowAppend property and the ForceTruncate property are set to FALSE, the existence of the file will cause this failure.

�The value for custom property "%1!s!" on %2!s! is incorrect.

xColumns "%1!s!" and "%2!s!" have incompatible metadata.

Opening the file "%1!s!" for writing failed because the disk is full. There is not sufficient disk space to save this file.

�Attempting to open the file for writing failed because the disk is full.

Generating a sort key failed with error 0x%1!8.8X!. The ComparisonFlags are enabled, and generating a sortkey with LCMapString failed.

�Transform failed to map string and returned error 0x%1!8.8X!. The LCMapString failed.

�Opening the file "%1!s!" for reading failed. The file was not found.

�Opening a file for reading failed. The file was not found.

�Opening the file "%1!s!" for reading failed. The path cannot be found.

�Opening a file for reading failed. The path was not found.

�Opening the file "%1!s!" for reading failed. There are too many files open.

�Opening the file for reading failed. There are too many files open.

�Attempting to open the file "%1!s!" for reading failed. Access is denied.

�Opening the file for reading failed. You do not have the correct permissions.

�The byte order mark (BOM) value for the file "%1!s!" is 0x%2!4.4X!, but the expected value is 0x%3!4.4X!. The ExpectBOM property was set for this file, but the BOM value in the file is missing or not valid.

HThe byte order mark (BOM) value for the file is not valid. The ExpectBOM property was set for this file, but the BOM value in the file is missing or not valid.

�The %1!s! is not attached to a component. It is required that a component be attached.

�The value for custom property %1!s! is incorrect. It should be a number between %2!d! and %3!I64d!.

�The custom property "%1!s!" cannot be specified for the aggregation type selected for this column. The comparison flags custom property can only be specified for group by and count distinct aggregation types.

�The comparison flags custom property "%1!s!" can only be specified for columns of with datatype DT_STR or DT_WSTR.

xAggregation on %1!s! failed with error code 0x%2!8.8X!.

lThere was an error setting up the mapping. %1!s!

`The %1!s! was unable to read the XML data.

�The %1!s! was unable to get the variable specified by the "%2!s!" property.

�The %1!s! contains a RowsetID with a value of %2!s! that does not reference a data table in the schema.

�The property %1!s! must either be empty, or a number between %2!u! and %3!u!. The Keys or CountDistinctKeys property has a invalid value. The property should be a number between 0 and ULONG_MAX, inclusive, or not be set.

�The aggregate component encountered too many distinct key combinations. It cannot accommodate more than %1!u! distinct key values. There are more than ULONG_MAX distinct key values in the main workspace.

The aggregate component encountered too many distinct values while calculating the count distinct aggregate. It cannot accommodate more than %1!u! distinct values. There were more than ULONG_MAX distinct values while calculating the count distinct aggregation.

�The attempt to write to the filename column failed with error code 0x%1!8.8X!.

�An error occurred, but the column that caused the error cannot be determined.

pUnable to upgrade lookup metadata from version %1!d! to %2!d!. The Lookup transform was unable to upgrade metadata from the existing version number in a call to PerformUpgrade().

pFailed to locate the ending boundary of a sentence.

dThe Term Extraction transformation is unable to process the input text because a sentence from the input text is too long. The sentence is segmented into several sentences.

lThe %1!s! was unable to read the XML data. %2!s!

�The call to Lookup transform method, ReinitializeMetadata, failed.

DThe lookup transform must contain at least one input column joined to a reference column, and none were specified. You must specify at least one join column.

The message string being posted by the managed error infrastructure contains a bad format specification. This is an internal error.

TWhile formatting a message string using the managed error infrastructure, there was a variant type that does not have formatting support. This is an internal error.

hThe %1!s! was unable to process the data. %2!s!

dThe property "%1!s!" on the %2!s! was empty.

Attempting to create an output with the name "%1!s!" for the XML table with the path "%2!s!" failed because the name is invalid.

dThe value was too large to fit in the %1!s!.

\The %1!s! was unable to process the data.

�The "%1!s!" failed because truncation occurred, and the truncation row disposition on "%2!s!" at "%3!s!" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

�The "%1!s!" failed because error code 0x%2!8.8X! occurred, and the error row disposition on "%3!s!" at "%4!s!" specifies failure on error. An error occurred on the specified object of the specified component.

�The SQLCE destination could not set the column values for the row.

hThe SQLCE destination could not insert the row.

xEncountered OLEDB error while loading column metadata.

pLookup reference metadata contains too few columns.

xEncountered OLEDB error while loading column metadata.

pLookup reference metadata contains too few columns.

@Unable to allocate memory.

PUnable to create workspace buffer.

�Unable to instantiate XML DOM document, please verify that MSXML binaries are properly installed and registered.

|Unable to load XML data into a local DOM for processing.

�The type of the runtime variable "%1!s!" is incorrect. The runtime variable type must be Object.

�The XML Source Adapter was unable to process the XML data. Multiple inline schemas are not supported.

�The XML Source Adapter was unable to process the XML data. The content of an element can not be declared as anyType.

The XML Source Adapter was unable to process the XML data. The content of an element can not contain a reference (ref) to a group.

�The XML Source Adapter does not support mixed content model on Complex Types.

The XML Source Adapter was unable to process the XML data. An inline schema must be the first child node in the source Xml.

DThe XML Source Adapter was unable to process the XML data. No inline schema was found in the source XML, but the "UseInlineSchema" property was set to true.

�The component cannot use a connection manager that retains its connection in a transaction with fastload or bulk insert.

�The %1!s! cannot be set to redirect on error using a connection in a transaction.

�The %1!s! does not have a corresponding input or output column.

xThere is no selected column to be written to the file.

The %1!s! has an invalid data type. Columns with data types DT_IMAGE, DT_TEXT and DT_NTEXT cannot be written to raw files.

�The external metadata collection is improperly used by this component. The component should use external metadata when appending or truncating an existing file. Otherwise, the external metadata is not needed.

|The %1!s! is mapped to an external metadata column with the id %2!d!. Input columns should not be mapped to external metadata columns when selected Write Option value is Create Always.

�The file cannot be opened for reading the metadata. If the file does not exist, and the component has already defined external metadata, you can set the "ValidateExternalMetadata" property to "false" and the file will be created at the runtime.

�Failed to access LOB data from the data flow buffer for data source column "%1!s!" with error code 0x%2!8.8X!.

pThe %1!s! was unable to process the XML data. %2!s!

�The XML Source Adapter was unable to process the XML data.

|The value %1!d! is not recognized as a valid access mode.

,Complete metadata information for the data source column "%1!s!" is not available. Make sure the column is correctly defined in the data source.

`Only lengths of User Name column, Package Name column, Task Name column and Machine Name column can be changed. All other audit column datatype information is read only.

�A rowset based on the SQL command was not returned by the OLE DB provider.

,A commit failed.

�The custom property "%1!s!" on %2!s! can only be used with ANSI files.

�The custom property "%1!s!" on %2!s! can only be used with DT_BYTES.

4The requested OLE DB provider %2!s! is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode. Error code: 0x%1!8.8X!.

4The requested OLE DB provider %2!s! is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x%1!8.8X!.

�The cache column, "%1!s!", is mapped to more than one column. Remove the duplicate column mappings.

hThe %1!s! is not mapped to valid cache column.

�Cannot map the input column, "%1!s!", and the cache column, "%2!s!", because the data types do not match.

�The number of input columns does not match the number of cache columns.

�The cache file name is either not provided or is not valid. Provide a valid cache file name.

�The index position of column, "%1!s!", is different from index position of Cache connection manager column, "%2!s!".

dFailed to load the cache from file, "%1!s!".

�The lookup input column %1!s! references non-index cache column %2!s!.

TFailed to get the connection string.

Cannot map the input column, "%1!s!", and the cache column, "%2!s!", because one or more data type properties do not match.

lCache column "%1!s!" was not found in the cache.

�Failed to map %1!s! to a cache column. The hresult is 0x%2!8.8X!.

�The %1!s! cannot write to the cache because the cache has been loaded from a file by %2!s!.

�The %1!s! cannot load the cache from file "%2!s!" because the cache has already been loaded from file "%3!s!".

8The output with ID %1!d! of Aggregate component is not used by any component. Please either remove it or associate it with an input of some component.

�The %1!s! failed to write the cache to file "%2!s!". The hresult is 0x%3!8.8X!.

PThe XML schema data type information for "%1!s!" on element "%2!s!" has changed. Please re-initialize the metadata for this component and review column mappings.

�%1!s! not used in join or copy. Please remove the unused column from the input column list.

,The sort failed due to a stack overflow while sorting an incoming buffer. Please reduce the DefaultBufferMaxRows property on the Data Flow Task.

0Consider changing the PROVIDER in the connection string to %1!s! or visit http://www.microsoft.com/downloads to find and install support for %2!s!.

�The file "%1!s!" was not found. Please verify the file path and try again.

�Select a table or view that contains the reference dataset, or specify a SQL statement to generate the reference dataset

Inferred indicator column "%1!s!" contains a null value. Inferred indicator columns should be Boolean columns without null values.

tThe error "%1!s!" occurred while processing "%2!s!".

tA hashtable with %1!lu! entries could not be created.

dAn expected attribute "%1!s!" was not found.

`An expected element "%1!s!" was not found.

8No status is available.

�Conversion failed because the data value was signed and the type used by the driver was unsigned.

�Conversion failed because the data value overflowed the type used by the driver.

8No status is available.

�Conversion failed because the data value was signed and the type used by the driver was unsigned.

�Conversion failed because the data value overflowed the type used by the driver.

8No status is available.

�Conversion failed because the data value was signed and the type used by the driver was unsigned.

�Conversion failed because the data value overflowed the type used by the driver.

8No status is available.

�Conversion failed because the data value was signed and the type used by the driver was unsigned.

�Conversion failed because the data value overflowed the type used by the driver.

�The total number of outputs and error outputs, %1!lu!, is incorrect. There must be exactly %2!lu!.

\Cannot retrieve output with index %1!lu!.

�The number of error outputs, %1!lu!, is incorrect. There must be exactly %2!lu!.

�Incorrect validation status value, "%1!lu! ". It must be one of the values found in the DTSValidationStatus enumeration.

dThe input "%1!lu!" has no synchronous output.

pThe input "%1!lu!" has no synchronous error output.

�The HowToProcessInput value, %1!lu!, is not valid. It must be one of the values from the HowToProcessInput enumeration.

�Failed to get information for row "%1!ld!", column "%2!ld!" from the buffer. The error code returned was 0x%3!8.8X!.

�Failed to set information for row "%1!ld!", column "%2!ld!" into the buffer. The error code returned was 0x%3!8.8X!.

PThe property "%1!s!" is not valid.

PThe property "%1!s!" was not found.

�Error assigning a value to the read-only property "%1!s!".

|The %1!s! does not allow the insertion of output columns.

The output columns' metadata does not match the associated input columns' metadata. The output columns' metadata will be updated.

�There are input columns that do not have associated output columns. The output columns will be added.

�There are output columns that do not have associated input columns. The output columns will be removed.

�The output columns' metadata does not match the associated input columns' metadata. The input columns will be unmapped.

�There are input columns that do not have associated output columns. The input columns will be unmapped.

4There is an input column associated with an output column, and that output column is already associated with another input column on the same input.

�The %1!s! does not allow the insertion of external metadata columns.

|4VS_VERSION_INFO������?�StringFileInfo�040904B0PlatformNT�ILegalTrademarksMicrosoft SQL Server is a registered trademark of Microsoft Corporation. CommentsSQL&GoldenBitsTrueLCompanyNameMicrosoft CorporationZFileDescriptionDTS - Messages Resourcesx,FileVersion2019.0150.2000.05 ((SQLServer).190924-2033).InternalNameDtsMsgd LegalCopyrightMicrosoft. All rights reserved.>OriginalFilenameDtsMsg.RllJProductNameMicrosoft SQL Server<ProductVersion15.0.2000.5DVarFileInfo$Translation �<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level='asInvoker' uiAccess='false' />
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
8?0�?+ *�H��
��?0�?10 +0L
+�7�>0<0
+�70 ���0!0 +]�@-_�}:��)�wU��T���0��0� 3 ������ 0
*�H��
0w10 UUS10U
Washington10URedmond10U
Microsoft Corporation1!0UMicrosoft Time-Stamp PCA0
180823202028Z
191123202028Z0��10 UUS10 UWA10URedmond10U
Microsoft Corporation1-0+U$Microsoft Ireland Operations Limited1&0$UThales TSS ESN:86DF-4BBC-93351%0#UMicrosoft Time-Stamp service0�"0
*�H��
�0�
��F
j��ܜ��\#�URf4��5�*���2u�d�'2aܸ=��
Z_I���� o���4V;@N�ջP�7U�Gc�$���ӊ�]�{���kDMԱFA�Cq�U�V���+#��@![3j��ݳ�2�M2_;ڐ�ٶ]�t�E�Ct�ՍfLka���8:�Cr0)UUj+a8�y���#��c�1a@�iZ�л�� #� �ξ)�֮L�,Fب,Kg3��E=�I�s6P��'���t*+�E�r�Q�� 0�0U���V��q|���$�$�>��0U#0�#4��RFp
�@�v��+��5�0TUM0K0I�G�E�Chttp://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl0X+L0J0H+0�<http://www.microsoft.com/pki/certs/MicrosoftTimeStampPCA.crt0U%0
+0
*�H��
��vB���x��Ẍ������d�$�&W��;�'g��9�F�7?}��P�_9a�⋋G��`1j_�׍E(��ũ#!1�K�k#Yɟ�u�Xy2O�!֕�����f�^���N��6U��i��49�@���ٮ>�\I@l��V���Y�+T?9]�\�n@�q0�0�,f�D]�� ��}1�!�,Q��g�5b�$���q��2Ӿ^�9l�J`��n���L��G)�jZ�^>��}�ƵT!z>9�y�s=�kw��<0��0�ߠ3�|��`����0
*�H��
0y10 UUS10U
Washington10URedmond10U
Microsoft Corporation1#0!UMicrosoft Code Signing PCA0
190502212033Z
200502212033Z0t10 UUS10U
Washington10URedmond10U
Microsoft Corporation10UMicrosoft Corporation0�"0
*�H��
�0�
����k*)�i퐭��՗+��IJ���E �Z:p�v�@�'�����Z3qʱ����^(��D�P��sY�Ep;��o�\ �(1���䱚GM<�J��f�,�U�muј^�;�F́X\��N��W���
%�%W�2�J~A��u}�ߋ�Nf
����L��,���i�HqxWw��� ����m.������:d�4���̑����yϼ̕}|�@�n���L`�!mW5�(ӭ
�܉����{0�w0U%0
+0Up���mu���*:'YG�0TUM0K�I0G1-0+U$Microsoft Ireland Operations Limited10U
229803+4541060U#0��p�R4���'���ؽ�mGN0bU[0Y0W�U�S�Qhttp://crl.microsoft.com/pki/crl/products/Microsoft%20Code%20Signing%20PCA(2).crl0f+Z0X0V+0�Jhttp://www.microsoft.com/pki/certs/Microsoft%20Code%20Signing%20PCA(2).crt0
*�H��
�N��{�b~�=�G@������Q��Q��F�!e^bm�5�Z�꼣�h����9qp�g�&��}ZJI�δ7�909��yD�oTRIn>����X�~�G�L"x���3'��
L8*��D�e��h��JY+{p���X�6����-'����ۦ����b�شx�/.�9��5t��"5>��'���`��$yN`҄�u��J
E�:|�M�:�g�Q��#'$غ�Ȳ�1��
���A\e�0��0���
a5E?0
*�H��
0_10
�&���,dcom10
�&���,d microsoft1-0+U$Microsoft Root Certificate Authority0
180920174200Z
210509232813Z0y10 UUS10U
Washington10URedmond10U
Microsoft Corporation1#0!UMicrosoft Code Signing PCA0�"0
*�H��
�0�
��������F��fɧ]
~�=���1��ԅ���2����A��7��|W����Z`�1
a�"�|V4b�^Z�.�@*�=�aD؎�6Y�c���������_+�P_� Ґ頷,DA�eR7,�����,���c�Q����8^|�����)@ߔv*�e��m�'�§���j�Ƨ�f�hw�^�� �R�sQ�*�Q#�I�����P^�Oc?�/���M+q�Y('M��^0�Z0U�0�0U�p�R4���'���ؽ�mGN0U�0 +�70# +�7<����Up�iB���8��W0 +�7
SubCA0U#0���`@V'��%�*�
S�Y�0PUI0G0E�C�A�?http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl0T+H0F0D+0�8http://www.microsoft.com/pki/certs/MicrosoftRootCert.crt0
*�H��
�={�.�6�B�UO�����9
������"˅yC�����5�˅�->M�Q�$����c������
m.U5�,yaƶM�V&��e��.�<He��D���4
ީ�c����d�U�����e~���0���;��u�]π��q�B��ғ��T�|!�싼�~�) P�+:�=��W��8��ߚ8Ё�'��y;4���"�e�La<��.2h�)���v�߆)�
㴳�L�gZT�Y'��HBn1L�L��h�#J�T㔕l����(�YD���򨅳=�*�7��=7�8�*G�gY�-�z�w��JI*t7��/��C-�2���LI�����G辞�1d������uI{db��~��g\AG�N6-�7�k�?R����"%�9[�Ez��������d�΋��}��mW[*{ol~�C�
�]�gԋ���Nz���߽4����gn�d��L�3��QpU�\}�ݧU��ǣ�Fz��D��c�}�"u0�0��
ah40
*�H��
0_10
�&���,dcom10
�&���,d microsoft1-0+U$Microsoft Root Certificate Authority0
070403125309Z
210403130309Z0w10 UUS10U
Washington10URedmond10U
Microsoft Corporation1!0UMicrosoft Time-Stamp PCA0�"0
*�H��
�0�
���l���H�*|k.���řQ#P���N$�ѧ�L�t0 ��T�I�B���\0&�k�{�������3$����g,�{���N���#Sʍ�E� �^�аB���l�g�(�FS����(F.'��OUR�,�j��0n��Y0��~֗��!�~����SmR�E��HJGf')f�����J����G ����Ux��P�0F��#F��-T��xA1w̛�;���a�
������"KT���� ���0��0U�0�0U#4��RFp
�@�v��+��5�0U�0 +�70��U#��0�����`@V'��%�*�
S�Y䤡c�a0_10
�&���,dcom10
�&���,d microsoft1-0+U$Microsoft Root Certificate Authority�y��J���LsX�.e0PUI0G0E�C�A�?http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl0T+H0F0D+0�8http://www.microsoft.com/pki/certs/MicrosoftRootCert.crt0U%0
+0
*�H��
����\D6�鴭w��yQM�.tq[m�ξ{��.���mb�W�N P��z@�W��X�����x���;�⾏
ȍH��S�O����jՀ���/��*$"p����x�.
��p�N��k
r���9�g-�Q�b\?�� ?�2��1Jv1=+r��p=��
��
a��׸�N��5+^���}B{�Sr!�0ʻxe\[
����<�fX�-/���QV�p�l�9L�y��zb))4wb�=m���,��C���}�㤨t5�N�q#&v<R�qZFC����MgȟB��y!��0f�B^Ȟ"!�C�+��H�,��2�L&*H$_Z�V�ޙ��:o��'t�v!����'T��j=��va�n����G�o��2l���QȌ#�f���d=-�Y���!嵰�c�xT�A.P����x����uْ�u"/2�n�[�%����!��Oɚ�I�eo�}�i��n꧗�1)��[\�M��/�?.Uk���1�)0�)
0��0y10 UUS10U
Washington10URedmond10U
Microsoft Corporation1#0!UMicrosoft Code Signing PCA3�|��`����0 +���0 *�H��
1
+�70
+�710
+�70# *�H��
1��޷�75��kZ�"���0N
+�71@0>� �SQL Server 2019��http://www.microsoft.com0
*�H��
��p<��1�s��0k�j���S�(��1r��m(��6B��C���rK���['-�gy�}Y.)�E���=����μѝ�����Z�<��O$7N։�'d[:��t�ܤB��5�t���|���l,�9u�q���t���-ԉ������ܬRv0Ch����^$M!�P�<���������+�����J%���T���/U{1�
���J�$3F16��L��&��a�8x�|E�a���^��&�0�$ *�H��
1�0�0��0w10 UUS10U
Washington10URedmond10U
Microsoft Corporation1!0UMicrosoft Time-Stamp PCA3 ������ 0 +�]0 *�H��
1 *�H��
0 *�H��
1
190924204416Z0# *�H��
1^���o^��a,�*5u
2N�0
*�H��
�(Ɲ��,�:��^K;�bGU�Ju�̦�^�����D?��7[�{�$��
V�E�£�Y4�}�C�%5��u�W�>!�K��ҥ NGv��|���������gz{��8�A�������
��b�M�O$��q�7x�v��6KH�V��랴���F
��M`�X��FT-t�qXrrJrȣ֜�f|�dHp��$�.�Qs��3�f�Ȍ� 7w����� ���=�rЯ�"�~���i]�J����͖
' PҌ�v�1�0�$u
+�71�$e0�$a *�H��
��$R0�$N10
`�He0\
+�7�N0L0
+�70 ���010
`�He ��{㬠�X���:��ɾ.@�vA���@쮱��
�0�0��3R�@�PV�u�R0
*�H��
0~10 UUS10U
Washington10URedmond10U
Microsoft Corporation1(0&UMicrosoft Code Signing PCA 20110
190502213746Z
200502213746Z0t10 UUS10U
Washington10URedmond10U
Microsoft Corporation10UMicrosoft Corporation0�"0
*�H��
�0�
���������t�����ǔߖ�6�+�xL���5���oK��w�U��buAN��[�V7V�p�Cn�3(A6��~��/�k����>��\�6��ɳ����mJ�
�X�%y�D�����*��Or�}Y�Gڗ}tP����M�4dc�睘�*�!�U��}�W����P��e���.����lA ��+4�Ih��z%�x�tr�
����������c� �����i��Zai^���76q�3ހ����0�~0U%0
+�7L+0U��[�e�'f��5kE�0TUM0K�I0G1-0+U$Microsoft Ireland Operations Limited10U
230012+4541360U#0�Hnd�Pӂ�77"�m��u�0TUM0K0I�G�E�Chttp://www.microsoft.com/pkiops/crl/MicCodSigPCA2011_2011-07-08.crl0a+U0S0Q+0�Ehttp://www.microsoft.com/pkiops/certs/MicCodSigPCA2011_2011-07-08.crt0U�00
*�H��
���D懾��,V�(�-����6@��m�z� 65�W��Q`[�F�y8��t�ھ$�&��C��=�d�R�m���(ߜ����S�]��!��h2]g����"���S��E��v���5@��7�8��t�=0|3e�?�O��%�vS�Y�������ޭ��b�����+O�yDT
�ͅC�8xQ#�+7&�T��",ۮ8��P���h�(�T@�`���T�l������T����G6~�ܷ�f��D�k�IB��� ��m������r����aݽ��G>ƚ읶��2>�Ҁ\�����]��r!���K��Q!��(�V�&sLDt�>��QZ�M����W5X��)l�}F�G�M3�s4��O��8v�vT���:�e:����*Ɲ�N�
���hP���z?别2��fwǴ��#cU�b���ӧx�\Ȇ޽�e,��Ul*!����43=+�
�m����
��ސ��n���Iy/钒>
�0�z0�b�
a��0
*�H��
0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1200U)Microsoft Root Certificate Authority 20110
110708205909Z
260708210909Z0~10 UUS10U
Washington10URedmond10U
Microsoft Corporation1(0&UMicrosoft Code Signing PCA 20110�"0
*�H��
�0�
���r.��n��M4��X!�B*k�ZP��8I���7k���8��9�1BӉ
yd�~�`$l��I��h^�ߛS�
,ï٩+�z �זY�`�fv�2R&/�PϳD�]��.u�h��m�:\��F��8d�nd5x��c-�@����
�\y�I)�
��w��=��+ZMV(�zr�:�I^���C���{�{��>��]�O��/Y�;-�3Xŷ>�2ӳ=����8~ҝ�,�NV�!5%�9ndS���#������_��R������!t%_(��'(8%�9J6�|���#��f�aj�(I�_��%]�!K>RĵW?$��z[/�#�p]QFw��Ἤ�_����UK�9��#I��D|E��rz�r�$߿F����Wۃ��MI0�����[���ݰf��{���K�I)�(��}g��bx_�/��W�\�w((��m�(�,�@7O��D�� L�ԥC/t��n�x X,]`��>O3�ڰ�ޞN�F�l���ֈ����0��0 +�70UHnd�Pӂ�77"�m��u�0 +�7
SubCA0U�0U�0�0U#0�r-:1�C�N���1�#�40ZUS0Q0O�M�K�Ihttp://crl.microsoft.com/pki/crl/products/MicRooCerAut2011_2011_03_22.crl0^+R0P0N+0�Bhttp://www.microsoft.com/pki/certs/MicRooCerAut2011_2011_03_22.crt0��U ��0��0�� +�7.0��0?+3http://www.microsoft.com/pkiops/docs/primarycps.htm0@+042 Legal_policy_statement. 0
*�H��
�g򆥘�Ty.��tg"���c��B�}�y��e_.,>��r�m���?�
�;�G���i�c�"5��]e��}�FPU��|�K�<B�Rа�k�>.)��=�Եw�9��d�D=xz#�}��t����&F*�����h�h.��*?*kXIc inZ�����F+�;н5�n%��'������(��M=����2���-�[��I9
�
�ƭ�����QEX82q'��'��,: i��Y�hno��t�@�*(>�?Mf��M��o}E�v�@*e��]Rb��c6��������'�ͥ���]cA�[��>w��u�aa������A�(��e/��\��֡F�Y� KH���)ű��?Ew5�Ң��zz"�H���G#�����k�K���ux��7�yK�ֳ#hu������i;��0�L���umc�=ѝVNO��W"�x2!z�A
�?��̤]����WqVNHE�Bɛv[
�Hk�y���mmj�Rs
zP�1�O0�K0��0~10 UUS10U
Washington10URedmond10U
Microsoft Corporation1(0&UMicrosoft Code Signing PCA 20113R�@�PV�u�R0
`�He���0
*�H��
10 *�H��
1
+�70
+�710
+�70/ *�H��
1" �0�[��
���5�]t�e���..��p6N��0N
+�71@0>� �SQL Server 2019��http://www.microsoft.com0
*�H��
�ض�0�,f�|�ޮi���Be��;C�0�3�Ti�zɥv!vg����4+S^5�N�\��/���8��p�_����U71�a��[(����0ze�'�ZOg{D
7e�<�[2Ʀf��J���R�?{��������>j��}�e��ճ�b��TY�l�� ���iΒ�����G����4�-8 ���6�7a��^�
���h�K�ޥSGd�xp�x��D��V���ea:q�������H%���0��
+�71��0�� *�H��
���0��10
`�He0�X*�H��
��G�C0�?
+�Y
010
`�He �;I�[�U�h��H�� Le
04��]��:a620190924204418.422Z0��Ԥ��0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1)0'U Microsoft Operations Puerto Rico1&0$UThales TSS ESN:B8EC-30A4-71441%0#UMicrosoft Time-Stamp Service��"0�q0�Y�
a �*0
*�H��
0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100
100701213655Z
250701214655Z0|10 UUS10U
Washington10URedmond10U
Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100�"0
*�H��
�0�
��
�w�: ����i�ktTե
����|hK,_���a�v�>f+[�S'1A�� �|a0Y�0D�`��TC�M�8�Bݓ��s0W&��E
��G�Ϳ$`2X`F�XG�2�tag�_�T�ϓL��Ħ]�an(������a�F�'$gr!��Kd�Pb�]�w=�Wu���BM@Q��>g�f��D~��K�n�ʱ��z*
1��N���5�x���<�/D����d��� �x����D]^�O"M���0��0 +�70U�c:\�1��C{|F�3hZ�mU0 +�7
SubCA0U�0U�0�0U#0��Vˏ�\bh�=��[�Κ�0VUO0M0K�I�G�Ehttp://crl.microsoft.com/pki/crl/products/MicRooCerAut_2010-06-23.crl0Z+N0L0J+0�>http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0��U ���0��0�� +�7.0��0=+1http://www.microsoft.com/PKI/docs/CPS/default.htm0@+042 Legal_Policy_Statement. 0
*�H��
��Q
���?�q=���!o���1����Wm0���f�j���x�Ǩ�%��kTW+Q�D��S���`�v�@@A��\�\�^5�$VKt�Bȯ���7}Z?�yJ�R�8�/y�e٩�k����zoK0D$"<�����Y)����p�2J'�U�/���3�b_��W@��Ιf���jb��J�&�9�Jqc�{!mÜ��<�}�j�x�m���8ؔ�ƥ
������B�����"8 �%�d��~cY%z.9Wv�q����a�˚�G����ͧ��}���;q �]t�"aڰPo�����1��:�eGx�H���r~akow��˧ �9����؂�r�����*T9�[��
U�z�s;�-��3.)��/T'!�ȬN�(���ۖ��B���AM�*��f0ӻt2K�c{���/�!�Y���D<�Pqס��U�i�W���0����M�
�]O�8/��X.�
�P5�� 'ճ~5��6��_��t�I0��0�ݠ3�D,��5r��0
*�H��
0|10 UUS10U
Washington10URedmond10U
Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100
190906204107Z
201204204107Z0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1)0'U Microsoft Operations Puerto Rico1&0$UThales TSS ESN:B8EC-30A4-71441%0#UMicrosoft Time-Stamp Service0�"0
*�H��
�0�
��t9���9p"hپ��=RƲ5��ʐ��aa��}��V\���&���@�y�%��!dQr���e(�W�1H���(.%{�X���ì`PxzdD��ib9�:�Un����¦�ј�^�L�0��V,���l�'.���f3�(�͘��/��^ͽ�;��k�d��
Mз�1ƪir��D�B��UF[�(�m��
�z������E��J-��5��a�+T��J�������z =ň��j�؇�z����0�0Ur:*�c�IE����mL$0U#0��c:\�1��C{|F�3hZ�mU0VUO0M0K�I�G�Ehttp://crl.microsoft.com/pki/crl/products/MicTimStaPCA_2010-07-01.crl0Z+N0L0J+0�>http://www.microsoft.com/pki/certs/MicTimStaPCA_2010-07-01.crt0U�00U%0
+0
*�H��
�B�v��"����5�г3�C�R�T�|���+��c���C&>� �-��[���
��ѹ~���/��љ��e�<�ic5��,�2 ^�4lNvg,k$!*W9;�e]†��"���>�&�8��Kqb2n,\?7�kǓ�*��!%H�нE��Mn�7~YDH��vVVW�w���
m�������7*Z�
�����&�P.��?{j�-��^&E�k��6�9z��X5B���mU-�G�:r!������0��0����Ԥ��0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1)0'U Microsoft Operations Puerto Rico1&0$UThales TSS ESN:B8EC-30A4-71441%0#UMicrosoft Time-Stamp Service�%
0 +��$�7H�cֵ�]�#���4���0�ۤ��0��10 UUS10U
Washington10URedmond10U
Microsoft Corporation1)0'U Microsoft Operations Puerto Rico1'0%UnCipher NTS ESN:4DE9-0C5E-3E091+0)U"Microsoft Time Source Master Clock0
*�H��
�4��0"20190924123746Z20190925123746Z0w0=
+�Y
1/0-0
�4��0
N�00
�5�06
+�Y
1(0&0
+�Y
�
0�`�
0� 0
*�H��
�U�bU�.�F��oJ���MU��.������q�r��]\��ǸU�Ͳ�k�M��o�~$�?���XPb,�ƃ�P�$d[8��?�mq۱Q�����;��6ྙ��JٳP�t����D�5�6M�Vbhn�mƍ�*讝��Y�̙,�oDPJ!nr�qS�P��'� �׼ y����Ջ���� l����^l)�|b�g��
gM�
�q�����L��s�
`�{�T%���Ah+�-1��0��0��0|10 UUS10U
Washington10URedmond10U
Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103�D,��5r��0
`�He��20 *�H��
1
*�H��
0/ *�H��
1" !RC�3v�Č+uQ�]:��ZӋ`J�0��$�V0��*�H��
1��0��0��0����$�7H�cֵ�]�#���40��0���~0|10 UUS10U
Washington10URedmond10U
Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103�D,��5r��0�= \��F7�)�{F0
*�H��
�.�l̔���+�`J��e&�]#P�/z� pˋa�����kZ@3��������tM���b�wd%]~7�W�k����� ���e�/���1Q1uRL<;� �?�cw��).XFLN4c�Z#�gԌ���p�Q`k��TS���oi�����.�Z�p؊X�i}���F'����V˔@!>Ѧ:�1��cs��$�W����!�M���D;�5 |/���1W�$\���2�BN�(l�5Nr�-a�