I would guess that the postoffice name is incorrect, since the report option should write out the number of messages for each folder tested.
Unfortunately, if you have the name of the postoffice wrong, the utility does not seem to report that. (I will log that as a change so that it can be improved upon).
Here is another command line I tried for a postoffice called MAILENABLE with one user called Andrew:
Hmm - strange - thanks for theupdate. My last suggestion then is to use filemon to see the path that the mepurge utility is attempting to access. Perhaps there is some sort of underlying path issue/confusion on the server.
If that does not work, hen I think what may be best is to raise a defect/issue with respect to the mepurge utility (you should place a reference to this thread). See: http://www.mailenable.com/support
If possible, then consider submitting RDP details in the appropriate section on the submission form so an engineer can diagnose on the server itself, since I doubt they will be able to reproduce - I certainly could not).
Note: Since you have ent edition, you could always try using the management service to clean up these directories. ie: Mepurge functionality is integrated into ent edition.
MailEnable wrote:
Note: Since you have ent edition, you could always try using the management service to clean up these directories. ie: Mepurge functionality is integrated into ent edition.
Is the mailbox clean up agent or another tool? The mailbox clean up agent is configured on each mailbox and is not really a solution with so many mailboxes.
cmd.exe:4476 OPEN D:\Perl\site\bin\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\Perl\site\bin\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE"*
cmd.exe:4476 CLOSE D:\Perl\site\bin\ SUCCESS
cmd.exe:4476 OPEN D:\Perl\site\bin\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\Perl\site\bin\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE
cmd.exe:4476 CLOSE D:\Perl\site\bin\ SUCCESS
cmd.exe:4476 OPEN D:\Perl\bin\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\Perl\bin\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE"*
cmd.exe:4476 CLOSE D:\Perl\bin\ SUCCESS
cmd.exe:4476 OPEN D:\Perl\bin\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\Perl\bin\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE
cmd.exe:4476 CLOSE D:\Perl\bin\ SUCCESS
cmd.exe:4476 OPEN D:\PHP\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\PHP\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE"*
cmd.exe:4476 CLOSE D:\PHP\ SUCCESS
cmd.exe:4476 OPEN D:\PHP\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\PHP\ NO SUCH FILE FileBothDirectoryInformation: MEPURGE
cmd.exe:4476 CLOSE D:\PHP\ SUCCESS
cmd.exe:4476 OPEN D:\MAILEN~1\BIN\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\MAILEN~1\BIN\ SUCCESS FileBothDirectoryInformation: MEPURGE"*
cmd.exe:4476 CLOSE D:\MAILEN~1\BIN\ SUCCESS
cmd.exe:4476 OPEN D:\MAILEN~1\BIN\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\MAILEN~1\BIN\ NO SUCH FILE FileBothDirectoryInformation: MEPurge.COM
cmd.exe:4476 CLOSE D:\MAILEN~1\BIN\ SUCCESS
cmd.exe:4476 OPEN D:\MAILEN~1\BIN\ SUCCESS Options: Open Directory Access: All
cmd.exe:4476 DIRECTORY D:\MAILEN~1\BIN\ SUCCESS FileBothDirectoryInformation: MEPurge.EXE
cmd.exe:4476 CLOSE D:\MAILEN~1\BIN\ SUCCESS
cmd.exe:4476 OPEN D:\MAILEN~1\BIN\MEPurge.exe SUCCESS Options: Open Access: All
cmd.exe:4476 QUERY INFORMATION D:\MAILEN~1\BIN\MEPurge.exe SUCCESS Attributes: A
cmd.exe:4476 QUERY INFORMATION D:\MAILEN~1\BIN\MEPurge.exe SUCCESS Length: 98304
cmd.exe:4476 OPEN D:\MAILEN~1\BIN\MEPurge.exe.Manifest FILE NOT FOUND Options: Open Access: All
Unfortunately that filemon log does not provide any clues. The log only reports some system path lookups performed by the operating system. Typically, any file accesses by the application itself would follow after the end of your log.
As such, either mepurge is not even looking at the file system or the log was truncated. Assuming the first, then perhaps regmon might be step in diagnosing - since it will report if there are any problems reading the config from the registry. Failing which, the ticket is the best way forward.
