Microsoft Dynamics NAV 2009 SP1 installation moment…

Recently i met customer problem where NAV 2009 SP1 components didn't work after "correct installation".

Problem is: customer installs NAV 2009 SP1 components by run msi file - for example "Microsoft Dynamics NAV SDK.msi". But this way doesn't install "Prerequisite Components" needed by NAV 2009 SP1. And it could be these installed NAV components will not work (because it missing prerequisites).

Only supported way to Install NAV 2009 SP1 components is - run "setup.exe".

However "setup.exe" will uninstall previous NAV version and installs new NAV 2009 SP1 version. If you need to have few NAV version installed - you need to run msi (instead of setup.exe).
So conclusion: both ways have it strength and weakness. You can choose what you want, just you need to know about possible issues...

Gedas Busniauskas (gediminb)
Microsoft Customer Service and Support (CSS) EMEA

Comments (7)

  1. M. Gertz says:

    EVERY other version of Navision had the option, to install the new version beside the old versions (and that is necessary for partners, which have customers with different versions).

    Why not in NAV 2009 (SP1) ?

    i cannot find a reason …

    Best regards

    M. Gertz

  2. gediminb says:

    I would say: it is incorrect impression "other versions installs and works beside older versions"…

    What installer does: it copies NAV files from cd to installation folder and add some registry entries to windows registry.

    So if there was older NAV installed, and now we installed another NAV (for example NAV 5), it looks like we have 2 versions fully installed. But it isn’t true, because newer registry entries overwrite older registry entries. So now when we call any automation from any of NAv we’ll get only newer version… If we double clik on db then it will be open with newer version only…

    So NAV 2009 prevent us from these issue – we have only one version installed. I think this is big feature.

    Partner who needs both version installed, can install it manual, but he must understand – here will be all mentioned problems.

  3. Roman says:

    Big feature???

    What are you speaking about???

    I’m enployee of MBS Partner. I’m programmer. Out clients have 4.0, 5.0 and 2009 versions of NAV. What should I do to install correctly all version of NAV???

    It’s very big trouble and it’s not "big feature"!!!

  4. gediminb says:

    Guys… Don’t panic 🙂

    1. Where do you see any software where you can install 2 versions on the same PC without issues: Office; SQL; IIS; TS??? So NAV is as everything around.

    2. Even in older NAV, when there was possible to install few versions, it doesn’t mean both versions works in full functionality.

    3. We have many problems when end users installs few versions of NAV and playing with both, then accidentally connect to real db, convert it and… Or both version uses the same zup file and something crashed… So this feature doesn’t allow to have 2 versions on the same pc for all end-users.

    4. You are skilled more than end-users and you can install 2 versions on the same pc (look to my article from 11/17/2009), so we lost nothing, except easy risky possibilities for "everybody".

  5. Robert says:


    1) SQL -> Yes supported, Office -> Yes allowed, IIS is ‘officially’ part of the OS, if you mean Terminal Services by TS the it’s definitly part of the OS.

    2) With Navision it’s possible to install all major versions together (for me that’s 2.0, 2.6, 3.01, 3.60, 3.70, 4.0, 5.0, 5sp1, 6.0 and 6sp1). The core Navision client works correctly and it _was_ a fully supported setup. The only issues you get are that with later versions the automation objects included with Navision are no longer compatible. (Specifically the Office connectivity DLLs at first)

    3) An ‘accidental’ upgrade is quite avoidable, first off the idiot who does it has to click through two warnings without bothering to even look at the message. Second they have to have administrator access to the database. And thirdly you, the person who installed it, didn’t bother to provide distinct shortcuts that go directly into the relevent databases.

    4) All the ‘skill’ it takes to install V3.60 and v3.70 on the same PC is to select the ‘new’ option in the wizard. Are you saying you can’t do that?

    Just to hammer home the point gediminb the registry entries that the windows installer puts in the registry are NOT NEEDED for 99% of the Navision v4 and below application, it is quite possible to just copy the files off the CD and run fin.exe or finsql.exe (The latter needs an mdac; it isn’t that fussy about versions though) and everything works except a couple of minor interfaces with external applications.

  6. Franz Wøhliche says:…/dd301130.aspx:

    Installing with individual .msi files, which was a supported scenario in earlier versions of Microsoft Dynamics NAV, is not supported in Microsoft Dynamics NAV 2009.

  7. Franz Wøhliche says:

    … But despite all the comments on this saying it is not possible to have earlier versions installed with NAV 2009, it is possible to install NAV 2009 without removing earlier versions – You just need to install using the customization option not typical – Use the wizard (the main installaiton file), which actually works great in this version. However there can be a future issue regarding coexistance of versions beyond NAV 2009.


Skip to main content