Измените свойство maximumerrorcount или устраните ошибки

У меня несколько работ и несколько пакетов. В SQL Server 2005 мы использовали пакеты DTS, но теперь они не функционируют (я знаю, что могу снова включить их, но мне это не нужно). Я получаю следующую ошибку при запуске одного из моих пакетов:

Сообщение: код предупреждения SSIS DTS_W_MAXIMUMERRORCOUNTREACHED. Метод Execution завершился успешно, но количество возникших ошибок (1) достигло максимально допустимого (1); приводящий к отказу. Это происходит, когда количество ошибок достигает числа, указанного в MaximumErrorCount. Измените MaximumErrorCount или исправьте ошибки.

Очевидно, это результат более ранней ошибки. Я не могу исправить эту ошибку, поэтому хочу увеличить MaximumErrorCount. Но даже несмотря на то, что в Интернете есть множество сообщений, в которых объясняется, что вы должны выбрать Свойства в пакете (или в работе?), В пакете нет Свойства больше (я нашел их под Интеграционные Услуги где они перечислены под Пакеты DTS что странно, учитывая, что мастер создал пакет, а DTS не поддерживается в 2008?), я понятия не имею, как заглянуть в пакет, на самом деле. И у работы есть Свойства, но нигде нет настройки Максимальное количество ошибок.

Может ли кто-нибудь быть для меня глазами и увидеть то, чего я не вижу? Где мне увеличить MaximumErrorCount в соответствии с сообщением об ошибке?

If MaximumErrorCount is reached, that does not mean the container is done and can no longer generate errors.  A container is a package, or a loop, or sequence, or a task host, or an event handler.

Container completion and Container failure are two different (but interrelated) concepts. One is an event, the other is is a state. Even if an container is in failed state (ExecutionResult), it may have work yet to do, and though its ExectutionResult is set to Failure, it is not necessarily finished.

Even with MaximumErrorCount set to one, a container may receive a large number of errors, Now, to observe this concept, do the following.

1. Save a file with the following xml (sample.xml)

<bib>

<book year=«1994«>

<title>TCP/IP Illustrated</title>

<author>

<last>Stevens</last>

<first>W.</first>

</author>

<publisher>Addison-Wesley</publisher>

<price>65.95</price>

</book>

</bib>

2. Save the following xml schema (xsd) into a file as well (sample.xsd).  Prepare for xsd to smiley conversion.

<?xml version=«1.0« encoding=«utf-8«?>

<xschema attributeFormDefault=«unqualified« elementFormDefault=«qualified« xmlns:xs=«http://www.w3.org/2001/XMLSchema«>

<xs:element name=«bib«>

<xs:complexType>

<xsequence>

<xs:element name=«book«>

<xs:complexType>

<xsequence>

<xs:element name=«title« type=«xstring« />

<xs:element name=«author«>

<xs:complexType>

<xsequence>

<xs:element name=«last« type=«xstring« />

<xs:element name=«first« type=«xstring« />

</xsequence>

</xs:complexType>

</xs:element>

<xs:element name=«publisher« type=«xstring« />

<xs:element name=«price« type=«xsecimal« />

</xsequence>

<xs:attribute name=«year« type=«xs:unsignedShort« use=«required« />

</xs:complexType>

</xs:element>

</xsequence>

</xs:complexType>

</xs:element>

</xschema>

3. Create a a package with a single data flow.
4. In the data flow, add an xml data source; Data Access Mode: Xml file location. Point the respective xml and xsd to the files created above.
5. Connect the «author» output of xml source to a Union all (or row count ) transform.
6 .Enable logging at the package level, log the error events specifically at the data flow level, and warnings at the package level.
7. Run the package, it should succeed.

Now edit the sample.xml file to contain the following (there are two deliberate errors)

<bib>

<book year=«1994«>

<title>TCP/IP Illustrated</title>

<author>

<last>Stevens</last>

<first>W.</first>

</author>

<publisher>Addison-Wesley</publisher>

<price>Sixty Five Ninety Five</price>

</book>

<bib>

Re-run the package.
How many errors are observed in the execution results windows or the Log Events window from the data flow alone. On Vista x86, eight are observed.
Did the dataflow and package fail? Yes and yes.

Here’s the Warning message received on the package itself. Note the number of errors raised, with no parallel containers.

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

Now, the message tells the author to «Change the MaxErrorCount» or fix the errors, but there another option (its called handling the error).

In the same package, create an OnError Event Handler on the data flow itself. In the handler, open the Variables window, select show system variables from the variables window toolstrip, and set the Propagate boolean System variable to false. Run the package again. How many errors were observed on the data flow task? On Vista eight are still observed. What containers failed? The data flow task failed, but the package succeeded.

The running total of errors which bubble or are directly directly fired by a given container are compared against that container’s MaximumErrorCount. If the number of errors is >= to the MaximumErrorCount, the execution result of the container is set to Failure, unless overridden by the ForceExecutionResult property.

Furthermore, if MaximumErrorCount is set to one on all containers, that does not means one error must of necessity stop the package either. When System:ropagate is set to false in an error event handler scoped below the package level, it may (at the designers discretion) halt error propagation up the container hierarchy, thus preventing the ExecutionResult on the package being set to Failure as well (at least on its account).

If MaximumErrorCount is reached, that does not mean the container is done and can no longer generate errors.  A container is a package, or a loop, or sequence, or a task host, or an event handler.

Container completion and Container failure are two different (but interrelated) concepts. One is an event, the other is is a state. Even if an container is in failed state (ExecutionResult), it may have work yet to do, and though its ExectutionResult is set to Failure, it is not necessarily finished.

Even with MaximumErrorCount set to one, a container may receive a large number of errors, Now, to observe this concept, do the following.

1. Save a file with the following xml (sample.xml)

<bib>

<book year=«1994«>

<title>TCP/IP Illustrated</title>

<author>

<last>Stevens</last>

<first>W.</first>

</author>

<publisher>Addison-Wesley</publisher>

<price>65.95</price>

</book>

</bib>

2. Save the following xml schema (xsd) into a file as well (sample.xsd).  Prepare for xsd to smiley conversion.

<?xml version=«1.0« encoding=«utf-8«?>

<xschema attributeFormDefault=«unqualified« elementFormDefault=«qualified« xmlns:xs=«http://www.w3.org/2001/XMLSchema«>

<xs:element name=«bib«>

<xs:complexType>

<xsequence>

<xs:element name=«book«>

<xs:complexType>

<xsequence>

<xs:element name=«title« type=«xstring« />

<xs:element name=«author«>

<xs:complexType>

<xsequence>

<xs:element name=«last« type=«xstring« />

<xs:element name=«first« type=«xstring« />

</xsequence>

</xs:complexType>

</xs:element>

<xs:element name=«publisher« type=«xstring« />

<xs:element name=«price« type=«xsecimal« />

</xsequence>

<xs:attribute name=«year« type=«xs:unsignedShort« use=«required« />

</xs:complexType>

</xs:element>

</xsequence>

</xs:complexType>

</xs:element>

</xschema>

3. Create a a package with a single data flow.
4. In the data flow, add an xml data source; Data Access Mode: Xml file location. Point the respective xml and xsd to the files created above.
5. Connect the «author» output of xml source to a Union all (or row count ) transform.
6 .Enable logging at the package level, log the error events specifically at the data flow level, and warnings at the package level.
7. Run the package, it should succeed.

Now edit the sample.xml file to contain the following (there are two deliberate errors)

<bib>

<book year=«1994«>

<title>TCP/IP Illustrated</title>

<author>

<last>Stevens</last>

<first>W.</first>

</author>

<publisher>Addison-Wesley</publisher>

<price>Sixty Five Ninety Five</price>

</book>

<bib>

Re-run the package.
How many errors are observed in the execution results windows or the Log Events window from the data flow alone. On Vista x86, eight are observed.
Did the dataflow and package fail? Yes and yes.

Here’s the Warning message received on the package itself. Note the number of errors raised, with no parallel containers.

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

Now, the message tells the author to «Change the MaxErrorCount» or fix the errors, but there another option (its called handling the error).

In the same package, create an OnError Event Handler on the data flow itself. In the handler, open the Variables window, select show system variables from the variables window toolstrip, and set the Propagate boolean System variable to false. Run the package again. How many errors were observed on the data flow task? On Vista eight are still observed. What containers failed? The data flow task failed, but the package succeeded.

The running total of errors which bubble or are directly directly fired by a given container are compared against that container’s MaximumErrorCount. If the number of errors is >= to the MaximumErrorCount, the execution result of the container is set to Failure, unless overridden by the ForceExecutionResult property.

Furthermore, if MaximumErrorCount is set to one on all containers, that does not means one error must of necessity stop the package either. When System:ropagate is set to false in an error event handler scoped below the package level, it may (at the designers discretion) halt error propagation up the container hierarchy, thus preventing the ExecutionResult on the package being set to Failure as well (at least on its account).

I have several jobs and several packages. In SQL Server 2005 we used to use DTS Packages, but they are now defunct (I know that I can re-enable them, but that’s not what I’m after). I receive the following error by running one of my packages:

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

Obviously, this is a result of an earlier error. I cannot fix that error, so I want to increase the MaximumErrorCount. But even though there are numerous posts on the internet explaining that you should select Properties on the package (or the job?), the package doesn’t have Properties anymore (I found them under Integration Services where they’re listed under DTS Packages which is odd, considering a wizard created the package and DTS is not supported by 2008?), I’ve no clue how to look into the package, really. And the job does have Properties, but nowhere is there a setting Maximum error count.

Can someone be the eyes for me and see what I cannot see? Where do I increase the MaximumErrorCount as requested by the error message?

I have several jobs and several packages. In SQL Server 2005 we used to use DTS Packages, but they are now defunct (I know that I can re-enable them, but that’s not what I’m after). I receive the following error by running one of my packages:

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

Obviously, this is a result of an earlier error. I cannot fix that error, so I want to increase the MaximumErrorCount. But even though there are numerous posts on the internet explaining that you should select Properties on the package (or the job?), the package doesn’t have Properties anymore (I found them under Integration Services where they’re listed under DTS Packages which is odd, considering a wizard created the package and DTS is not supported by 2008?), I’ve no clue how to look into the package, really. And the job does have Properties, but nowhere is there a setting Maximum error count.

Can someone be the eyes for me and see what I cannot see? Where do I increase the MaximumErrorCount as requested by the error message?

3 ответа

Лучший ответ