Error Number - 10040 - Invalid error handling

Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.

Error Number - 10040 - Invalid error handling

Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.

Error not flowing down Error Precedent Constraint path

I have a dataflow task which keeps erroring, at which point the flow should go down the red path to my error handling SQL Task.

But it is failing to do so.

anyone know why?

What type of transform are you using? (note: task is for control flow not data flow) Have you set up your error output to redirect rows on error? How about for truncation?

etc...

|||

Adolf,

could you explain bettter what is your problem?

You have in eventhandler a SQL task to save the inesperated error, true?

the error is in this SQL Task?

Regards!

|||This is occuring at the Control Flow level.

The design:
A data flow task has two paths coming out of it: 1 green, 1 red.
The green path continues on to another DF task, the red goes to an SQL task.

What happens:
The DF turns red but the flow does not then progress to the SQL task. It just stops.|||What I failed to mention was that the SQL task has 3 other failure paths joining it

I just set the precedence to "OR" instead of "AND" and it works.