Pervasive "Arithmetic overflow occurred." message

I'm encountering a problem with a SQL Server 2000 installation. The steps
to reproduce are simple: log in to the server via OSQL or "Query Analyzer".
Run "sp_help". I immediately receive several "Arithmetic overflow
occurred." messages followed by the standard results expected from
"sp_help". All other queries also report the same error message, though the
results seem to be correct. Doesn't matter what DB I'm running against.
Doesn't matter what ID I've logged in with. I've tried different client
machines. I don't see the problem when I connect to other SQL Server 2000
installations. I also tried it from the console of the SQL Server machine
itself w/"Query Analyzer". Same result.
What would cause this and how do I correct it?
Thanks,
--David
I'd suggest applying the latest service pack
You can get it here :-
http://www.microsoft.com/technet/pro...s/default.mspx
HTH. Ryan
"David Ehrlich" <djehrlich@.hotmail.com> wrote in message
news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
> I'm encountering a problem with a SQL Server 2000 installation. The steps
> to reproduce are simple: log in to the server via OSQL or "Query
> Analyzer". Run "sp_help". I immediately receive several "Arithmetic
> overflow occurred." messages followed by the standard results expected
> from "sp_help". All other queries also report the same error message,
> though the results seem to be correct. Doesn't matter what DB I'm running
> against. Doesn't matter what ID I've logged in with. I've tried different
> client machines. I don't see the problem when I connect to other SQL
> Server 2000 installations. I also tried it from the console of the SQL
> Server machine itself w/"Query Analyzer". Same result.
> What would cause this and how do I correct it?
> Thanks,
> --David
>
|||Are you able gauge which line on sp_help the error is occurring?
If so, you could open the stored procedure and see the source of the problem
Jack Vamvas
__________________________________________________ ________________
Receive free SQL tips - register at www.ciquery.com/remotedba.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"David Ehrlich" <djehrlich@.hotmail.com> wrote in message
news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
> I'm encountering a problem with a SQL Server 2000 installation. The steps
> to reproduce are simple: log in to the server via OSQL or "Query
Analyzer".
> Run "sp_help". I immediately receive several "Arithmetic overflow
> occurred." messages followed by the standard results expected from
> "sp_help". All other queries also report the same error message, though
the
> results seem to be correct. Doesn't matter what DB I'm running against.
> Doesn't matter what ID I've logged in with. I've tried different client
> machines. I don't see the problem when I connect to other SQL Server 2000
> installations. I also tried it from the console of the SQL Server machine
> itself w/"Query Analyzer". Same result.
> What would cause this and how do I correct it?
> Thanks,
> --David
>
|||Looks to me like we're current (at least for SQL Server 2000):
SELECT @.@.VERSION
GO
Arithmetic overflow occurred.
<...snip...>
Arithmetic overflow occurred.
-----------
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23ZQVmF4GGHA.2212@.TK2MSFTNGP15.phx.gbl...
> I'd suggest applying the latest service pack
> You can get it here :-
> http://www.microsoft.com/technet/pro...s/default.mspx
> --
> HTH. Ryan
> "David Ehrlich" <djehrlich@.hotmail.com> wrote in message
> news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This happens on _any_ query, stored procedure, etc. For instance (pieced
together from "Query Analyzer"):
SELECT @.@.VERSION
GO
Arithmetic overflow occurred.
<...snip...>
Arithmetic overflow occurred.
-----------
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
"Jack Vamvas" <info@.nospam.com> wrote in message
news:dqj6l6$2v3$1@.nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com...
> Are you able gauge which line on sp_help the error is occurring?
> If so, you could open the stored procedure and see the source of the
> problem
>
> Jack Vamvas
> __________________________________________________ ________________
> Receive free SQL tips - register at www.ciquery.com/remotedba.htm
> SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
> New article by Jack Vamvas - SQL and Markov Chains -
> www.ciquery.com/articles/art_04.asp
>
> "David Ehrlich" <djehrlich@.hotmail.com> wrote in message
> news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
> Analyzer".
> the
>
|||I did two things and the problem disappeared:
1. I installed the latest _security_ patches (the latest service patches
were
already installed).
2. As required by the security patches, I rebooted the machine.
Seems odd that the problem would be cured by one of these two actions.
Good thing this wasn't a production SQL Server.
--David
"David Ehrlich" <djehrlich@.hotmail.com> wrote in message
news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
> I'm encountering a problem with a SQL Server 2000 installation. The steps
> to reproduce are simple: log in to the server via OSQL or "Query
> Analyzer". Run "sp_help". I immediately receive several "Arithmetic
> overflow occurred." messages followed by the standard results expected
> from "sp_help". All other queries also report the same error message,
> though the results seem to be correct. Doesn't matter what DB I'm running
> against. Doesn't matter what ID I've logged in with. I've tried different
> client machines. I don't see the problem when I connect to other SQL
> Server 2000 installations. I also tried it from the console of the SQL
> Server machine itself w/"Query Analyzer". Same result.
> What would cause this and how do I correct it?
> Thanks,
> --David
>
|||David,
Just seen this KB http://support.microsoft.com/kb/911851/
Chris
"David Ehrlich" <djehrlich@.hotmail.com> wrote in message
news:e55FzMIHGHA.1288@.TK2MSFTNGP09.phx.gbl...
>I did two things and the problem disappeared:
> 1. I installed the latest _security_ patches (the latest service patches
> were
> already installed).
> 2. As required by the security patches, I rebooted the machine.
> Seems odd that the problem would be cured by one of these two actions.
> Good thing this wasn't a production SQL Server.
> --David
> "David Ehrlich" <djehrlich@.hotmail.com> wrote in message
> news:uIzZU$3GGHA.740@.TK2MSFTNGP12.phx.gbl...
>
>