Here is my log. i’ve tried sub level streaming, deleting 50% of my scene and it still doesnt package successfully
Looks to me like the lighting info in “FirstPersonExampleMap_BuiltData” is too large for a normal cook. Must be smaller than 2GB.
When I have this problem I go through my scene and reduce the lightmap resolution on meshes that can afford to have lower res lightmaps until the built data is below 2GB.
“Compress lightmaps” in world settings should also be set to true.
I have heard that the lighting info can be split up into separate files so as to have each chunk smaller than 2GB but all in all contain the higher res information for the whole scene. I have not been able to figure out how to do that, though. Would love to know 
Hi i actually tried reducing the built data to less than 2GB and i have the “Compress Lightmaps” in the world settings checked but i still having the same result. The weird thing is that the fMemoryWriter does not support larger than 2 GB Archive Name: None.
Hi, i have recently solved this issue by reducing my scenes built data to around 1.3GB and increasing the Post Processing Volume → misc → Screen percentage to 200% and I was able to build it successfully.
Jup, had forgotten to mention the screen percentage setting in my first post. Also, in my experience the 2 GB limit is a bit fuzzy, particularly when comparing it to the number given in Build → Lighting Info → Lighting StaticMesh Info.
Happy to hear you got it working.
Me again.
Now I actually have the same problem myself and am not satisfied with my own solution
Tried to package a project in 4.17 which I had previously set up in 4.15. In 4.15 the packaging ran through but now in 4.17 I see the error that you saw as well. It appears to do with the size of the lighting build data (2GB max). However, the actual file size of that build-data on disk is only 1.8GB.
Did anybody else observe this? Is this really something to do with the UE version update?
I will start setting up my projects with sublevels in the future to keep the lighting info more under control, but for now I’d be interested in understanding the 2GB problem.