Error: Exception 0x80030070 - insufficient disk space to complete operation.

Dave Hooton said:

Whilst browsing my log I noticed a series of entries like this:-

Error    Exception    Exception 0x80030070 in : There is insufficient disk space to complete operation.[e:\ccnet\working\digitallibrary\common\...

I had been playing around with My Passage Guide (on Desktop) using large ranges like Matt-Acts and had noticed some slow response which came from generating the Cross References section. I don't have a \ccnet folder on my E:\ drive - it may have been temporary - but the drive has 52 GB free space.

The error message is generated automatically by Windows; in this case it has nothing to do with disks (or the E: drive) but is caused by being unable to allocate memory for temporary storage. Unfortunately, I can't tell from the log what was trying to allocate the memory and causing this error.

Dave Hooton said:

Also, what is the meaning of the series of messages like:-

Warn    KeyLinkManager    Matched override reference gnt/132837 in LLS:46.30.4 but there were no corresponding milestones for the headword/reference.

I'm not totally sure about this one, but I suspect it might indicate a tagging problem in Louw-Nida; I'll file a bug report.

Dave Hooton said:

Bradley Grainger said:

The error message is generated automatically by Windows; in this case it has nothing to do with disks (or the E: drive) but is caused by being unable to allocate memory for temporary storage. Unfortunately, I can't tell from the log what was trying to allocate the memory and causing this error.

Is there anything I can do to diagnose it further?

The actual error being issued is "STG_E_MEDIUMFULL", which is documented at http://msdn.microsoft.com/en-us/library/ee489596.aspx. Our code is returning that error because its underlying request to allocate more memory is failing.

You could look at the "Memory (Private Working Set)" column in Task Manager at the time it happens and see if it seems unusually high. As I mentioned before, I can't tell from the logs what it's trying to allocate this storage for, so I don't have a good guess at how much memory it needs, but I would imagine that the private bytes counter would have to be pretty high (> 1.5GB) for it to fail. OTOH, if it were that high, I would expect the app to crash with an OutOfMemoryException (which doesn't seem to be the case). So... I'm a little puzzled.