There are some things not clear for users that want to run Dynamics NAV on Vista.  I would like to give you a clear picture on what needs to be done.

NAV and Vista Compatibility:

These Dynamics NAV versions are compatible with Vista:

• NAV 4.0, SP3 with
  • Update 1, KB 931841, Build 24080 (required)
    • This update includes Client files, NAS, NODBC, NSSDK, ADCS
  • Update 2, KB 933727, Build 24219 (optional)
    • This update includes Client files, NAS
  • Update 3, KB 936602, Build 24449 (optional)
    • This update includes Client files, NAS, SERVER

You can find more info hier:

https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={1A824679-0B9B-4BA7-BF5A-C6EB77FC43B3}&NRORIGINALURL=/partnersource/products/navision/newsevents/news/msdynav40_sp3_officevistacompatb.htm?printpage=false&NRCACHEHINT=Guest&printpage=false&wa=wsignin1.0

• NAV 5.0

When you want to install Dynamics NAV 4.03 and updates, make sure run run the setup as an administrator (Right click and select Run as Administrator).

When you want to install servers - uninstall existing versions first, then Run as Administrator.

Post installation information.

If you want to run the Dynamics NAV SQL Server Option and Microsoft SQL Server 2005, you have to set a traceflag.  How do you do that?

1. Go to SQL Server Configuration Manager
2. Go to the properties of the Microsoft SQL Server (MSSQLSERVER)
3. Click the "Advanced" Tab
4. Click Startup Parameters, and add the traceflag:

;-T 4616

The Startup Parameters should look something like:

1. Restart the Microsoft SQL Server Service

What does this traceflag do?

If you enable traceflag 4616, SQL Server turns off catalog permission checks completely for application roles.  Microsoft Dynamics NAV application roles need to have access to the metadata.

Known issues:

• Error when installing Dynamics NAV 4.0 SP3 or updates:
  • "The guide was interrupted before the installation of Microsoft Business Solutions-Navision 4.0 SP3 was completed.

The system has not been changed.  Run the installation program again later to completed the installation"

• Solution: Run the setup as Administrator!

• Error when running 4.0Sp3 client on vista:
  • "There are errors in the text conversion (Text no. 46-100 does not exist in the .stx file).

Internal error: 47-1"

And:

"Runtime Error!

R6025 - pure virtual function call"

• Solution:

Install update 1 for SP3, KB 931841

Note: updates are language/country sensitive!!

• Error when installing Dynamics NAV 4.0 Sp3 update 1:
  • "Error code: 1158"
  • Solution:

Check you're installing correct language/country version

Alternatively, install update1 on another workstation (or VPC), then copy and paste client files.

Tip:

To run NAV application older then 4.00SP3:

• Runtime Upgrade to Vista-supported clients
• Use TS or CITRIX
• Use Microsoft Virtual Server client
• Use Microsoft Virtual PC

Sources: Own experiences / Webcast by Jasminka Vukovic / MiBuSo

I just added 2 spreadsheets to the download section: a Granule List for Dynamics NAV 5.0 and 4.0.

You can use the Granule Lists to determine what objects are included in a certain granule, or in what granule a specific object is included, and this way detaermine which granules your customer needs to buy in order to gain access to certain objects.

The spreadsheet lets you filter on Granule Numbers, Object Types and Object Numbers.

You can find the download here.

My customer had the feeling that his former partner had done some "not-standard" developments in his  database, and he wanted to get a clear picture about this. Therefore, he contacted our company to do a 1  day investigation of the custom developments in his database, to get a picture on what is wrong, and  what should be done.

Here is a little description on how I do this, which might be useful to y'all.

Some considerations:

• Everyone can change the modified flag. This means that when you filter "modified=yes", you're  never sure you got all modified objects.
• Not everyone documents their code. This means you can't rely on documentation either.

This in consideration, I just compare every object to the base version. And guess what ... there is a rather  quick way to do that.

First of all you have to determine the base version.

First of all, click Help / About.  It could be that the client had an runtime upgrade, so be careful.  You  should interprete the version that is NOT between brackets (between brackets is the client version).  The  part that is NOT between brackets should be the database version.  Actually, it executes the code of CU1,  trigger "ApplicationVersion".  Sidenote: this trigger should always be changed when doing a full upgrade!   Also, this trigger should ONLY be changed when doing a full upgrade.

You see that only checking the "about" isn't enough.

What I also do is checking the version list of some base objects, like:

• Codeunit 80, 90, 12
• Table 17, 18, 32

The version is usually something like: NAVW14.00.  This is a 4.0 (no SP).  E.g. NAVW14.00.02 would be a  4.00SP2.

If you got all this info, I think you get a pretty good idea of what version the base version is.

Second, you export EVERY object to text from both the customized version and the base version.  After  that, you split the files with one of the many split file tools that you can download on the forums.  Here is  a link: http://www.mibuso.com/dlinfo.asp?FileID=831 .

I use the Arasis Merge to compare my files. 

Why?  Because it is not only possible to do a three way compare and merge (not interesting for this topic,  but very interesting for merge-jobs), but it has also a reporting functionality, where you can create an  HTML report based on the changed that it finds between the files of two folders.

When you run the report for your two folders, you get a summery like this:

Doesn't look exciting yet, except for point 2, I think.

BUT, furthermore, there is an HTML summery report where you can drill down till code level what the changes are.  So you get a list like this:

The blue lines are the objects that are changed.  If you click on such a line, you get a report which summerizes the changes in that file only:

And also a detail like:

It is very easy to drill down from overall level to code level.

This way, it's quite easy to get a picture of:

• All customizations in all objects
• The way it was coded
• The way it was documented
• The kind of functionalities that were created
• The way that "standard NAV methodology" was used (TEST NEAR, TEST FAR, DO IT, CLEAN UP)
• ...

Kind regards,

Eric Wauters