Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 0 subscribers
  • Views 5211 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pure Message PMDebugLogs folder growing excessivly large

mbjoe

After upgrading to the latest version of PureMessage we noticed that a folder in the root of C called PMDebugLogs is growing constantly and filling up all space on the C drive on our Exchange server.

Is there a way to purge this folder, move it to a different drive or dump it completely? We just started having this issue after the upgrade.

:26755


This thread was automatically locked due to age.
  • 0

    Hi,

    Generally, that folder is only used for debugging support issues, so this would imply that there was a problem with a previous version of PureMessage that required log collection but debugging wasn't disabled afterwards.

    If you aren't running into any problems with PureMessage, it is safe to remove a registry key within the HKLM hive that points to it -- HKEY_LOCAL_MACHINE\SOFTWARE\SOPHOS\PMDebugLogs and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SOPHOS\PMDebugLogs for most flavours of Windows -- and then restart all the PureMessage services. (If you're running Windows 2003, there's a chance this may require a reboot since 2003 may not fully commit the change.)

    However, if you are continuing to run into PureMessage issues, you can modify the paths within that key to point to another folder. Some files in the PMDebugLogs folder will have an active lock with the process tied to it, so moving/deleting the files

    Since modifying the registry has the potential to interfere with normal Windows behaviour, it's recommended that you backup the registry prior to any changes. However, I would recommend calling/emailing support for assistance when working with the registry -- one of our frontline staff can help determine if any setting specific to your environment needs to be incorporated.

    :27045
Unfiltered HTML