cancel
Showing results for 
Search instead for 
Did you mean: 

Error msg : Service cannot be reached after deploying application on SAPWAS

Former Member
0 Kudos

Hi,

I am trying to deploy Business Objects Enterprise XI 3.0 on SAP Application Server (7.0). Able to create .EAR file and deployment is also getting successfully completed.

I am able to login and view reports in Central Management Console but in Infoview

Getting error while clicking on Document list.

Error msg : Service cannot be reached

What has happened?

URL

http://dssdev.ril.com/SAP/jsp/InfoView_Listing/infoviewListing.faces

call was terminated because the corresponding service is not available.

Note:

The termination occurred in system BD3 with error code 404 and for the reason Not found.

The selected virtual host was 0 .

What can I do?

Please select a valid URL.

If you do not yet have a user ID, contact your system administrator.

ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:SUN64_BD3_01-v:0-s:404 r:Notfound

HTTP 404 - Not found

Your SAP Internet Communication Framework Team

What could be the reason for the error as deployment goes fine and have checked all the services which are up and running. How to check if Infoview is been deployed properly or not.

regards,

Madhavi

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Madhavi,

To check the detailed log, please replicate the error and go to j2ee\server0\log directory and check the latest defaultrace file.

One of the easiest ways to check if the component has been deployed successfully or not and/or the version of the component, please execute :

http://<host>:<port>;

where host : where engine is hosted

port : the http port at which it listens. It is always 5<instance id>00

Select 'System Information' link , logon with j2ee administrator, click on 'all components' link. It will show you version info of all components deployed. If the component is not deployed, it won't be shown here.

Hope this helps,

Snehal

Former Member
0 Kudos

Dear Madhavi,

In the worst case, you can restart the J2EE stack/ engine and check out. If problem still persists, then maybe a depedency / prerequisite component is not running/ upto the SP level required by your application.

Regards,

Veera