Error accessing .Net portal component

[Former Member]

We are running EP 6.0 SP19 on Windows 2003 with .NET 2.5.

When using Firefox 3.x or MS Internet Explorer 8.0 Beta, we get the following:

Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:portal_content/com.bitech.BI_Tech/com.bitech.EP_Phase_II/com.bitech.Roles/

com.bitechnologies.Employees/com.bitech.EP_Test/com.bitech.Order_Inquiry/com.bitech.Orders_Inquiry

Component Name : BITech.CustomerPortal.PortalComponents.OrderInquiry

iView cannot display.

Could not process the .NET portal component.

Contact your administrator if the problem persists.

Recommended actions for administrators:

1. View the portal log for more information.

2. To display the ASP.NET messages in the browser, set the Display ASP.NET Stack on ASP.NET Error property of

'iViewProcessorService' service to 'true'.

Exception id: 10:22_26/01/09_0015_2394850

See the details for the exception ID in the log file

I can't find anything in SAP OSS notes. Has anyone run across this?

Thanks,

Bill Cooper

Edited by: Michael Nicholls on Jan 27, 2009 1:14 PM

[Former Member]

That was the 1st thing I did. It took awhile but I found the setting and made the change. I've not seen any further information available in the browser or in any of the logs.

We also update the server to the latest service packs and versions of .NET. That didn't help.

I think the problem lies with home the browser (whether IE 8 beta or Firefox 3) handles the .NET code form the iViews. We had a similar problem when IE 7 came out that required a patch from SAP as well as changes to the .NET code.

If we are the only ones running into this problem it must be because of some unique coding in the iViews. This is a black box routine to use as we had our consultants develop and maintain the iViews. They want a blank check to fix the problem and I'm not willing to give that to them.

I'm at a loss as to where else to turn.

Bill

[Former Member]

Hi Bill,

This is an interesting problem in particular you say this is only an issue with IE 8 beta and Firefox 3; since we are seeing a server side error being generated I would initially not expect the problem to lie in the browser (client side) version. The following is what I would suggest.

1. Raise an SAP OSS message an query why you cannot see any additional error information when you make the setting as specified. If you could see more about the error it might help you solve it.

2. Can you try to run the ASP.NET code outside of the portal - that might allow you to see the errors since it may be that the portal is insulating them from you. Can you call these applications directly from a browser?

Of course new versions of browser can sometimes introduce unexpected results esp. if the server is expecting the browser to send it some information but for whatever reason it doesn't get it. Maybe IE8 or Firefox 3 have introduced some additional security settings that are mucking things up for you. I believe I heard that in IE8 there is a compatibility mode that makes it work like IE7 - you could try that and see if you get a different result.

Sorry I can't be of more help,

BRgds,

Simon

[Former Member]

Here is the entry from the log file

#1.5#00145E689E07005A000000D300000B8C00046166A3ED1E6E#1232993371650#/System/Server#sap.com/irj#com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(String from, String to)#bcooper#170##sfulep01.americas_EPP_2394850#bcooper#1bff83e0ebd311ddccd400145e689e07#SAPEngine_Application_Thread[impl:3]_37##0#0#Warning#1#com.sap.engine.core.classload.impl0.LoadContextImpl#Java###Cannot find loader CORE:sap.com/com.sap.portal.usermanagement.admin on the system, but will register reference for furture usage.#2#CORE:sap.com/com.sap.portal.usermanagement.admin#interface:keystore_api#

#1.5#00145E689E07006A0000007100000B8C00046166D3356DEF#1232994164962#/System/Server#sap.com/irj#com.sap.portal.dotnet#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Mon Jan 26 10:22:44 PST 2009##

#1.5#00145E689E07006A0000007200000B8C00046166D3356FA4#1232994164962#/System/Server#sap.com/irj#com.sap.portal.dotnet#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 2,5,PRT-Async]##0#0#Fatal#1#com.sap.portal.dotnet#Java###Exception in ASP.NET##

#1.5#00145E689E07006A0000007300000B8C00046166D33570CC#1232994164962#/System/Server#sap.com/irj#com.sap.portal.prt.request#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception in PortalRequestManager.dispatchRequest without timeout#

#1.5#00145E689E07006A0000007500000B8C00046166D335747D#1232994164962#/System/Server#sap.com/irj#com.sap.portal.portal#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception ID:10:22_26/01/09_0015_2394850#

#1.5#00145E689E07006F0000006D00000B8C00046166D94DE0FC#1232994267228#/System/Server#sap.com/irj#com.sap.portal.dotnet#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 6,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Mon Jan 26 10:24:27 PST 2009##

#1.5#00145E689E07006F0000006E00000B8C00046166D94DE2B1#1232994267228#/System/Server#sap.com/irj#com.sap.portal.dotnet#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 6,5,PRT-Async]##0#0#Fatal#1#com.sap.portal.dotnet#Java###Exception in ASP.NET##

#1.5#00145E689E07006F0000006F00000B8C00046166D94DE3AC#1232994267228#/System/Server#sap.com/irj#com.sap.portal.prt.request#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 6,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception in PortalRequestManager.dispatchRequest without timeout#

#1.5#00145E689E07006F0000007100000B8C00046166D94DE8A0#1232994267243#/System/Server#sap.com/irj#com.sap.portal.portal#bcooper#173##sfulep01.americas_EPP_2394850#bcooper#4f8b2270ebd611ddc67700145e689e07#Thread[PRT-Async 6,5,PRT-Async]##0#0#Error#1#/System/Server#Plain###Exception ID:10:24_26/01/09_0016_2394850#

#1.5#00145E689E07006D0000007A00000B8C00046166F0750C18#1232994655696#/System/Server#sap.com/irj#com.sap.portal.dotnet#arrow#174##sfulep01.americas_EPP_2394850#arrow#3dd26ec0ebd711dda83300145e689e07#Thread[PRT-Async 5,5,PRT-Async]##0#0#Error#1#com.sap.portal.dotnet#Java###Mon Jan 26 10:30:55 PST 2009##

[Former Member]

Hi Bill,

To me that suggests that there is an actual error in the ASP.NET code. Have you done step 2 that is suggested above?

2. To display the ASP.NET messages in the browser, set the Display ASP.NET Stack on ASP.NET Error property of 'iViewProcessorService' service to 'true'.

This must be a portal service setting. This might shed more light on the error itself.

BRgds,

Simon

[Former Member]

Hi Bill,

My first recommendation would be to look at the log file and find out more about the error. In the error message it says: "See the details for the exception ID in the log file"

If you can post those details it might help us get to the bottom of this.

Hope this helps,

Simon