If you make a connection with invalid information (enter the wrong passwordfor the DB user for example) the admin module will create the connection but the logon will fail . Once you have created the connection because the connection is "bad" you can not remove it. You will receive the message that you do not have permission to remove the selected database connection.
Could not connect to database cm_typical@DIM14. Please check DB name and DB connection , and that the remote listener is running. Logging into the Desktop Client and DMCLI work as expected with no errors.
- Attempts to open an ADO connection to the db using that connection string So if this is failing : - try toggling thenetwork library selection via the Advanced button in the PO Logon dialog
For debug this situation I enabled SDP trace logs and found an event trigger called old connection name. I think that's why action driven deployment is failed .
The Crystal Cache Server then returns a generic error indicating a general failure of the Crystal Page Server. However, the viewer then makes a second request (a retry) to the next available Page Server thereby opening a second connection to the database (and using a second concurrent database license).
4) Restart IIS 5) In the peadmin module when making the database connection you must also specify the servername: Port ID (example: acme:9999) for the Server since localhost will not be used. 6) When launching the Portfolio Edge website you must add the Port ID in the web address: http://acme:9999/portfolioedge "
