For additional instructions on running the tool, please refer to Using The Case Diagnostic Tool (CDT).
Start the CDT on the OSCE server with the issue and select all options. If the issue persists, download and run the Case Diagnostic Tool (CDT) on the OSCE server in order to collect debugging logs as follows: This will allow the updates to complete successfully. An alternative is to reboot the OSCE server. Restart the server's OSCE Master Service to release the mutex when the error message persists for more than 30 minutes during manual update attempts. For additional information, refer to the OSCE 11.0 Service Pack (SP) 1 Administrator's Guide, which can be downloaded from the OSCE Software Download Center. Re-install or upgrade the OSCE Plug-in Manager to the latest version. When this occurs, the following entries appear in the ofcdebug.log: Line 513124: 2016 06/28 18:31:11 (00) (D) FileChangeActionThread - CreateMutex:. This problem can occur when the OSCE Master Service cannot get the mutex held by the Plug-in Manager. However, if issues happen where the mutex is not released, then the message continues to be displayed long after the actual timeouts have passed. 
While the update proceeds and waits for the timeout, it shows the common message "Another update session is in progress".
Scheduled update => timeout = 30 minutes. 
Set proxy setting => timeout = 10 seconds. The mutex is used during the following timeout intervals: The download process is protected by a mutual exclusion object (mutex).
0 kommentar(er)
