It is hard to say what might have gone wrong. Perhaps the best thing I can do is give you a little info to help you figure out what to do next.
The underlying page-to-gallery connection is stored in the GalleryControlSetting table. In a default installation, there is one record in there:
Code:
GalleryControlSettingId ControlId SettingName SettingValue
---------------------------------------------------------------------
1 ~/default.aspx|g GalleryId 1
The control ID is a pipe-delimited string containing the web page name and the ID of the gallery control on that page. You can look in this table to see if the data has the expected values; you can also edit it manually if it is so screwed up that the Gallery Manager doesn't work right.
Alternatively, you can override the page-to-gallery mapping in that table by hard-coding a gallery in the web page. When you open the web page (e.g. default.aspx) in a text editor, notice the gallery control is defined like this:
Code:
<gsp:Gallery ID="g" runat="server" />
If you add a GalleryId attribute, it will override the page-to-gallery mapping on the Gallery Manager page:
Code:
<gsp:Gallery ID="g" runat="server" GalleryId="1" />
Use this trick to hard code the gallery IDs for all your galleries. This might be useful if some bug is preventing the normal gallery management from working right.
Architecturally, the app should be able to handle thousands of galleries, although in practice I have no experience with anyone using 10 or more galleries in a real-world app. Not that they don't exist, but I am not aware of them.
I don't know much about the internal limitations of the 3rd party app in the Binary Pack, but if you want to troubleshoot I would try creating a thumbnail from the PDF with the command line. You'd use the ImageMagick executable (convert.exe). If that works, it should also work in the gallery. If not, then you might try finding an ImageMagick forum to figure out why.
Roger Martin
Creator and Lead Developer of Gallery Server Pro