Community Tips and Tricks
Community Tips & TricksMattJ from the community had some file corruption problems, causing the ExportTools.bundle to fail, and here are his words on the issue:
If “Extended” fails in PMS for Windows 8.1:
- Open the ExportTools.bundle log file in Word, Notepad, or Wordpad. The file is usually in this folder:
“C:\users<username>\AppData\Local\Plex Media Server\Logs\PMS Plugin Logs” with a file name like “com.plexapp.plugins.ExportTools.log”. Sort by “Date Modified” to get the latest.
- Search for “Exception”. This is where the plugin has stopped and begins to write to the output.
- Scroll up a little bit to find the failed Media ID number. It will be the last request for Metadata before the failure and will look something like this (your IP and media ID number will differ):
Requesting 'http://127.0.0.1:324...y/metadata/1404' followed shortly thereafter by the exception...
CRITICAL (logkit:25) - Detected an exception in scanMovieDB Extended
- Copy http://127.0.0.1:324...y/metadata/1404 (your version) to the clipboard.
- Open any browser and paste the address from the previous step, remembering to remove the ' and to specify the local IP address of the PMS server. (Note: If your outside your LAN, you'll need to specify the IP address of your router and the port opened to PMS. See the Plex support page if you don't know how to do this.)
- Search for “container=”. If ANY of the container values show
<container=””>, chances are the file is corrupt. As the PMS XML is derived from the file, and ExportTools.bundle depends on the XML to do its business, the corrupt file is causing the failure and not ExportTools.bundle. - Now that you know the file name, try to open the file directly from the library (not using Plex). If you get an error, you need to fix or delete the file, update your database (make sure the entry is gone), and then run ExportTools.bundle in “Extended” mode again.
This procedure should also apply for similar errors while running ExportTools.bundle in "Extreme" and "Extreme 2" modes.
Note: You may have to repeat these steps several times if have a large library and ExportTools.bundle continues to fail. The good news is that you’ll be cleaning up your database at the same time.
sandersoni from the community was struggling with getting an export path right on a Synology NAS, where the Plex Server had the needed rights , and here's what he found out:
If you are not familiar with how to address your Synology NAS, you can find a valid path by checking the path to one of your PLEX libraries (Sections), and derive a path from that.
Most likely it will look something like: /volume1/media/movies/
(Editors note: Above would work on all server platforms)