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 :
Two errors raised (far below the connection to the database) :
Any help / idea will be appreciated,
Thanks, Xavier.
*This post is locked for comments
Thanks. Your detailed answer really helped me a lot.
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
;-)
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
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
Missing (1st bullet point) : I used ServiceTierAdministration to add the new NST binaires and create the new instance.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156