Errors occurring during rebuilding of indexes for song or songs

Applicable SongShow Plus Versions: 
This article applies to all version 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:
When attempting to rebuild the indexes for any of the integrated song databases (Stock Hymns, Christmas Carols and SongShow Plus) various errors occur including Catastrophic Error, Invalid Pointer and SSP not responding.

 Possible Cause:
There is no fixed limit for the number of songs in SongShow Plus, however, this is most likely caused by a practical limit of the number of songs in the SongShow Plus database, which appears to be around 1980 songs.
To verify if this is the issue you can move several song files from the root of the songs folder to a temp location, then try to rebuild the index again.  If it is successful you may have too many songs entered.

Possible Solution:
Examine your songs list. If you have songs that you no longer need or you have extra copies of songs, you can delete these songs and try rebuild the index again.

Possible Solution:
Examine your songs list. If you have songs that you do not use often or are seasonal, you can move these songs to a new folder for later use and try rebuild the index again.
 
Possible Solution:
If you have songs that you need to keep that exceed the recommended limit and intend to accumulate more songs, the User Database Plug-in would be a good solution.  This allows the user to create a number of additional databases that are SSP accessible.  If you want to move existing songs to this newly created database see the KB article on importing into a User Database.

NOTE: It is not recommended to manually copy any song files into any SSP database folders.  This can cause unexpected and undesirable SongShow Plus behavior.  The backup/restore utility can be used to move a large number (or all) songs to a different system.

If this article does not resolve the issue, contact the Support Team.

(TS33)