5.0.01 upgrade- looping through job ledger entry

Cindy101

Hello,

So far so good, I think this upgrade I'm doing is going well (3.6 all the way to 5.0 sp1). That is until this morning when I started the 5.0.01 upgrade toolkit...

For the last 1.5 hours or so it has been looping through the Job Ledger Entry table, the first time I ran this it gave me this error after about 40 minutes of running - internal error 1355

So I'm getting kind of nervous here, anybody know what is going on? Or why/where that error came from?

Thanks.

Some more info:
At first I though it may have been a key issue with codeunit 104045 - step 1 in the upgrade - so I went though and made sure I had the two key that the codeunit was using SETCURRENTKEY on -

"Related to Budget","Job No.","Entry Type","Phase Code","Task Code","Step Code"
and
"Job No."

It seems to still be happening, and as it is looping (I really hope not once per entry because their job ledger is VERY big) it is using the Entry No. as the key. I didn't see any FINDs in the codeunit where it hadn't set the key for jobledgerentry so I don't know why it would be using Entry No. as the key...

Cindy101

I'm pretty sure I've found a solution to this, turns out there was a RESET used on jobledgerentry2, and afterwards no key set.

Here is a snippet of the code from the upgrade toolkit codeunit


IF FINDSET THEN
REPEAT
JobLedgerEntry2.RESET;
//ADDED THIS
JobLedgerEntry2.SETCURRENTKEY("Job No.","Closed by Entry No.");
JobLedgerEntry2.SETRANGE("Job No.","Job No.");
JobLedgerEntry2.SETRANGE("Closed by Entry No.","Entry No.");
IF JobLedgerEntry2.FINDFIRST THEN BEGIN

So I had to add in the SETCURRENTKEY