|
Home > Archive > WebSphere Portal Server > August 2006 > Error 503: Failed to load target servlet [portal]
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error 503: Failed to load target servlet [portal]
|
|
|
| Hi,
I am getting this error 'Error 503: Failed to load target servlet [portal]' when I open my main portal page.
I know a few people have had this problem, and its caused by a bad connection to the backend database. However, I do not know how to fix it!
Can anyone guide me, as to where I can make a change in the portal config files, to get it to work. i have found a huge number of usernames as 'db2admin' in multiple configuration files. Can someone please tell me which file and field needs to be changed
for this?
thank you,
ankur
| |
| kai Schwidder 2004-08-19, 7:49 am |
| ankur_chakore@hotmail.com wrote:
> Hi,
>
> I am getting this error 'Error 503: Failed to load target servlet
> [portal]' when I open my main portal page.
>
> I know a few people have had this problem, and its caused by a bad
> connection to the backend database. However, I do not know how to fix it!
>
> Can anyone guide me, as to where I can make a change in the portal config
> files, to get it to work. i have found a huge number of usernames as
> 'db2admin' in multiple configuration files. Can someone please tell me
> which file and field needs to be changed for this?
>
> thank you,
> ankur
1) Make sure you have run db2profile of the DB2 instance under your current
user where you start the portal server
2) have a look at the portal log file: tail
-f /opt/Websphere/PortalServer/log/SystemOut.log
Under linux/windows this is the common error. To avoid it make sure that the
db2profile script is part of your local profile.
| |
|
| Try stopping both servers, "server1" and "WebSphere_Portal", and restarting the DB2 service, then, try to logon again to the Portal. Sometimes, the error is caused because the Portal is not communicating right with the database.
My personal recommendation, reboot the system first.
|
|
|
|
|