One scenario that will cause this error is if SBM is started and the database is not available at that time. If you start or make the database available after SBM is started the User Workspace UI will recover gracefully and the SBM UI will work as expected but Composer ( Tomcat / JBoss ) isn't able to gracefully recover from this situation causing Composer to throw the error above.
The record list with the 'select .TS_ID, .TS_UUID from with (nolock) where TS_ID in (select TS_SOURCERECORDID from TS_USAGES where TS_FIELDID=153 and TS_RELATEDRECORDID=7)' select statement could not be read from the '' table.
Application Repository is inaccessible too with "Internal Server Error (500)" Running Static Diagnostics test shows all successful except Notification server and Mail Client Database Connection: Cannot connect to the Application Engine database or an internal error has occurred server.log showing many JDBC connection error such as:
Open the PPM Administration tool and Click New ( If you're running Windows 2008 right click on the PPM Administration icon and choose to "Run as Administrator" or you might get an error saying "Logon Failed: Unable to connect to database " when you finish.) Name the connection Click the "Only Connection" radio button
Open an existing item that had this problem before and verify your changes worked. If you look at the details for this driver on the Microsoft download scren it has the following text to show that this driver can be used with the followiing database versions. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database
With any of the errors above it basically means JBoss or Tomcat can't communicate with the database. When JBoss starts it reads the following files in order to connect to the database [SBM Install Dir]\Common\jboss405\server\default\deploy\commonlogger-ds.xml
In order to fix this situation you can either open configurator and go to the Database Servers screen and click the Upgrade Database link to upgrade the orchestration engine database or deploy the application again via composer or the repository.
One common scenario that may lead to an apparent corrupted password in the config file is when the document store database is copied from a test environment to a production environment or vice versa and the password used by the docstore is different on the two systems. In this case a new connection would need to be created on the server the db was copied to because the connection information is stored in the web.config file in the Documents Manager folder and if the passwords don't match the errors above can happen.
