Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
It might be that you are trying to execute some large powershell processes and you get this System.OutOfMemoryException error. It happened to me when working with the new (still unreleased) version of This is Merging! for Dynamics NAV.
If you are suffering from the same issue, what Powershell is telling you is that the Powershell session is using more memory than allowed by the system.
And since Waldo released a Powershell Wrapper for NAV (which is what TIM uses) and I was getting this error, I thought it would be interesting to make a quick blog post about it.
In order to find out how much memory you have assigned you can do it by typing the following in a powershell command prompt (preferibly with admin rights):
In my case it is telling me that the maximum memory allowed per shell is 1024MB. It was not enough in my case I have enough memory in my computer, so I decided to assign more. And I did
In order to do so, type the following command:
set-item wsman:localhost\shell\maxmemorypershellmb 2048
Needless to say you can modify the value at the end of the instruction to suit your needs.
Once we have changed that we can check if the value has actually been changed by executing the first command:
So it is changed. Nice
The post Fix Powershell error: System.OutofmemoryException (incl. NAV PSM wrapper) appeared first on Code4NAV.com.
Business Applications communities