The meeting add-in for Adobe Connect Professional has a built-in debugging feature. It is disabled by default, but can be enabled when required.
Note: Adobe Technical Support sometimes asks you to enable logging to assist them in troubleshooting a support request.
To enable add-in logging, follow the instructions below for the appropriate operating system:
Windows: Download the attached mms.zip file to the workstation where you want to enable logging. Extract the mms.cfg file and place a copy in: C:/Windows/system32/Macromed/Flash (32-bit Windows) and C:/Windows/SysWOW64/Macromed/Flash (64-bit Windows).
Download mms.cfg file generate add-in logs on Windows OS
Mac OS: Download the mms.zip file to the workstation where you want to enable logging. Extract the file into this directory: MainDisk:Library:Application Support:Macromedia
Download mms.cfg file to generate add-in logs on mac OS
Ubuntu: No mms file is required; the log is created automatically
Connect creates the log file the first time that you enter a meeting room. By default, the log file is named connectaddin.log, and is created in the following folders:
- C:/Documents and Settings/{user}/My Documents (Windows XP) or C:/Users/{user}\Documents (Windows Vista and Windows 7)
- MainDisk:Users: (Mac OS)
- ~/ (Ubuntu)
The following configuration parameters can be edited in the mms.cfg file to control logging functionality.
| Log file entry |
Usage |
| PlayerLogging |
0 to disable, 1 to enable logging. |
| SingleLogFile |
0 for multiple log files, 1 for a single log file. When set for multiple log files, the log filenames are appended with a timestamp. Therefore, there can be logs for multiple instances of the Add-in. |
| LogSizeLimit |
Number of kilobytes limit to the log file. Default is 1024 (1 MB) |
Note: For performance reasons, only enable logging for debugging purposes. Disable logging by setting PlayerLogging=0 in the mms.cfg file and saving the file.
Keywords:
fd606fac
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
