Use of debugger and adding status messages to NAV Data upgrade

rsaritzky

Hi all,

I'm testing the conversion of a pretty large database from NAV2009 to NAV2016, and the "Step 2" moving it to 2015 (one of the steps) takes quite a long time. We have a number of custom tables that has caused the process to stop with an error. One of the errors perplexed me for quite awhile. It would have been simpler if I could have used the debugger and seen where the process was when it generated the error. So, does anyone know, in NAV2015

1. During a Data upgrade process, can you add your own Dialog boxes with progress indicators? The "standard" progress window of 25%, 50%, 75%, 100% if you have 4 companies isn't much help. I'd like to put a window in that displays which function is being executed. In the Pre-2009 "old days", I modified the upgrade codeunits all the time to give me more detailed status.

2. Can you use the debugger during the Data Upgrade process. I tried this a couple of times, starting the debugger and then select "Debug next session". I then got an error, but the Debugger didn't kick in.

Any experiences out there with either of these?

Thx

Ron

mohana_cse06

1. you can check the progress in powershell scripts also.
2. we can use debugger in data upgrade. what is the error message?

jglathe

Hi Ron,

no and no. Data Upgrade is strange in this way. You can't even do explicit locking. If you want to run code only once (not by company), the best way I found was to check in the upgrade code if it's the first company in the list you're on. This prevented unwanted collisions. There also seems to be a way to set it in the FunctionType property, but this is NAV2016 CU4. Oh, and the "continue" feature is unreliable, btw. If an error occurs during data upgrade, consider the database as inconsistent. Meaning, for the live conversion no errors should occur at all.


with best regards

Jens

rsaritzky

Thanks Jens - too bad we have to "guess" on some upgrade errors. I've encountered an "Array dimensions exceeded supported range" error during data upgrade. I know it's related to the "User Rename" step. This error seems to be elusive - searches point to Powershell running out of memory. I expanded PS's memory allocation, but still got the error. Took that part out and created a SQL script based on Lars Westman's blog. Good news is that it reduced the data upgrade processing time by 56 hours...

Ron

mohana_cse06

1. you can check the progress in powershell scripts also.
2. we can use debugger in data upgrade. what is the error message?

jglathe

Hi Ron,

no and no. Data Upgrade is strange in this way. You can't even do explicit locking. If you want to run code only once (not by company), the best way I found was to check in the upgrade code if it's the first company in the list you're on. This prevented unwanted collisions. There also seems to be a way to set it in the FunctionType property, but this is NAV2016 CU4. Oh, and the "continue" feature is unreliable, btw. If an error occurs during data upgrade, consider the database as inconsistent. Meaning, for the live conversion no errors should occur at all.


with best regards

Jens

rsaritzky

Thanks Jens - too bad we have to "guess" on some upgrade errors. I've encountered an "Array dimensions exceeded supported range" error during data upgrade. I know it's related to the "User Rename" step. This error seems to be elusive - searches point to Powershell running out of memory. I expanded PS's memory allocation, but still got the error. Took that part out and created a SQL script based on Lars Westman's blog. Good news is that it reduced the data upgrade processing time by 56 hours...

Ron