.NET PDK 2.0, 64 bit, .NET runtime server issue

[Former Member]

Hello,

I am struggling with the .net runtime server connectivity

I have followed

"Installation, Upgrade and Configuration Guide Portal Development Kit for Microsoft .NET Release 2.x September 2006"

available from service marketplace

nw2004s ep 7.0 sp9, win2k3, 64 bit, vs2003, .net pdk 2.0

sections "5.2. Configuring Portal Runtime for .NET"

and sections "5.3 Configuring Portal-Side Settings" have been especially noted and completed

i have configured the port 8070 as the tcp port to avoid any conflicts, [i first tried with 8050, but got exactly the same results]

i have also created an extra service 8071, but it had no effect on the error message

when i click 'Check Server' in System Admin >> Support >> Support Desk >> .NET Service Configuration >> .Net Runtime server 'Check Server'

Net Runtime server: 10.8.2.64:8070 did not respond. Make sure the server is running and configured correctly.

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

1. .NET Runtime Servers Configuration = 10.8.2.64=10.8.2.64:8070;

2. Portal Servers Configuration = 10.8.2.64:8071

3. .NET Runtime Failover Servers Configuration = 10.8.2.64=10.8.2.64:8070;

4. Allow Server Affinity = true

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

6. Enable Ja.NET Logging = true

7. Lease Duration (seconds) = 5

8. Request Timeout (milliseconds) = 5000

9. Production Mode = false

The Active Ports utility reading :

epsrv.exe 6044 0.0.0.0 8071 LISTEN TCP C:\Tools\VSNET2003\SAP\PRT\Server01\epsrv.exe

epsrv.exe 5424 0.0.0.0 8070 LISTEN TCP C:\Tools\VSNET2003\SAP\PRT\Server00\epsrv.exe

Deplyment from vs.net is successful, but then i preview the ivew i get the error message :

Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:portal_content/PDK_for_NET/myDesk/iviews/PortalComponent1

Component Name : myDesk.PortalComponent1

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings.

Exception id: 03:42_21/11/06_0009_14987050

See the details for the exception ID in the log file

Thank you in advance for your time and patience.

with respect,

amit

-

---

#1.5#0017087CFA8000700000001900000FC8000422B933975172#1164078736690#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8162##RTAKL064_EPR_14987050#CHAWATHE#17258700790e11dbae0b0017087cfa80#SAPEngine_Application_Thread[impl:3]_23##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve User for System #1#portal_content/RTNZ_Desktop/RT1# #1.5#0017087CFA8000700000001A00000FC8000422B93397863C#1164078736700#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8162##RTAKL064_EPR_14987050#CHAWATHE#17258700790e11dbae0b0017087cfa80#SAPEngine_Application_Thread[impl:3]_23##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve Password for System #1#portal_content/RTNZ_Desktop/RT1#

#1.5#0017087CFA80006F0000001C00000FC8000422B933A3A6C9#1164078737500#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8165##RTAKL064_EPR_14987050#CHAWATHE#17db1b60790e11dbbb6a0017087cfa80#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve User for System #1#portal_content/RTNZ_Desktop/RT1# #1.5#0017087CFA80006F0000001D00000FC8000422B933A3A810#1164078737500#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8165##RTAKL064_EPR_14987050#CHAWATHE#17db1b60790e11dbbb6a0017087cfa80#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve Password for System #1#portal_content/RTNZ_Desktop/RT1#

#1.5#0017087CFA80005F0000002500000FC8000422B934ECA6BA#1164078759060#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8169##RTAKL064_EPR_14987050#CHAWATHE#24b36040790e11dbc72e0017087cfa80#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve User for System #1#portal_content/RTNZ_Desktop/CR2# #1.5#0017087CFA80005F0000002600000FC8000422B934ECA812#1164078759060#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8169##RTAKL064_EPR_14987050#CHAWATHE#24b36040790e11dbc72e0017087cfa80#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve Password for System #1#portal_content/RTNZ_Desktop/CR2#

#1.5#0017087CFA8000600000002000000FC8000422B934F4B591#1164078759590#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8171##RTAKL064_EPR_14987050#CHAWATHE#25074ca0790e11dbad090017087cfa80#SAPEngine_Application_Thread[impl:3]_28##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve User for System #1#portal_content/RTNZ_Desktop/CR2# #1.5#0017087CFA8000600000002100000FC8000422B934F4B6D8#1164078759590#/System/Server#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#CHAWATHE#8171##RTAKL064_EPR_14987050#CHAWATHE#25074ca0790e11dbad090017087cfa80#SAPEngine_Application_Thread[impl:3]_28##0#0#Warning#1#com.sap.portal.ivs.semantic.systemLandscape#Java###Failed to retrieve Password for System #1#portal_content/RTNZ_Desktop/CR2#

#1.5#0017087CFA8000680000004300000FC8000422B9397109A7#1164078834840#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#CHAWATHE#8180##RTAKL064_EPR_14987050#CHAWATHE#51cdb3a0790e11dbbd4b0017087cfa80#SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: myDesk#

#1.5#0017087CFA8000680000004400000FC8000422B939712011#1164078834850#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8180##RTAKL064_EPR_14987050#CHAWATHE#51cdb3a0790e11dbbd4b0017087cfa80#SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#com.sap.portal.dotnet#Java###Deploying on .NET server.#1#myDesk# #1.5#0017087CFA8000680000004500000FC8000422B939716CBC#1164078834870#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#CHAWATHE#8180##RTAKL064_EPR_14987050#CHAWATHE#51cdb3a0790e11dbbd4b0017087cfa80#SAPEngine_Application_Thread[impl:3]_37##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: myDesk# #1.5#0017087CFA80006B0000001D00000FC8000422B939E4848E#1164078842410#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#CHAWATHE#8183##RTAKL064_EPR_14987050#CHAWATHE#5659f280790e11dbb3b40017087cfa80#J-Integra for .NET TP Thread 2##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: myDesk# #1.5#0017087CFA80006B0000001E00000FC8000422B939E498E0#1164078842420#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8183##RTAKL064_EPR_14987050#CHAWATHE#5659f280790e11dbb3b40017087cfa80#J-Integra for .NET TP Thread 2##0#0#Info#1#com.sap.portal.dotnet#Java###Deploying on .NET server.#1#myDesk#

#1.5#0017087CFA80006B0000001F00000FC8000422B939E4EA33#1164078842440#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#CHAWATHE#8183##RTAKL064_EPR_14987050#CHAWATHE#5659f280790e11dbb3b40017087cfa80#J-Integra for .NET TP Thread 2##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: myDesk#

#1.5#0017087CFA8000750000002900000FC8000422B93CB2F325#1164078889500#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#CHAWATHE#8192##RTAKL064_EPR_14987050#CHAWATHE#72684260790e11db9fbe0017087cfa80#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: myDesk#

#1.5#0017087CFA8000750000002A00000FC8000422B93CB307CA#1164078889500#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8192##RTAKL064_EPR_14987050#CHAWATHE#72684260790e11db9fbe0017087cfa80#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#com.sap.portal.dotnet#Java###Deploying on .NET server.#1#myDesk# #1.5#0017087CFA8000750000002B00000FC8000422B93CB3633C#1164078889520#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#CHAWATHE#8192##RTAKL064_EPR_14987050#CHAWATHE#72684260790e11db9fbe0017087cfa80#SAPEngine_Application_Thread[impl:3]_8##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: myDesk# #1.5#0017087CFA8000740000003100000FC8000422B93D1C1520#1164078896390#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.deployment#CHAWATHE#8194##RTAKL064_EPR_14987050#CHAWATHE#76882ae0790e11dbbdfc0017087cfa80#SAPEngine_Application_Thread[impl:3]_12##0#0#Info#1#com.sap.portal.prt.runtime.deployment#Plain###Deploying application: myDesk# #1.5#0017087CFA8000740000003200000FC8000422B93D1C29DB#1164078896390#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8194##RTAKL064_EPR_14987050#CHAWATHE#76882ae0790e11dbbdfc0017087cfa80#SAPEngine_Application_Thread[impl:3]_12##0#0#Info#1#com.sap.portal.dotnet#Java###Deploying on .NET server.#1#myDesk#

#1.5#0017087CFA8000740000003300000FC8000422B93D1C89AA#1164078896420#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.loader#CHAWATHE#8194##RTAKL064_EPR_14987050#CHAWATHE#76882ae0790e11dbbdfc0017087cfa80#SAPEngine_Application_Thread[impl:3]_12##0#0#Info#1#com.sap.portal.prt.runtime.loader#Plain###Loading application: myDesk#

#1.5#0017087CFA80006D0000002400000FC8000422B93E7DF78E#1164078919580#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8200##RTAKL064_EPR_14987050#Guest#844e7940790e11dbcdfd0017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.portal.dotnet#Java###Tue Nov 21 16:15:19 NZDT 2006 Problem Conecting to host: tcp://localhost:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA80006D0000002500000FC8000422B93E7E09BB#1164078919580#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8200##RTAKL064_EPR_14987050#Guest#844e7940790e11dbcdfd0017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.portal.dotnet#Java###Tue Nov 21 16:15:19 NZDT 2006 Problem Conecting to host: tcp://localhost:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA80006D0000002600000FC8000422B93E7E1B51#1164078919590#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8200##RTAKL064_EPR_14987050#Guest#844e7940790e11dbcdfd0017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#com.sap.portal.dotnet#Java###Tue Nov 21 16:15:19 NZDT 2006 Problem Conecting to host: tcp://localhost:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA80006D0000002700000FC8000422B93E7E21FF#1164078919590#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#8200##RTAKL064_EPR_14987050#Guest#844e7940790e11dbcdfd0017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Fatal#1#com.sap.portal.dotnet#Java### Problem Conecting to host: tcp://localhost:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA80006D0000002800000FC8000422B93E7E25A5#1164078919590#/System/Server#sap.com/irj#com.sap.portal.portal#CHAWATHE#8200##RTAKL064_EPR_14987050#Guest#844e7940790e11dbcdfd0017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/System/Server#Plain###Exception ID:04:15_21/11/06_0011_14987050#

-

---

[fabio_sarmento]

Possible causes for your issue:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings

So did you installed Portal Runtime 2.0 for .Net.

https://websmp107.sap-ag.

de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000887162006E

Please refer to document as above.

Regads,

Fabio

[Former Member]

Hi Rima,

thanks for the local debugging hint.

upon stopping the .net runtime server, the mutex error dissappears, but i still get the same error as displayed above [error between linking the .net runtime & the portal server]

and effectively cannot get into the code.

thanks for the help, also please let me know if you have any experiemntal thoughts that may yeild some results. i'm blocked here )

with respect,

amit

[Former Member]

Hi Rima,

<br>

how are you doing today ?

<br>

for some reason the wrapping on this message is not taking the \n (newline) character, and it is all in one line

<br>

thank you for your help. i am yet to try local debugging,

<br>

but could connect the .net runtime engine to the portal to be able to successfully deploy

and publish a portal component with my given config

<br>

when i want to preview my portal component in the portal i still face the below listed errors

please instruct me on how to proceed from here on ...

<br>

-

---

<br>

Portal Runtime Error

<br>

An exception occurred while processing a request for :

iView : PortalApplicationTest.PortalComponent1

Component Name : PortalApplicationTest.PortalComponent1

<br>

iView cannot display.

<br>

There was a problem processing this .NET component

Contact your administrator if the problem persists.

<br>

Exception id: 12:48_31/01/07_0008_49569850

<br>

See the details for the exception ID in the log file

<br>

-

---

<br>

#1.5#0017087CFA8000640000004E000010F00004284A7D1804A5#1170200298260#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#7351####e614f3a0b0ba11dbc4500017087cfa80#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Exception ID:12:38_31/01/07_0006_49569850

[EXCEPTION]

#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component Component : myDesk.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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215) at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645) 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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753) at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240) at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522) at java.security.AccessController.doPrivileged(Native Method) at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.RuntimeException: <br>iView cannot display. <br>There was a problem processing this .NET component <br>Contact your administrator if the problem persists 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) ... 29 more # #1.5#0017087CFA80005F00000033000010F00004284A86E3FB41#1170200462620#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#7351####48188120b0bb11db9a9f0017087cfa80#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server#Java###Exception ID:12:41_31/01/07_0007_49569850 [EXCEPTION] #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Component : myDesk.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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)

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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)

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

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

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

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.RuntimeException: <br>iView cannot display. <br>There was a problem processing this .NET component <br>Contact your administrator if the problem persists

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)

... 29 more

#

#1.5#0017087CFA8000680000001E000010F00004284AA2EC86A9#1170200932940#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#7351####6062f5c0b0bc11db9e5a0017087cfa80#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/System/Server#Java###Exception ID:12:48_31/01/07_0008_49569850

[EXCEPTION]

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

Component : PortalApplicationTest.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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)

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.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)

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

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

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

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.RuntimeException: <br>iView cannot display. <br>There was a problem processing this .NET component <br>Contact your administrator if the problem persists

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)

... 29 more

[Former Member]

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

with respect,

amit

Message was edited by:

amit chawathe

Message was edited by:

amit chawathe

[Former Member]

Hi Rima,

how are you doing ?

my apologies for taking this long to reply.

my time was diverted to another project, and now i have returned to this problem

i have set up the .net runtime server on a 32 bit machine [my development laptop]

and configured the J2ee server to point to it and am running hotfix 2 for nw2004s & ie7

i have been able to successfully deploy a small hello world component

but when i go to preview it i get a time out resulting in the error

Portal Runtime Error

An exception occurred while processing a request for :

iView : myDesk.PortalComponent1

Component Name : myDesk.PortalComponent1

iView cannot display.

The request has timed out.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not pointing to the correct.NET runtime server.

3. The log-on account for the Portal Runtime for .NET service doesn't have the necessary permissions.

Exception id: 06:54_30/01/07_0004_49569850

See the details for the exception ID in the log file

Jan 30, 2007 5:04:20 PM com.sap.portal.dotnet [SAPEngine_Application_Thread[impl:3]_34] Fatal: Problem Conecting to host: tcp://10.8.1.101:8050

2114.092: [GC 2114.093: [DefNew: 131314K->43774K(131328K), 0.3807165 secs] 755209K->691433K(1004800K), 0.3809071 secs]

2370.429: [GC 2370.458: [DefNew: 131326K->22807K(131328K), 0.1962961 secs] 778985K->677290K(1004800K), 0.1965018 secs]

2381.688: [GC 2381.688: [DefNew: 110359K->42557K(131328K), 0.1764394 secs] 764842K->697039K(1004800K), 0.1766175 secs]

2570.792: [GC 2570.793: [DefNew: 130109K->19803K(131328K), 0.1322899 secs] 784591K->680345K(1004800K), 0.1326228 secs]

2637.453: [GC 2637.454: [DefNew: 107355K->12237K(131328K), 0.0783806 secs] 767897K->672780K(1004800K), 0.0786216 secs]

3247.767: [GC 3247.815: [DefNew: 99789K->12526K(131328K), 0.6022541 secs] 760332K->673068K(1004800K), 0.6459001 secs]

Jan 30, 2007 5:25:54 PM com.sap.portal.dotnet [J-Integra for .NET TP Thread 2] Fatal: Problem Conecting to host: tcp://10.8.1.101:8050

3756.733: [GC 3756.733: [DefNew: 100078K->15237K(131328K), 0.0993948 secs] 760620K->675779K(1004800K), 0.0995894 secs]

4405.156: [GC 4405.156: [DefNew: 102789K->16113K(131328K), 0.0755677 secs] 763331K->676655K(1004800K), 0.0757694 secs]

5231.698: [GC 5231.699: [DefNew: 103665K->17526K(131328K), 0.0825231 secs] 764207K->678069K(1004800K), 0.0827223 secs]

6492.844: [GC 6492.844: [DefNew: 105078K->18566K(131328K), 0.1011519 secs] 765621K->679108K(1004800K), 0.1013474 secs]

7088.692: [GC 7088.692: [DefNew: 106118K->17189K(131328K), 0.0894604 secs] 766660K->677731K(1004800K), 0.0896532 secs]

7196.235: [GC 7196.235: [DefNew: 104741K->17247K(131328K), 0.0818744 secs] 765283K->677790K(1004800K), 0.0820544 secs]

7411.757: [GC 7411.758: [DefNew: 104799K->20137K(131328K), 0.0920864 secs] 765342K->680679K(1004800K), 0.0922826 secs]

7956.100: [GC 7956.100: [DefNew: 107689K->24368K(131328K), 0.1104160 secs] 768231K->684911K(1004800K), 0.1106084 secs]

Jan 30, 2007 6:43:52 PM com.sap.portal.dotnet [J-Integra for .NET TP Thread 2] Fatal: Problem Conecting to host: tcp://10.8.1.101:8050

Jan 30, 2007 6:54:24 PM com.sap.portal.dotnet [SAPEngine_Application_Thread[impl:3]_18] Fatal: Problem Conecting to host: tcp://10.8.1.101:8050

8942.752: [GC 8942.752: [DefNew: 111920K->22764K(131328K), 0.1106429 secs] 772463K->683306K(1004800K), 0.1108338 secs]

-

---

when i use active ports to check if the ports are available

the ip address of the 8050, 8060 ports is : 0.0.0.0

how do i change this to 10.8.1.101 ?

effectively when the j2ee engine on my 64 bit server tries to connect to my dev laptop, it cannot find it and hence times out

-

---

when i debug locally, the following error occurs

'DefaultDomain': Loaded 'c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll', No symbols loaded.

'ep': Loaded 'C:\Tools\SAPTools\NPDKVS2003AddIn\Debug\ep.exe', No symbols loaded.

'ep.exe': Loaded 'c:\windows\assembly\gac\system.windows.forms\1.0.5000.0__b77a5c561934e089\system.windows.forms.dll', No symbols loaded.

'ep.exe': Loaded 'c:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll', No symbols loaded.

'ep.exe': Loaded 'c:\windows\assembly\gac\sap.portal.web\1.2.0.0__50436dca5c7f7d23\sap.portal.web.dll', No symbols loaded.

'ep.exe': Loaded 'c:\windows\assembly\gac\sap.portal.common\1.2.0.0__50436dca5c7f7d23\sap.portal.common.dll', No symbols loaded.

'ep.exe': Loaded 'c:\windows\assembly\gac\system.web\1.0.5000.0__b03f5f7f11d50a3a\system.web.dll', No symbols loaded.

'Domain2': Loaded 'c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\sap.portal.web\1.2.0.0__50436dca5c7f7d23\sap.portal.web.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system.runtime.remoting\1.0.5000.0__b77a5c561934e089\system.runtime.remoting.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system.web\1.0.5000.0__b03f5f7f11d50a3a\system.web.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system.xml\1.0.5000.0__b77a5c561934e089\system.xml.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system.web.mobile\1.0.5000.0__b03f5f7f11d50a3a\system.web.mobile.dll', No symbols loaded.

'6a484304': Loaded 'c:\windows\assembly\gac\system.web.regularexpressions\1.0.5000.0__b03f5f7f11d50a3a\system.web.regularexpressions.dll', No symbols loaded.

An unhandled exception of type 'System.InvalidOperationException' occurred in system.web.dll

Additional information: Mutex could not be created.

-

---

why does the mutex error occur when debugging locally ?

am i missing a relevant permission ?

with respect,

amit

[rima-sirich]

Hello Amit,

Mutex error is a known issue in PDK 2.0 for .NET. It happens when you are debugging and in the same time there is a Portal Runtime for .NET node running

in your machine. It happens even if they are using a different ports. So the

resolution is to stop Portal Runtime for .NET nodes if you want to debug.

Regards,

Rima.

[Former Member]

Hi Rima,

I apologise for the delay in applying your recommendation.

I am currently loaded with another task.

as i could not get the .net server runtime up and running in time, i need to deliver the ivews using developer studio.

i will definitely come back to this and request of your timely help.

thank you for your patience.

with respect,

amit

[Former Member]

Hi Rima,

I will imlement your recommendations on local debugging on monday

got side tracked to another issue today.

have a nice weekend.

with respect,

amit

[Former Member]

Shalom Rima,

How are you doing today ?

>> Are both the Portal and the Portal Runtime for Microsoft .NET installed on the same machine that is 10.8.2.64 ?

yes

>> if so, then you can use the localhost instead of the machine ip.

done it with no change in behaviour

>> I would also recommend you to:

>> 1. restart the iViewProcessorService in the Portal after re-configuring it.

done

>> 2. restart both Portal Runtime for Microsoft .NET nodes.

done

>> If after all that, you are still not able to view a .NET iView, I would recommend >> you to restart the Portal.

done

still no change in behaviour.

thank you for your time and effort on the issue, but i am still blocked.

with respect,

amit

[rima-sirich]

Hi Amit,

The error you get means that the Portal is not able to establish a connection to the

Portal Runtime for Microsoft .NET. Usually, it means that there is a problem in

iViewProcessorService configuration. In order to eliminate this possibilty, I would

suggest you to debug <b>locally</b> your PortalComponent. You can read about it in

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/go/km/docs/library/dotnet/pdk%20for%20.net/developer's%20Guide%20PDK%202.0%20for%20.NET/index.html">PDK 2.0 for .NET Development Guide</a> -> Programming with PDK for .NET ->

Previewing and Debugging Portal Components -> Debugging a Portal Component.

If you succeed to debug locally, then the problem is for sure in iViewProcessorService configuration.

If you don't succeed to debug locally, then probably the problem is in your system landscape.

Good luck,

Rima.

[Former Member]

Hi Romi,

How are you doing ?

I have implemented the changes as recommended by you.

They still yeild the same result. Do you have anyother recommendations ?

To confirm, Hotfix 1 had been installed previous to the sdn post as part of the installation as per the note 975922

-

---

Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:com.sap.portal.system/temporaryobjects3/3d039c4bb87a46549969050f0cd13154/page1_PortalComponent1

Component Name : myDesk.PortalComponent1

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings.

Exception id: 12:19_22/11/06_0001_14987050

See the details for the exception ID in the log file

-

---

1. .NET Runtime Servers Configuration : *=10.8.2.64:8070;

2. Portal Servers Configuration : 10.8.2.64:8075

3. .NET Runtime Failover Servers Configuration : *=10.8.2.64:8070;

4. Allow Server Affinity : true

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

6. Enable Ja.NET Logging : false

7. Lease Duration (seconds) : 5

8. Request Timeout (milliseconds) : 5000

9. Production Mode : false

-

---

#1.5#0017087CFA80006A000000A500001394000422CA087FC1E1#1164151028170#/System/Server#sap.com/irj#com.sap.portal.activityreport.aggregator#J2EE_GUEST#0####687ea2a079b611db8bf00017087cfa80#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.portal.activityreport.aggregator#Java###Starting aggregator in 43 minutes##

#1.5#0017087CFA80006D0000001300001394000422CA097E162E#1164151044840#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.masthead on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.masthead#library:com.sap.portal.common#

#1.5#0017087CFA80006D0000001400001394000422CA09842B3F#1164151045240#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.toplevel on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.toplevel#library:com.sap.portal.common#

#1.5#0017087CFA80006D0000001500001394000422CA0985EB4C#1164151045350#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.pagetoolbar on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.pagetoolbar#library:com.sap.portal.common#

#1.5#0017087CFA8000740000000C00001394000422CA09E00950#1164151051260#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_10##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.detailedtree on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.detailedtree#library:com.sap.portal.common#

#1.5#0017087CFA8000740000000D00001394000422CA09E6403A#1164151051670#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_10##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.dynnavarea on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.dynnavarea#library:com.sap.portal.common#

#1.5#0017087CFA8000740000000E00001394000422CA09E9647D#1164151051870#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_10##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.navigation.targets on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.navigation.targets#library:com.sap.portal.common#

#1.5#0017087CFA8000740000000F00001394000422CA0AD6940E#1164151067410#/System/Server/WebRequests#sap.com/irj#com.sap.engine.services.servlets_jsp.server.runtime.client.PrintWriterImpl#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_10##0#0#Warning#1#com.sap.engine.services.servlets_jsp.server.runtime.client.PrintWriterImpl#Plain###Error while closing the stream.#

#1.5#0017087CFA8000790000000D00001394000422CA0B420500#1164151074460#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#com.sap.portal.prt.runtime.broker#Plain###[PortalComponentItem.refresh] AuthRequirement property is deprecated for EP6.0 components, please check: com.sap.portal.support.desk.default#

#1.5#0017087CFA8000690000001300001394000422CA0BE020D1#1164151084820#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader sap.com/com.sap.portal.dotnet.framework.configuration on the system, but will register reference for furture usage.#2#sap.com/com.sap.portal.dotnet.framework.configuration#library:com.sap.util.monitor.grmg#

#1.5#0017087CFA8000690000001400001394000422CA0BE6741E#1164151085230#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_38##0#0#Info#1#com.sap.portal.dotnet#Java###Local host is , local port is ; remote host is , remote port is .#2#10.8.2.64#8075# #1.5#0017087CFA8000740000001000001394000422CA0CF6B0C0#1164151103070#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_10##0#0#Info#1#com.sap.portal.dotnet#Java###Local host is , local port is ; remote host is , remote port is .#2#10.8.2.64#8075#

#1.5#0017087CFA80005F0000005B00001394000422CA0D34BAA5#1164151107140#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_15##0#0#Info#1#com.sap.portal.dotnet#Java###Deployment hook is loaded.#1#com.sap.portal.dotnet.framework#

#1.5#0017087CFA8000660000004000001394000422CA0F09B614#1164151137880#/System/Server#sap.com/irj#com.sap.portal.transport#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#SAPEngine_Application_Thread[impl:3]_26##0#0#Warning#1#com.sap.portal.transport#Plain###attributeToOptionValue: deprecated transport mode 'all' set in attribute, converting to new value 'data'.#

#1.5#0017087CFA8000D10000000000001394000422CA1173053B#1164151178330#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Wed Nov 22 12:19:38 NZDT 2006 Problem Conecting to host: tcp://10.8.2.64:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA8000D10000000100001394000422CA11740919#1164151178400#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Wed Nov 22 12:19:38 NZDT 2006 Problem Conecting to host: tcp://10.8.2.64:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA8000D10000000200001394000422CA1174A9E2#1164151178440#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Wed Nov 22 12:19:38 NZDT 2006 Problem Conecting to host: tcp://10.8.2.64:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA8000D10000000300001394000422CA1174D79A#1164151178450#/System/Server#sap.com/irj#com.sap.portal.dotnet#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Fatal#1#com.sap.portal.dotnet#Java### Problem Conecting to host: tcp://10.8.2.64:8070

iView cannot display.

Could not connect to the .NET runtime server.

Contact your administrator if the problem persists.

Possible reasons:

1. The Portal Runtime for .NET service is not running or installed.

2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings##

#1.5#0017087CFA8000D10000000400001394000422CA1174E1B0#1164151178450#/System/Server#sap.com/irj#com.sap.portal.prt.request#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception in PortalRequestManager.dispatchRequest without timeout#

#1.5#0017087CFA8000D10000000600001394000422CA11755F5D#1164151178490#/System/Server#sap.com/irj#com.sap.portal.portal#CHAWATHE#276##RTAKL064_EPR_14987050#Guest#70013e2079b611db80180017087cfa80#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception ID:12:19_22/11/06_0001_14987050#

-

---

[rima-sirich]

Hi Amit,

Are both the Portal and the Portal Runtime for Microsoft .NET installed on the same machine

that is 10.8.2.64 ? If so, then you can use the localhost instead of the machine ip.

I would also recommend you to:

1. restart the iViewProcessorService in the Portal after re-configuring it.

2. restart both Portal Runtime for Microsoft .NET nodes.

If after all that, you are still not able to view a .NET iView, I would recommend you to restart the Portal.

Regards,

Rima.

[Former Member]

Hi Maheswaran.B,

How are you doing ?

Thank you for your quick response.

>>Did you install the .NET Runtime in the Portal Server?

yes

>>If you have already installed the .NET Runtime, check whether the service is running in Windows Services List.

yes

>>If it is still running, then you can do the following options...

>>1. Restart the .NET Runtime Service and try viewing the ivew, or

>>2. Reinstall the .NET Runtime in the Portal Server side.

i have restarted the service several times with no change in beahviour

reinstallation is kept untill there is no other possible solution, which might not even help analysing the problem at hand.

with reapect,

amit

[rima-sirich]

Hi Amit,

Do following changes in the configuration values:

1. .NET Runtime Servers Configuration

10.8.2.64=10.8.2.64:8070 to *=10.8.2.64:8070 as in the left side you should write your Portal Server Node Id, in case you don't know it use * instead

2. Portal Servers Configuration

10.8.2.64:8071 to 10.8.2.64:8075 as 8071 is already used by additional Portal Runtime for Microsoft .NET node that you created

3. .NET Runtime Failover Servers Configuration

10.8.2.64=10.8.2.64:8070 to *=10.8.2.64:8070 like in step 1

6. Enable Ja.NET Logging

true to false as this is very bad setting for performance even if you are in development and not in production

And restart iViewProcessorService.

Regards,

Rima.

P.S. By the way, EP7 SP9 supports work with PDK 2.0 only if Hotfix 1 for PDK 2.0 is installed.

[Former Member]

Hi Amit,

Did you install the .NET Runtime in the Portal Server?

If you have already installed the .NET Runtime, check whether the service is running in Windows Services List.

If it is still running, then you can do the following options...

1. Restart the .NET Runtime Service and try viewing the ivew, or

2. Reinstall the .NET Runtime in the Portal Server side.

Hope it helps.

Regards,

Maheswaran.B