Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Exception during Extract rule connecting to external database

SA-83413

Summary



Exception occurs when running the Business Intelligence Exchange (BIX) Extract rule to connect to an external database.


Error Messages



The DataSource java:comp/env/jdbc/sqlPEGAPHL is invalid: Unable to obtain DataSource object: code: SQLState: Unexpected exception resolving reference Message: DatabaseException caused by prior exception: javax.naming.NamingException: Unexpected exception resolving reference [Root exception is java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerDriver] DatabaseException caused by prior exception: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerDriver | SQL Code: 0 | SQL State: null The DataSource java:comp/env/jdbc/sqlPEGAPHL is invalid: A connection could not be obtained.


Steps to Reproduce

  1. Create a BIX Extract rule whose output data is saved in an external database
  2. Create a Database rule which used JDBC connection pool details
  3. Run the Extract rule


Root Cause



A defect or configuration issue in the operating environment.


Resolution

Perform the following local-change:

Add the mssql-jdbc-7.2.1.jre8.jar file in lib directory of Tomcat server and restart the server.


 

 

Suggest Edit

Published August 19, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us