Master Article - Entity Service Showing Notifications Failed Previously

The Entity Service seems to have stopped running. When looking at the Scheduler it shows On Hold or stuck in a Running Status. When looking in the Entity Service Notifications folder, all he notifications are showing Failed Previously.

• Payroll 
• Entity Service Configuration
• Scheduler Queue
• Time and Attendance 

• EERP (Munis) App server and TA (ExecuTime) App servers were not communicating.
• The Munis Entity Service Configuration record is incorrectly setup with a Username and Password

• Incorrect Notification URL or Notification URL had a trailing Space.

• The Subscriber settings description is set to ExecuTime Integration instead of ExecuTime.
• Issue with DNS records, DNS records needed to be added to allow the servers to talk to one another.
• Incorrect Genero and/or Web and/or Notification URLs defined on the Tyler Connectivity tab in Time and Attendance or Invalid Certificate 

• Entity Service Configuration showing Failed Previously - Error Processing Payload - TCP runtime exception Connection Timeout Expired
• Munis Entity Service Configuration processing failed - 401 Unauthorized
• Entity Service Configuration showing Notifications for ExecuTime Failed Previously - 404 Not Found Error
• Tyler Integration Not Running - EERP Entity Service Configuration Code and Description Must Match Tyler Notification Subscriber Code in Time and Attendance
• Entity Service Configuration showing Failed Previously - Error Processing Payload - TCP runtime exception Name resolution failed
• Entity Service Configuration showing Failed Previously - Error Processing Payload - TCP runtime exception Server name does not Match Certificate