HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1 
Author Message
 HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1
Has anyone ever seen this error? It began popping up all
over our system recently and I can't find any rows that
contain a date with a year greater than 9999.  Any help
is appriciated.

ERROR MESSAGE:

Server: Msg 542, Level 16, State 1, An invalid datetime
value was encountered. Value exceeds the year 9999.

Thanks,

Ryan Grim



Sat, 29 Oct 2005 22:23:35 GMT
 HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1

I would start checking if the database is corrupt (DBCC CHECKDB). I assume you do this
regularly, so you might just go to the log from last execution and check there.

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

Quote:

> Has anyone ever seen this error? It began popping up all
> over our system recently and I can't find any rows that
> contain a date with a year greater than 9999.  Any help
> is appriciated.

> ERROR MESSAGE:

> Server: Msg 542, Level 16, State 1, An invalid datetime
> value was encountered. Value exceeds the year 9999.

> Thanks,

> Ryan Grim



Sun, 30 Oct 2005 09:10:36 GMT
 HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1
The CHECKDB operation has been done and corruptions found
and corrected.  Here is the interesting thing...there is
a column in one table that is of DATETIME data type and
contained this value.... 16058-08-30 13:55:00.000 ...how
is this even possible?  We corrected the record
containing the incorrect year and rebuilt the indexes for
that table and everything is functioning properly.  Any
ideas?

Thanks,

Ryan

Quote:
>-----Original Message-----
>I would start checking if the database is corrupt (DBCC

CHECKDB). I assume you do this
Quote:
>regularly, so you might just go to the log from last

execution and check there.
Quote:

>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?

oi=djq&as_ugroup=microsoft.public.sqlserver
Quote:




Quote:
>> Has anyone ever seen this error? It began popping up
all
>> over our system recently and I can't find any rows that
>> contain a date with a year greater than 9999.  Any help
>> is appriciated.

>> ERROR MESSAGE:

>> Server: Msg 542, Level 16, State 1, An invalid datetime
>> value was encountered. Value exceeds the year 9999.

>> Thanks,

>> Ryan Grim

>.



Sun, 30 Oct 2005 15:06:56 GMT
 HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1
Hi Ryan,

Seems to me that the data is corrupt. Can you reproduce the problem?

In addition, what is version of SQL Server? What operation are you
performing that will cause "An invalid datetime value was encountered.
Value exceeds the year 9999."?

This posting is provided "AS IS" with no warranties, and confers no rights.

Regards,

Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message




| Subject: Re: HELP - SQL Server 7.0 Error - Msg 542, Level 16, State 1
| Date: Wed, 14 May 2003 07:06:56 -0700
| Lines: 45

| MIME-Version: 1.0
| Content-Type: text/plain;
|       charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcMaIhRfZGWRrUWqTu+55aWSNEQ/Nw==
| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.server:286732
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| The CHECKDB operation has been done and corruptions found
| and corrected.  Here is the interesting thing...there is
| a column in one table that is of DATETIME data type and
| contained this value.... 16058-08-30 13:55:00.000 ...how
| is this even possible?  We corrected the record
| containing the incorrect year and rebuilt the indexes for
| that table and everything is functioning properly.  Any
| ideas?
|
| Thanks,
|
| Ryan

Quote:
| >-----Original Message-----
| >I would start checking if the database is corrupt (DBCC
| CHECKDB). I assume you do this
| >regularly, so you might just go to the log from last
| execution and check there.
| >
| >--
| >Tibor Karaszi, SQL Server MVP
| >Archive at: http://groups.google.com/groups?
| oi=djq&as_ugroup=microsoft.public.sqlserver
| >
| >


| >> Has anyone ever seen this error? It began popping up
| all
| >> over our system recently and I can't find any rows that
| >> contain a date with a year greater than 9999.  Any help
| >> is appriciated.
| >>
| >> ERROR MESSAGE:
| >>
| >> Server: Msg 542, Level 16, State 1, An invalid datetime
| >> value was encountered. Value exceeds the year 9999.
| >>
| >> Thanks,
| >>
| >> Ryan Grim
| >>
| >
| >
| >.
| >
|



Tue, 01 Nov 2005 03:19:38 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Help: SQL Error: Msg 7134, Level 16, State 2

2. Server: Msg 7399, Level 16, State 1, Line 1 error on .mdb as linked server

3. Server: Msg 7399, Level 16, State 1, Line 1 error on .mdb as linked server

4. Help.Error: Msg 7399, Level 16, State 1, Line 1

5. Error Message: Server: Msg 7392, Level 16, State 2

6. Error: Server: MSG 7392, Level 16, State 2

7. Select error:Server: Msg 8120, Level 16, State 1, Line 1

8. Server: Msg 107, Level 16, State 3 Error

9. SQLServer Msg 2506, Level 16, State 3 Error - Help Needed

10. Msg 7343, Level 16, State 4 (Sql Server Link to Access)

11. SQL Server 7: Error Msg - Error: 1222, Severity: 16, State: 50 Lock Request Timeout period exceeded

12. Msg 5159, Level 16, State 1 OS Error 38


 
Powered by phpBB® Forum Software