Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Moderators: Site Moderators, FAHC Science Team

Post Reply
csm725
Posts: 7
Joined: Tue Feb 14, 2012 5:38 pm

Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by csm725 »

Hey everyone.
I uploaded this WU after a ~48 minute TPF all the way through and saw the following error in my Langouste log:
Image
FAH and Langouste terminal windows report no issues whatsoever.
I'd appreciate if it could be checked why I got no points.
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by sortofageek »

You didn't get credit because you weren't able to complete the WU and return results successfully. Whether that is a bad WU or some other problem isn't clear yet.

I did check the database for Project: 6903 (Run 3, Clone 6, Gen 90). So far, there are no results from anyone. I will mark it for follow-up.
csm725
Posts: 7
Joined: Tue Feb 14, 2012 5:38 pm

Re: Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by csm725 »

Okay, thanks.
ChelseaOilman
Posts: 1037
Joined: Sun Dec 02, 2007 3:47 pm
Location: Colorado @ 10,000 feet

Re: Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by ChelseaOilman »

It's not a bad WU. Someone else has successfully finished and received credit for it.

Your WU (P6903 R3 C6 G90) was added to the stats database on 2012-03-29 06:07:54 for 261528 points of credit.
csm725
Posts: 7
Joined: Tue Feb 14, 2012 5:38 pm

Re: Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by csm725 »

Oh well.
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project: 6903 (Run 3, Clone 6, Gen 90) - no credit

Post by bruce »

There are a number of forum reports where we see the message "Read packet limit of X... Set to Y." and in all cases, folks seem to have had trouble getting the server to grant credit. This message is only seen on V6 client or earlier, and it has never really been fully explained. I recommend that you upgrade to the V7 client. I have a strong suspicion that you'll never have this problem again.
Post Reply