When the installer fails to connect to your existing Oracle DB during an upgrade it is possible that the Oracle SID stored in the registry is incorrect. The value to check is:
1.) installed POWEb 2.) Create Web connection using POSecurityAdmin/pacedge Receive error message: "The specified database is not a Project Office 3.0 database"
When run report from Visual Studio or Report Server, get error "A connection cannot be made to the database . Object reference not set to an instance of an object"
After starting the VRS Upgrade GUI and then entering in the credentials for the database , the following error was received: Error: unable to connect to the specified DBMS
During upgrade to TT661 on a new Windows2003 server, connected to Oracle server, error ".... select statement could not be read from the 'Attachments table'", as the following screenshot
The setup of Mariner and Microsoft SQL Reporting Services (SRS) requires that both servers can initiate communication with each other. Mariner makes a call to the SRS server which in turn makes calls to the database via a data source that is setup in SRS. All calls to the Mariner database are processed through the Mariner Web application server.
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.
