cancel
Showing results for 
Search instead for 
Did you mean: 

SRM MDM Search UI Internal Server Error 500

Former Member
0 Kudos

Hello,

we are running SRM MDM Catalog 3 SP03 Patch 6 and can't reach the search UI. We get the following Error message:

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

java.lang.NoSuchMethodError: com/sap/mdm/extension/data/commands/RetrieveLimitedRecordsCompoundExCommand.setRetrieveResultCounts(Z)V

at com.sap.srm.mdm.Model.executeRetrieveLimitedRecordsCompoundEx(Model.java:2102)

at com.sap.srm.mdm.Model.performSearch(Model.java:2337)

at com.sap.mdm.srmcat.uisearch.master.Master.callModelSearch(Master.java:1980)

at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.callModelSearch(InternalMaster.java:981)

at com.sap.mdm.srmcat.uisearch.master.Master.doInitialize(Master.java:1486)

... 32 more

When switching the UI Configuration of the Repository to Services (MLV) there's no problem to reach the search ui.

Yesterday we get another error message concerning the index therefor we decide to patch from sp03 patch 5 to patch 6. Now we get the error message mentioned above.

Can someone tell what's wrong with the data? Two weeks ago before my vacations starts all runs fine with sp03 patch 5. Yesterday after vacation we get this error message. My colleagues told me that they only restarted the MDM server several times but they didn't changed anything.

Accepted Solutions (0)

Answers (2)

Answers (2)

Tamas_SAP
Employee
Employee
0 Kudos

Hi Rico,

as I can see from the connection test, neither the MDM JAVA API is on SP3 P6, nor the server.

You have only 7.1.00.79 instead 7.1.03.45.

Please check that the deployment was successfully and also the MDM server was installed correctly.

After SCA deployment you should restart the J2EE server!

Regards,

Tamá

Former Member
0 Kudos

Thanks alot for your help.

you were right with the version number. but we had the problem that we can't update the server because it's running on a linux os. And the hints of the sap support were less helpful because they mentioned on windows installations. My suggestion was that they have no idea to manage problems on linux os regarding MDM.

But an reinstallation had helped to get the right server version.

Now all works fine. Until the next sp

Thanks for your advice.

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Please make sure the patch level for MDM Server and Serach UI are same level.

Regards,

Masa

Former Member
0 Kudos

Helllo, thanks for the fast answer.

we have installed the patch from 14th September 2009 (Monday) SP03 Patch 6 and there was both patched the server and the search ui.

The connection test is also unsuccesful

See the Connection test log:

************************************************

Details:

!======================================!

Host-Adresse = 192.168.0.106

Host Name = s27sr7.DBC

!======================================!

MDM-Server-Ports werden geprft...

Verbindungsfehler (Port 59950)

############################################################################################

java.net.ConnectException: Verbindungsaufbau abgelehnt

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:220)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)

at java.net.Socket.connect(Socket.java:479)

at java.net.Socket.connect(Socket.java:429)

at java.net.Socket.<init>(Socket.java:336)

at java.net.Socket.<init>(Socket.java:181)

at com.sap.srm.mdm.conntest.ConnectionTest.ping(ConnectionTest.java:112)

at com.sap.srm.mdm.conntest.ConnectionTest.TestConnection(ConnectionTest.java:204)

at com.sap.mdm.srmcat.uiutil.conntest.ConnTestView.onActionStartTest(ConnTestView.java:154)

at com.sap.mdm.srmcat.uiutil.conntest.wdp.InternalConnTestView.wdInvokeEventHandler(InternalConnTestView.java:144)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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

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:386)

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

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

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

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

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

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(AccessController.java:219)

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

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

############################################################################################

JAVA-API-Version von MDM ermitteln

Admin Version = 7.1.00.13 [Interface CRC=0x6307d3f9]

Build Version = 7.1.00.76

Content Version = 7.1.00.11 [Interface CRC=0x757e892]

Meta Version \t= 7.1.00.03 [Interface CRC=0x06b4a577]

!======================================!

Verbindung zu MDM-Server 192.168.0.106 wird hergestellt

MDM-Server-Version wird ermittelt...

Version = Version 7.1 (7.1.00.79)

!======================================!

Installierte Repositories werden ermittelt...

-> SR7_MDM3_Catalog_4_Produktiv (DB2/ORCL)

-> SR7_MDM3_Catalog_7 (DB2/ORCL)

-> SR7_MDM3_Catalog_9 (DB2/ORCL)

-> SR7_MDM3_Catalog_Test_4 (DB2/ORCL)

-> SR7_MDM3_Catalog_10_Dienstl (DB2/ORCL)

-> SR7_MDM3_Catalog_5_Produktiv (DB2/ORCL)

-> SR7_MDM3_Catalog_Test_5 (DB2/ORCL)

Verbindungstest war fehlerhaft