Skip to Content
0
Former Member
Feb 01, 2007 at 02:19 AM

separated j2ee & n pdk servers configuration problem

21 Views

Hi,

i can preview a portal page, but the iview within gives an error.

please let me know the configuration to be changed in order to successfully run the Portal Component [ivew] using the .NET PDK

i am running the following:

portal server

J2ee - java stack : nw2004s : sp09

win2k3 : 64 bit

ip : 10.8.2.64

sys no : 04

url portal access : http://10.8.2.64:50400/irj/portal

.net pdk 2.0 for vs 2003 : hf1, hf2

win xp sp1 : 32 bit

ip: 10.8.1.101

server00

ports 8050 & 8051 are opened on the firewall

Property Editor - ara:/applications/com.sap.portal.dotnet.framework/services/iViewProcessorService

1. .NET Runtime Servers Configuration

*=10.8.1.101:8050;

2. Portal Servers Configuration

*=10.8.2.64:50400;

3. .NET Runtime Failover Servers Configuration

*=10.8.1.101:8050;

4. Allow Server Affinity

true

5. Display ASP.NET Stack on ASP.NET Error

false

6. Enable Ja.NET Logging

false

7. Lease Duration (seconds)

10

8. Request Timeout (milliseconds)

10000

9. Production Mode

false

Ofer's reply on

could-not-find-portal-application-comsapportalcomm

was helpful, but still not allowing my portal component to run successfully

a question on the Portal Servers Configuration

my current *=10.8.2.64:50400;

default : *=localhost:8051

i have also tried with

*=10.8.2.64:8051; [but this was just a trial, as i do not have the 8051 port on the portal server listening]

what is the port number i should be pointing to on the portal server ?

with respect,

amit

-


default.trc error message :

Exception ID:02:44_01/02/07_0002_49569850

[EXCEPTION]

com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Component : pcd:portal_content/PDK_for_NET/myDesk/pages/page1/page1_PortalComponent1

Component class : com.sap.portal.dotnet.framework.iViewProcessorComponent

User : Administrator

at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:375)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)

at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)

at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)

at java.lang.Thread.run(Thread.java:534)

Caused by: java.lang.RuntimeException: <br>iView cannot display. <br>Could not connect to the .NET runtime server. <br>Contact your administrator if the problem persists.<br>Possible reasons:<br>1. The Portal Runtime for .NET service is not running or installed.<br>2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings

at com.sap.portal.dotnet.framework.iViewProcessorService.handleRequestCompletion(iViewProcessorService.java:383)

at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:139)

at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:36)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

... 7 more

-


Exception in PortalRequestManager.dispatchRequest without timeout

[EXCEPTION]

java.lang.RuntimeException: <br>iView cannot display. <br>Could not connect to the .NET runtime server. <br>Contact your administrator if the problem persists.<br>Possible reasons:<br>1. The Portal Runtime for .NET service is not running or installed.<br>2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings

at com.sap.portal.dotnet.framework.iViewProcessorService.handleRequestCompletion(iViewProcessorService.java:383)

at com.sap.portal.dotnet.framework.iViewProcessorService.ProcessRequest(iViewProcessorService.java:139)

at com.sap.portal.dotnet.framework.iViewProcessorComponent.doContent(iViewProcessorComponent.java:36)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:375)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)

at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)

at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)

at java.lang.Thread.run(Thread.java:534)

-


-


The system server log entry:

Wed Jan 31 13:38:04 NZDT 2007 Processing request failed on host: tcp://10.8.1.101:8050 Could be a problem in the PDK for .Net framework!

and i have ensured that the service logon has write priviliges on

1> windows Temp

2> ms .net framework

3> program files prt for ms.net

the installation verification tool

reports that it did not find the file :

SAP.Portal.DotNET.RunTime.Installer.dll file

all other files have verisons 1.2.0.0 or 2.0.0.13