Trapeze Pass: Troubleshooting DB connectivity between the Trapeze Service Shell and the Schedule Server

So, recently came across an unreported connectivity problem between the MT portal and the Schedule Server.  It seems that the ping from MT does not necessarily test DB connectivity.  So at least in V1 of the MT Portal, a successful ping does not mean that a scheduling call to the schedule server will succeed.  So, the MT homepage indicates that there was a successful load, but if you actually try to schedule, you'll get an error in the sched server log without the error being returned to MT. Here's a snippet of the error from the schedule server.  Note: a certain level of trace will have to be turned on:



<Message tcftype="10">ConnectionPool::GetConnection - failed to connect to datasource

SQLConnect returned SQL_ERROR (from HDBC), SqlState=28000, Native Error=18456, SQL_ERROR=0
Message=[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user &#39;trapeze&#39;.</Message>

So, I'm pretty sure the above login failed message has to do with the user name password configured within the Service Shell as seen below (Shell menu item, then Configuration), as opposed to the ODBC.

That said, it seems that the shell uses both the configured value (as above) as well as the SQL account configured within the ODBC.