Failed to find current installed version of PRPC while updating to Pega 7.3 from 7.2.2
Hi All,
We are updating Pega 7.2.2 to 7.3, while updating we have encountered below error
Error Message: setup\scripts\setupDatabase.xml:1513: Failed to find current installed version of PRPC
We have gone through the all PDN articles and made mentioned changes but no luck, Please Can anyone help on this.
https://pdn.pega.com/support-articles/upgrade-716-failed-find-current-installed-version
https://pdn.pega.com/support-articles/upgrade-718-failed-find-current-installed-version-prpc etc
Thanks,
Shravani
Pegasystems Inc.
US
Hi Shravani,
I had seen an issue with your jdbc url which is represented in your log file is different to the one that Pega has recommended as follows:
jdbc:microsoft:sqlserver://server:1433; database=dbName;SelectMethod=cursor;SendStringParametersasUnicode=false
Log file message:
pega.jdbc.url=jdbc:sqlserver://localhost:1433;database=SuperClaims;SelectMethod=cursor;SendStringParametersAsUnicode=false
Try to follow the above syntax and let me know if it helped you.
Regards
Mahesh
Virtusa
IN
Hi Mahesh,
Thanks for the suggestion,
By default jdbc url (jdbc:sqlserver://localhost:1433;database=dbName;SelectMethod=cursor;SendStringParametersAsUnicode=false) is prompting while updating the pega anyhow, I have given the path which you have shared but it is throwing an error even though the driver is available. PFA for the same.
Regards,
Shravani
Pegasystems Inc.
US
As per your document, looks like you had not replaced server text with your IP/Domain/localhost in ...//server:1433;.. depends on where your database resides.
Kindly test with this change and see if your test connectivity works.
Updated: 22 Sep 2017 8:02 EDT
Pegasystems Inc.
US
Is your 7.2.2 environment a split or single schema? What are the names of the schema(s)?
From the logs you have specified a single schema named dbo2 as both your rules and data schemas. Is it that you have already done the migrate step #1 to migrate your existing rules tables and pr_data_admin tables to this new dbo2 schema?
Virtusa
IN
Thanks for the update.
Is your 7.2.2 environment a split or single schema? Single Schema
What are the names of the schema(s)? dbo in Pega7.2.2
From the logs you have specified a single schema named dbo2 as both your rules and data schemas.
Is it that you have already done the migrate step #1 to migrate your existing rules tables and pr_data_admin tables to this new dbo2 schema? NO, We have created a new schema i.e:dbo2 (Single schema in 7.3)
Pegasystems Inc.
US
So in your dbo2 schema you have copied all of the tables from your dbo schema?
As the pega73 user that you are trying to run this upgrade as please connect to the database and run this database query:
SELECT count(pzcodesetversion), pzcodesetversion, pzcodeset FROM dbo2.pr_engineclasses GROUP BY pzcodeset, pzcodesetversion
Pegasystems Inc.
US
I do not understand what you are trying to do. If you didn't copy your 7.2.2 tables from dbo to this new dbo2 schema then what are you trying to update to 7.3? If you are trying to do an in place update from 7.2.2 to 7.3 and the schema that actually has your tables in it is dbo then you need to update the rules and data schema names to be dbo.
Virtusa
IN
Hi,
Thanks for the update.
We are doing the update for the first time,We have copied all of the tables from dbo schema to dbo2
So in your dbo2 schema you have copied all of the tables from your dbo schema? Yes
As the pega73 user that you are trying to run this upgrade as please connect to the database and run this database query:
SELECT count(pzcodesetversion), pzcodesetversion, pzcodeset FROM dbo2.pr_engineclasses GROUP BY pzcodeset, pzcodesetversion: PFB for query result.
(No column name) pzcodesetversion pzcodeset
17 07-10-25 pega-enginecode
143921 07-10-27 pega-enginecode
Pegasystems Inc.
US
Are you saying that you are running this update script from the database server node? When you ran the database query and logged in as pega73 database user was the tool that you were connected to also running on the database server node and you used the localhost in the url in the same way to connect and run the query?
Are you saying that you are running this update script from the database server node? When you ran the database query and logged in as pega73 database user was the tool that you were connected to also running on the database server node and you used the localhost in the url in the same way to connect and run the query?
In the scripts/config directory of the media there is a file called deploylogging.properties. Edit this file to change line 3
from: .level=INFO
to: .level=CONFIG
Resume the update and see if the logs show the exception that is being thrown from the query.