Nav 2013 R2 with multiple versions on same machine -> NST failed to start

(0) Share

Report

Posted on by X. GARONNAT

Hi,

On my dedicated server/VM (WS 2008 R2 Std), 3 NST are currently running for months with build 7.1.36035 without any problem (installed with DVD + Update rollup 3 applied).

Today I wanted to run a new NST with build 7.1.36703 (Update 7) on the same server :

Use dedicated folder C:\Program Files\Microsoft Dynamics NAV\71\DynamicsNAV71-36703
Setup the new NST to use the same user account and use a new database (on same SQL instance)
Start the new NST and ... it definitely won't start

Two errors raised (far below the connection to the database) :

.Net Runtime event 1025 with : The original message is: 'Server instance: DynamicsNAV71-36703 "MicrosoftDynamicsNavServer$DynamicsNAV71-36703 is using the configuration file: C:\Program Files\Microsoft Dynamics NAV\71\DynamicsNAV71-36703\Microsoft.Dynamics.Nav.Server.exe.config"'
Application Error event 1000 : Patu to app failed h: C:\Program Files\Microsoft Dynamics NAV\71\DynamicsNAV71-36703

Any help / idea will be appreciated,
Thanks, Xavier.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

X. GARONNAT on at

Like (0)

Report

Missing (1st bullet point) : I used ServiceTierAdministration to add the new NST binaires and create the new instance.

Was this reply helpful? Yes No
iwheatley 180 on at

Like (0)

Report

you need to create the new instance using powershell new-service command pointing it at the new directory structure, you may need to manually modify the config files in the new directories also

Was this reply helpful? Yes No
Verified answer

iwheatley 180 on at

Like (0)

Report

Like this

11. Type NEW-SERVICE and press [ENTER]

12. It will ask you to enter the name of the new service Enter MicrosoftDynamicsNAVServer$<DBNAME>

13. It will then ask you for the Binary Path Name

a. Enter the following modifying the locations to match your new files and folders

b. "C:\Program Files\Microsoft Dynamics NAV\71(36366)\Service\Microsoft.Dynamics.Nav.Server.exe" $d2013R2UPGRADETOOLKIT config "C:\Program Files\Microsoft Dynamics NAV\71(36366)\Service\Instances\d2013R2UPGRADETOOLKIT\d2013R2UPGRADETOOLKIT.config"

14. You can now change the required settings in the Microsoft Dynamics NAV 2013 R2 Administration console

Was this reply helpful? Yes No
Verified answer

X. GARONNAT on at

Like (1)

Report

Hi,

Thanks for your help. In fact, the .NET Runtime error 1025 was due to missing rights for my dedicated service account : has to put my domaine service account into the local Administrators group.

So here are my actions to make it work (considering you already have a RTM working service) :

On my SQL Server :

- restore new cronus 7.1.36703 database (from zip shipped into Cumulative Update file)

- add rights to my NAV domain service account :

• CREATE USER [DOMAINE\NAVServiceAccount] FOR LOGIN [DOMAIN\NAVServiceAccount]
• ALTER ROLE [db_datareader] ADD MEMBER [DOMAIN\NAVServiceAccount]
• ALTER ROLE [db_datawriter] ADD MEMBER [DOMAIN\NAVServiceAccount]
• ALTER ROLE [db_ddladmin] ADD MEMBER [DOMAIN\NAVServiceAccount]
• GRANT VIEW DATABASE STATE TO [DOMAIN\NAVServiceAccount]

On my NAV Server :

- assign domain service account to local Adminsitrators group

- copy existing (RTM=) folder C:\Program Files\Microsoft Dynamics NAV\71\Service to my own folder C:\Navision\Service.71-36703

- copy new binaires from Cumulative Update (..\NST\*.*) to C:\Navision\Service.71-36703 (replace all files)

- use Nav Powershell to add new service (dont use "." into service name, use "-" instead !) :

New-Service -Name 'MicrosoftDynamicsNAVServer$DynamicsNAV71-36703' -BinaryPathName '"C:\Navision\Service.71-36703\Microsoft.Dynamics.Nav.Server.exe" $DynamicsNAV71-36703 /config "C:\Navision\Service.71-36703\Microsoft.Dynamics.NAV.Server.exe.config"' -ependsOn 'HTTP' -Description 'Service handling requests to Microsoft Dynamics NAV application.' -DisplayName 'Microsoft Dynamics NAV Server DynamicsNAV71-36703]' -StartupType Manual

- setup new service in the Nav admin console (or CustomSettings) :

• Database Server
• Database Instance
• Database Name
• Port (for all services)
• Login Account (change to my NAV domain service account : DOMAIN\NAVServiceAccount)

- change ServiceName in CustomSettings.config : <add key="ServerInstance" value="DynamicsNAV71.36703" />

- change new service startup mode to Automatic with services.msc

;-)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks. Your detailed answer really helped me a lot.

Was this reply helpful? Yes No