Just installed Hub Server 6.0.1.3 - Worker process suddenly stopped

I upgraded to Hub Server 6.0.1.3 and I started to receive this error message overnight, which is the main time I run the majority of the scripts.

The worker '######### (Chris's Account)' suddenly stopped — a restart is scheduled in 120 seconds.
Please check the Windows Event log for Application errors.

Here is the event log error:

Log Name: Application
Source: Application Error
Date: 6/26/2026 3:57:20 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SVA-ENG-RPT02.Presidio.Corp
Description:
Faulting application name: Morph.Server.Worker.exe, version: 6.0.1.3, time stamp: 0x6a060000
Faulting module name: KERNEL32.DLL, version: 10.0.20348.5256, time stamp: 0x433e7192
Exception code: 0xc00000fd
Fault offset: 0x0000000000001839
Faulting process id: 0x25ac
Faulting application start time: 0x01dd0537b8483d58
Faulting application path: C:\Program Files\EasyMorph Server\Morph.Server.Worker.exe
Faulting module path: C:\Windows\System32\KERNEL32.DLL
Report Id: 4f6653b8-bd9a-4c01-ba0a-85749e8d080d
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
0
2
100
0
0x80000000000000

29611

Application
SVA-ENG-RPT02.Presidio.Corp

Morph.Server.Worker.exe
6.0.1.3
6a060000
KERNEL32.DLL
10.0.20348.5256
433e7192
c00000fd
0000000000001839
25ac
01dd0537b8483d58
C:\Program Files\EasyMorph Server\Morph.Server.Worker.exe
C:\Windows\System32\KERNEL32.DLL
4f6653b8-bd9a-4c01-ba0a-85749e8d080d

BTW, this is not a one-off event, it is continuing to happen.

@Chris_Graziosi, we are looking into this. Can you please also send the Hub's debug logs (by default stored in "C:\ProgramData\EasyMorph Server\Logs\Debug log") to support@easymorph.com?

Just sent an e-Mail to support. I upgraded my Easymorph 5 server, and the path for the server is:
C:\Program Files\EasyMorph Server
and there is not Logs directory in that structure and I could not find the debug log anywhere in that directory.

Sorry, just found out that it is a hidden folder. I sent over the log file requested.

The ProgramData folder is hidden by default. You can see it by checking the "Hidden items" option in Windows File Explorer:

I have sent a few logs and even some Action Items to support. Looks like I am pushing the limits to some of the actions, but they work in the older version of your software.

@Chris_Graziosi, thank you for the project. It crushed for us too.

Have you considered refactoring your expressions to something like this?

The "Create table" action now supports adding two columns, so it would be more convenient than the example.

I would love to do something different, but because of the size of those actions, I cannot get into them to even try to change them to something else. This script has not been touched in months, and so, I need to be able to at least read the action to get the data out. Again, it worked in version 5.9 of your software without issues.

@Chris_Graziosi, EasyMorph project is just an XML file. I have extracted and decoded the expressions from it and sent them to you via email. I also took the initiative and extracted value pairs from those expressions into datasets in case you would like to refactor those projects.

The "Create list" action has issues with a large number of values too. It works, but in a not very responsive way. So I would suggest using datasets instead. You can edit a dataset directly from an "Import dataset" action.

In version 6, we've moved to a newer .NET version 8 (used to be v4.8). It's a substantial change, so it may take some time to iron out issues like that. We will also add a test for 600 nested if functions to ensure this problem is captured before releasing the software.

Going forward, I'd suggest using lookup tables instead of doing lookups with IFs. Keeping lookup tables in .dset files also makes them re-usable. Besides that, .dset files can be edited in EasyMorph - we've added Dataset Editor:

@Chris_Graziosi, the issue has been fixed. You can get the updated Desktop and Hub versions on the corresponding download pages.

We expect your projects to work as before. But if they won't, there will be an error message instead of a crash, and you'll be able to simplify your expressions (the source of the issue is the expression "deepness", so splitting a single complex expression into two should definitely help).