In this case, the exception is logged, and all the service's dependents will be trapped in a waiting state. This type of error will typically be due to transient conditions, like an incorrectly configured IP address, disk space issues, and so on. The correct behavior here is to log the error and let the user decide (based on the GUI or perhaps by deployment plan policy) whether to fix the issue and retry the failed service, let the error stand, or pull out the deployment unit.