Community Discussions and Support
mbxmaint_ui malfunction?

Joerg,

Your experience matches mine.  Glad to know that I'm not the only one.

 

 

<p>Joerg,</p><p>Your experience matches mine.  Glad to know that I'm not the only one.</p><p> </p><p> </p>

Corrupted mailbox...

Ran mbxmaint_ui using *.pmm in the "Folder to check" path...

mbxmaint_ui stopped with "Checking 'FOL03" as the final line displayed. 

I ran it again and this time it stopped with "Folder appears O" as the final line.  

Anyone have any thoughts on what appears to be an mbxmaint_ui  malfunction?  This mailbox contains +700 folders.

Edit:

Modified the "folder to check" setting to "FOL03*.PMM" but got the same stall
Modified the "folder to check" setting to 'FOL03A*.PMM, no stall
Modified the "folder to check" setting to 'FOL03B*.PMM, no stall
Modified the "folder to check" setting to 'FOL03C*.PMM, no stall
Continued in this manner until all had been checked.

My assumption is that mbxmaint_ui chokes when a large number of folders are requested to be checked. 

<p>Corrupted mailbox... Ran mbxmaint_ui using *.pmm in the "Folder to check" path... mbxmaint_ui stopped with "Checking 'FOL03" as the final line displayed.  </p><p>I ran it again and this time it stopped with "Folder appears O" as the final line.   Anyone have any thoughts on what appears to be an mbxmaint_ui  malfunction?  This mailbox contains +700 folders. </p><p>Edit:</p><p>Modified the "folder to check" setting to "FOL03*.PMM" but got the same stall Modified the "folder to check" setting to 'FOL03A*.PMM, no stall Modified the "folder to check" setting to 'FOL03B*.PMM, no stall Modified the "folder to check" setting to 'FOL03C*.PMM, no stall Continued in this manner until all had been checked. My assumption is that mbxmaint_ui chokes when a large number of folders are requested to be checked.  </p>

[quote user="Brian Fluet"]My assumption is that mbxmaint_ui chokes when a large number of folders are requested to be checked.[/quote]

Never heard of such an issue before, you might want to ask David Harris yourself whether he believes this could be possible or not.

<p>[quote user="Brian Fluet"]My assumption is that mbxmaint_ui chokes when a large number of folders are requested to be checked.[/quote]</p><p>Never heard of such an issue before, you might want to ask David Harris yourself whether he believes this could be possible or not. </p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

I never contacted David about this but a post over on the discussion list may be relevant.  A poster made the following observation about the mbxmaint file versions in v4.72 being older than the ones in previous versions.

v4.72
mbxmaint.exe        169,472        4/17/2011 4:29:56 PM
mbxmaint_ui.exe    180,736        4/17/2011 4:29:56 PM

Previous versions back to v4.63 (farthest I checked)
mbxmaint.exe        175,800        12/21/2011 1:46:40 AM
mbxmaint_ui.exe    187,064        12/21/2011 1:46:40 AM

An unknown is whether the December version fixed a flaw in the April version.  Another unknown is which version I was using when I encountered my problem (I have both readily available to me here at the office).

Edit:  The versions that are in the .zip file from the downloads area of this sight show a last modified date of 2/14/11.

 

<p>I never contacted David about this but a post over on the discussion list may be relevant.  A poster made the following observation about the mbxmaint file versions in v4.72 being older than the ones in previous versions.</p><p>v4.72 mbxmaint.exe        169,472        4/17/2011 4:29:56 PM mbxmaint_ui.exe    180,736        4/17/2011 4:29:56 PM Previous versions back to v4.63 (farthest I checked) mbxmaint.exe        175,800        12/21/2011 1:46:40 AM mbxmaint_ui.exe    187,064        12/21/2011 1:46:40 AM</p><p>An unknown is whether the December version fixed a flaw in the April version.  Another unknown is which version I was using when I encountered my problem (I have both readily available to me here at the office).</p><p>Edit:  The versions that are in the .zip file from the downloads area of this sight show a last modified date of 2/14/11. </p><p> </p>

I've made a note that I need to check the version difference out. Brian, if you could, would you be willing to send me the PMM/PMI file pair for the damaged folder so I can test the code out? I won't read anything and will delete it when I've done what I need.

Cheers!

-- David --

I've made a note that I need to check the version difference out. Brian, if you could, would you be willing to send me the PMM/PMI file pair for the damaged folder so I can test the code out? I won't read anything and will delete it when I've done what I need. Cheers! -- David --

There isn't a damaged folder David.  I repaired two that got damaged due to simultaneous access by a co-worker.  Out of an abundance of caution I tried to check all of the folders using PATH\*.PMM in mbxmaint_ui.  That is when I ran into the hang problem.  I ran it multiple times (3 or 4) and it hung each time but in a different place.  Processing the files in batches worked.  I can't tell you the size of the batches though, I just batched it on filename change (eg: FOL00*.PMM, FOL01*.PMM,...).  Luckily there were only a few user created folder file names.

There isn't a damaged folder David.  I repaired two that got damaged due to simultaneous access by a co-worker.  Out of an abundance of caution I tried to check all of the folders using PATH\*.PMM in mbxmaint_ui.  That is when I ran into the hang problem.  I ran it multiple times (3 or 4) and it hung each time but in a different place.  Processing the files in batches worked.  I can't tell you the size of the batches though, I just batched it on filename change (eg: FOL00*.PMM, FOL01*.PMM,...).  Luckily there were only a few user created folder file names.

I think there are some problems within the graphical output of the GUI version. I experience also some oddities when checking a complete big folder structure with *.pmm in path. Sometimes the batch output stops although the button "CHECK" is still in depressed position. Then I have to wait until the checking process is really finished. Or it is not willing to start after a lot of other folder checks done before. Then I have to exit and restart it and it works again.

But because I use it very rarely, I faced the facts. [;)]

<p>I think there are some problems within the graphical output of the GUI version. I experience also some oddities when checking a complete big folder structure with *.pmm in path. Sometimes the batch output stops although the button "CHECK" is still in depressed position. Then I have to wait until the checking process is really finished. Or it is not willing to start after a lot of other folder checks done before. Then I have to exit and restart it and it works again.</p><p>But because I use it very rarely, I faced the facts. [;)] </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft