Shibd Daemon Failed to Start

One of the most common problems why the SP daemon does not start is malformed configuration files. In many cases this uses the xerces library which handles the parsing of the configuration files to throw exceptions. Check that your AAP.xml and shibboleth.xml files have the correct syntax and well-formed.

try to run shibd using -console so that it can spits out the logs on your console. Also, enable -check (on windows) or -t (on *nix) to make it check your shibboleth.xml. Not all configuration section can be checked by -check, but it's better than nothing