This is often caused by a lack of memory on the machine. I often see this is I have a lot of applications open while trying to run some workspace. In addtion to memory you should also check the amount of free space you have on your C: drive. If this is getting low you might also see this. The C drive is used as virtual memory.

Thank you @virtualcitymatt​  , all your set conditions are tick marked.

1. Space in C drive 79 GB, and D drive 60.5 GB available.
2. I didnt run with cache, hope you had seen in snapshot.
3. No other application opened, two folders were opened.
4. And the system is 128 GB RAM, physical machine.

Above all, memory issue means, it will say Disk space not available.

@Ryan Cragg1​  @dijkdjv​  or people from FME please give solution.

Because its 3D city modelling, average running time is 4 hours can't rely on FME.

Please help.

That's a lot of memory, so unlikely and issue, however, FME does sometimes operate (in some cases) that machine will have 3 times the amount of hard disk space as memory so there could be certain conditions where this might be an issue. But here is does seem unlikely.

You can rule this out if it always fails at the exact same point. Then it's most likely a data issue.

One thing you can try is to perform some GeometryValidataion on the features (Use Surfaces and Solids as the pre-set type.

I also notice a lot of warnings in the workspace, something here could give us a clue.

Another thing to try is to use the Old version of the Cesium Writer (works differently). This was available in FME versions FME 2020. If you want to try this out let me know and I'll upload a workspace with the old version in it which you can copy into the new workspace.

I can see that it looks like you've tried to run it without appearances, did this succeed? I assume so given your last comment. In this case it could be somewhere there might be some texture file with a format or structure witch is unhanded. You can use an AppearanceExtractor to get the unique appearances , filter for textures and the try and write out the Texture Files with a PNG Writer to see if you get any more clues.

If you do suspect it's data related then you might be able to isolate the problem data by splitting the data into sections and outputting four different datasets. Brute Force and slow but might be your fastest approach in the end

Thank you @virtualcitymatt​ for the timely response.

1. Memory Issue : As you said ruled out.
2. Data Issue : yes thats the only possibilty, i too accept that, for that i individually convert 417 buildings into cesium it produced correct output for files, once again confused.
3. Version ISSUE : I tried with 2022.1.2, 2022.1.3 and 2022.2.4 , because I need texture atlas option in writer.

As you suggested let me try your last suggestion like appearance extractor, let me try to write it into PNG and give you feedback.

Thankyou once again