Common Maestro ERP Connection Issues
This section explains the most common health check issues found for organizations using the Maestro adapter. Each described error focuses on what the issue means, possible causes, and how to proceed.
When an error in this documentation includes [session ID], the message displayed on your screen will instead contain a unique, temporary session identifier. Use the remaining text to locate the relevant guidance.
Select one of the following error types to view more details.
- Maestro session could not be initialized
- Maestro session became obsolete while opening the database
- Maestro session became obsolete during login
- Connection closed during the Maestro login
- Maestro closed the connection without responding
General Guidance for End Users
These errors do not usually indicate that you did anything wrong. They typically indicate an issue with the Maestro web server, session, service availability or network connectivity.
Next Steps
- Run the health check again once.
- Capture the complete error message exactly as it appears.
- Record the approximate date and time of the error.
- Provide the organization ID and related transaction details, if available.
Note: Do not include passwords or other credentials in support tickets, emails, or screenshots.
- If the error persists, contact Textura Support, your ERP administrator or your ERP consultant.
Related Topics
Maestro session could not be initialized
Maestro session became obsolete while opening the database
Maestro session became obsolete during login
Connection closed during the Maestro login
Maestro closed the connection without responding
Last Published Friday, September 25, 2026