this is the first time I posted this, so I didn't repost :)
I do not have backups. However, Our program synchronizes with our server
(not using replication, it's manual) and I can see the files written out for
transmitting. When the record was written out on 5/20, that evening, it
went to our central server perfectly (our server has the correct data). The
user in question continued using our system each day until 5/25, when the
error first popped up. The problem is, one of our screens at the kiosk
shows his last 20 scores, and the date they were played. Querying up the
invalid date caused a runtime error, which we trapped in .NET. We first
thought it was a connection issue, but tracked it down to this date.. It
does not occur for any other user.
System.InvalidOperationException: Internal connection fatal error.
at System.Data.SqlClient.SqlDataReader.InternalClose(Boolean closeReader)
at System.Data.SqlClient.SqlDataReader.Close()
Then, in another part of our system, this error came up:
System.Data.SqlClient.SqlException: An invalid datetime value was
encountered. Value exceeds the year 9999.
The statement has been terminated.
And we were able to tie 2 and 2 together.
It may be corruption, but of 1 record? Very strange.
[quoted text, click to view] "Will" <will@crazy-pug.co.uk> wrote in message
news:1182815212.438736.305320@n2g2000hse.googlegroups.com...
> On Jun 25, 12:51 pm, "AC" <a...@b.com> wrote:
>> I had a client call today and report an error of an invalid date. I had
>> him
>> backup his database and send it to me. When I got it, I looked at the
>> table
>> in question and our table has 2 datetime fields in it.
>>
>> Their values are:
>>
>> DatePlayed: -15398-06-22 00:00:00.000
>> DatePosted: 2007-03-29 00:00:00.000
>>
>> The DatePlayed is obviously wrong. The DatePosted is also wrong (not
>> wrong
>> format) because it should be 5/20/07. I looked through the logs OUR
>> PROGRAM
>> produces and determined that.
>>
>> On 5/20, this record was added just before 1pm. DatePlayed was set to
>> 5/20/07 and DatePosted is automatically set by a constraint to 5/20.
>>
>> Everything was fine from 5/20 until 5/25 with this record.....
>>
>> On 5/25, the invalid date error came up.
>>
>> NO editing of rthis record occurred in that timeframe. BCP was NOT used
>> to
>> insert this record.
>>
>> Anyone have any insight on how this may happen?
>
> Do you have any backups from 5/24, with the incorrect date in them?
>
> It _could_ be database corruption, but I've seen reports of -ve dates
> before - haven't a clue what causes them, though (note - by 'before' I
> actually mean quite recently, so it's possible that this is a repost
> and I'm remembering the last post... :)).
>
