cancel
Showing results for 
Search instead for 
Did you mean: 

MDM connection issue - after upgrade

Former Member
0 Kudos

We recently upgraded our MDM server from 7.1.8 to 7.1.10

Also we upgraded our SRM Netweaver Java system from

Older verson

SAP NW 701 SP11,  SRM-MDM Catalog 3.0 SP12.

to newer version SAP NW 7.02 SP12,  SRM-MDM Catalog 3.0 SP12.

After the upgrade our Connector, connector, API and web_ui version is

sap.com MDM_CONNECTOR 710.700 SP10 (1000.710.700.10.3.20130514184504) SAP AG MAIN_M711000P_C 20130525093657
sap.com MDM_JAVA_API 710 SP9 (1000.710.0.9.284.20120904094400) SAP AG SAP AG 20130501163745
sap.com MDM_WEB_UI 710.700 SP8 (1000.710.700.8.8.20111127132149) SAP AG MAIN_MD71800P_C 20121017004731


But after the upgrade, we are facing the below issue, when we try to connect to the MDM server using

http://hostname:port/SRM-MDM/SRM_MDM

java.lang.NullPointerException

at com.sap.mdm.srmcat.uisearch.master.Master.loadRepository(Master.java:1457)

at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.loadRepository(InternalMaster.java:956)

at com.sap.mdm.srmcat.uisearch.master.LoginView.onActionconnect(LoginView.java:464)

at com.sap.mdm.srmcat.uisearch.master.wdp.InternalLoginView.wdInvokeEventHandler(InternalLoginView.java:222)

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

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

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

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

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

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

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)

We are not sure whether the below forum is helpful to our issue.

http://scn.sap.com/thread/3288672

Has anyone faced this issue?

Regards


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Solution is to

downgrade MDM server to 7.1.9 and downgrade MDM connector to 710.700 SP09.

Regards

Senthil