In the GB Version of Nav 2016 Build 46290 (CU9) - when I export the Objects as Text it gets to 2171 of 4631 and just stops - same happened in the CU8 version! Anybody else noticed this and know what's happening?
1. Office is needed for outlook integration
2. Install office after installation of NAV is not enough
3. Re-Install NAV Outlook add-in after installation of Office is not enough.
4. Repair Nav installation after installation of Office is not enough
5. Completely uninstalled NAV and reinstalled. --> OK
Hi Archer89 - your probably right but in the pass you received a message warning of this but now it just clashes without noting which object it was that it clashed on?
Hi Jonathan thanks for all your help.
Seems to be the Outlook Synch.... Codeunits (5300..5312) that I can't Design or Export! Have you got Nav 2016 CU9 and experiencing the same issue?
in that case, it means, they are not within your license.
is outlook installed on the server? if not, then try exporting the objects on a client, where outlook is installed.
or simply exclude the outlook sync codeunits from export.
best regards
Franz Kalchmair, MVP
Alias: Jonathan Archer
1. Office is needed for outlook integration
2. Install office after installation of NAV is not enough
3. Re-Install NAV Outlook add-in after installation of Office is not enough.
4. Repair Nav installation after installation of Office is not enough
5. Completely uninstalled NAV and reinstalled. --> OK
Answers
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
same problem, .fob export works fine. Using also CU9
do you have a developer license? if yes, it could be a bug --> microsoft support
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Thanks for the feedback appreciate.
Stops at CU5065 and can export that codeunit singly as a Text File! Yes am using a Dev Licence.
With thanks
The offending object likely is not CU 5065 but one of the succeeding objects, likely the following, but there might be several objects in between.
restart nav service
try again
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Seems to be the Outlook Synch.... Codeunits (5300..5312) that I can't Design or Export! Have you got Nav 2016 CU9 and experiencing the same issue?
With thanks
is outlook installed on the server? if not, then try exporting the objects on a client, where outlook is installed.
or simply exclude the outlook sync codeunits from export.
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
Thanks for the further details.
Use our Dev 2016 Licence in NAV 2009 and I can open CU 5300. Using the same Dev 2016 Licence in Nav 2016 CU9 and it clashes!
Yes have Outlook installed.
Have included our permissions range which shows were allowed to open, adjust and execute that set of codeunits.
What happened to the old message of not having the right read permission access?
With thanks
Franz Kalchmair, MVP
Alias: Jonathan Archer
please like / agree / verify my answer, if it was helpful for you. thx.
Blog: http://moxie4nav.wordpress.com/
No this is a pure Nav 2016 GB CU9 Database with no adjustments whatsoever - just wanted to backup the Text Objects prior to any changes.
With thanks
You can find the files on the NAV installation media, in folder
Copy the OLSync folder+files to the Add-ins folder of your client-installation; default location would be
Or re-run the installation and add the Outlook Synchronisation option.
1. Office is needed for outlook integration
2. Install office after installation of NAV is not enough
3. Re-Install NAV Outlook add-in after installation of Office is not enough.
4. Repair Nav installation after installation of Office is not enough
5. Completely uninstalled NAV and reinstalled. --> OK
Other option is to not text export the Outlook Codeunit Objects (CU5300.. CU5313) !