Aha! Did you just use the configuration wizard to provision your search service? If so, you may run into a variety of issues. I fully recommend using PowerShell to provision enterprise search, on the plus side it also gives you a nice database name without the horrible GUI ID.

Here is a script that works pretty well. It’s also pretty self explanatory. You can use this to provision multiple search instances. Maybe you want a service for general content (People and content) and maybe another one for top secret senior leadership documents? Hopefully, this should help.