intermittent errors retrieving messages

[davehatz]

I have retrieved @ 11000 messages from the 73-87ChevyTrucks board.  
Several messages terminate download and crash the software with the following error;

"Error during write message to database.
Error information; The field is too small to accept the amount of data you attempted to add.  Try inserting or pasting less data."

I've checked several of the messages that crashed PGO to see if the individual  post included an entire digest or was not present at all.  The online messages look normal. ???

I would write the early posts off as missing but there are several groups of recent messages that give this error as well.

David

[Wilson Logan]

Hi Dave,

It could be due to the recent Yahoo changes or it could be someone with an outrageously long Yahoo user ID. Can you tell if its the same guy every time?

Thanks,

Wilson.

[wundrbee]

I get this error from time to time, also. I don't know what causes it, but I do know that if you open PGO and hit "refresh" that PGO will not shut down when you get this error. If you have this error and the group is selected - where you can see your list of messages for that group and hit recieve messages then PGO will crash / shut down. You still do not get that particular message, but PGO stays open and keeps running.

So as a work around for when I'm not at the PC to monitor the error messages and hit "OK" every time it happens, is to set that groups setting not to be included during refresh and when I am at the PC where I can monitor it - I change it back.

I hope that makes sense!

Tammi Upshaw

P.S. I wouldn't try anything in regards to downloading messages at the moment until Wilson and Alex figure out this Yahoo Format mess.

[Wilson Logan]

Hi Tammi,

Sound advice.

I think the base problem may be that the uder id field is too small. I seem to remember making it 80 characters, whcih should be enough but you know what some people are like.

Anyway, have you noticed the problem being linked to particular posters or does it seem random?

Cheers,

Wilson.

[wundrbee]

I don't think it is random. It always happens with a certain persons name or ID. Sometimes it's more than one person in a group, but it's always the same.

Tammi Upshaw

[Wilson Logan]

Tammi,

The next time yo see it happen, can you note down the groupname, userid & message number & I'll have a look at it?

Thanks,

Wilson.

[davehatz]

Wilson
The group is 73-87ChevyTrucks.  
I looked at which messages were missing in the first 100 as this is where I had the most trouble.  I haven't tried to grab the messages again.

#9, 13, 15, & 17 gave me the error.  
I looked over the missing messages for similarities such as username,  Quoting an entire 25 message digest.....   The usernames of the first few missing messages are munged by Yahoo with  @xxxxx.xxxxxxxxxxxxx... However these same users posted messages that I was able to retrieve further along in the archive without an error.  
Message 79 and 80 are by the same individual 79 came through 80 didn't.

I just tried message #9. The subject and username came through as expected with no message body also as expected no error though...
I don't know if this tells you anything at all right now as the message body wasn't downloaded....
On the surface it looks like the large field error was produced by something odd about the actual message body....  

I'll wait for the patch to do any more checking.

[wundrbee]

The next time yo see it happen, can you note down the groupname, userid & message number & I'll have a look at it?

Only after Yahoo stops mucking around with their format and you and Alex can play super heroes and come out with a patch to save the day ;D

Tammi Upshaw
Who is most frustrated with Yahoo at the moment.

[Wilson Logan]

Dave,

The user id field is limited to (I think) 80 chars but the message body field is a memo type field, so space is allocated to it dynamically. Effectively, it can't run out of space before it runs out of memory. And that would generate a different error message.

Odd!

Wilson.

[davehatz]

Wilson
Whatever you fixed in patch 2.5.35 appears to have fixed this issue as well....  
Thanks!!  ;D

[ricoman]

Wilson
Whatever you fixed in patch 2.5.35 appears to have fixed this issue as well....  
Thanks!!  ;D

2.5.35???? Where is it???? couldn't find it anywhere

[Wilson Logan]

There's a new patch to 2.5.037 (see top of page in News).

Cheers,

Wilson.