- The Central Management Store (CMS) value TmfFileSearchPath is not set. In this case, the search can decode events only if the event metadata is available in the Default.tmx file. This file is located in the following folder: %program files%\Common files\Microsoft Lync Server 2013\Tracing\Frequently, events from computers other than the querying computer correspond to different builds and are not described in the Default.tmx file. Therefore, you receive the error message. In this situation, the first troubleshooting step should be to run the Get-CsClsConfiguration command to determine check whether the value is set.
- The CMS value TmfFileSearchPath is set. However, the Universal Naming Convention (UNC) path to which it is pointing does not contain the necessary .tmx file. That is, there is no .tmx file that corresponds to the build from which the logged event is received.
To correct this situation, follow these steps:
- Find the Default.tmx file from the relevant build.
- Copy this file to the path that is set in the CMS value "TmfFileSearchPath."
- Rename the file by using a name that begins with the string "default_" and has the extension "tmx."
To update the CLS .tmx file search path, run the following cmdlet:
Set-CsClsConfiguration –TmfFileSearchPath <New Tmf Search Path>Note: Make sure that the new .tmf search path contains all the .tmx files for the environment under the root directory.
The TmxFileSearchPath, if set, should be a UNC path, or DFS path, so that it is accessible from multiple computers. If the TmxFileSearchPath is not a UNC or DFS path, then on each and every machine any reference to a *local* folder path should contain all needed TMX files. Local file paths will work, but can be tedious to maintain.
There is no need to set the TmfFileSearchPath to ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Tracing\’, because every ClsAgent looks at this location automatically.The Default.tmx files are located in the Skype for Business Server 2015 or Lync Server 2013 Common Files location under the \Tracing folder.
Article ID: 3053646 - Last Review: 20 May 2015 - Revision: 1