I believe the cause of these problems is that the FME Server processes on one of the nodes have entered a corrupt state. The processes will not respond to Windows Service requests to shutdown, but they are still sending the correct signals to the other node indicating they are alive and well.
It’s not clear why these processes are becoming corrupt for some users. If you encounter this problem, please
contact our Technology Experts team to report it.
Resolution
To get the system working correctly, follow these steps:
- Shutdown the FME Server Windows Services.
- Open the Task Manager or equivalent and terminate all processes that start with "FME"
- Start the FME Server Windows Services.
@aaronkoning I'm having the same issues for some time now, and issued a support ticket for it.
It seems that the schedules are owned by the node that was active at the moment of creating a schedule. When this node becomes inactive node, the schedule isn't showing untill 'the schedule owner' becomes active node again. Schedules not just invisible, even not running anymore...
@aaronkoning I'm having the same issues for some time now, and issued a support ticket for it.
It seems that the schedules are owned by the node that was active at the moment of creating a schedule. When this node becomes inactive node, the schedule isn't showing untill 'the schedule owner' becomes active node again. Schedules not just invisible, even not running anymore...
Hi Jereonklien, I'm sorry to see this happening. We are going to meet internally to improve this. I have some questions that will help our discussions and might help other FME Server users that are running into this:
- Can you tell me if you are seeing FME* processes that remain even after the Windows Services are shutdown?
- How often is this problem occurring? Is it seemingly random?
- When this happens, are there any configurations being applied to the operating system, security or anything else related to the machine where FME Server is installed?
- What do you have to do to get things back to a healthy state?
Again, I apologize for this problem and we are looking at how to stop it from happening.