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

Pega installation fails



Pega application is installed on Microsoft SQL Server, however, the engine does not launch after deploying prweb.war on JBoss.

Error Messages

[com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource] (ServerService Thread Pool -- 18) Bootstrap datatables schema: pegadata.dbo
SEVERE [com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource] (ServerService Thread Pool -- 18) Unable to connect to database.  Will only use properties from file.: Invalid object name 'pegadata.dbo.pr_data_admin'.

Steps to Reproduce

  1. Run without specifying any information for Rule and Data schemas.
  2. Deploy Pega application on JBoss with data source configuration.

Root Cause

A software use or operation error.

According to the Pega install logs, and were blank.
This was because,

     [echo]  No schema provided, defaulting to user default of dbo 
     [echo] Rules schema has been set to 'dbo'


Make the following change to the operating environment:

Pega is installed in the default DBO schema.

Change the below script in JBoss standalone.xml,

<simple name="java:/prconfig/database/databases/PegaRULES/defaultSchema" value="pegarules.dbo"/> 
<simple name="java:/prconfig/database/databases/PegaDATA/defaultSchema" value="pegadata.dbo"/>

and set them to,

<simple name="java:/prconfig/database/databases/PegaRULES/defaultSchema" value="dbo"/>
<simple name="java:/prconfig/database/databases/PegaDATA/defaultSchema" value="dbo"/>

Suggest Edit

Published September 21, 2018 - 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