question

Oscar W2 avatar image
0 Likes"
Oscar W2 asked Chandler commented

Simulation won't run

4x3 FH.fsm

When trying to run the simulation I get the following error immediately:

exception: Executive::__reset()

exception: int Executive::reset()

exception: reset

Changing the process flow or making a completely new process flow doesn't solve anything.

I can run completely new models, but not this one.

File attached!

FlexSim 22.0.0
exceptionresetexecutive
4x3-fh.fsm (183.5 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Phil BoBo avatar image
0 Likes"
Phil BoBo answered Chandler commented

Chairs 10-12 in the Chairs2 MultiLocation are misconfigured and are throwing the exception on reset.

If you delete that object and recreate it, then the error goes away.

I'll add a case to the dev list to look into this, but if you have any more information about how those chairs were created or modified to cause this issue, that would be helpful.

· 4
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Oscar W2 avatar image Oscar W2 commented ·

Thank you, it solved the issue!

I just added extra chairs to the chair-group by 1) putting checkmark in "Edit mode", 2) adding 3 chairs and moving them a bit around, 3) unchecking "Edit mode".

0 Likes 0 ·
Chandler avatar image Chandler commented ·
How did you identify that problem? I have a similar issue and would like to know how to troubleshoot it
0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Chandler commented ·
This was 18 months ago, but I guess I probably deleted objects and pressed Reset until the reset exception stopped happening in order to narrow down which object(s) were throwing the exception.
1 Like 1 ·
Chandler avatar image Chandler Phil BoBo ♦♦ commented ·
Thanks. I was wondering whether it was information in a log somewhere or a process like you've described.
0 Likes 0 ·