Question
Mphasis
IN
Last activity: 10 May 2020 13:59 EDT
Not able to login after upgrade to 8.3.1
Hello,
We are upgrading from Pega platform 7.3.0 to 8.3.1
Post upgrade we are not able to login to the application. Login screen comes, after entering the credentials a blank blue screen comes, so we cannot proceed further. We restarted servers clearing pr_temp but still same issue.
In the log we see below errors.
2020-05-04 14:04:15,877 [175yr.dc-ratingen.de] [ STANDARD] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - Internal error: failed to retrieve checksum from ConclusionCache for an existing instance of Rule-File-Text class: "webwb.pzpega-ui-inspector-panel.css"
2020-05-04 14:04:15,877 [175yr.dc-ratingen.de] [ STANDARD] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - An internal error occurred while looking up static content information. Please contact your system administrator for help.
Hello,
We are upgrading from Pega platform 7.3.0 to 8.3.1
Post upgrade we are not able to login to the application. Login screen comes, after entering the credentials a blank blue screen comes, so we cannot proceed further. We restarted servers clearing pr_temp but still same issue.
In the log we see below errors.
2020-05-04 14:04:15,877 [175yr.dc-ratingen.de] [ STANDARD] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - Internal error: failed to retrieve checksum from ConclusionCache for an existing instance of Rule-File-Text class: "webwb.pzpega-ui-inspector-panel.css"
2020-05-04 14:04:15,877 [175yr.dc-ratingen.de] [ STANDARD] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - An internal error occurred while looking up static content information. Please contact your system administrator for help.
2020-05-04 14:04:15,878 [175yr.dc-ratingen.de] [ STANDARD] [ ] [ ] (ticcontent.StaticContentClient) WARN - An internal error occurred while looking up static content information. Please contact your system administrator for help. resulted in "500" http response from request /-Y_n0g1ZkUjELaFhdaBKnhbDHrR3m1dq*/webwb/pzpega-ui-automation-style-bundle_11902511792!!.css requestor=HM7MZ2PC59U16QEEBNXRPJ8IGCICHL16SA referrer=http:// Proprietary information hidden:7550/prweb/-Y_n0g1ZkUjELaFhdaBKnhbDHrR3m1dq*/!STANDARD?pzuiactionzzz=CXtpbn1YNUdpMG1vUzZQMUZ1anJROE43ZlN0RUR5Mmp0MEhnNFNwUm12UEFWVzQrVDgwVDBuVGZXVmNldlRZTVNOQklQdCszQlM3MW9nemVxRUFoOVkvdTdoNXgrYWtDT0JSbFRtN29md3RCMDRYcz0%3D*
Thanks in advance
Sathish
***Edited by Moderator Marissa to update Platform Capability tags****
Accepted Solution
Updated: 7 May 2020 8:39 EDT
Mphasis
IN
Hello,
We had call with pega expert and decided to re run the upgrade script. After running the script, the issue is resolved and now we are able to login successfully.
We upgraded all lower environments before, but not encountered such issue.
Thanks
Sathish
Pegasystems Inc.
US
Is the [email protected] operator enabled? If it is, do you see the same error when trying to log in with that operator?
Pegasystems Inc.
IN
Looks like css is corrupted.
Check if there are 404 or 500 errors on the static content requests ,you can open the developer options(press F12) and check it .
You can raise a SR so that one of our engineers will assist you further.
Pegasystems Inc.
US
If you decide to open a a case with our Support Engineers, please mention this post and let us know the INC ID so that we may track this for you, Satish!
Thanks!
Marissa | Senior Moderator | Pega Collaboration Center
Accepted Solution
Updated: 7 May 2020 8:39 EDT
Mphasis
IN
Hello,
We had call with pega expert and decided to re run the upgrade script. After running the script, the issue is resolved and now we are able to login successfully.
We upgraded all lower environments before, but not encountered such issue.
Thanks
Sathish
Pegasystems Inc.
IN
Hi,
The logs show errors in the upgrade.
You can also verify from the upgrade logs whether the upgrade happened properly or not.
If there are errors in the upgrade you need to fix that first.