500:internal server error

[former_member198652]

Hello Experts,

  We are unable to access IDM WEB UI in our environment & we are able to access IDM Admin UI and UME successfully.

When we try to access, http://host:port/idm url

we are getting error : 500 internal server error

After doing some changes, idstore = 2, we are seeing new error 'No identity Stores are available'.

Please help us in resolving the same

Thanks,

Jaya

[Steffi_Warnecke · Accepted solution]

Hello Jaya,

where did you set "idstore = 2"? In the NWA for the IDM? Or in the management console?

Regards,

Steffi.

[former_member198652 · Accepted solution]

Hi Steffi,

I set in NWA>configurations>java Systems>idm jmx app custom value as 2.

Regards,

Jaya

[Steffi_Warnecke]

And your identity store in the MMC has the ID 2?

[former_member198652]

Hi Steffi,

You mean enterprises people ids ?

It is 1/Enterprises people.

previously we set idstore as 1, we have 500 internal error while accessing the user web UI. but am able to login in Admin UI.

Now I changed to 2. it is throwing error as no identity stores are defind in user UI and Web UI.

I think it is supposed to be 1, but it is throwing 500 internal error in user web UI and but am able to login in to Admin UI.

Regards,

Jaya

[Steffi_Warnecke]

You need to set the ID of the store, that you are using in the MMC as your identity store.

If you use the "Enterprise people" identity store, it should be ID = 1 and thus you need to set that number in the NWA as well.

If you have created a custom identity store in the MMC, you need to use the ID of that store in the NWA settings.

As the error says, there is no ID store 2 in your setup, so you need to put the correct one. After that we can deal with the "real" error.

[former_member198652]

Hi Steffi,

Am attaching the error in user web UI, please see the error screen below.

am able to login into Admin UI normal.

Regards,

Jaya

[Steffi_Warnecke]

Hello Jaya,

can you check the log viewer in the NWA? There should be some more useful information for this error.

And maybe it's my eyes, but the screenshot is too pixely to make out details on it. 😕

Regards,

Steffi.

[former_member198652]

Hi Steffi,

Am attaching the Screenshot.

May this is properly visible.

Please check and guide me

500   Internal Server Error

SAP NetWeaver Application Server/Java AS

The initial exception that caused the request to fail, was:

java.lang.NoSuchMethodError: com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDTable.setOnSelect(Lcom/sap/tc/webdynpro/progmodel/api/IWDAction;)V

    at com.sap.idm.wd.wf.requestsearch.wdp.InternalRequestSearchView.wdCreateUITreeForGroup(InternalRequestSearchView.java:1375)

    at com.sap.idm.wd.wf.requestsearch.wdp.InternalRequestSearchView.wdCreateUITreeForTransparentContainerOldFashion(InternalRequestSearchView.java:1310)

    at com.sap.idm.wd.wf.requestsearch.wdp.InternalRequestSearchView.wdCreateUITree(InternalRequestSearchView.java:1294)

    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.createUITree(DelegatingView.java:82)

    at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:552)

    ... 79 more

See full exception chain for details.

Failed to process request. Please contact your system administrator.

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.

Correction Hints

The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.

If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.

[Steffi_Warnecke]

Yes, that's better. ^^

But please share the log from the NWA, too.

[former_member198652]

Hi Steffi,

Please find the log

	error	2014-11-07	02:05:28:645	Exception occured during processing of Web Dynpro application  sap.com/tc~idm~wd~workflow/Idm. For details, check entry 005056A37ED604210000000600001F98 in trace.	/System/UserInterface	com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable	sap.com/tc~wd~dispwda
	Log Record Details Message: Exception occured during processing of Web Dynpro application  sap.com/tc~idm~wd~workflow/Idm. For details, check entry 005056A37ED604210000000600001F98 in trace. Date: 2014-11-07 Time: 02:05:28:645 Category: /System/UserInterface Location: com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable Application: sap.com/tc~wd~dispwda Thread: Thread[HTTP Worker [@304746693],5,Dedicated_Application_Thread] Data Source: j2ee\cluster\server0\log\system\userinterface_00.log Arguments: DSR Transaction: 89675c60666511e48b9d005056a37ed6 Message Code: Session: 188 Transaction: User: jkumar Time Zone: 0-800 CSN Component: BC-WD-JAV DC Component: tc~wd~webdynpro Correlation ID: 3792150000000004 DSR Root Context ID: 99737C10666511E4AB79005056A37ED6 DSR Connection: 89675c60666511e48b9d005056a37ed6 DSR Counter: 0 Log ID: 005056A37ED604210000000700001F98 Host: BMCDD1DBAP01 System: DN1 Instance: J00 Node: server

[bxiv]

How did you go about installing IdM to the Java stack?  Also is this a vanilla java system or did you install the IdM SCAs to an already existing system?

Also what version of NW did you install?

NW 7.3 & 7.31 have specific requirements for SPs that have to be installed before you try to run IdM.

I don't think this is an IdM issue its more of a technical system issue within the java stack and could be something as simple as starting a service.

[Former Member]

Hello Jaya,

Can you please confirm all your IDM components are at same patch levels.

Thanks,

Krishna.