Adobe Connect Support Blog

Updated April 20, 2022

Troubleshooting Verbose Meeting Application Logging in Classic View

On occasion it can be difficult to get verbose logging to work client-side with the Adobe Connect Meeting Application in Classic View. The tech-note describing how to set it up is here: Enable logging | Meeting App

The tech-note correctly describes where to place the customized mms.cfg file for use with both 64 bit and 32 bit Windows clients as well as for the Mac OS.

If after following the instructions in the tech-note, you still do not see any verbose logs, one possible cause is that there may be an additional mms.cfg file in an alternate location on the client that is blocking the log creation process. To remedy this, add the customized debug mms.cfg to the following locations after renaming any existing mms.cfg files (to allow them to be restored after verbose logging or debugging is complete):

Here are the locations (more than in the tech-note):

  • Windows (32 bit) :

In: C:\Windows\System32\Macromed\Flash\mms.cfg
or C:\Windows\System32\mms.cfg

  • Windows 7 (64 bit):

In: c:\Windows\SysWOW64\Macromed\Flash\mms.cfg
After placing the mms.cfg in both folders, be sure to close all instanses of the Adobe Connect Meeting Application and then open it only in the one Meeting that you wish to troubleshoot.

A problem may arise if the Adobe Connect Meeting Application was recently installed. The directory structure for mms.cfg may not exist. You may need to create the folders, Macromed/Flash and place the mms.cfg manually into the newly created folders. This will trigger verbose logging as expected.

Administration, Application, Clustering, Edge Server, General, Meeting, SSL

Join the discussion