NAV2013 --> 2013R2 Upgrade problem
taher.bha
Member Posts: 48
Hi experts,
I'am trying to upgrade A NAV2013 database to NAV2013R2 following Ms guide (see http://go.microsoft.com/fwlink/?LinkId=324164). I'am using a French localisation.
I'am having the following erreor when trying to running the Example.ps1 using powershell ISE as a final step. The script is supposed to automate the process based on given prerequisities.
The script Example.ps1 is originally located in the WindowsPowerShellScripts\Upgrade from the NAV2013R2 DVD.
Before running the script i manually run the following commande : Import-Module C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1
Here's the script's execution error :
COMMENTAIRES : Admin connection to ServerInstance 'MicrosoftDynamicsNavServer$1_64e8311c-1548-4d98-a120-fbc135594b6b' has been closed
Invoke-NAVCodeunit : Le terme «Invoke-NAVCodeunit» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou programme exécutable.
Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct et réessayez.
Au caractère Invoke-UpgrateToolkitStep1ProcessPreconditionsPerCompany:91 : 91
+
+ CategoryInfo : ObjectNotFound: (Invoke-NAVCodeunit:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
...
A possible english translation of the bold part of the message (google's) would be : The term 'Invoke-NAVCodeunit "is not recognized as the name of a cmdlet, function, script file or executable program.
Check the spelling of the name, or if a path exists, verify that the path is correct and try again.
Any Ideas ? Thanks in advance.
I'am trying to upgrade A NAV2013 database to NAV2013R2 following Ms guide (see http://go.microsoft.com/fwlink/?LinkId=324164). I'am using a French localisation.
I'am having the following erreor when trying to running the Example.ps1 using powershell ISE as a final step. The script is supposed to automate the process based on given prerequisities.
The script Example.ps1 is originally located in the WindowsPowerShellScripts\Upgrade from the NAV2013R2 DVD.
Before running the script i manually run the following commande : Import-Module C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1
Here's the script's execution error :
COMMENTAIRES : Admin connection to ServerInstance 'MicrosoftDynamicsNavServer$1_64e8311c-1548-4d98-a120-fbc135594b6b' has been closed
Invoke-NAVCodeunit : Le terme «Invoke-NAVCodeunit» n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou programme exécutable.
Vérifiez l'orthographe du nom, ou si un chemin d'accès existe, vérifiez que le chemin d'accès est correct et réessayez.
Au caractère Invoke-UpgrateToolkitStep1ProcessPreconditionsPerCompany:91 : 91
+
+ CategoryInfo : ObjectNotFound: (Invoke-NAVCodeunit:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
...
A possible english translation of the bold part of the message (google's) would be : The term 'Invoke-NAVCodeunit "is not recognized as the name of a cmdlet, function, script file or executable program.
Check the spelling of the name, or if a path exists, verify that the path is correct and try again.
Any Ideas ? Thanks in advance.
0
Answers
-
It seems that it is still referring to the Management DLL of NAV 2013, where Invoke-NAVCodeunit was not available. Do you have both NAV 2013 and NAV 2013 R2 installed on this box? Try running Repair (from the Add/Remove Programs) on NAV 2013 R2 installation or uninstall NAV 2013 from this box until the upgrade is complete.
There are more elaborate ways of making NAV 2013 and NAV 2013 R2 coexist on the same box - there is a hotfix released for NAV 2013 which solved the problem of 2 management dlls running side-by-side - you can search the forum, or you can try replacing the “Add-PSSnapin "Microsoft.Dynamics.Nav.Management"” line with Import-Module “C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1” line everywhere in the upgrade scripts... but the workarounds above are the quickest.
Best regards,
DMC0 -
Thanks a lot DMC.
Both 2013 and 2013R2 versions were indeed on my laptop. Reinstalling Dynamics Nav 2013 R2 with latest Rollup Update resolved the issue.
Thx again.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 333 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions