Clue - look at CMD window. This issue will stay open as a known bug, but there is a workaround.
This issue happens when you have run the simulation and created Supplement Output Files, and left one of the output files open in another application, such as Excel. When you attempt to run the simulation again, the application is in an inconsistent state. An error message is shown in the CMD window that is similar to:
“Error ** : apparent-events-table-writer: Device or resource busy error when attempting to open file [lists files path]”
Upon returning to the Input side, the “Delete and apply changes” seems to happen, but it does not reset all the results. The scenario appears to have results present, which is shown by leaving the action button in “Return to Input” and showing that green bar with simulation results. If you attempt to run, it will return you to the Result screen which shows the hourglass as if the application is starting to run. It will stay in this state indefinitely, unless you terminate it by closing with the X.
Solution
This solution takes several steps, and you may have clicked around a few times trying to figure out what happened. The CMD error is the clue, so be sure you have checked it.
First, ensure that the output file is no longer open in the other application. Next, navigate to the Supplemental Output File folder within your scenario in the ADSM Workspace. Delete the whole Supplemental Output File folder. Close the application. The CMD window may stay active, with the message “Attempting to close server”. If this happens, close the CMD window with the X.
Upon restart, the scenario should be reset and available as usual. Result should not be present, so you are free to change parameters and run again.
Clue - look at CMD window. This issue will stay open as a known bug, but there is a workaround.
This issue happens when you have run the simulation and created Supplement Output Files, and left one of the output files open in another application, such as Excel. When you attempt to run the simulation again, the application is in an inconsistent state. An error message is shown in the CMD window that is similar to:
“Error ** : apparent-events-table-writer: Device or resource busy error when attempting to open file [lists files path]”
Upon returning to the Input side, the “Delete and apply changes” seems to happen, but it does not reset all the results. The scenario appears to have results present, which is shown by leaving the action button in “Return to Input” and showing that green bar with simulation results. If you attempt to run, it will return you to the Result screen which shows the hourglass as if the application is starting to run. It will stay in this state indefinitely, unless you terminate it by closing with the X.
Solution This solution takes several steps, and you may have clicked around a few times trying to figure out what happened. The CMD error is the clue, so be sure you have checked it.
First, ensure that the output file is no longer open in the other application. Next, navigate to the Supplemental Output File folder within your scenario in the ADSM Workspace. Delete the whole Supplemental Output File folder. Close the application. The CMD window may stay active, with the message “Attempting to close server”. If this happens, close the CMD window with the X.
Upon restart, the scenario should be reset and available as usual. Result should not be present, so you are free to change parameters and run again.