NAV 2015 Crash on Import Objects

mark_au

Hi community,

I've been having a weird issue with NAV 2015 Development Environment crashing when importing FOBs (not always though). I think I've found the reason so thought I'd share symptoms and solutions in case anyone else hits this.

The issue comes with the way I deploy changes, I take a backup of the objects I'm about to overwrite in my production database, which seems to be the trigger if you do it following the steps below:

1. Create FOB of change in DEV/TEST database to release to LIVE
2. Run the import in LIVE, and leave the import worksheet open
3. Open Object Designer, mark the objects that will be loaded from the FOB, and export as FOB and TXT to roll-back to in case of issue
4. Switch back to the Import Worksheet, and finish loading the objects
5. This is when the development environment crashes

It seems that switching over and exporting whilst the Import Worksheet is open is the cause of the problem, so not leaving the Import Worksheet open whilst exporting is the simple solution!

- Mark

geordie

Which CU are you using?
Can you ensure, if the dev and live are on separate servers, that you are using the same build?

mark_au

CU1. I haven't tried on a later build yet, haven't had the time.

DEV/LIVE are on the same server in every place I've had it happen, and definitely using the same build.

On my local laptop with a demo instance I had the same issue on the same service by:
1. Connect to plain demo database
2. Export any object (I picked a report once, table another time)
3. Import the fob and leave the Import Worksheet open
4. Export another object
5. Switch back and finish import on the Import Worksheet
6. Crash.

All on the same server and NAV session, so no risk of mixing builds etc.

davmac1

I always cancel the import. Do my exports. Then do the import for real.
Only takes a little bit longer.
To me, it is not a problem worth solving.
I am guessing you are throwing off versioning, but that is just a guess.

geordie

Agree with David.

Plus I was not able to replicate this issue with my CU4 installation.