Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 krishna prasad venu (krishnaprasadv)
Capgemini

Capgemini
US
krishnaprasadv Member since 2016 1 post
Capgemini
Posted: Apr 16, 2017
Last activity: Apr 28, 2017
Posted: 16 Apr 2017 21:43 EDT
Last activity: 28 Apr 2017 14:36 EDT
Closed

/PRWEB Requested resource not available

I am new to pegaworld and installed the recent version of pega. Installation was successful but when i click the login shortcut 404 message(PRWEB requested resource is not available) is displayed . i have tried different options but unable to resolve the issue.Can anyone please help me out on this.

***Moderator Edit: Vidyaranjan | Updated Categories***

To see attachments, please log in.
Security

Posted: 7 years ago
Posted: 16 Apr 2017 22:09 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi KrishnaPrasad,

Is it a personal Edition ?

What do you mean by Login shortcut? Post installation, one must ensure that app server is running successfully with an active connection to Pega rulebase DB.

Have you tried logging in using http://YourHost:Port/prweb URL?

Can you share us the error screenshot and logs if any? We can help! 

 

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 17 Apr 2017 21:16 EDT
krishna prasad venu (krishnaprasadv)
Capgemini

Capgemini
US

Sorry for not being clear. 

Yes, it is a personal edition. Let me explain the events 

i had personal edition 7.2.1 version and was working fine. I used it for a month .

I recently downloaded the 7.2.2 version and installed it.After install i tried starting up the server using the startup icon that is created on the desktop.It says server starting but with error message of cmd is not recognized as internal or external command.

So i started the tomcat server by going in to \bin folder and started the server successfully.

Once i click the login icon on the desktop it routes to http://localhost:8086/prweb and gives 404 error . I have attached screenshot of it. 

thanks for the reply

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 17 Apr 2017 22:58 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi Krishna,

Hope the older PE 7.2.1 instance is not interfering with 7.2.2 setup on your machine.

Just to confirm, removing the prweb from  http://localhost:8086 URL shows a tomcat home page?

I think we will have to look into the logs when you bring up your tomcat server. Can you scan your tomcat folder for Catalina.out n PegaRULES logs and share it here?

 

Thanks!

To see attachments, please log in.
Posted: 7 years ago
Posted: 18 Apr 2017 0:15 EDT
krishna prasad venu (krishnaprasadv)
Capgemini

Capgemini
US

yep, i am able to see the tomcat home page with http://localhost:8086 URL.

i have scanned the tomcat folder and found catalina.log file . I have attached the screenprint. I am a backend developer and very much new to this nuances. Please have patience if i am doing wrong.

To see attachments, please log in.
Posted: 7 years ago
Posted: 18 Apr 2017 0:43 EDT
Lakshmi Venkatesh Kakumani (kakul)
PEGA
Associate Technical Solutions Engineer
Pegasystems Inc.
IN
Hi, In the manager app of Apache home page, did you find /prweb started already? Try restarting it from the manager app. Are you getting any error? Also try redeploying the prweb war through the console if you find the same issue.
To see attachments, please log in.
Posted: 7 years ago
Posted: 19 Apr 2017 22:03 EDT
krishna prasad venu (krishnaprasadv)
Capgemini

Capgemini
US

on the Apache home page, the prweb app has not started. i tried restarting it but it fails with the message 

FAIL - Application at context path /prweb could not be started.

redeploying through console also did not work.

To see attachments, please log in.
Posted: 7 years ago
Posted: 19 Apr 2017 22:24 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi Krishnaprasad,

Please attach the latest Catalina.out log which is a complete one. The screenshot didn't really provide any useful info on failure deployment.

To see attachments, please log in.
Posted: 7 years ago
Posted: 21 Apr 2017 0:17 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi KrishnaPrasad,

From the server logs, it is clear that DB connection failure occurred.

 

Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:239)
    at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
    at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:127)

Please ensure to check the following. The JDBC URL and connections properties specified in context.xml should be validated. 

  • PostgreSQL isn't running on your machine

Show More

Hi KrishnaPrasad,

From the server logs, it is clear that DB connection failure occurred.

 

Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:239)
    at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
    at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:127)

Please ensure to check the following. The JDBC URL and connections properties specified in context.xml should be validated. 

  • PostgreSQL isn't running on your machine

  • PostgreSQL isn't listening for TCP/IP connections on 5432 - To check this run netstat -a & check if Postgres is waiting for connections on 5432 port.

  • Any other firewall services are blocking the connection from Tomcat to Postgres may be. 

  • In some cases, editing pg_hba.conf file under postgresql directory did help to allow all connections. (The cause is that the PostgreSQL pga_hba.conf file is not set to TRUST versus IDENT)

 

If you face any difficulties in validating/trying the above things, maybe you can raise one SR and get quick assistance on a screen share. I am sure support engineers can resolve this much quicker. 

 


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 28 Apr 2017 14:36 EDT
krishna prasad venu (krishnaprasadv)
Capgemini

Capgemini
US

I have validated the above listed things and looks like postgres is waiting for connection. Everything else looks good.

I have installed pega in my company's laptop and think this should have something to do with the firewall services. I have given it up and waiting to see if I can connect to pega on my companies cloud network. I do not have access to raise the SR.

Appreciate your help in providing me the inputs

To see attachments, please log in.

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

Pega Collaboration Center 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