These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Industry job cannot be completed,.Output container is too small.

First post
Author
Previous Topic Next Topic
Dunpeal Hunter
Zervas Aeronautics
#1 - 2014-11-05 18:35:35 UTC
Just reposting my in-game ticket to here, seeing if anyone else has this problem as well.

Hello. I just finished 2 seperate jobs of 2 megathrons, but i forgot to check on which container the output of the finished ships will be. So it was trying to complete the job to a Small Audit Log Secure Container, but that obviously didnt work because of the volume, and i got this message:

You can't add the Megathron as there simply isn't enough room for it to fit. It takes up 50000,01 units of volume, and there are only 116,60 left.

Is there any change you could move it for me to another container, or directly to my hangar? I couldnt see any way to do it myself.

Also maybe its an idea to add a cargo volume checker, to see if your current output place is big enough to handle the job? That would be very helpful to prevent this in the future.

o7
Dunpeal Hunter

I dont know if this is important or not, but i have chickens.....
GM Arcade
Game Masters
C C P Alliance
#2 - 2014-11-05 20:04:38 UTC
Please submit a ticket if you have not already done so. We should be able to help resolve this and get you the job outputs.

Lead GM Arcade | Customer Support Manager
Beness
Vojtech Fekete
#3 - 2014-11-14 20:45:10 UTC
Dunpeal Hunter - I had the same issue with a Dominix. I resolved the issue because of slow ticket response time.

Solution: Repackage the currently targeted container and deliver the job.

The job seems tied to the container ID, not name, so you can move the BPOs/BPCs in your current Small Audit Log Secure Container to a new Small Audit Log Secure Container with the same name prior to repackaging the current one.
Dr Farallon
Moongoo Mining and Mixing
Goonswarm Federation
#4 - 2014-11-15 06:56:22 UTC
I've tried the work-around and its not working for me. I repackaged and even reprocessed the container I assume is the destination container and it still says not enough room.
Beness
Vojtech Fekete
#5 - 2014-11-16 14:12:11 UTC
Instead of blindly repackaging, try putting something 5m3 into the container you think is targeted. If the available space in the error message doesn't change, you've got the wrong container.
Shawn Thornton
Center for Advanced Studies
Gallente Federation
#6 - 2014-11-26 00:29:58 UTC
Had the same problem. In the event you can't repackage the container because of an audit log, another option is to simply move the container to a ship. I keep my bpos in a small secure.

Move the offending output container into a ship and you don't have to repackage it. Also, the default output is typically the same container the bpo/bpc was in (assuming it was in a container).