Note for Servers
Because of current limitations on the Minecraft engine, when starting a new save on dedicated servers the target database won't be generated until a currently online OP runs the /kismet reset command. Running it from the server console won't work, it has to be done from a client-hosting process.
Most, if not any, of the mod features won't work properly until this is done. This is noticeable by any displays in the world having the crystals darkened out, as in the following picture.
Also, target database seeding requires extensive client <=> server communication so this process may need to be repeated in case of failure. Sorry.
Thankfully, this is an one-off procedure as the database is stored in the world save. Although /kismet reset should be run again if you have done any configuration changes relation to recipes or available items (such as adding a new server-side mod, or disabled a recipe) to update the database, but the mod will still function fine without it.
Essentially, dedicated server instances can't figure out item and block sub-types as the processes to gain these are gated behind client-only code. And this is necessary as, without it, Minecraft servers can't guess that there's different kinds of wool blocks or tree logs or potions, just to mention a few. Fixing this outside of my control would require a lot of API-breaking changes from Forge.
If you really must, /kismet serverOnlyReset rebuilds the database without any required client interaction. I offer no extra responsibilities if the target selection is poorer as a result.
Another (frankly silly) alternative is setting the config Generate Items to None and adding all desired block sub-types, by hand or /kismet force, to the Forced Targets list, these also in the configs.