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

0724.Logos4Exception.zip

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.

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.

thanks,

Find more posts tagged with

Comments

Lynden O. Williams

Dave if you are stumped, what do you expect of the rest of us. [:)]

Dave Hooton

https://community.logos.com/discussion/comment/155651#Comment_155651

Dave if you are stumped, what do you expect of the rest of us.

Sympathy[:(]

Lynden O. Williams

https://community.logos.com/discussion/comment/155653#Comment_155653

[:(] [:'(]

Bradley Grainger (Logos)

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.

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

https://community.logos.com/discussion/comment/155663#Comment_155663

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.

Thanks for that, Bradley.

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?

Bohuslav Wojnar

https://community.logos.com/discussion/comment/155693#Comment_155693

Dave, it was funny to see you asking questions here [:)] I always thought you are here for answers [H]

By the way, thank you for all you do for the Logos community here on the forum. [Y]

Dave Hooton

https://community.logos.com/discussion/comment/155718#Comment_155718

Thanks Bohuslav. The questions probably revealed some bugs and there isn't much on the net about the 0x80030070 error because my thread made it to page 1 of Google!

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/155693#Comment_155693

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.

Dave Hooton

https://community.logos.com/discussion/comment/155970#Comment_155970

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)

I did a PG on Josh-Ezek and private memory got to 1085 MB before it crashed with OutOfMemoryException! After restarting L4 memory got as high as 1110 MB but it did not crash. The high memory is definitely occurring in the Cross References section, but I have not seen the Exception 0x80030070! But this is a young session, so I'll see what happens after a day or so.

Mark Barnes

https://community.logos.com/discussion/comment/156009#Comment_156009

Two similar errors might help you in your diagnosis, Bradley. Both are caused by experiments on processing large amounts of data. Interesting, the folder path is the same as Dave's. Is the problem a hard-coded folder name in Logos?