Skip to main content

Error: 'System.OutOfMemoryException' when trying to open or save or use a plan

Steps you can take to resolve an OutOfMemoryException error when opening, saving, or using a plan in Orchestrate.

Written by Arthur Ashdown

You may see this error when opening or saving a plan, creating a secondary plan, or adding works orders. Work through the solutions below in order until the issue is resolved.


Solution 1: Upgrade Orchestrate

A 64-bit version of Orchestrate is available from version 7.66, which significantly improves memory handling. Please upgrade to the latest version of Orchestrate.


Solution 2: Archive completed tasks

Archiving completed tasks from a previous period will clear space on the database and may reduce memory usage. To do this, first filter for the tasks you want to archive:

  1. Select Edit, then select In date range.

  2. Select the relevant options, for example, Tasks: Finish, Date options: Between dates, then click OK.

  3. Select Planning, then select Archive completed tasks.

🤓Tip: Select a meaningful date range to archive, such as completed tasks from 2018 to 2021, to free up a significant amount of space without affecting recent data.


Solution 3: Reduce or delete the number of open plans

If you are not yet in a position to upgrade, avoid having multiple copied plans open at the same time. Close any plans that are not currently in use and work with one plan at a time. Delete old plans from Plan Explorer sub-directories e.g. Saved Plans (select file, plan explorer).


Solution 4: Reboot servers

As a further workaround, rebooting the RDS or SQL server may also help to free up memory.


Solution 5: Obtain memory dump

When you next see these memory error message, please proide a memory dump at this exact point without closing the window will help us see what is causing this. If the user uses Orchestrate on a local machine, run the following command line:

C:\>whoami
  1. Log into the computer (server) where Orchestrate is running via the remote desktop connection

If there are multiple VMs where Orchestrate could be running on (e.g. multiple CTR boxes for MyDesk), you should check every one of them until you can find the offending Orchestrate instance.

2. Identify the offending Orchestrate instance

  • Open the Task Manager

  • Click Users tab

  • Find the user with the User ID

  • Find the running Orchestrate instance:

3. Capture a memory dump and save it as a file (*.DMP)

  • Right click Orchestrate instance

  • Click Create dump file menu

Once the dump is created, send it over support. Please start a conversation on the Access Community Portal. How to contact Support via the MyAccess Portal | Orchestrate Help Centre

Did this answer your question?