Friday, October 21, 2011

NAV 2009, 2009 SP1 and 2009 R2 in Same Machine Continued...

Hi all,

As promised in earlier post  that I will try to figure out the way to run classic report from Role Tailored client which is not installed on my machine.
One of my post  I explained that from where Role Tailored client find the path of classic client, I am just using that.
My machines have NAV 2009 SP1 Installed. I went to registry editor (regedit.exe) to find the key where the information of classic client in stored.

As you can see in the screen shot above (FOR WIN 7) that the information about classic client is stored in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CurrentVersion\App Paths\finsql.exe
Go to File & select Export and save the registry file on desktop with Name say NAV Classic for NAV 2009 SP1. Now open the file in notepad.

The selected line shows the path of finsql that need to start when we execute a report whose RTC Layout is not created.
Let’s change the file and make changes for other versions (NAV 2009 & NAV 2009 R2) classic default Path.
I saved the file with name NAV Classic for 2009 & NAV Classic for 2009 R2 and here how they looks.

Let’s create a new Report in NAV 2009 R2 say Test Report and try to run that report from RTC.
As expected I got the error.

Now let’s add information for classic client in Registry for NAV 2009 R2. For this just double click the registry file that we have created for NAV 2009 R2.
An Warning will appear, click yes.

Now let’s again try to run that report. (during this operation the RTC Client should be closed).

And it’s done.

You can restore the path of default version but just clicking on the registry file that we have saved in the first step.
Thanks & Regards,
Saurav Dhyani

Saturday, October 8, 2011

NAV 2009, 2009 SP1 and 2009 R2 in Same Machine

Hi all,

After Microsoft Released NAV 2009 Three Tier Architecture, we find issues while testing RTC on a version which is not installed.

Most of us uninstall current version and install the required version just for testing purpose.

I thought of creating multiple services for NAV 2009, NAV 2009 SP1 and NAV 2009 R2 in same machine with diffrent port numbers, so that we can run RTC also whenever required.

My Machine have NAV 2009 SP1 installed and i copied the Classic, Service and RoleTailored Client folder on my C Drive for Other two Versions.

I have created two Folders NAV2009 & NAV2009R2 inside "C:\Program Files\Microsoft Dynamics NAV\60".

For Creating Service for NAV 2009 i used the command-

SC CREATE MicrosoftDynamicsNAV2009 binpath= "C:\Program Files\Microsoft Dynamics NAV\60\NAV2009\Service\Microsoft.Dynamics.Nav.Server.exe" start= auto obj= "NT Authority\NetworkService" type= own

For Creating Service for NAV 2009 R2 i used the command-

SC CREATE MicrosoftDynamicsNAV2009R2 binpath= "C:\Program Files\Microsoft Dynamics NAV\60\NAV2009R2\Service\Microsoft.Dynamics.Nav.Server.exe" start= auto obj= "NT Authority\NetworkService" type= own

The Ports numbers i changed in CustomSetting.config file of three Services are-

Version Port Number
NAV 2009 6046 & 6047
NAV 2009 SP1       7046 & 7047
NAV 2009 R2 8046 & 8047

And after starting each service i Ran the .exe file from each RoleTailored Client Folder, which gives an error in the start where is says that version does not match, this is because it tries to connect to Default Port.

Once we change the port number it connect to the service.

* Remember
1) I have used the service Logon Credentials to "NT Authority\NetworkService" and it will only work if the you have created the Network Service on the database you want to connect and set its schema to $ndo$navlistener.
   For more information how to do that read the post here.

2) The RTC client will work fine but only for RTC objects, i mean to say that if you have any report which is not developed for RTC Client, you will not be able to run it (beacause while opening a classic report from RTC,it looks in the registry for the path of classic client, which will be set to default for the version that is installed.)

3) FOR windows 7 User Please Run Command Prompt as RUN AS ADMINSTRATOR.

I will try to find a work around for the same and will post again.

Thanks & Regards,
Saurav Dhyani