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.
Sunday, March 11, 2012
Error Number - 10040 - Invalid error handling
Labels:
application,
appreacited,
database,
error,
handling,
invalid,
message,
microsoft,
mysql,
number,
oracle,
production,
ran,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment