Getting a “Duplicates not allowed” error when attempting to backup song files
Applicable SongShow Plus Versions:
This article applies to all versions of SongShow Plus
* Updates correcting this issue may be available. Ensure that you are using the most current build of SongShow Plus from the Download page before proceeding. *
Symptom:
The user is getting a “Duplicates not allowed” error when attempting to backup song files. This is most likely from a pre conversion build of SongShow Plus prior to SSP 8.4, sometimes when transferring files to a new machine.
Possible Cause:
This error may be caused by a previous practice of manually copying song files. The error indicates that there are duplicate titles within the song file(s). This can occur even if the file name is not the same. FYI - in later SSP builds there were tools included and eventually, conversion of the songs format to prevent this type of issue.
Possible Solution:
The simplest solution would be to install the latest version on the old machine. This can be activated with licenses you have available. Once installed and activated you can open SSP do the following:
- Select the songs tab.
- Select the "U" icon for search all songs. This will generate the song list.
- Assuming your songs show up - continue. If not ensure that the Media Files path is correct - Configuration Settings - Media Files Location - Path
- From the top tool bar select Tools > Database Utilities > SongShow Plus > Rebuild Indexes...
- Click Yes to continue.
- Once this is complete, from the top tool bar select Tools > Database Utilities > SongShow Plus > Fix-up Song Titles...
- Click Yes to continue.
- This may prompt for duplicates or other issues to delete song files. Typically, these are corrupt in some way and do not show up in the songs list anyway. Proceed with deleting/editing the song files.
- Once this is complete restart SSP and the backup process should work as expected. FYI - Ensure you are selecting the "Songs" option for backing up song files and NOT the "SongShow Plus Database" option. The latter has been deprecated and is only for legacy use.
If this article does not resolve the issue, contact the Support Team.
(TS433)